BSOD on fresh install

[Jluras]

Hi, I reformatted and installed a fresh copy of Win7 Pro x64 on my PC because it was having BSOD issues and then reinstalled my chipset, network, and audio drivers. Not long after installing only those things I experienced another BSOD. I'm not sure what caused it but I'm 100% sure its not my RAM or my processors. Ive run Memtest 86+ multiple times for over 7 passes as well as a stress test on my CPU which ran for 6 hours with no problems. The problem that came up was a 7f. Here is the dump and thank you for your time!

 

[Jonathan_King]

Welcome!

Please enable driver verifier: http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

After it has caused several crashes, follow these directions: http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

Thanks,
~JK

...Summary of the Dumps:

[font=lucida console]
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Aug 15 13:29:55.566 2010 (GMT-4)
System Uptime: 0 days 0:08:02.096
BugCheck 7F, {8, 80050031, 6f8, fffff80002ad031d}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
BUGCHECK_STR:  0x7f_8
PROCESS_NAME:  drvinst.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
[/font]

 

[Jluras]

I let it BSOD a few times (took a while) and did the health report for you! Sorry for the long wait but I wanted (hopefully) enough minidumps.

 

[Jonathan_King]

Be sure to upload the output folder found in Documents. This is the actual script data.

 

[Jluras]

Oh shoot, sorry about that! Sorry for the late replies; I have a crazy schedule.

 

[Jonathan_King]

Please enable driver verifier: http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

...Summary of the Dumps:

[font=lucida console]
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Aug 16 22:27:23.262 2010 (UTC - 4:00)
System Uptime: 0 days 1:31:48.822
BugCheck A, {fffff8c0031fca20, 2, 0, fffff80002c32204}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+200a2 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Aug 15 13:29:55.566 2010 (UTC - 4:00)
System Uptime: 0 days 0:08:02.096
BugCheck 7F, {8, 80050031, 6f8, fffff80002ad031d}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
BUGCHECK_STR:  0x7f_8
PROCESS_NAME:  drvinst.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Aug 16 17:01:39.869 2010 (UTC - 4:00)
System Uptime: 0 days 0:03:11.429
BugCheck A, {fffff8c0031fca20, 2, 0, fffff80002c6e204}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+200a2 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Aug 16 17:40:45.721 2010 (UTC - 4:00)
System Uptime: 0 days 0:07:21.267
BugCheck A, {fffff8c0031fca20, 2, 0, fffff80002c72204}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+200a2 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
[/font]

 

[Jluras]

Driver verifier was on for all the new BSODs (the one without was the same one i linked from my first post). They all say drvinst.exe seems to be the problem but I'm not sure how to go about handling the file.

 

[Jonathan_King]

I wouldn't pay too much attention to the dumps that says that. All it means is that drvinst.exe was running at the time of the crash.

Time for some hardware checks.

For RAM:

Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 6 passes.

For hard drive, test it with SeaTools, or the utility for your hard drive found here: Hard Drive Diagnostics Tools and Utilities (Storage) - TACKtech Corp.

For CPU: http://www.sevenforums.com/tutorials/100352-cpu-stress-test-prime95.html

Be sure to report the temps Speedfan gives.

 

[Jluras]

Ok, so I ran Prime 95 for 9.5 hours with no errors. Cores #0 and #1 ran at about 57-58 degrees Celsius. Cores #2 and #3 ran at about 49-50 degrees. So no real overheating issues. I then ran Memtest again while I was at work and it completed 12 passes without any errors as well. Finally, I couldn't get Seatools to work OR figure out the other option.

 

[Jonathan_King]

I see you have a Hitachi drive. The Hitachi diagnostic is here: http://www.hitachigst.com/hdd/support/downloads/dft32_v416_b00.iso

After that ISO is downloaded, burn it to a CD, with either ImgBurn, or with the default Windows Disc Image Burner (right-click on the ISO).

 

[Jluras]

Everytime I ran the diagnostic I got the same error when trying to detect my IDE Drive.

 

[Jonathan_King]

What is the error?

 

[Jluras]

Error codes 0984 or 7520. The test would never get past trying to detect my drive.

 

[Jonathan_King]

How about the SeaTools program? Did it error, or do you need assistance with it?

 

[Jluras]

After reinstalling it for the third time it appears to be working. I ran both short and long tests and my hard drive is running just fine.

 

[Jluras]

I BSOD again and thought you might enjoy the minidump Thank you again for all your help so far.

 

[Jonathan_King]

The dump blames your ATI GFX drivers. I see they are the April version. Please install the July version: Graphics Drivers & Software

Test GPU temps: SpeedFan - Access temperature sensor in your computer

...Summary of the Dumps:

[font=lucida console]
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Aug 21 14:26:11.887 2010 (UTC - 4:00)
System Uptime: 0 days 0:11:04.416
BugCheck 7F, {8, 80050031, 6f8, fffff88004ba04c8}
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : atikmdag.sys ( atikmdag+34b4c8 )
BUGCHECK_STR:  0x7f_8
PROCESS_NAME:  Borderlands.ex
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
[/font]

 

[Jluras]

I wiped the 10.7 drivers for the 10.5 because borderlands has a memory issue where it eventually locks up your PC.

 

[Jonathan_King]

Well try using the July drivers, but don't play Borderlands yet. See if they resolve the issue.

In the mean time, go ahead and test GPU temps.

 

[Jluras]

Hrrmmm... speedfan doesn't seem to be detecting my graphics card so I can't get a reading on it.