Intermittent System Lockups/BSoD

[djhawk]

Well we've been running with the verifier for a while now. I'm sure it's been over 24 hours of actual usage time. No more blue screens, just lots of occasional freezes.

 

[richc46]

Just check for any dump reports. If none we can move on.

 

[djhawk]

No, no more dump reports since that last one unfortunately.

 

[richc46]

Use the computer until the next dump report. If it looks like a hardware issue, we can start those round of tests.
turn off verifier.

 

[djhawk]

We've waited a while but still we're only getting freezes with no dump reports. No BSDs. The only other oddity is that occasionally the screen will go black for a few seconds, then come back and there will be a message that the display driver stopped responding but has recovered. It has done this in the past too with a different OS and also now with updated drivers, so that's not new.

 

[richc46]

If it happened with a different OS may be the actual card.

 

[djhawk]

Sorry, I was wrong! There was a dump report from 2 days ago that I didn't know about. Here it is.

 

[richc46]

STOP 0x0000009F: DRIVER_POWER_STATE_FAILURE Usual causes: Device driver

Driver Verifier Inst
Since the driver that crashed you has not been listed you should run driver verifier
Please run Verifier with these settings:

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

Enable the driver verifier
www.sevenforums.com/crash-lockup-debug-how/65331-using-driver-verifier-identify-issues-drivers.html

 

[djhawk]

Ok, here's the latest BSoD dumpfile.

 

[richc46]

Take a look for yourself, not much help

 opyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\richc46\AppData\Local\Temp\Temp1_022611-22027-01[1].zip\022611-22027-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16695.x86fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0x8281b000 PsLoadedModuleList = 0x82963810
Debug session time: Sat Feb 26 13:53:51.933 2011 (GMT-5)
System Uptime: 0 days 0:09:45.008
Loading Kernel Symbols
................................................Unable to add module at ff140000
[B]Loading User Symbols
Loading unloaded module list
.......................Missing image name, possible paged-out or corrupt data.
[/B].......