BSOD on fresh install

Jluras · 15 Aug 2010

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 · 15 Aug 2010

Welcome!

Please enable driver verifier: Driver Verifier - Enable and Disable

After it has caused several crashes, follow these directions: https://www.sevenforums.com/crashes-d...tructions.html

Thanks,
~JK

...Summary of the Dumps:

Code:


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
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨

Jluras · 16 Aug 2010

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 · 17 Aug 2010

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

Jluras · 17 Aug 2010

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

Jonathan_King · 17 Aug 2010

Please enable driver verifier: Driver Verifier - Enable and Disable

...Summary of the Dumps:

Code:


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
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨

Jluras · 17 Aug 2010

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 · 17 Aug 2010

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:

JK said:

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: https://www.sevenforums.com/tutorials...t-prime95.html

Be sure to report the temps Speedfan gives.

Jluras · 19 Aug 2010

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 · 19 Aug 2010

I see you have a Hitachi drive. The Hitachi diagnostic is here: http://www.hitachigst.com/hdd/suppor...2_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).