Random BSOD possibly related to Kernel-Power

Code:

BugCheck A, {3db2f08, 2, 0, fffff800032f0cfc}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption

Followup: memory_corruption
---------

Test your RAM modules for possible errors.

How to Test and Diagnose RAM Issues with Memtest86+

Run memtest86+ for at least 8 consecutive passes.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Let us know the result. If possible, a camera snap of the memtest86+ screen before closing the program would be nice.

Nice.

Now let us search for another possible cause of the memory corruption, any driver passing bad information to the memory. So enable Driver Verifier to monitor the drivers.

Driver Verifier - Enable and Disable

Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

Ive just set it up and restarted the computer and immediately got a BSOD on reboot... appears to be related to "ksaud.sys". I cant seem to find the minidump file.



The computer then rebooted and windows is working fine in normal mode for now.

ksaud is Creative USB Audio Driver.

Code:

01/08/2012 9:18:35 PM  C:\Windows\system32\drivers\ksaud.sys

You are using a USB Sound Blaster HD. Update its driver from Creative's site.

So the issue still remains. Ive downloaded the most up to date driver, tried plugging it into a different usb port, tried a few other things, and was still getting the BSOD ksaud.sys.

So I just figured "what the hell lets just unplug it"... with the USB unplugged ive just received a new BSOD which appears to be memory related:



Ive opened up the case and checked to ensure the ram sticks were still within the slot, which they were properly secured. I gave it a good clean up (there was tons of dust inside). Ive also taken out each of the 3 sticks out ram out of the slots, cleaned them, cleaned the slots, and put them back in at different locations. Still getting the ksaud.sys error. Have not received the memory_management error since but have the USB sound card unplugged

DV is still enabled.

If you remove the USB Sound Blaster HD, how it goes? Can you try removing it?