Quick question

[MattDHarris]

My system has been experiencing BSODs about once a day now. It started about 2 days after I got my new video card but I also have a Hard Drive that is failing and is going to be replaced in a few days. So I was wondering if that could be causing the BSODs or if I have another more serious problem.

All of my parts except my Hard drives are brand new and this is on a fresh install of Windows Home Premium x64.

Attached are my .dmp files

 

[Night Hawk]

Hello MattDHarris Welcome to the Seven Forums!

Without even a look at the dump file you provided you are likely experiencing two main causes.
1) leftover drivers from the previous video card not cleaned off fully
2) A failing hard drive is a source for an endless list of errors.

A third possible cause may be the incorrect drivers for the new card you have or simply a bad install of Windows/drivers seen and possibly due to problems with the main drive. If the fresh install went bad from the start resulting from a bad drive that would account for a list of problems.

The course of action now best advised would be making sure you have everything backed up from the failing drive in anticipation of replacement where you will be seeing another clean install. If you still continue to see problems then you have to start looking for other likely causes including high temps and possible memory faults.

 

[Jonathan_King]

I've run the dump files. I see one 0x24 BSOD: NTFS.sys. That sometimes points to a hard drive issue (but not always), but it makes sense if your drive is failing.

I'd second Night Hawk's advice to get that data backed up and replace the drive.

Could you run driver verifier? http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

Finally, run the blend and small FFTs Prime95 tests: http://www.sevenforums.com/tutorials/100352-cpu-stress-test-prime95.html

...Summary of the dumps:

[font=lucida console]
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Wed Mar  2 19:07:35.079 2011 (UTC - 5:00)
System Uptime: 0 days 0:49:11.000
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+46411 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x18
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x18_CORRUPT_REF_COUNT_nt!_??_::FNODOBFM::_string_+46411
SystemProductName = To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Tue Mar  1 00:58:18.700 2011 (UTC - 5:00)
System Uptime: 0 days 0:21:41.011
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+2be79 )
BUGCHECK_STR:  0x1a_782
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x1a_782_nt!_??_::FNODOBFM::_string_+2be79
SystemProductName = To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Tue Mar  1 00:35:58.164 2011 (UTC - 5:00)
System Uptime: 1 days 10:06:01.475
Probably caused by : Ntfs.sys ( Ntfs!NtfsCachedRead+180 )
PROCESS_NAME:  TeamViewer.exe
BUGCHECK_STR:  0x24
DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE
FAILURE_BUCKET_ID:  X64_0x24_Ntfs!NtfsCachedRead+180
SystemProductName = To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
[/font]

 

[MattDHarris]

Ok, so after running driver verifier it blue screened on start up. I let it do this multiple times just to make sure all the dumps were the same, which they are. So i am going to only upload one of the 7 I got.

Edit: Just had 2 more blue screens while running IL-2. They are both attached.

 

[Jonathan_King]

Could you please upload a full jcgriff2 report?

http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

 

[MattDHarris]

Alright, here is the jcgriff2 report.

 

[Jonathan_King]

Thanks.

It appears that your Etron USB 3.0 drivers are the cause of these ones. Please install these updated ones: Etron Technology Inc.

EtronHub3.sys     Mon Oct 25 03:08:24 2010 (4CC52CE8)
EtronXHCI.sys     Mon Oct 25 03:08:22 2010 (4CC52CE6)
FNETTBOH_305.SYS  Wed Nov 03 02:24:26 2010 (4CD1001A)
FNETURPX.SYS      Fri Oct 03 22:27:02 2008 (48E6D476)

Go ahead and disable driver verifier now; let's hope the BSODs stop.

...Summary of the dumps:

