BSOD BCCode 50 and a

I've been getting BSOD's for as long as I could remember. I looked up the usual causes for what I was getting and would update my drivers and hope for the best. Most of the time this would work out for the error I was getting (BCCode d1) but now I've been getting BCCode 50 which says its crashing because of 'dxgmms.sys' with 'Page Fault in Non Paged Area' and BCCode a which usually will say 'IRQ_NOT_LESS_OR_EQUAL'. I also remember getting a Bad_Pool_Header error but I'm not sure which error it is associated with. I've done a clean install of windows and reinstalled graphics and mobo drivers and such and don't see what else I can do at the moment. I attached a file with my minidumps and the system report info.

Had this computer for 2 years (No upgrades aside from a heatsink)
I run on Windows x64 Ultimate
Q8200 Processor ~2.3 ghz - stock
EVGA 9800 GT GPU - stock settings
4gb RAM (2gbx2)

Craezin said:

I've been getting BSOD's for as long as I could remember. I looked up the usual causes for what I was getting and would update my drivers and hope for the best. Most of the time this would work out for the error I was getting (BCCode d1) but now I've been getting BCCode 50 which says its crashing because of 'dxgmms.sys' with 'Page Fault in Non Paged Area' and BCCode a which usually will say 'IRQ_NOT_LESS_OR_EQUAL'. I also remember getting a Bad_Pool_Header error but I'm not sure which error it is associated with. I've done a clean install of windows and reinstalled graphics and mobo drivers and such and don't see what else I can do at the moment. I attached a file with my minidumps and the system report info.

Had this computer for 2 years (No upgrades aside from a heatsink)
I run on Windows x64 Ultimate
Q8200 Processor ~2.3 ghz - stock
EVGA 9800 GT GPU - stock settings
4gb RAM (2gbx2)

16 of 44 related to video. the rest various hardware complaints. I would start with the following

The results from the DMP files do not give a definitive answer. While we investigate further here are a few things that you can do.

Re-install the video driver using this method.

When upgrading your graphic driver you MUST remove all traces of the current driver. In order to do that we recommend using http://phyxion.net/Driver-Sweeper/Dr...Version-3-1-0/

When it is removed then download and install the fresh copy.

1-Run a system file check to verify and repair you system files. You do this by typing cmd in search, then right click and run as admin. SFC/ SCANNOW

2-Download a 3rd party app called memtestx86, burn it so cd, and run memtest for 5-6 passes.

3-Event viewer
There are several ways to find what the problem is. The best is to go into event viewer (type eventvwr in search). Go to the windows log>application tab.

You want to look for critical errors (they have red in the left column ).

When you find them you want to look for critical errors that say app hang, app crash, or anything that relates to the problem.

When you find them please note the event ID, and the source codes and tell us what they are.

4-Device manager
Please go to start>search>type device manager. (Win 7 and Vista)
Are there any "unknown devices" with yellow triangles on them?
Is you driver there , listed, and working?

If your driver is missing, or there is a yellow triangle on it, you will need to update it.

5-Driver verifier
Beyond that, please run Verifier with these settings:

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"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
- 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 (an estimate on my part).

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:

Code:

Delete these registry keys (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

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

I did your reinstallation driver method, system scan, and didn't find anything out of place in event viewer besides it saying that my computer shut down unexpectedly. Will try memtest tomorrow as I cannot do it tonight. If that passes I'll try the driver verifier.

I will report back after that If I get a bluescreen, thanks for the swift response.

Tried out driver verifier and to my surprise it wouldn't even let windows start up. I had to do a restore from start up repair and I obtained the one dmp file it kept from today. (Ran it twice to see if there was any variety).