Windows 7: Multiple BSODs, mostly while gaming

PropaneTankHank · 22 Feb 2012

Hey guys, was wondering if you could help me clear something up. I've had my computer for just over a year, and about two months ago my computer started BSODing. The ones I've gotten are:
System_Service_Exception (most frequent)
Driver_IRQL_Less_Or_Not_Equal
PAGE_FAULT_IN_NONPAGED_AREA
Interrupt_Exception_Not_Handled (only once)
I think there was also another error, but I'm not exactly certain which one.

Now, about a month ago, I brought the computer to a friend who builds/fixes PCs. He ran hardware tests, deemed that it wasn't a RAM issue and that something in the software was faulty, so he formatted and reinstalled windows. This worked for a couple of days, but the BSODs started happening again. They haven't happened yet when not gaming (Starcraft 2, steam related games, etc) but before I formatted they could happen when watching a stream or even just browsing. The computer will also BSOD without giving any particular error message, and when I do BSOD I usually have to wait 5-10 minutes before turning the computer back on, as it simply won't load up upon automatic restart, and if I try to boot it up after turning the power off too quickly, it'll start beeping constantly and do nothing.

Upon googling common problems, AVG seemed to be a popular culprit for causing them, but I went ahead and uninstalled it and I have still BSOD'd. I also turned off all forms of overclocking (to my knowledge).

My specs are:
OS: Windows 7 Professional 64 bit
GPU: XFX Radeon HD 6850
CPU: AMD Phenom II X6 1100T
RAM: 2 4GB Corsair CMX4GX3M1A1333C9 sticks
Motherboard: Gigabyte GA-880GM-D2H

I will run memtests overnight, but for now I was wondering (and hoping) that someone could help me find a solution that isn't just hardware failure. I'm hoping it is just some drivers are outdated and need to be replaced, but I'm not sure how to check everything and if someone can explain to me how to provide dumps for them, I will gladly do so. Thanks!

Edit: Missed the BSOD Posting Instructions thread, will attach my dumps in a minute.

zigzag3143 · 22 Feb 2012

We do need the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

If you are overclocking STOP

You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

Quote:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
*If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.

To ensure minidumps are enabled:

Quote:

* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under the Advanced tab, click on the Startup and Recovery Settings... button.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.

PropaneTankHank · 22 Feb 2012

Attachment 199741

I've attached the minidump folder and all of it's contents, appreciate the explanation. :) Let me know if I've done anything wrong or if you need anything else.

zigzag3143 · 22 Feb 2012

Quote: Originally Posted by PropaneTankHank

Attachment 199741

I've attached the minidump folder and all of it's contents, appreciate the explanation. :) Let me know if I've done anything wrong or if you need anything else.

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.

Quote:

*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

Quote:

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.

PropaneTankHank · 22 Feb 2012

I ran one test with memtest86 and it came up with 116736 errors. Is there any way to tell from those errors which stick, if not both, isn't working?

zigzag3143 · 22 Feb 2012

Quote: Originally Posted by PropaneTankHank

I ran one test with memtest86 and it came up with 116736 errors. Is there any way to tell from those errors which stick, if not both, isn't working?

Yes run one at a time.