[font=lucida console]
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Wed Mar  2 21:17:25.368 2011 (UTC - 5:00)
System Uptime: 0 days 0:01:04.320
*** WARNING: Unable to verify timestamp for EtronXHCI.sys
*** ERROR: Module load completed but symbols could not be loaded for EtronXHCI.sys
*** WARNING: Unable to verify timestamp for FNETTBOH_305.SYS
*** ERROR: Module load completed but symbols could not be loaded for FNETTBOH_305.SYS
Probably caused by : FNETTBOH_305.SYS ( FNETTBOH_305+3e80 )
BUGCHECK_STR:  0xc9_228
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  csrss.exe
FAILURE_BUCKET_ID:  X64_0xc9_228_VRF_FNETTBOH_305+3e80
SystemProductName = To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Wed Mar  2 21:15:23.414 2011 (UTC - 5:00)
System Uptime: 0 days 0:01:03.741
*** WARNING: Unable to verify timestamp for EtronXHCI.sys
*** ERROR: Module load completed but symbols could not be loaded for EtronXHCI.sys
*** WARNING: Unable to verify timestamp for FNETTBOH_305.SYS
*** ERROR: Module load completed but symbols could not be loaded for FNETTBOH_305.SYS
Probably caused by : FNETTBOH_305.SYS ( FNETTBOH_305+3e80 )
BUGCHECK_STR:  0xc9_228
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xc9_228_VRF_FNETTBOH_305+3e80
SystemProductName = To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Wed Mar  2 21:08:57.851 2011 (UTC - 5:00)
System Uptime: 0 days 0:01:04.178
*** WARNING: Unable to verify timestamp for EtronXHCI.sys
*** ERROR: Module load completed but symbols could not be loaded for EtronXHCI.sys
*** WARNING: Unable to verify timestamp for FNETTBOH_305.SYS
*** ERROR: Module load completed but symbols could not be loaded for FNETTBOH_305.SYS
Probably caused by : FNETTBOH_305.SYS ( FNETTBOH_305+3e80 )
BUGCHECK_STR:  0xc9_228
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xc9_228_VRF_FNETTBOH_305+3e80
SystemProductName = To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Wed Mar  2 19:07:35.079 2011 (UTC - 5:00)
System Uptime: 0 days 0:49:11.000
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+46411 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x18
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x18_CORRUPT_REF_COUNT_nt!_??_::FNODOBFM::_string_+46411
SystemProductName = To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
[/font]

 

[Night Hawk]

One thing to mention here is that you will likely continue to see a different error for each other new BSOD as long as the ntkrnlmp.exe file is involved in any more of them. That or the other main system files are possibly in need of repair/replacement due to the drive itself.

I'm sure you'll be glad when the new drive is in and all these are no longer a problem. The help here by Jonathan_King will get you through until then.

 

[MattDHarris]

Well the new drive should get here tomorrow but the bad drive doesn't have my windows install on it, it just has all of my non essential programs (games).

Anyway I tried to install the latest Etron driver, it took about 3 tries but I am still getting the same c9 error when I enable Driver verification.

I have also run memtest no errors after 7 passes and Prime95 for about 8 hours on blend with no issue.

 

[Night Hawk]

If you custom installed the games onto the bad drive those may run into their own errrors.

The good news for you is being able to rule any bad memory being a cause for concern. If everything went flawlessly with the 7 install the next step will looking back at each thing you added on until seeing the blue screens.

If you disabled everything in the msconfig Startup and suddenly they all stop you saw a bad install of something with Eltron coming in at the top of list. They only recently moved into USB 3.0 technologies moving away from desktop/laptop memory as well as onboard memory for video cards.

As far as the Eltron usb driver was that the EJ168 USB 3.0 host controller? Your board may not even use that particular driver if you went to Eltron directly. Asrock has an H67 with variations seen at their support site. H67 Motherboard Series - Download Files form ASRock Inc. > Latest Drivers Update

 

[MattDHarris]

I think I may have sorted it out as I can now boot with driver verifier running. Turns out I had an old Flash drive plugged into one of my USB 3.0 slots and I didn't realize it but legacy support was disabled in the BIOS causing at the very least the C9 stop error.

I hope that is the only issue and if it is thank you for the help, I really appreciated it.

 

[Night Hawk]

Ironically I was going to ask if you had been using the 3.0 ports at all just is case you had been plugging a 3.0 device in. It seems you found that out yourself. You still will be running into other blue screens however until everything is sorted out. That only explains a few not all of them.

To avoid seeing that happen again you may want to grab a small hub you can have out in front or top of the case rather then reaching in back all the time. When you are reaching in bacck and feeling around without looking you won't see the different color on the 3.0 ports. You would be surprized at how many might have that happen!