Windows 10: Frequent BSOD When Waking From Sleep

So this one's been puzzling me for a while. I'm getting very frequent BSOD, and it most commonly occurs when waking the computer up from sleep in the morning. The error code is frequently different, and sometimes I don't get a crash but just get weird behavior. Like chrome can't open any webpages, or I can't switch songs on spotify while alt-tabbed and windows fails to create that little sound dialog in the top left of the screen with current song and volume.

I've also had the computer straight up crash with no BSOD (unless it just restarted before the screen turned on?) and had the computer cycle through a bunch of solid color screens and a few gradients on wakeup and then turn off.

It's been happening for a while now, but I don't believe it started happening around the time I upgraded my RAM/Graphics card... but I could be misremembering.

I ran MemTest, and got 1 error on the third (of four) pass of test 7, but it never reoccured - so I'm not sure what that means.

I am not able to run driver verifier - I get stuck in a blue screen loop on boot with it. The following occured when I tried to run it:

• System Thread Exception
• Page Fault
• Driver Verifier IOManager Violation

All in all, I'm thinking it's a memory issue but hoping its a driver issue since I don't want to have to deal with RMAing my RAM and it's probably past date anyways.

Also, the DM Log tool always saves to the C drive even though my desktop is on another HDD - thought I wasn't getting the zips at first. But, attached!

System Info:

• Windows 10
• i5 4670k
• 16 GB DDR3 RAM Corsair
• GTX 1070
• Z87X-UD3H-CF Mobo

:)

 

Problems with sleep

when you wake from sleep, do you get a BSOD?

nevermind.. just looked at your links..

are you running on an SSD?

 

BSoD Analysis request

Hi

My friend had the BSoD on his laptop when waking from sleep and hyper sleep. Here are the data I've collected.

https://1drv.ms/f/s!AgEj5P7CvitTgeVSS6_zXrAZAVioxA

Thank you in advance

 

Was this using MemTest86+......note the +

If so, then it is significant. You need to test the individual RAM modules to determine if its that, or the RAM module slots on the motherboard.

Follow the steps as laid out here:
MemTest86+ - Test RAM Windows 10 BSOD Tutorials

 

Was just MemTest86 - will run + now! Back with results in a bit

 

Follow the instructions in the tutorial....it will be several hours before you will have a result.

 

In the past few days I installed the debugger and when I processed the zip files there were 11 in the month of May.

When you see these in the results how do you find the application related to the *.sys driver?
How do you know which ones are good versus bad or important versus unimportant results?

Probably caused by : dxgmms2.sys ( dxgmms2! ?? ::FNODOBFM::`string'+29c2 )
Probably caused by : ntkrnlmp.exe ( nt!RtlEqualUnicodeString+4 )
Probably caused by : WdFilter.sys ( WdFilter!MpCreateSection+138 )
Probably caused by : NETIO.SYS ( NETIO!IndexListClassify+97 )
Probably caused by : Pool_Corruption ( nt!ExFreePool+bc4 )
Probably caused by : ntkrnlmp.exe ( nt!PspCatchCriticalBreak+d6 )
Probably caused by : NTFS.sys ( NTFS!NtfsUpdateLcbDuplicateInfo+5e )
Probably caused by : WdFilter.sys ( WdFilter!MpPreCleanup+ed )
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 )
Probably caused by : memory_corruption
Probably caused by : memory_corruption ( ONE_BIT )

 

Use Driver Reference Table (DRT)

Windows drivers are never bad, rather falsely reported as the cause.

 

Ran 10 passes of MemTest86+, no errors!