New Built System BSOD HELL


  1. NewSystemBuild
    Posts : 5
    Windows 7 Home Premium 64
       New #1

    New Built System BSOD HELL


    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.
      My Computer
    Quote Quote

  3. NewSystemBuild
    Posts : 5
    Windows 7 Home Premium 64
    Thread Starter
       New #2

    Here are some more reports.
      My Computer
    Quote Quote

  4. usasma
    Posts : 5,705
    Win7 x64 + x86
       New #3

    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:
    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
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
      My Computer
    Quote Quote

  6. NewSystemBuild
    Posts : 5
    Windows 7 Home Premium 64
    Thread Starter
       New #4

    Thank you


    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.
      My Computer
    Quote Quote

 

  Related Discussions
I built a new system myself with the following components: i7 2600k @ 4.5ghz asus p8p67 deluxe gskill ripjawsx 16gb 2133mhz @ 2200mhz asus eah4870 1gb crucial m4 64gb wd caviar black 500gb everything has been running smoothly for approximately 6 months, i have been very pleased with how...
BSOD on newly built system
in BSOD Help and Support

hey everyone i just built my new computer, yes it my first one i got it all assembled but im having problems with drivers im pretty sure thats what it is. this is the BSOD i get once in awhile playing Starcraft 2. Problem signature: Problem Event Name: BlueScreen OS Version: ...
BSOD hell on brand new system
in BSOD Help and Support

I keep getting BSODs on my new system. This is quite literally a brand new, clean system, built from the ground up. The screens come at seemingly random times (even when the computer is sitting idle) as there is nothing we are doing the same each time. We have gone through and updated every last...
BSOD on self built system (NEW)
in BSOD Help and Support

Been getting 4 BSOD at least and this is the first system I've been having BSOD's. I'm assuming its a hardware problem, but I'm not an expert so here you go and thank you in advanced: Current OS: Windows 7 Home Premium x64
BSOD newly built system
in BSOD Help and Support

Just built up a 6 core AMD 1075T Asus M4A89GTD PRO 4 gig or ram ddr3 corsair dominator. Using 64 bit 7 and using on board graphics. Any Ideas would really help me out.:cry: Problem signature: Problem Event Name: BlueScreen OS Version: 6.1.7600.2.0.0.768.3 Locale ID: 1033 ...
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

 й Designer Media Ltd
All times are GMT -5. The time now is 15:38.
Find Us