Random BSOD's on Win7 x64

The errors point at hardware and memory corruption.

Please start by running these hardware diagnostics:
Memory Diagnostics (read the details at the link)
HD Diagnostic (read the details at the link)

Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Malware (read the details at the link)

robertftw said:

Thanks for the answer.
Sorry have been busy during the holidays that's why no answer.

Anyway, all these tests came out fine. Have done the memorytest a few times before with no errors. Also tried to swapout the memorysticks, but still gotten the bsod.
Today I have already had 2(quite unusual), while doing nothing really.
The first one I got when I just used firefox.
The second one I got while I was afk and just downloading a game over Steam.

Just been through your dumps as well and bad ram does seem the likely culprit
Did you run memtest from bootable cd?
If so did you leave it running overnight, need to get min 5 passes pref to be sure the longer the better

On the HDD diags be sure you ran full complete tests checking everything possible

Also from an elevated command prompt(right click run as admin) type >sfc /scannow
to check integrity of system files

Have you updated all poss drivers/bios/chipsets

Please post the memory dump files that have occurred since you first posted them.
That'll be anything after 12/19/09

Hi, just been through your last bunch of dumps and there all the same they all report 0xA errors = memory corruption

This is likely to be a problem with either ram or a driver passing bad info

We have already checked the physical ram with memtest but not the passing of info from ram through motherboard, one option would be to run a stress test to make sure the ram is performing under load condition

The other option is to check drivers, for this i would consider using driver verifier which is not something im familiar enough with to instruct others about, usasma^^^ might be the man for this part he seems to be the expert, hopefully he will check back to this thread soon and give his opinion

Sorry i couldnt help any more than this

Yep, this looks like prime territory for Driver Verifier (all STOP 0xA errors).
Please follow these instructions for using it:

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 "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.

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.
If that doesn't work, post back and we'll have to see about fixing the registry entry off-line.

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

That dump is like the rest 0x1a memory management

One thing we havent mentioned is ram settings in bios, have you ever changed these eg trying to overclock? i would go into bios and check the settings for your ram and make sure they are correct ie ram voltage and latency, cant be anymore specific cause you havent filled in your system specs, sometimes auto is not the best way i always manually enter the settings i want, you could even try underclocking by reducing the speed of the ram slightly to see if it helps stability, might be nothing but its worth looking at

Other than that i think driver verifier is the way forward