Semi-frequent BSOD's with new hardware


  1. Posts : 5
    Windows 7
       #1

    Semi-frequent BSOD's with new hardware


    Hey all,

    Just put together a new computer a week or so ago. Threw in the best I could find for the money I had;

    Sabertooth 990FX Motherboard
    AMD FX 8-core CPU
    16gb RAM
    Radeon HD 5770 GPU (Old)
    as well as a new hard drive and optical drive

    The Windows 7 OS (64 bit) I have came from a friend; I do not know if he got his copy from a store or via other means.

    And lately I am getting a BSOD roughly once a day. I started up my computer today, and had a BSOD after just 5 minutes of active time.

    If you can help me at all before I start opening up my computer and reseating everything, I'd appreciate it greatly.

    Here is my minidumps and system health.
      My Computer


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

    I don't know if your copy of Windows 7 is legal (based on your description).
    Please do the following:
    - activate/validate the Windows installation at Genuine Microsoft Software
    Activate - What is validation and how does it work? - Microsoft Windows - Click on the VALIDATE NOW button on the left side
    Validate - Activate Windows 7 on this computer - Follow the instructions to activate your system
    - don't use "leaked"/torrent builds (if this is the case we may never find a fix)

    We cannot provide support for illegal installations of Windows.

    While waiting for your response, I will go so far as to analyze the info that you've provided.....

    Perfmon reports that the "dirty bit" is set on your E: and H: drives
    Run CHKDSK /R /F on each of those drives. If this doesn't fix the problem, then the next step is to format the drive (and this will erase all info on those drives).

    You don't have SP1 installed. Please do this:
    Installing Windows 7 Service Pack 1
    1. Visit the PC manufacturer's website and update ALL drivers. DO NOT use Windows Update or the "Update drivers" function of Device Manager.
    2. Check Device Manager for any unknown/disabled devices - if there are unknown/disabled devices, fix them with the latest drivers from the device manufacturer's website (not the PC Manufacturer)
    3. Visit Windows Update and get all updates
    4. Visit Windows Update and get Service Pack 1 (usually under Important Updates). Read these notes for installing SP1: Steps to follow before you install Windows 7 SP1 and Windows Server 2008 R2 SP1 from the Microsoft Download Center
    5. Visit Windows Update and get any other available updates
    Daemon Tools (and Alcohol % software) are known to cause BSOD's on Win7 systems due to the sptd.sys driver.
    Please uninstall the program, then use the following free tool to ensure that the troublesome sptd.sys driver is removed from your system (pick the 32 or 64 bit system depending on your system's configuration): DuplexSecure - FAQ

    AMD OverDrive (AODDriver2.sys) is either a stand-alone application, or a component of the AMD VISION Engine Control Center.
    Please uninstall the AMD OverDrive program as it can cause BSOD's on your system.
    If it's the stand-alone app, uninstall it via Control Panel...Programs...Uninstall a program
    If it's in the AMD VISION Engine Control Center, you can uninstall it using the AMD uninstall tool (or uninstall the entire AMD VISION Engine Control Center application through Control Panel

    If overclocking, please stop. Remove the overclock and return the system to stock/standard values while we're troubleshooting. Once the system is stable again, feel free to resume the overclocking.

    Please uninstall MSI Afterburner (the same components are used in Riva Tuner and EVGA Precision - so avoid them also). It is a known cause of BSOD's in some Win7 systems.

    BSOD BUGCHECK SUMMARY
    Code:
    
    Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\012312-20373-01.dmp]
    Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
    Debug session time: Mon Jan 23 09:10:51.007 2012 (UTC - 5:00)
    System Uptime: 0 days 0:08:20.427
    Probably caused by : ntkrnlmp.exe ( nt!ObpCloseHandleTableEntry+51 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x3B
    PROCESS_NAME:  svchost.exe
    FAILURE_BUCKET_ID:  X64_0x3B_nt!ObpCloseHandleTableEntry+51
    Bugcheck code 0000003B
    Arguments 00000000`c0000005 fffff800`031ea321 fffff880`0abe7170 00000000`00000000
    BiosVersion = 0813
    BiosReleaseDate = 10/24/2011
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\012212-21886-01.dmp]
    Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
    Debug session time: Sun Jan 22 19:04:54.586 2012 (UTC - 5:00)
    System Uptime: 0 days 4:45:03.006
    Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_LINEAR_POOL::Free+e6 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x50
    PROCESS_NAME:  dwm.exe
    FAILURE_BUCKET_ID:  X64_0x50_dxgmms1!VIDMM_LINEAR_POOL::Free+e6
    Bugcheck code 00000050
    Arguments ffffffff`ffffffe9 00000000`00000000 fffff880`07dd2a2a 00000000`00000000
    BiosVersion = 0813
    BiosReleaseDate = 10/24/2011
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\011912-39811-01.dmp]
    Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
    Debug session time: Thu Jan 19 06:22:24.527 2012 (UTC - 5:00)
    System Uptime: 0 days 9:52:26.947
    Probably caused by : ntkrnlmp.exe ( nt!CmpGetNameControlBlock+12e )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x3B
    PROCESS_NAME:  svchost.exe
    FAILURE_BUCKET_ID:  X64_0x3B_nt!CmpGetNameControlBlock+12e
    Bugcheck code 0000003B
    Arguments 00000000`c0000005 fffff800`02f60a39 fffff880`0ce79aa0 00000000`00000000
    BiosVersion = 0813
    BiosReleaseDate = 10/24/2011
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\011812-20997-01.dmp]
    Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
    Debug session time: Wed Jan 18 20:28:44.262 2012 (UTC - 5:00)
    System Uptime: 0 days 14:06:08.682
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+13b42 )
    BUGCHECK_STR:  0x1a_41201
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  atieclxx.exe
    FAILURE_BUCKET_ID:  X64_0x1a_41201_nt!_??_::FNODOBFM::_string_+13b42
    Bugcheck code 0000001A
    Arguments 00000000`00041201 fffff683`ff7f5b00 0f900003`f0727025 fffffa80`0cf8d450
    BiosVersion = 0813
    BiosReleaseDate = 10/24/2011
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
      
      
      My Computer


  3. Posts : 5
    Windows 7
    Thread Starter
       #3

    I spoke to my friend and he assured me it was legal; and I can confirm this as I had already activated and validated my Windows 7 the day of installation.

    I did all that you asked, though, I don't think I can uninstall the AMD utilities, as I believe the drivers for my GPU came along with it. (I could be wrong; I'll look further into this if I continue to experience BSOD's.)

    Chkdsk didn't do anything noticeable. It ran, checked the disks, then closed. How will I tell if it did not work?

    I'm currently installing SP1, as well. I will let you know if any further BSOD's occur.
      My Computer


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

    Don't worry about the drivers - in the absence of ATI drivers, Microsoft supplies drivers.
    But, let's do this a different way:
    - download the latest Display Driver Only from the ATI website here: ATI Radeon
    - Uninstall all ATI stuff from your system (video will still work) using Control Panel...Programs...Uninstall a program
    - Install the freshly downloaded Display Driver Only that you downloaded previously.
    - monitor for further BSOD's


    Here's how to see what CHKDSK did:
    CHKDSK LogFile:
    Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter
    Expand the Windows logs heading, then select the Application log file entry.
    Double click on the Source column header.
    Scroll down the list until you find the Chkdsk entry (wininit for Win7) (winlogon for XP).
    Copy/paste the results into your next post.
      My Computer


  5. Posts : 5
    Windows 7
    Thread Starter
       #5

    Just want to mention something: I left my computer on all night tonight for the first time without waking up to a BSOD error message on bootup. I'll continue to monitor and follow the steps you described, but thusfar it's working perfectly. Thank you so much for your help.
      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 19:10.
Find Us