Seemingly random BSOD's, different errors

[ayearinaminute]

Hello!

I've been getting seemingly random BSOD's for the past weeks and I decided to format since it's a relatively fast and easy way for a fresh start. The BSOD's could occur at any time, when gaming, browsing the desktop or the web, listening to Spotify, installing WoW, during startup. Sometimes several times a day and other times there could be a long time between the BSOD's.

But after the format and during the installation process of windows update I got a BSOD and the whole OS got corrupt so I formatted again and this time all of the windows updates has been installed but I've encountered BDOD's anyways.

I've run memtest and checked the hdd's with checkdisk, cleared CMOS, scanned with MSE and Malwarebytes and opened up the case, making sure everything is correctly fitted.

Most of the hardware is from dec 2008 except the sound card (2011), MB (2011) and graphics card (2010).

I've seen page_fault_in_nonpaged_area, driver_irql_not_less_or_equal, atikmdag.sys and ntfs.sys since the BSOD's has started to appear. The attached dump files are made after I formatted and re-installed the OS.

 

[JMH]

These crashes were caused by memory corruption/exception (probably a driver).
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 6 or 8 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.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html



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.