repeated BSOD crashes - many types

pt007786 · 31 Oct 2016

I've been unable to locate the problem of repeated crashes now over a period of 9 months. I've had every message you can get, it seems. (The last 3 were : win32kbase, win32kfull and bad pool header). They are occurring about once a day now. They occur after the computer is on for a while (I leave it on overnight). The last two crashes were present when I got up in the morning. About 9 months ago I updated to Windows 10, installed a second monitor and upgraded to 8G of memory and changed my system drive to SSD. So it has been hard to determine where the problem lies. I installed driver updates when I've been able to find them.

I have been putting up with the problem, but now I'm having to recover from corrupt data each time. So I need to do something about it!

I hope someone can delve a little deeper than I can.

Thanks of the help

- Paul

Ztruker · 02 Nov 2016

The latest dump indicates a problem with FSPFltd2.sys

Code:

BugCheck 19, {20, ffffc40a3b745430, ffffc40a3b745560, 4130003}
*** WARNING: Unable to verify timestamp for FSPFltd2.sys
*** ERROR: Module load completed but symbols could not be loaded for FSPFltd2.sys
Probably caused by : FSPFltd2.sys ( FSPFltd2+3d62 )

This belongs to something called FSPro File Filter 2 which is old: 3/06/2011 10:59:38 PM
I recommend uninstalling it. If you need it or something like it, see if there is a newer version available or a replacement for it.

pt007786 · 03 Nov 2016

I uninstalled the fspro software and rebooted. However a few hours later I had another BSOD.
I have attached the latest reports.

Help is much appreciated.

Ztruker · 03 Nov 2016

The 11/3 6:21 dump shows a problem with the Nvidia driver/card.

Code:

ffffcc00`3c93f2b0  fffff80d`1878c790Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
 nvlddmkm+0x8ac790

You have version 341.98 installed. The Nvidia web site has version 342.0 available.

Remove and install latest Nvidia drivers:
I suggest completely uninstalling the Nvidia display drivers using Display Driver Uninstaller (DDU) from WagnardMobile (near bottom of page) then get the latest driver for you Nvidia card here: NVIDIA Driver Downloads
Then do a custom install of only the NVidia graphics driver and the PhysX driver.
See if that gets rid of the problem.

pt007786 · 08 Nov 2016

Okay. I did a DDU uninstall and reinstalled the latest 342.0 driver.

The latest BSOD report is attached.

Thank you.

Ztruker · 08 Nov 2016

The newest dump is complaining about FSPFltd2.sys:

Code:

BugCheck 19, {e, ffffc50d106c4e10, 19e38c6570007a00, 19e38c6570887a03}

*** WARNING: Unable to verify timestamp for FSPFltd2.sys
*** ERROR: Module load completed but symbols could not be loaded for FSPFltd2.sys

This belongs to FSPro Labs program. I don't see anything like My Lockbox, Hide Folders or Hide FOlder Extensions in your install or uninstall files. Dated 3/06/2011.

The previous dump shows a problem with : rtwlanu.sys

Code:

BugCheck 1E, {ffffffffc0000005, fffff80ba9426259, 0, ffffffffffffffff}

*** WARNING: Unable to verify timestamp for rtwlanu.sys
*** ERROR: Module load completed but symbols could not be loaded for rtwlanu.sys

This is for your Wireless Lan (WiFi) I think. Dated 2012.

The dates are not bad for Windows 7 but terrible for Windows 10 if you go there again.

pt007786 · 09 Nov 2016

OK.
The FSPFltd2.sys was left over from the uninstall of Hide Folders last week. It's deleted now.
I also deleted the old wifi driver - rtwlanu.sys

After a reboot, the system worked through the night, but shortly after I woke the display, the system crashed.

Latest crash reports attached.

Ztruker · 09 Nov 2016

Give Driver Verifier a try, see if it gives us any better information:

===================================================
Driver Verifier is a diagnostic tool built into Windows 10, it is designed to verify both native Microsoft drivers and third party drivers. Driver Verifier's verification process involves putting heavy stress on drivers with the intention of making bad, outdated, incompatible or misbehaving drivers fail. The required result is a BSOD (Blue Screen of Death) which will generate a crash dump for debugging purposes.
Machines exposed to Driver Verifier will run very sluggishly due to the stress being applied to the drivers.

Driver Verifier - Enable and Disable in Windows 10

Pay close attention to

PART TWO

and make sure the correct boxes are checked.

Warning:
It is not advised to run Driver Verifier for more than 48 hours at a time. Disable Driver Verifier after 48 hours or after receiving a BSOD, whichever happens soonest.

Always create a Restore Point prior to enabling Driver Verifier.

What we're looking for is a BSOD with a mini dump that will tell us what driver caused it.

pt007786 · 10 Nov 2016

Verifier: I've awakened a monster!
I got a result - totrec8.sys
But took me 2 hours to get the monster back in the cage. The startup methods : command line and the disable drivers did not work. (I forgot to do a restore point).
Finally managed to do a Ctrl-Alt_del to task manager as soon as windows opened & then accessed Verifier
Brrr!
I'll upgrade Total Recorder & see what happens.
Thanks.

Ztruker · 10 Nov 2016

If you can, run DM_Log_collector again so I can look at the dump