Windows 10: BSOD where WinDbg suspects ntkrnlmp.exe

Hello.

I have been having BSOD issues for the last several months on this laptop. They most commonly appear when I'm playing music and/or games, and it has gotten to the point where I am hesitant to even play online games anymore, as I often end up getting a BSOD in the middle of a game.

I recently upgraded to Windows 10 hoping that it may help things, but it did not. I followed a WinDbg guide (from sevenforums I believe) and found that one of my video drivers was failing, so I updated that and my BSOD issues have become less frequent, but they still persist. The most recent crashes blame ntkrnlmp.exe and the reading I've done suggests that ntkrnlmp.exe is most likely a red herring and the actual issue lies elsewhere. I tried running Prime95's Blend Test, but it just caused my computer to BSOD after 10-15 minutes, and all of the tests in the log succeeded. Event viewer lists recent bugchecks as 0x0000003d and 0x0000001a.

I don't really know where to go from here. Any help would be greatly appreciated.

Thanks!

:)

 

Win10 BSoDs, KMODE_EXCEPTION_NOT_HANDLED and ATTEMPTED_SWITCH_FROM_DPC

WinDbg show the errors point to the snapman.sys:

Probably caused by : snapman.sys ( snapman+18e81 )

The snapman.sys, which appears to be dated from 2006, is a driver for Acronis TI

So try updating or just uninstalling Acronis TI.

If WinDbg showed the ntkrnlmp.exe at fault make sure you are the latest version of WinDbg and that the symbol path has been set - there are steps in the following link :

Install and Configure WinDBG for BSOD Analysis

 

Win10 BSoDs, KMODE_EXCEPTION_NOT_HANDLED and ATTEMPTED_SWITCH_FROM_DPC

I went ahead and uninstalled the snapman drivers, and haven't had another BSoD in the last hour.

Will report back if it happens again.

Thank you!

 

Please run MemTest86+ to test your RAM, MemTest86+ tutorial
MemTest86+ needs to be run for at least 8 passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.