Windows 7: BSOD Playing various games, closing games, no overheating.

Erushnak · 28 Apr 2012

Hello, first time poster looking for help as I can't diagnose my issue after trying numerous things. Currently when I play a game the BSOD happens randomly, I can go a whole day without it, or it can happen frequently. It happens the most when I close or exit a game, then it'll kick to a blue screen.

I really appreciate what you guys do and I hope I followed all the instructions right on how to post my logs and stuff, here's the attachment and some basic system specs:

OS: Windows 7 Ultimate x64
I have reinstalled to this computer numerous times.

CPU: Intel Core 2 Quad q9550 @ 2.83 ghz

GPU: Radeon HD 5770

Mem: 4 Gigs of Memory

Motherboard: p5n32-e sli nforce 680i chipset

zigzag3143 · 28 Apr 2012

Before we can even begin to find the underlying cause you need to update the following drivers. Especially asacpi.sys. Yours is from 2005

Code:

ASACPI.sys    3/27/2005 10:30:36 PM        
Lycosa.sys    1/18/2008 4:51:42 AM        
nvm62x64.sys    10/17/2008 5:01:06 PM       
netr28x.sys    2/25/2009 11:02:09 PM

How To Find Drivers:

Quote:

- 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 Reference Table

Erushnak · 28 Apr 2012

I appreciate you taking the time to help me today. I'm at work right now but I will definitely take care of those drivers and get back with you if it bsods again.

Erushnak · 28 Apr 2012

Update!

Got home from work, updated all my drivers you listed to the latest I could locate, played Tera for about an hour and got another BSOD.

Here's the new dump and new perfmon.

Erushnak · 29 Apr 2012

Small update, seems to be happening a little more frequently since the updates to the drivers. Here's a couple from last night.

zigzag3143 · 29 Apr 2012

Quote: Originally Posted by Erushnak

Small update, seems to be happening a little more frequently since the updates to the drivers. Here's a couple from last night.

Invalid memory address blamed on an OS file (doubtful)

Please run a system file check to verify the OS.

If that comes back clean please run verifier to find out which driver is misbehaving.

SFC /SCANNOW Command - System File Checker

How to use the System File Checker tool to troubleshoot missing or corrupted system files on Windows Vista or on Windows 7

* If you are overclocking anything reset to default before running these tests.
In other words STOP!!!

* If you have a Raid update its Driver.

Driver Verifier

Quote:

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 to identify issues with Windows drivers for advanced users

Driver Verifier

Using Driver Verifier (Windows Drivers)

Erushnak · 29 Apr 2012

Small update, got home from work about an hour ago. I ran the system file check on verify only, here's the logs. I'm going to run the repair on them and then I'll get back with any crashes.

Erushnak · 01 May 2012

Update. I ran the verifier and when I booted up I crashed twice on Lycosa.sys

So I removed it and used the default ms keyboard driver and then got the last crash you see.

Any advice?

writhziden · 07 May 2012

Security Software: ??? I recommend either of these two setups:

Download and install the security setup of your choice, update the software, and then run a full scan of your system for viruses and malware. If you only install MSE, I would also suggest installing and updating Malwarebytes : Free anti-malware, anti-virus and spyware removal download, but do not start the free trial/full version of Malwarebytes. Run a full scan with Malwarebytes after updating it. Post back the results.

The crashes were caused by a USB device. Could be remnants of the keyboard that gave the Lycosa.sys crash, or it may be another device. What USB peripherals are you using? Before doing the following, disable Verifier using the steps given by zigzag3143.

Start with USB Driver - General Fix for Problems to resolve the USB issues. Also, USB ports can sometimes enter a safe power state to protect the system from power surges due to USB devices. To reset the USB ports to a nominal power state:
1. Shut down and turn off the computer.
2. Unplug the computer from the wall or surge protector (then remove the battery if it is a laptop).
3. "Remove the computer from any port replicator or docking station, disconnect
  cables to printers or devices such as external monitors, USB memory sticks or SD cards, headset or external speakers, mouse or auxiliary keyboard, turn off WIFI and Bluetooth wireless devices." (Use Hard Reset to Resolve Hardware and Software Issues HP Pavilion dv5000 Notebook PC series - HP Customer Care (United States - English))
4. Hold down the power button for 30 seconds. This closes the circuit and ensures all
  power from components is drained to clear the software connections between the BIOS
  and hardware and clear any corruption in the temporary memory.
5. (If it is a laptop, plug the battery back into the laptop and then) Plug the computer back into the wall. Do not reconnect any unnecessary peripherals; monitor, keyboard,
  and mouse should suffice and be the only peripherals reconnected.
6. Turn it on to reinitialize the software connections between the BIOS and hardware

Windows 7: BSOD Playing various games, closing games, no overheating.

BSOD Playing various games, closing games, no overheating. problems?