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!
Welcome!
Please enable driver verifier: Driver Verifier - Enable and Disable
After it has caused several crashes, follow these directions: http://www.sevenforums.com/crashes-d...tructions.html
Thanks,
~JK
...Summary of the Dumps:
Please enable driver verifier: Driver Verifier - Enable and Disable
After it has caused several crashes, follow these directions: http://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 �������������������������������������������������������������������������������������� 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.
Sorry for the long wait but I wanted (hopefully) enough minidumps. Be sure to upload the output folder found in Documents. This is the actual script data.
Oh shoot, sorry about that! Sorry for the late replies; I have a crazy schedule.
Please enable driver verifier: Driver Verifier - Enable and Disable
...Summary of the Dumps:
...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 �������������������������������������������������������������������������������������� 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.
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: 
�� Quote: Originally Posted by JK 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...t-prime95.html
Be sure to report the temps Speedfan gives.
Time for some hardware checks.
For RAM:
�� Quote: Originally Posted by JK 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 CPU: http://www.sevenforums.com/tutorials...t-prime95.html
Be sure to report the temps Speedfan gives.
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.
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).
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).
Everytime I ran the diagnostic I got the same error when trying to detect my IDE Drive.
What is the error?
Error codes 0984 or 7520. The test would never get past trying to detect my drive.
How about the SeaTools program? Did it error, or do you need assistance with it?
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.
I BSOD again and thought you might enjoy the minidump Thank you again for all your help so far.
Thank you again for all your help so far. 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:
Test GPU temps: SpeedFan - Access temperature sensor in your computer
...Summary of the Dumps:
Code:
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 �������������������������������������������������������������������������������������� I wiped the 10.7 drivers for the 10.5 because borderlands has a memory issue where it eventually locks up your PC.
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.
In the mean time, go ahead and test GPU temps.
Hrrmmm... speedfan doesn't seem to be detecting my graphics card so I can't get a reading on it.
I ran the test for just over 2 hours and there were no artifacts. The temp of my card stayed at around 81-83 degrees the entire time. So, no real issues with the card it appears (unless that's too hot).
Do you have another video card you can use? Maybe borrow one from a friend, or take of from another computer.
dang, not really... Is there any other tests we can run?
BSOD again. Anything you can get from this would be super helpful! Thank you again for everything so far!
I still really wish for a GFX card change.
Just a thought, disable your Creative Audio drivers, in Device Manager. ...Summary of the Dumps:
Just a thought, disable your Creative Audio drivers, in Device Manager.
Code:
Ctafiltv.sys Thu Aug 14 02:48:33 2008
Code:
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Mon Aug 23 18:20:57.616 2010 (UTC - 4:00) System Uptime: 0 days 2:06:40.146 BugCheck 7F, {8, 80050031, 6f8, fffff80002c7af06} Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 ) BUGCHECK_STR: 0x7f_8 PROCESS_NAME: System �������������������������������������������������������������������������������������� Do you think it's because of the Catalyst Control Center? or is this type of this just more common on ATI cards? I might looks into buying an Nvidia if you think it will help.
In my experience, I have seen more nVidia crashes, most likely because nVidia cards are more common.
I'd say neither manufacturer is better at crashes than the other, really.
Can you uninstall the CCC, and install the driver only?
I'd say neither manufacturer is better at crashes than the other, really.
Can you uninstall the CCC, and install the driver only?
I just found it, I'm going to do this. *EDIT* Just installed the driver only. Lets see what happens.
Damn, once again! I might have access to an Nvidia card. I'll swap it out as soon as I can.
I just installed a GeForce 9800 GT. Lets see how this baby runs.
I'm interested to see the results of the card swap.
The dump was uninformative, so if you get more BSODs, please enable driver verifier: Driver Verifier - Enable and Disable
The dump was uninformative, so if you get more BSODs, please enable driver verifier: Driver Verifier - Enable and Disable
Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Jonathan\AppData\Local\Temp\Temp1_minidump.zip\082610-17908-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 (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Machine Name: Kernel base = 0xfffff800`02c04000 PsLoadedModuleList = 0xfffff800`02e41e50 Debug session time: Thu Aug 26 18:16:54.426 2010 (UTC - 4:00) System Uptime: 0 days 2:06:47.971 Loading Kernel Symbols ............................................................... ................................................................ ...................... Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 7F, {8, 80050031, 6f8, fffff80002c79928} Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 ) Followup: MachineOwner --------- 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* UNEXPECTED_KERNEL_MODE_TRAP (7f) This means a trap occurred in kernel mode, and it's a trap of a kind that the kernel isn't allowed to have/catch (bound trap) or that is always instant death (double fault). The first number in the bugcheck params is the number of the trap (8 = double fault, etc) Consult an Intel x86 family manual to learn more about what these traps are. Here is a *portion* of those codes: If kv shows a taskGate use .tss on the part before the colon, then kv. Else if kv shows a trapframe use .trap on that value Else .trap on the appropriate frame will show where the trap was taken (on x86, this will be the ebp that goes with the procedure KiTrap) Endif kb will then show the corrected stack. Arguments: Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT Arg2: 0000000080050031 Arg3: 00000000000006f8 Arg4: fffff80002c79928 Debugging Details: ------------------ BUGCHECK_STR: 0x7f_8 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: 2 LAST_CONTROL_TRANSFER: from fffff80002c73ca9 to fffff80002c74740 STACK_TEXT: fffff880`009efce8 fffff800`02c73ca9 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx fffff880`009efcf0 fffff800`02c72172 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69 fffff880`009efe30 fffff800`02c79928 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2 fffdf880`02f1b468 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!RtlContractHashTable+0x18 STACK_COMMAND: kb FOLLOWUP_IP: nt!KiDoubleFaultAbort+b2 fffff800`02c72172 90 nop SYMBOL_STACK_INDEX: 2 SYMBOL_NAME: nt!KiDoubleFaultAbort+b2 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9 FAILURE_BUCKET_ID: X64_0x7f_8_nt!KiDoubleFaultAbort+b2 BUCKET_ID: X64_0x7f_8_nt!KiDoubleFaultAbort+b2 Followup: MachineOwner --------- Well, It's been a few days since I switched to the Nvidia 9800 GT and I havn't had a single problem. I suppose it is my graphics card after all. The motherboard I have has Nvidia written all over it and there are some Nvidia drivers that I could never sweep when I used driver sweeper. Could my mobo just not like my video card?
Probably more like the card is faulty. Try installing it on another machine, and see if you get BSODs then.
Well, unfortunately I can not fit my video card into his tower and his PSU wouldn't be able to handle it either. My cmputer did BSOD again though with the Nvidia and I have a minidump for you (driver verifier on).
I have a few more minidumps for you (driver verifier on and with the Nvidia card).
Two of the dumps were corrupted.
You may try updating your Intel wireless drivers: � Network Adapter Driver for Windows 7*
What is the make and model of your PSU?
...Summary of the Dumps: Could you get your motherboard tested by the PC shop?
You may try updating your Intel wireless drivers: � Network Adapter Driver for Windows 7*
What is the make and model of your PSU?
...Summary of the Dumps:
Code:
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Sun Aug 29 15:12:18.558 2010 (UTC - 4:00) System Uptime: 0 days 0:00:13.745 BugCheck A, {0, 2, 0, fffff80002c972b3} Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 ) DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP BUGCHECK_STR: 0xA PROCESS_NAME: System �������������������������������������������������������������������������������������� Hmm, well I changed my network driver and I'm not sure if I can get my motherboard checked any time soon. Is there nothing else I can do? I'll leave driver verifier on and report any crashes that I have. All the BSOD after switching to the Nvidia have been from the network driver I'm sure (it was sketchy anyhow, dropping and not picking up internet randomly on start-ups). And all the codes from the BSODs were the same.
More minis! This is getting out of control!
It seems like a certain hardware issue. It may be worth the money to take it to the shop and have them test/swap out components until they figure out what's wrong with it.
If the computer is still under warranty, now would be an excellent chance to use it.
The last thing I can suggest is updating your Creative sound drivers.
If the computer is still under warranty, now would be an excellent chance to use it.
The last thing I can suggest is updating your Creative sound drivers.
Well thank you for all the help. If there is anything I can do for you/the site let me know! The service was incredible and I'd like to give back.
�� Quote: Originally Posted by Jluras 
Well thank you for all the help. If there is anything I can do for you/the site let me know! The service was incredible and I'd like to give back.
Recommending us to others is also appreciated!
Không có nhận xét nào:
Đăng nhận xét