Blue Screen of Death (BSOD) on Windows 10

I've been getting hit with the Blue Screen of Death more and more frequently lately, forcing me to manually reboot my PC just to get back up and running. I'm running Windows 10, which I upgraded to from Windows 7 Ultimate. Everything was working perfectly fine for months on end, but now I'm seeing this error message about ten times a day.

I would really appreciate any help or a solid solution you guys might have.

Just grab WhoCrashed 5.53 and run an analysis—it should give you a pretty clear idea of what's actually causing this...

http://www.resplendence.com/downloads

Man, I went through this exact same nightmare. It would work fine for a bit, then—BAM—BSOD. Sometimes it’d last five minutes, sometimes it’d give me two hours of peace before crashing again. I even tried swapping out different versions of Windows and even jumped over to Linux just to be sure. Total wash. Nothing worked.

Turns out, it wasn't an OS issue at all. I tested pretty much every single component. The culprit? My motherboard finally kicked the bucket. 😢 Ever since I swapped it out for a new one, everything has been running smooth as silk. :knockwood:

Crash Dump analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\WINDOWS\Minidump

Your system is configured to capture crash dumps.

The system experienced a crash on Thu 15.12.2016. 19.03.16
crash dump file: C:\WINDOWS\Minidump\121516-23718-01.dmp
The culprit seems to be this specific module: nvlddmkm.sys (nvlddmkm+0x3E15B0)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80936C215B0, 0xFFFF98006B885738, 0xFFFF98006B884F60)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\System32\DriverStore\FileRepository\nv_ dispiwu.inf_amd64_9ff5ab165faead52\nvlddmkm.sys
product: Nvidia Windows kernel mode driver, version 369.09
company: Nvidia Corporation
description: Nvidia Windows kernel mode driver, version 369.09
Bug check description: Essentially, a system thread triggered an exception that the error handler wasn't able to manage.
This looks like a standard software driver issue rather than a physical hardware failure.
A third-party driver was pinpointed as the most likely reason for this crash. I'd recommend checking if there is a newer update available for: nvlddmkm.sys (Nvidia Windows kernel mode driver, version 369.09, Nvidia Corporation).
Google query : Nvidia Corporation SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M on Thu 15.12.2016. 19.03.16

The system went down on Thu 15.12.2016. 19.03.16
crash dump file: C:\WINDOWS\memory.dmp
It appears the following module was responsible: nvlddmkm.sys (nvlddmkm+0x3E15B0)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF80936C215B0, 0xFFFF98006B885738, 0xFFFF98006B884F60)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\System32\DriverStore\FileRepository\nv_ dispiwu.inf_amd64_9ff5ab165faead52\nvlddmkm.sys
product: Nvidia Windows kernel mode driver, version 369.09
company: Nvidia Corporation
description: Nvidia Windows kernel mode driver, version 369.09
Bug check description: This error indicates that a system thread threw an exception that the error handler failed to intercept.
A third-party driver was flagged as the probable cause of this error. You should probably search for an update for: nvlddmkm.sys (Nvidia Windows kernel mode driver, version 369.09, Nvidia Corporation).
Google query : Nvidia Corporation SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

A crash occurred on Thu 15.12.2016. 17.26.47
crash dump file: C:\WINDOWS\Minidump\121516-49234-01.dmp
This was likely triggered by the module: nvlddmkm.sys (nvlddmkm+0x3E15B0)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8003B4B15B0, 0xFFFFE70069F022B8, 0xFFFFE70069F01AE0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\System32\DriverStore\FileRepository\nv_ dispiwu.inf_amd64_9ff5ab165faead52\nvlddmkm.sys
product: Nvidia Windows kernel mode driver, version 369.09
company: Nvidia Corporation
description: Nvidia Windows kernel mode driver, version 369.09
Bug check description: This signifies that a system thread produced an exception that the error handler could not handle.
This points toward a typical software driver bug and doesn't look like a hardware issue.
A third-party driver was identified as the potential root cause. I suggest looking for a driver update for: nvlddmkm.sys (Nvidia Windows kernel mode driver, version 369.09, Nvidia Corporation).
Google query : Nvidia Corporation SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M

The computer crashed on Thu 15.12.2016. 03.30.16
crash dump file: C:\WINDOWS\Minidump\121516-24109-01.dmp
The following module was likely the cause: nvlddmkm.sys (nvlddmkm+0x3E15B0)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80DE1FB15B0, 0xFFFFE700311F8738, 0xFFFFE700311F7F60)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\System32\DriverStore\FileRepository\nv_ dispiwu.inf_amd64_9ff5ab165faead52\nvlddmkm.sys
product: Nvidia Windows kernel mode driver, version 369.09
company: Nvidia Corporation
description: Nvidia Windows kernel mode driver, version 369.09
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This looks like a classic software driver issue rather than anything involving your actual hardware.
It seems a third-party driver is the most likely culprit behind this system error. I'd recommend hunting down an update for this specific driver: nvlddmkm.sys (Nvidia Windows kernel mode driver, version 369.09 , Nvidia Corporation).
Google query : Nvidia Corporation SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M

