BSOD on New Build


  1. Posts : 4
    Windows 7 RC Build 7100
       #1

    BSOD on New Build


    Hi Everyone.

    Just put together a new HTPC for a friend of mine. Here are the specs:

    AMD Athlon II X3 440
    Gigabyte
    GA-880GM-USB3 (rev. 1.0)
    Geil 4gb Value 1600
    WD 1TB Green
    Gigabyte Ati 5570 1gb

    The windows is windows 7 ultimate x64 (retail).

    The rig is brand new, did a clean install and after around 10 mins, while trying to install microsoft office, the BSOD appeared. i had earlier done a clean format because the bsod kept appearing when installing certain software, or running programs like autocad or photoshop. Would appreciate any input, thank you!!
      My Computer


  2. Posts : 4
    Windows 7 RC Build 7100
    Thread Starter
       #2

    *bump*
      My Computer


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

    Unfortunately, the Windows Debugging Tools aren't able to access symbols for your operating system 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

    Please install the drivers for this device (likely a part of the chipset drivers for your motherboard/system):
    Universal Serial Bus (USB) Controller PCI\VEN_1033&DEV_0194&SUBSYS_50071458&REV_03\4&87DAECB&0&0028 The drivers for this device are not installed.
    Please run Driver Verifier according to these directions:
    Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

    So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

    Then, here's the procedure:
    - Go to Start and type in "verifier" (without the quotes) and press Enter
    - Select "Create custom settings (for code developers)" and click "Next"
    - Select "Select individual settings from a full list" and click "Next"
    - Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
    NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
    - Select "Select driver names from a list" and click "Next"
    Then select all drivers NOT provided by Microsoft and click "Next"
    - Select "Finish" on the next page.

    Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

    Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

    If you can't get into Windows because it crashes too soon, try it in Safe Mode.
    If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

    If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:
    Code:
    Delete these registry keys (works in XP, Vista, Win7):
            HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
            HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel
    More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users
    BSOD BUGCHECK SUMMARY
    Code:
    
    *** 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: Sat Sep  4 06:20:32.857 2010 (UTC - 4:00)
    System Uptime: 0 days 0:13:03.480
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    BugCheck 3B, {c0000005, fffff80002b69bb9, fffff880050fc820, 0}
    Probably caused by : ntoskrnl.exe ( nt+34dbb9 )
    BUGCHECK_STR:  0x3B
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
      
      
     
     
      My Computer


  4. Posts : 4
    Windows 7 RC Build 7100
    Thread Starter
       #4

    thank you for the input usasma! after installing the USB driver there has not been any bluescreens (none that he has informed me of at least). many thanks.
      My Computer


  5. Posts : 5,705
    Win7 x64 + x86
       #5

    Glad to hear it. Thanks for letting us know!
      My Computer


 

  Related Discussions
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 22:25.
Find Us