BSOD mostly after waking from sleep, sometimes more

[CelestialScribe]

Hi all.

Recently I'd been having problems with BSOD on waking from sleep mode. This also happened some other times as well.

I wondered whether it had anything to do with my MBOX 2 Mini sound card drivers. I formatted the hard drive, started Windows again. Still happening.

I've attached a Log Collector file. I'm not sure what the problem is and I'm not that computer savvy. Would appreciate any help anyone can give!

 

[Golden]

fffff880`046395f0  fffff900`00000000
fffff880`046395f8  00000000`000003b9
fffff880`04639600  fffff960`0014e000*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
 win32k+0xee000
fffff880`04639608  fffff880`009ed180
fffff880`04639610  00000000`00000000
.
fffff960`00060000 fffff960`00382000   win32k   T (no symbols)           
    Loaded symbol image file: win32k.sys
    Image path: \SystemRoot\System32\win32k.sys
    Image name: win32k.sys
    Timestamp:        unavailable (00000000)
    CheckSum:         00000000
    ImageSize:        00322000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

This is the first time I've ever seen a Windows system file flagged in this manner.

Do the following:
1. Click Start

2. In the search box, type cmd
3. In the list that appears, right-click on cmd.exe and choose Run as administrator
4. In the command window that opens, type sfc /scannow and hit enter.
5. Repeat step 4 an additional 3 times, one immediately after the other.
6. Report the output of the above.

Now ensure Windows is fully updated.

Lastly, run a scan for rootkits using this tool and report back:
TDSSKiller Download

 

[CelestialScribe]

Did all that you said, no violations found and the rootkit tool came up negative.

 

[Golden]

Follow:
1. Log in as administrator, open Windows Explorer and go to C:\Windows\Minidump
2. Delete all .dmp files in that folder
3. Run Driver Verifier as follows:

Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.
http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

Driver Verifier will cause your computer to run very sluggishly - this is normal. What it is trying to do is force your system to BSOD and isolate the offending driver/s. When it does, reboot, disable driver verifier, reboot as normal, re-run the DM Log Collector, and upload the new ZIP file here.

I recommend creating a system restore point before turning on driver verifier:
http://www.sevenforums.com/tutorials/697-system-restore-point-create.html

If your system fails to boot to desktop once driver verifier is enabled, turn it off by booting into Safe Mode:
http://www.sevenforums.com/tutorials/69585-safe-mode.html