|25 Apr 2012||#1|
| || |
Random BSOD while playing games.
I am using Windows 7 Ultimate x64 Retail. My computer randomly locks up while playing video games. It will either lead to a lock up or after 30s-2minutes it will start responding and speed through all the commands I sent. So like 25 task managers suddenly appear at once.
This doesn't happen consistently at all. Could lock up 5 times in one day or not at all for a week. Seems to be a different BSOD each time, but I am not sure.
Most of my system was custom built around a year ago, recently replaced my graphics card 3 or 4 months ago.
There are quite a few things broken with this OS install, but I am trying to hold out for Windows 8 so I don't have to reinstall everything twice.
|My System Specs|
|25 Apr 2012||#2|
| || |
Lets start with the obvious
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
ASUSTeK Computer Inc. - Motherboards- ASUS P5K-VM
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 before).
Old drivers needing updating
pcouffin.sys 12/5/2006 10:39:30 AM LMIRfsDriver.sys 7/14/2008 12:26:56 PM UltraMonUtility.sys 11/13/2008 9:10:30 PM hamachi.sys 2/19/2009 6:36:41 AM amdxata.sys 5/19/2009 1:56:59 PM
- 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.
- - Driver manufacturer links are on this page: Drivers and Downloads
Three of four were blamed on memory corruption. I think asacpi.sys is the probable cause but if updating it doesnt help run these.
These crashes were caused by memory corruption/exception (Cx05) 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 a Raid update its Driver.
*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-7 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.
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.
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"
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.
If you are using win 8 add these
- Concurrency Stress Test
- DDI compliance checking
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.
Thanks to JGriff2 & Usasma.
Using Driver Verifier (Windows Drivers)
|My System Specs|
|Similar help and support threads for2: Random BSOD while playing games.|
|Random BSOD, while playing games (WoW, LoL)||BSOD Help and Support|
|Random BSOD's when playing games||BSOD Help and Support|
|Random BSOD's - mostly while playing games.||BSOD Help and Support|
|BSOD while not playing games.Random||BSOD Help and Support|
|Random BSOD While playing Games.||BSOD Help and Support|
|Random BSOD while playing games||BSOD Help and Support|
|Random BSOD when playing games||BSOD Help and Support|