Bsod

The story of this section, BSOD. They are coming almost always during a game. For the first few days it was mostly dxgmms1.sys as the listed issue. I flashed the bios for my mobo and that seemed to take care of it for a few days, but now it's back again.

I'm occasionally getting an ntfs.sys error as well. I'm leaning towards a video issue vs. memory or HD, but I will be running Memtest86+ tonight. SFC and chkdsk came up clean, as well as the Windows memory test.

Machine is a home build, Windows 7 Ultimate full retail, fresh install on a new OCZ SSD about a month ago. No issues up until the last week. .dmp's from the last week included.

Any help is much appreciated!

Robby316 said:

The story of this section, BSOD. They are coming almost always during a game. For the first few days it was mostly dxgmms1.sys as the listed issue. I flashed the bios for my mobo and that seemed to take care of it for a few days, but now it's back again.

I'm occasionally getting an ntfs.sys error as well. I'm leaning towards a video issue vs. memory or HD, but I will be running Memtest86+ tonight. SFC and chkdsk came up clean, as well as the Windows memory test.

Machine is a home build, Windows 7 Ultimate full retail, fresh install on a new OCZ SSD about a month ago. No issues up until the last week. .dmp's from the last week included.

Any help is much appreciated!

Two major problems that need to be fixed before we can find the true caquse of these 25 crashes.



1-ASACPI.SYS

The pre 2009 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-Old drivers including chipset drivers.

Code:

ASACPI.sys    3/27/2005 10:30:36 PM        fffff880`075f4000    fffff880`075fc000    0x00008000    0x42476c4c                        
SiWinAcc.sys    6/14/2007 8:02:02 PM        fffff880`01075000    fffff880`0107e000    0x00009000    0x4671d6fa                        
SiRemFil.sys    6/20/2007 3:42:10 PM        fffff880`01bab000    fffff880`01bb3000    0x00008000    0x46798312                        
SI3132.sys    10/3/2007 2:39:29 PM        fffff880`01184000    fffff880`0119e000    0x0001a000    0x4703e1e1                        
nvm62x64.sys    10/17/2008 5:01:06 PM        fffff880`0708a000    fffff880`070edd80    0x00063d80    0x48f8fd12

How To Find Drivers:

- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads


3-I would also remove Avast and replace with Microsoft Security Essentials

http://files.avast.com/files/eng/aswclear5.exe

Virus, Spyware & Malware Protection | Microsoft Security Essentials

Thanks for the quick replies. Made the necessary updates (thanks to Maguscreed for the ASACPI file!) and switched to MSE. Played the game again, still got a BSOD. DMP attached.

Side note - nvm62x64.sys is an nVidia ethernet driver, and I had already tried a full board driver update from the asus website, which should have included the most up-to-date driver, no?

Updated but still got another 2 BSOD's today. Here's the latest DMPs. So damn frustrating.

Robby316 said:

Updated but still got another 2 BSOD's today. Here's the latest DMPs. So damn frustrating.

None of these 4 crashes could identify the faulting driver please run driver verifier.

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

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.

Quick update: After the 2 BSOD's I posted, I have not gotten any since then, so I'm tentatively calling this solved. I'll update if I get any more. Thanks for the help everyone!