Windows 10: Occasional BSOD / freeze

Hey guys.

So, a little backstory - last month, I RMA'd my motherboard (MSI Z97S SLI Krait) and re-installed it. A couple of weeks later, I got random BSODs. There doesn't seem to be a definite pattern to them. Some are while I'm playing a game, some are while I'm just watching a video. Some days, I don't see one at all. The error I've seen mostly is IRQL_not_less_or_equal.

I'm thinking it's a driver issue, though I have no idea where to start looking. I tried using the Windows debugging tool, all I could find was "probably ntkrnlmp.exe".

Thanks in advance for any help.

:)

 

UNEXPECTED_STORE_EXCEPTION and CRITICAL_PROCESS_DIED BSOD appears randomly

Occasionally when using the computer, it freezes, then the BSOD appears with the UEXPECTED_STORE_EXCEPTION or the CRITICAL_PROCESS_DIED message.

Here are the files: Files

 

UNEXPECTED_STORE_EXCEPTION and CRITICAL_PROCESS_DIED BSOD appears randomly

Occasionally when using the computer, it freezes, then the BSOD appears with the UEXPECTED_STORE_EXCEPTION or the CRITICAL_PROCESS_DIED message. My computer also did not produce any dump files from the crash.

 

The 6/12 dump at 1:02AM indicates some problems with:

Code: *** WARNING: Unable to verify timestamp for usbfilter.sys *** ERROR: Module load completed but symbols could not be loaded for usbfilter.sys *** WARNING: Unable to verify timestamp for rtwlanu.sys *** ERROR: Module load completed but symbols could not be loaded for rtwlanu.sys Probably caused by : memory_corruption[/quote] usbfilter.sys dated Tue Aug 28 21:27:12 2012 belongs to AMD USB Filter Driver.
rtwlanu.sys dated Thu Oct 01 02:13:28 2015 belongs to Realtek WLAN Wireless USB 2.0 Adapter.

Is the current mother board a MSI Z97S SLI Krait also?

Is the AMD USB on the motherboard?
Is the Realtek a USB dongle?

Need to find updated drivers for both of these.

 

Yes, that's my mobo. My WLAN adapter is a dongle. As for the AMD USB, I'm not too sure - my case has a few USB ports. Seems more likely to be on my mobo. I'll see what I can do about my wireless adapter's drivers.

Edit: Dunno anything about the AMD USB filter drivers. I honestly don't know where to look for them. As for the WLAN adapter, I found drivers for what I have, but they're from 2012. Device manager tells me that the drivers I have currently are from 2015.

 

For AMD, try here: Download AMD USB Filter Driver 2.1.10.295 for Windows 10, Windows 10 64 bit

Edit: Can't get to any us.msi.com or MSI Global. so can't chech there to see what drivers might be available.

 

All right, I found some LAN drivers for my mobo that are really recent, so I installed those. As for the USB filter - not sure where to install that. Device management lists probably every single USB port that I have.

Though I've gone three days without a BSOD, so fingers crossed that something I changed worked. I'll update if something goes wrong.

 

Hoping Attachment 85887

 

All right, well, finally got a new BSOD 4 days later. This time the error read "wpp system_service_exception", if I remember right.

The log collector isn't working right for me - it isn't producing a .zip file - so I'm just gonna include the most recent dump file in a .zip.

 

The latest dump indicates WppRecorder.sys as the cause. This belongs to Microsoft so is unlikely to be the real cause.

In a couple instances of similar BSODs with WppRecorder.sys, the cause was the Anti-virus software, AVG. Looks like you have Avira so please uninstall it and use the built in Windows Defender (this is what I use) for now until we are done here. See if that makes any difference.

Also still indicating a problem with the Nvidia driver:
Code: ffffd000`2097c118 fffff800`f5cf8ff1Unable to load image 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+0x128ff1[/quote] I think it's time to run Driver Verifier:

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

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.

 

My system blue screened immediately once Windows started to load up. Here's the most recent dump.

 

The latest indicates a problem with ScpVBus.sys:
Code: Unable to load image ScpVBus.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for ScpVBus.sys *** ERROR: Module load completed but symbols could not be loaded for ScpVBus.sys Probably caused by : ScpVBus.sys ( ScpVBus+b174 )[/quote] Product: Scp Virtual Bus Driver
Company: Scarlet.Crush Productions
Description: Scp Virtual Bus Driver

Please run the following from a Elevated Command Prompt. Upload oemDrivers.txt and attach here. May have to zip it first, not sure.

pnputil -e > oemDdrivers.txt

 

Hopefully I did this right.

 

Yes, that was perfect. Unfortunately it had no trace of ScpVBus. it shows in drivers.txt with a 2013 date. I think it may haave something to with a Xbox controller but not sure.

Try running sfc /scannow from a Elevated Command Prompt. See if it gets any errors and if so what they are.

 

"Windows Resource Protection did not find any integrity violations". So it says.