Windows 10: BSOD After Never Shutting Down Solved


  1. Posts : 3
    Windows 10 Professional
       21 Dec 2015 #1

    BSOD After Never Shutting Down


    Hello, I've been getting a lot of BSOD after upgrading to Windows 10. At first I suspected that the bluescreens came from having never shut down my computer (it's either in sleep mode or being used). It's annoyed me to the point that I need help. My system was overclocked to 4.5 GHz but I've since defaulted all settings in the BIOS.

    Here is the WhoCrashed analysis:
    On Mon 2015-12-21 7:20:44 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\122115-11687-01.dmp
    This was probably caused by the following module: hal.dll (hal+0x35EE1)
    Bugcheck code: 0x9C (0x0, 0xFFFFD001F8B64760, 0x0, 0x0)
    Error: MACHINE_CHECK_EXCEPTION
    file path: C:\Windows\system32\hal.dll
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Hardware Abstraction Layer DLL
    Bug check description: This bug check indicates that a fatal machine check exception has occurred.
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



    On Mon 2015-12-21 7:20:44 AM GMT your computer crashed
    crash dump file: C:\Windows\memory.dmp
    This was probably caused by the following module: hal.dll (hal!HalBugCheckSystem+0x661)
    Bugcheck code: 0x9C (0x0, 0xFFFFD001F8B64760, 0x0, 0x0)
    Error: MACHINE_CHECK_EXCEPTION
    file path: C:\Windows\system32\hal.dll
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Hardware Abstraction Layer DLL
    Bug check description: This bug check indicates that a fatal machine check exception has occurred.
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



    On Mon 2015-12-21 7:10:24 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\122115-16265-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x14F4D0)
    Bugcheck code: 0x101 (0x30, 0x0, 0xFFFFD00194640180, 0x2)
    Error: CLOCK_WATCHDOG_TIMEOUT
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Thu 2015-12-10 7:40:59 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\121015-16890-01.dmp
    This was probably caused by the following module: dxgmms2.sys (dxgmms2+0x0)
    Bugcheck code: 0x19 (0xD, 0xFFFFD00022994330, 0xFFFFE00204C4EA76, 0xFACF18C28AE4B557)
    Error: BAD_POOL_HEADER
    file path: C:\Windows\system32\drivers\dxgmms2.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: DirectX Graphics MMS
    Bug check description: This indicates that a pool header is corrupt.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



    On Thu 2015-11-26 5:12:44 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\112515-13484-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x14F4D0)
    Bugcheck code: 0x19 (0xD, 0xFFFFD00023611330, 0x0, 0x9E51E71FCDA3AF72)
    Error: BAD_POOL_HEADER
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that a pool header is corrupt.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Tue 2015-10-20 1:57:44 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\101915-13000-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x14E240)
    Bugcheck code: 0x19 (0xD, 0xFFFFD00022655330, 0x0, 0x79DDD4F1F0A06772)
    Error: BAD_POOL_HEADER
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that a pool header is corrupt.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Sat 2015-09-19 3:22:35 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\091815-9390-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x14E240)
    Bugcheck code: 0x19 (0xD, 0xFFFFD00024006330, 0xFFFFE00111F31B01, 0x58C99CCC589263E6)
    Error: BAD_POOL_HEADER
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that a pool header is corrupt.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
    Attachment 54625
      My ComputerSystem Spec


  2. Posts : 11,514
    Windows 10 Pro
       21 Dec 2015 #2

    Please remove / disable items from the startup in taskmanager
    These programs could interfere with the boot process giving you trouble and increase the boot time.

    In case of
    If you are using a program like Ccleaner please stop using it while troubleshooting.
    This because programs like Ccleaner remove dump files that are needed to troubleshoot.
    Or configure Ccleaner to not remove dump files:
    Please try to update your BIOS
    Attachment 54629
    Code:
    BIOS Version:              American Megatrends Inc. 2501, 2015-06-24
    SABERTOOTH Z97 MARK 2 | Motherboards | ASUS Global
      My ComputersSystem Spec


 

Related Threads
Need help for remotely shutting down pc from another desktop I need your help, shutting down other computer is "access is Denied" pls. help...
shutting down system in General Support
For some reason my system will not shut down and turn off completely under windows 10; only my monitor will go into power save mode but my system itself will just restart. Is this because I have a board that is not windows 10 compatible and the fact...
Hi, I put a new SSD in my PC, installed it clean with windows 7 from my DVD, then I used an ISO on my memory stick to upgrade to windows ten. Everything was working fine, graphics drivers installed, headset working, steam working, skype working....
Shutting Off Cortana in Software and Apps
Is there a way to stop Cortana running in the background. I see it in the "Task Manager', but you cannot 'End Task' it as it comes right back.
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 19:05.
Find Us