Solved Multiple BSOD's while gaming, idling.

[Salamandrex]

For the past month I've run into a nasty number of BSOD's and the occasional system freeze where my whole computer locks up and requires a manual reboot. On reboot my Mobo asks to run setup(F1) or continue with default settings (F2) AMI is the maker not sure of the specifics. After uninstalling drivers multiple times for sound, as well as graphics nothing seemed to correctly fix my problem and I took it to bestbuy (still under warranty) for a hardware check which came back fine. I tried re-installing windows via a return to factory settings as well as a fresh install using the disk after that failed as well. Now i'm at a loss as to how to fix my problems, any help would be greatly appreciated.

 

[zigzag3143]

Before we can begin to investigate we need you to update the follow driver. asacpi.sys/ Yours is from 2005

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

 

[Salamandrex]

Thanks for the response I updated said driver and about an hour and a half later my computer froze up again, no bsod though. I loaded up DOTA 2 and ran well for ~ 40 minutes then the freeze happened. Running temp on my graphics card was normal.

 

[zigzag3143]

Thanks for the response I updated said driver and about an hour and a half later my computer froze up again, no bsod though. I loaded up DOTA 2 and ran well for ~ 40 minutes then the freeze happened. Running temp on my graphics card was normal.

Have you uploaded the new Dmps?

 

[Salamandrex]

Sorry about that here are the latest dmps. Thanks for the help.

 

[zigzag3143]

These were related to your AVG. I would remove and replace it with MSE at least to test.

I note you have AVG.
AVG can be a contributing cause of BSOD'S .
Please remove and replace with Microsoft Security Essentials AT LEAST TO TEST

Download tools and utilities | AVG Worldwide


Microsoft Security Essentials - Free Antivirus for Windows

 

[Salamandrex]

Thanks for the help so far, got a BSOD as running the uninstaller but so far everything seems to be working fine with Essentials installed. Will keep you posted.

 

[Salamandrex]

Had another BSOD while watching a youtube video after uninstalling avg and installing Windows Security Essentials. Followed by a BSOD on boot up at the welcome screen.

 

[Salamandrex]

Tried to run in safe mode and try a virus scan with Windows Security Essentials, constant blue screening ensued.

 

[zigzag3143]

Tried to run in safe mode and try a virus scan with Windows Security Essentials, constant blue screening ensued.

These are all over the map.

Please download the free version of Malwarebytes.
Update it immediately.
Do a full system scan
Let us know the results at the end.

Malwarebytes : Download free malware, virus and spyware tools to get your computer back in shape!

 

[Salamandrex]

After a full scan it came back clean. It might be worth noting My original guess was malware/virus related and when AVAST! and Malawarebytes came back negative I resorted to restoring to factory settings, and when that cropped up with the same problems about 4 days later I tried a fresh windows install using a 64bit home premium cd and now here I am. I still do have the old windows files on the computer if that helps in any way. Again thank you for the help!

 

[Salamandrex]

Here are the latest dmp's if they help in anyway.

 

[zigzag3143]

Here are the latest dmp's if they help in anyway.

If this is still happening after a clean install we have to start thinking hardware. You arent overclocking right?

Lets run memtest and verifier to start.



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.



Memtest.

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

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html






Driver Verifier

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/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"
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 JCGriff2 & Usasma.

Sysnative Forums

Driver Reference Table (DRT)

Using Driver Verifier to identify issues with Windows drivers for advanced users

Driver Verifier

Using Driver Verifier (Windows Drivers)

 

[Salamandrex]

I think I've found the problem, the front usb ports on my computer seem to cause crashes when they're in use. Is this something that would crop up with similar error reports?

 

[zigzag3143]

I think I've found the problem, the front usb ports on my computer seem to cause crashes when they're in use. Is this something that would crop up with similar error reports?

Could be, and if so it is either software (or more likely) Hware.

http://www.sevenforums.com/tutorials/165554-usb-driver-general-fix-problems.html?filter

 

[Salamandrex]

After removing the hardware from the front USB ports it's gotten better, however the past 2 days I did receive two non-BSOD crash both while playing Diablo 3, if that matters, with nothing plugged into the front two ports. Is it possible for this to be a separate issue and if so any idea of the culprit? Thanks

 

[zigzag3143]

After removing the hardware from the front USB ports it's gotten better, however the past 2 days I did receive two non-BSOD crash both while playing Diablo 3, if that matters, with nothing plugged into the front two ports. Is it possible for this to be a separate issue and if so any idea of the culprit? Thanks

Since the first problem seems better we need a couple of DMPS after that to find the current issue. Upload them as they happen.

 

[Salamandrex]

Still keeping pace with the one crash per day.

 

[zigzag3143]

Still keeping pace with the one crash per day.

None of them appear verified, but in looking at them another way I noticed that both AdAware, and AVGtray were in serveral of them.

I would remove both and replace with MSE>

 

[Salamandrex]

I removed both programs earlier when it was suggested and switched to Malwarebytes and MSE. So it seems odd that they would cause the BSOD. I searched through programs and files to find any trace of either program and all that was left were the uninstallers of each program. Any ideas as to how they would still cause it?