Windows 7: Lots of BSODs (dxgmms1.sys atikmpag.sys etc)

continente · 11 Jul 2011

Hi,

I have been having daily BSODs for some time now. They seem somewhat random, although more prevalent when gaming, so I decided to format the PC. Well, it's exactly the same scenario so I'm pretty sure it's not software related.
Also, sometimes when booting I get this and I have to try some times to make it successfully boot.

I'm using Windows 7 Ultimate x64 and the hardware is about 3 years old (Intel C2Q Q9450, ATi HD4870, ASUS P5Q Deluxe) and not overclocked.

I have attached the files suggested in the sticky.

Thanks.

zigzag3143 · 11 Jul 2011

Quote: Originally Posted by continente

Hi,

I have been having daily BSODs for some time now. They seem somewhat random, although more prevalent when gaming, so I decided to format the PC. Well, it's exactly the same scenario so I'm pretty sure it's not software related.
Also, sometimes when booting I get this and I have to try some times to make it successfully boot.

I'm using Windows 7 Ultimate x64 and the hardware is about 3 years old (Intel C2Q Q9450, ATi HD4870, ASUS P5Q Deluxe) and not overclocked.

I have attached the files suggested in the sticky.

Thanks.

Two problems are immediately apparent. First

1-ASACPI.SYS a major cause of BSOD's in the 2005 rev.

The pre 2009 version of this driver is a known BSOD cause.

The 2005 version of this driver is a known BSOD cause.
Please visit this link: ASUS teK Computer Inc. -Support- Drivers and Download P7P55D LE
ASUSTeK Computer Inc. -Support- Drivers and Download P7P55D LE

Scroll down to the Utilities category, then scroll down to the "ATK0110 driver for WindowsXP/Vista/Windows 7 32&64-bit" (it's about the 12th item down).
Download and install it.
Go to C:\Windows\System32\drivers to check and make sure that the ASACPI.sys file is date stamped from 2009 or 2010 (NOT 2005).

2-Memory corruption caused by an un-named driver. Please run these two tests

Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program.

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.

Driver verifier

Quote:

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/Windows 7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

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. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

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.

continente · 11 Jul 2011

Thanks for the response.

I downloaded and installed the updated version of the ATK0110 driver but unfortunately it did not solve the issue as I just had another BSOD caused by dxgmms1.sys (according to windbg at least).

I had already ran memtest but I wasn't aware that I should test every stick individually so I'll do it tonight and report back.

Tomorrow I will then try Driver verifier.

continente · 12 Jul 2011

Update

I ran memtest (7 passes) on each of the ram sticks and it passed and I left the pc turned off.
When I tried to boot it, it just wouldn't boot. It would display the corrupted image I showed on the first post (more: 1 2 3) and always reboot before it got to windows.

Well after a thousand tries here I am it finally boot up, I will try driver verifier later, but I am quite afraid it will just go down and not boot anymore.

lht001300000 · 12 Jul 2011

Apparently your display memory is corrupted or GPU is down for your ATI display, if you didn't improperly update your BIOS.

Are you seeing the same white stuff each time started?
or different pattern each time?

continente · 12 Jul 2011

The exact same pattern everytime.

lht001300000 · 12 Jul 2011

I think you should try using a different display if you have. As mostly those strokes across the screen everywhere are due to non-functional display, and that matches with that you get BSOD more frequently when gaming, which stress your display a lot more.
Also, if you plan to re-install a copy of windows for test purpose, only install the minimum amount of driver that makes all ! in hardware manager disappear. Additional drivers may cause crashes.

continente · 14 Jul 2011

I have tried a different monitor and it gives me the same pattern. Also I noticed that if I let it boot despite the image being corrupted the BSOD is always because of atikmpag.sys.
Anyways thanks for the help, but I'll send it to a repair shop.

Windows 7: Lots of BSODs (dxgmms1.sys atikmpag.sys etc)

Lots of BSODs (dxgmms1.sys atikmpag.sys etc) problems?