BSOD when computer goes to sleep mode - 0x0000000a

Hi JMF11.

The crash dumps are not very informative themselves.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

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

If it does not show any error, 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.
____________________________

Code:

BugCheck A, {fffff8a0003274e0, 2, 0, fffff80002e5deaa}

Probably caused by : cng.sys ( cng!GatherRandomKey+294 )

Followup: MachineOwner
---------

ASUS PID on MSI?

In that case you may try a bootable memtest86+ CD.

Boot into Safe mode and disable Driver Verifier.

Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus.
5. Apply > OK
6. Accept then restart.

Now enable Driver Verifier again. Hopefully this time it will generate a crash dump.

JMF11 said:

Hi,

Last update: I followed the instructions to boot in safe mode. Through trial and error process I identified the drivers that generated the crash at the boot when using DV. It is mbfilt64.sys.

I excluded this mbfilt64.sys from the list of the drivers to be verified, and then Seven is booting fine. It was stable all over the night.

This driver seems to be related to the Realtek audio chipset, and HD audio. I went to realtek website and downloaded the last versions of the drivers and installed them. Seems that It didn't changed anything as the dirver version is the same... and it still crash at the boot if in DV list.

I unchecked it from DV list, and let the PC running for today, testing at least the other drivers.

Regards,

JMF

Your experience with mbfilt64.sys is normal. There is no update to this driver, and sometimes it causes problems in simple safe mode boot, too.

BTW, I dont have mbfilt64.sys present in my system, though I have RTKVHD64.sys present there.

Just being curious about that particular driver, I have a request to you (not a suggestion; it might not form a part of the troubleshooting, but will help me to enhance my knowledge). Can you please upload the list of all the third party drivers Using NirSoft DriverView :

• Download and execute Driverview
• View > Hide Microsoft Drivers
• Edit > Select all
• File > Save Selected Items
• In the Save dialog, Set the path to desktop, Put "Driverview" in the name field, and save.
• Zip the .txt file and upload it.

As it is not present in my system, your upload will help me to learn the actual status of this driver.