Windows 7: New Built System BSOD HELL

NewSystemBuild · 12 Sep 2010

I typed in the most common on Google, and it brought me to this forum! Perhaps you guys can help me out. The title of the error is BUGCODE_USB_DRIVER. I send along the dump file with this.

NewSystemBuild · 12 Sep 2010

Here are some more reports.

usasma · 14 Sep 2010

This seems to be a hardware problem. 10 memory dumps, 3 different BSOD errors, and it blames 5 different things.

Unfortunately, the Windows Debugging Tools aren't able to access symbols for your operating system files for some (BUT NOT ALL) of the dump files (in particular NTOSKRNL.EXE / NTKRNLMP.EXE / NTKRNLPA.EXE / NTKRPAMP.EXE) from the Microsoft Symbol Server - so that makes debugging them difficult if not impossible.

Please do the following (this will not affect the analysis of the current files - but it may help later files that are acquired):
- activate/validate the Windows installation at Genuine Microsoft Software
- run sfc.exe /scannow to replace any problem files
- open a support incident with Microsoft to see if they can fix the missing symbols issue ( Windows 7 Solution Center )
- If that doesn't fix it, then wipe the hard drive and reinstall Windows
- don't use "leaked"/torrent builds

Start with these free diagnostics:

Quote:

H/W Diagnostics:
Please start by running these bootable hardware diagnostics:
Memory Diagnostics (read the details at the link)
HD Diagnostic (read the details at the link)

Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Malware (read the details at the link)

BSOD BUGCHECK SUMMARY

Code:


Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Sep 12 21:56:32.934 2010 (UTC - 4:00)
System Uptime: 0 days 0:06:22.729
BugCheck FE, {5, fffffa8004e4c1a0, 10024396, fffffa8004d6a800}
Probably caused by : usbehci.sys ( usbehci!EHCI_PollActiveControlEndpoint+57 )
BUGCHECK_STR:  0xFE
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Sep 12 21:49:18.530 2010 (UTC - 4:00)
System Uptime: 0 days 0:04:29.951
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
BugCheck FE, {5, fffffa8004d8a1a0, 10024396, fffffa8005b48500}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  0xFE
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Sep 12 21:42:51.300 2010 (UTC - 4:00)
System Uptime: 0 days 0:04:05.720
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
BugCheck FE, {5, fffffa8004d241a0, 10024396, fffffa8004c45c50}
Probably caused by : Unknown_Module_fffff880`019baf40 ( Unknown_Module_fffff880`019baf40>+12b78b2 )
BUGCHECK_STR:  0xFE
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Sep 12 21:01:37.232 2010 (UTC - 4:00)
System Uptime: 0 days 0:06:02.011
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
BugCheck FE, {5, fffffa8004faf1a0, 10024396, fffffa8005761460}
Probably caused by : usbehci.sys ( usbehci!EHCI_sMode_PollEndpointSlot+67 )
BUGCHECK_STR:  0xFE
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Sep 12 20:51:56.610 2010 (UTC - 4:00)
System Uptime: 0 days 0:02:26.015
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
BugCheck FE, {5, fffffa8004fb31a0, 10024396, fffffa800584f250}
Probably caused by : usbehci.sys ( usbehci!EHCI_sMode_PollEndpointSlot+67 )
BUGCHECK_STR:  0xFE
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Sep 12 20:30:59.551 2010 (UTC - 4:00)
System Uptime: 0 days 0:02:59.330
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
BugCheck FE, {5, fffffa8004eb61a0, 10024396, fffffa800537cc50}
Probably caused by : usbehci.sys ( usbehci!EHCI_PollActiveControlEndpoint+57 )
BUGCHECK_STR:  0xFE
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Sep 12 20:26:14.738 2010 (UTC - 4:00)
System Uptime: 0 days 0:02:48.517
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
BugCheck 1E, {ffffffffc0000005, fffff8800581b47d, 0, ffffffffffffffff}
Probably caused by : Unknown_Module_fffffa80`04ff2e68 ( Unknown_Module_fffffa80`04ff2e68>+1d0bc0 )
BUGCHECK_STR:  0x1E_c0000005
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Sep 12 20:19:51.831 2010 (UTC - 4:00)
System Uptime: 0 days 0:02:29.610
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
BugCheck D1, {fffff88001300f6c, 2, 8, fffff88001300f6c}
Probably caused by : Ntfs.sys ( Ntfs! ?? ::NNGAKEGL::`string'+7d28 )
BUGCHECK_STR:  0xD1
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Sep 12 20:17:00.062 2010 (UTC - 4:00)
System Uptime: 0 days 0:02:09.841
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
BugCheck 1E, {ffffffffc0000005, fffff80002ba6f8c, 0, ffffffffffffffff}
Probably caused by : ntoskrnl.exe ( nt+1a3f8c )
BUGCHECK_STR:  0x1E_c0000005
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Sep 12 19:45:35.712 2010 (UTC - 4:00)
System Uptime: 0 days 0:09:45.155
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
BugCheck 1E, {0, 0, 0, 0}
Probably caused by : Unknown_Module_fffffa80`04ba99a0 ( Unknown_Module_fffffa80`04ba99a0>+ed708 )
BUGCHECK_STR:  0x1E_0
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

NewSystemBuild · 14 Sep 2010

Thank you for your response! I have already set to return the motherboard and have ordered another one. Hopefully that is the issue. That was my best guess, given the variety of errors. I can't even post anymore, even if i reset the bios, so I can't even run the tests. I guess we'll find out if that's the case, when I get a new one in. I did not have enough time to run any kind of tests, when I first got it working. My hope is that nothing else in the system is damaged from the motherboard! (assuming that that is the problem). If it's the CPU, it is also under warranty. I'll find out soon.

Windows 7: New Built System BSOD HELL

New Built System BSOD HELL problems?