Blue screen help

I hope you can help me with these blue screens - I was having problems with nuidfltr, but I ran driver verifier on it a couple of times after updating the driver from microsoft and it seems like it is working ok

I'm only using MSE for AV

I also ran SFC /SCANNOW and attached the results.

Thanks for your help. I have been using windbg to look at the dump files, but I'm only a noob and I didn't get anywhere

Have you run memtest86?


BugCheck 1A, {3452, 72672000, fffff70001081dd8, 0}
PROCESS_NAME:  explorer.exe
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+339e3 )
ntkrnlmp.exe - Microsoft Corporation

BugCheck A, {fffffffffffffd21, 2, 0, fffff80002e59dba}
Probably caused by : cng.sys ( cng!GatherRandomKey+22c )An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
cng.sys - Kernel Cryptography, a driver file from company Microsoft Corporation belonging to product Microsoft® Windows® Operating System.

BugCheck 1E, {ffffffffc0000005, fffff80002ed17c0, 0, 24}
PROCESS_NAME:  explorer.exe
Probably caused by : ntkrnlmp.exe ( nt!KiIpiSendRequest+70 )KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
ntkrnlmp.exe - Microsoft Corporation


You may want newer versions of these:

amdxata.sys Tue May 19 20:56:59 2009
Graphics Drivers & Software

e1y62x64.sys Wed Oct 21 00:06:09 2009
There may be a newer version:
(Intel Wireless)

GEARAspiWDM.sys Mon May 18 15:17:04 2009
GEAR Software - DVD Mastering Software & CD Burning Software & GEAR PRO Mastering (uninstall or update)

stwrt64.sys Mon Oct 12 04:38:26 2009
Integrated Device Technology - Semiconductor Solutions - Homepage (update if a newer version is available)

Hi Robert.

I've looked over the verified crash dumps. All of the drivers are in excellent shape. Unfortunately, this very likely means that there is a RAM defect. You can use Memtest86+ to test the memory. Overnight testing is best to show any potential errors. Sometimes, it is necessary to isolate the faulty module by removing all others and testing by you may eventually have to test one at time to find errors.

Please keep us updated on your finding. If you do find that you have fault RAM, replace it and don't forget to disable Driver Verifier once the system is stable for a full day or so.

Found one bad stick so far - thanks for the help!

Well first time I have gone more than a day without a blue screen - computers working great. Thanks again!

This website is not affiliated, owned, or endorsed by Microsoft Corporation. It is a member of the Microsoft Partner Program.