Random BSOD's, error 0xa

Basically, these errors started during games. Specifically Batman Arkham City. I thought it was just that game, so I moved on to Portal 2. It happened again. I cleaned out my computer of any dust and cleared up any loose cables, which still didn't work. I then downloaded a program to monitor the temp of my GPU, which was running normal (idled around 35 - 40c and reached about 70c playing most games). It also started blue screening at random intervals. Sometimes it would be sitting on the desktop doing nothing, other times on sites like YouTube. Really, it didn't even have to be doing anything GPU intensive like I originally thought. I ran memory tests first using Prime95, which came up clean. After that, I ran memtest86+ overnight. After 11 passes, no errors came up. I ran a hard drive test to check for errors/faulty sectors, and that also came up clean. I reseated the RAM and GPU, both of which didn't help. After that, I decided to do a little research. I found out that my GPU commonly caused problems with BSOD's, so I RMA'd it. After thinking that solved it with no blue screens for about a week, they started up again. Now out a GPU, using onboard graphics, I'm desperate for ideas. I replaced my SATA cable just today and it's still causing it. My CPU temperatures are normal. The only thing I can think of is some sort of driver issue now, but I have no idea how to debug BSOD's on my own. Any help would be wonderful. Oh, and I forgot to mention that my computer is only a year old, and about a month ago I formatted it and reinstalled Windows.

Specs:
Windows 7 Home Premium x64 OEM
Asrock Extreme3 890GX motherboard
AMD Phenom II X4 @ 3.5GHz
GPU was ATI Radeon HD 6870 - still is, once I get it back from RMA
G.SKILL RAM 2 x 2 GB
Western Digital Caviar Black 1TB HDD
750 watt PSU
Oh and I run MSE for my antivirus, which has caused a few errors in my event logs. Not sure if that has anything to do with it.

I doubt you need most of this, but any other info I can give for you please just let me know!

Thanks!

As you have run Memtest already please run Driver verifier...

Note > If you are overclockng STOP!

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Special Pool", "Force Pending I/O Requests" and "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen.
Continue to use your system normally, and if you know what causes the crash, do that repeatedly.
The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.
If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

Using Driver Verifier to identify issues with Windows drivers for advanced users.

I'm currently running the verifier now. I'll be away from my computer for the weekend, but back Sunday afternoon. Also, one thing I've noticed that's common between the last two crashes is this message.

Microsoft Antimalware has encountered an error trying to load signatures and will attempt reverting back to a known-good set of signatures.
Signatures Attempted: Current
Error Code: 0x80070002
Error description: The system cannot find the file specified.
Signature version: 0.0.0.0;0.0.0.0
Engine version: 0.0.0.0

It appeared in the event log a few seconds before crashing. Might that have something to do with it?

adrastea said:

I'm currently running the verifier now. I'll be away from my computer for the weekend, but back Sunday afternoon. Also, one thing I've noticed that's common between the last two crashes is this message.

Microsoft Antimalware has encountered an error trying to load signatures and will attempt reverting back to a known-good set of signatures.
Signatures Attempted: Current
Error Code: 0x80070002
Error description: The system cannot find the file specified.
Signature version: 0.0.0.0;0.0.0.0
Engine version: 0.0.0.0

It appeared in the event log a few seconds before crashing. Might that have something to do with it?

There appears to be some information and a fixit here.
You receive a "0x80070002" or "0x80070003" error code after you download an update from Windows Update, from Microsoft Update, or from Windows Server Update Services

I completely uninstalled MSE, and replaced it with our school's free student Symantec AV. After that, it worked for a day, then, the next time I started it, before even loading my desktop, it blue screened. During the blue screen it did a physical memory dump, restarted my computer, and loaded up the desktop just fine. I checked the event logs and there were no errors before or after the blue screen.
I've attached the updated crash report with today's blue screen dump file.

Re your installing Symantec.
That is contrary to what we recommend as Norton is often implicated in BSOD's.

1. These crashes were caused by memory corruption/exception (probably a driver & likely Symantec.)
Please run these two tests to verify your memory and find which driver is causing the problem.

If you are overclocking anything reset to default before running these tests.
In other words STOP!!!

If you have Raid > update its Driver.


Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

RAM - Test with Memtest86+



Driver verifier

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Special Pool", "Force Pending I/O Requests" and "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen.
Continue to use your system normally, and if you know what causes the crash, do that repeatedly.
The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.
If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

Using Driver Verifier to identify issues with Windows drivers for advanced users

2. As stated above Symantec is a frequent cause of BSOD's.
I would remove and replace it with Microsoft Security Essentials AT LEAST TO TEST


http://us.norton.com/support/kb/web_...080710133834EN

Microsoft Security Essentials - Free Antivirus for Windows

Ok. I removed Symantec and reverted back to MSE. Also, I have already tested using Memtest86+. It ran for 11 passes with no errors. I received my GPU after RMA'ing it, so I reinstalled that. Driver verifier has been running since the last poster said to use it, however my computer hasn't blue screened at all yet. Now that I'm back for the week and able to use it more frequently, it'll probably do it again.

Upload any further DMP files.

So it crashed again just now. I was just using Google Chrome to go on Facebook. After a few minutes of that it crashed. I'm attaching the new dump file for you to look at. Also, when my computer restarted, a popup came up saying Google Installer crashed. Not sure what that was about. Nothing was installing on my computer at the time. Also, while writing this, it blue screened again. This time after restarting a box popped up saying windows firewall has prevented some features of Akamai NetSession from running. Uploading both the dump files now.

Your most recent crash was not driver verified or was not verifiying the driver that causes the problem.

I would verify all drivers, and I would run a system file check



SFC /SCANNOW Command - System File Checker

How to use the System File Checker tool to troubleshoot missing or corrupted system files on Windows Vista or on Windows 7