Your computer hit a wall on Wed 14.12.2016. 21.11.42
crash dump file: C:\WINDOWS\Minidump\121416-23500-01.dmp
The crash was likely triggered by this module: nvlddmkm.sys (nvlddmkm+0x3E15B0)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80CB72F15B0, 0xFFFF80018DBD8738, 0xFFFF80018DBD7F60)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\System32\DriverStore\FileRepository\nv_ dispiwu.inf_amd64_9ff5ab165faead52\nvlddmkm.sys
product: Nvidia Windows kernel mode driver, version 369.09
company: Nvidia Corporation
description: Nvidia Windows kernel mode driver, version 369.09
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a standard software driver bug and isn't likely tied to a hardware failure.
A third-party driver has been flagged as the probable cause of this error. You should probably check for an update for: nvlddmkm.sys (Nvidia Windows kernel mode driver, version 369.09 , Nvidia Corporation).
Google query : Nvidia Corporation SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M

--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

I've gone through and analyzed 13 crash dumps, though I've only included the 5 most relevant ones here. A third-party driver is clearly the reason your system keeps crashing. Your best bet is to head over to the manufacturer's website and see if they've released any updates for these drivers. You can use the links below to run a quick Google search for them:

nvlddmkm.sys (Nvidia Windows kernel mode driver, version 369.09 , Nvidia Corporation)

If there aren't any updates available yet, try Googling the driver names along with the specific error messages you're seeing. Throwing in your PC's brand and model name can also help; you might find some helpful threads from other users dealing with the exact same headache.

For more context, take a look at the general troubleshooting tips for system crashes.

Just a heads-up: it’s not always a guarantee that the driver identified is the sole reason for the crash—sometimes the real issue lies elsewhere. That said, checking for driver updates and keeping Windows updated (either manually or via automatic updates) is the right first step. If you suspect it's actually a hardware issue, searching Google for the bug check error combined with your computer's specific model and brand might give you some more clues to follow.

So.... what now???

It looks like the report indicates your Nvidia driver is what’s causing the system to crash, so your best bet would be to go ahead and run a driver update.

He can give it a shot, but honestly, if everything was running smooth before, an update shouldn't just kill his PC out of nowhere. I ran into that exact same error message myself. I went through pretty much every driver version under the sun and... yeah, nothing worked.
But hey, whatever, let him try.

http://www.guru3d.com/files-details/...-download.html

I'd suggest using this removal tool to wipe those Nvidia drivers out completely. Honestly, it's way more effective than just doing a standard uninstall through Windows—it actually scrubs all those leftover traces from your registry and wherever else they might be hiding on the partition. Once you've given the PC a quick restart, just grab the latest drivers straight from the official Nvidia website and see if that smooths things out.

Do I need to do the same thing? 🙂

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Wed 14.12.2016. 7:27:00 your computer crashed
crash dump file: C:\WINDOWS\Minidump\121416-31484-01.dmp
This was probably caused by the following module: atikmpag.sys (atikmpag+0xCF38)
Bugcheck code: 0x116 (0xFFFFCB8E96424010, 0xFFFFF80EE2ECCF38, 0x0, 0xD)
Error: VIDEO_TDR_ERROR
file path: C:\WINDOWS\system32\drivers\atikmpag.sys
product: AMD driver
company: Advanced Micro Devices, Inc.
description: AMD multi-vendor Miniport Driver
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.).
Google query: Advanced Micro Devices, Inc. VIDEO_TDR_ERROR

On Wed 14.12.2016. 7:27:00 your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: atikmpag.sys (0xFFFFF80EE2ECCF38)
Bugcheck code: 0x116 (0xFFFFCB8E96424010, 0xFFFFF80EE2ECCF38, 0x0, 0xD)
Error: VIDEO_TDR_ERROR
file path: C:\WINDOWS\system32\drivers\atikmpag.sys
product: AMD driver
company: Advanced Micro Devices, Inc.
description: AMD multi-vendor Miniport Driver
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.).
Google query: Advanced Micro Devices, Inc. VIDEO_TDR_ERROR

On Fri 18.11.2016. 14:49:45 your computer crashed
crash dump file: C:\WINDOWS\Minidump\111816-35812-01.dmp
This was probably caused by the following module: atikmdag.sys (atikmdag+0xB073C)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80A4FD8073C, 0xFFFFA2808C393720, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\drivers\atikmdag.sys
product: ATI Radeon Family
company: Advanced Micro Devices, Inc.
description: ATI Radeon kernel mode driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: atikmdag.sys (ATI Radeon kernel mode driver, Advanced Micro Devices, Inc.).
Google query: Advanced Micro Devices, Inc. SYSTEM_SERVICE_EXCEPTION

--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

3 crash dumps have been found and analyzed. 2 third party drivers have been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

atikmdag.sys (ATI Radeon kernel mode driver, Advanced Micro Devices, Inc.)
atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.

If you want some broader advice on how to tackle these kinds of system crashes, you should probably check out the general troubleshooting guide here.

Just a heads-up: you can't always be 100% sure if a specific driver is actually the culprit or if some other module is pulling the rug out from under you. That said, it’s usually worth checking for driver updates from the manufacturers, and honestly, just keeping Windows update running or set to automatic is pretty much standard practice. If you suspect a hardware component is acting up, try doing a quick Google search using the specific bug check error code alongside your PC's brand and model. It might give you a better lead on what's actually going wrong.

Yeah, looking at your report, it seems like those Intel drivers are definitely causing some headaches..