BSOD Crash on New Build

Page 1 of 4 123 ... LastLast

  1. Posts : 22
    Windows 7 Home Premium 64-bit
       #1

    BSOD Crash on New Build


    This was my first attempt at a new complete system build. I bought the computer off a friend in need of cash and had to replace a dead mobo and psu. Its been giving me a BSOD from the very beginning. No idea what's causing it except it seems to happen more frequently when watching a video clip or playing a game (maybe a problem with the graphics card?). All the drivers appear to be up to date.

    Windows 7 64-bit 6.1.7600 Build 7600 Full retail version

    Thanks so much for your help!!
      My Computer


  2. Posts : 11,840
    64-bit Windows 8.1 Pro
       #2

    The dmp(s) point to ntkrnlmp.exe or ntoskrnl.exe as the probable cause. We know this is not the case, as these are core OS files, and will definitely not cause a BSOD. They are just the default files the debuggers blame when they can't see a better cause. We need to enable Driver Verifier to help pinpoint the faulting module...

    - 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"
    - 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).

    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1A, {41790, fffffa80009a2180, ffff, 0}
    
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+33906 )
    
    Followup: MachineOwner
    ---------
    
    
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1A, {41790, fffffa80009a21b0, ffff, 0}
    
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+33906 )
    
    Followup: MachineOwner
    ---------
      My Computer


  3. Posts : 22
    Windows 7 Home Premium 64-bit
    Thread Starter
       #3

    wow. I did that and rebooted. Now it crashes just after I log into windows. Doesn't even finish pulling up the desktop or give me time to click on anything. This time the BSOD is pointing to clbudf.sys

    What's next?
      My Computer


  4. Posts : 11,840
    64-bit Windows 8.1 Pro
       #4

    That is the purpose of driver verifier ... upload the NEW .dmp files..
      My Computer


  5. Posts : 11,840
    64-bit Windows 8.1 Pro
       #5

    clbudf.sys is your Cyberlink UDF Driver ... you can download the latest version from http://www.cyberlink.com/downloads/s...dex_en_US.html but we still need the new .dmp file..
      My Computer


  6. Posts : 22
    Windows 7 Home Premium 64-bit
    Thread Starter
       #6

    Ok. Sorry that took me so long. I had to restart in safe mode as it kept giving a BSOD as soon as I logged in. I've attached the latest dump files. Each time it would BSOD I removed the related program from the startup list in msconfig or uninstalled (some was bloatware). Then rebooted the computer, which would give me a new BSOD. Seems like this might be a never-ending trend. Insights please?

    Adam
      My Computer


  7. Posts : 22
    Windows 7 Home Premium 64-bit
    Thread Starter
       #7

    I've been getting BSOD referencing my graphics card driver, a seagate driver, and the cyberlink driver. I think I've resolved those by either uninstalling the software and driver or updating to the most current driver. Now I'm getting these 2 dumps. Is this ever going to end? lol
      My Computer


  8. Posts : 22
    Windows 7 Home Premium 64-bit
    Thread Starter
       #8

    Anyone?
      My Computer


  9. Posts : 1
    Windows 7 Ultimate 32 bit
       #9

    PLEASE HELPPPPPPP =(

    ==================================================
    Dump File : 012411-17390-01.dmp
    Crash Time : 1/24/2011 7:19:48 AM
    Bug Check String : BAD_POOL_HEADER
    Bug Check Code : 0x00000019
    Parameter 1 : 0x00000020
    Parameter 2 : 0xfdeddf40
    Parameter 3 : 0xfdeddf80
    Parameter 4 : 0x4a0800ab
    Caused By Driver : win32k.sys
    Caused By Address : win32k.sys+ce508
    File Description : Multi-User Win32 Driver
    Product Name : Microsoft® Windows® Operating System
    Company : Microsoft Corporation
    File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
    Processor : 32-bit
    Computer Name :
    Full Path : C:\Windows\Minidump\012411-17390-01.dmp
    Processors Count : 2
    Major Version : 15
    Minor Version : 7600
    Dump File Size : 139,440
    ==================================================



    ==================================================
    Dump File : 012611-24421-01.dmp
    Crash Time : 1/26/2011 5:45:23 AM
    Bug Check String : BAD_POOL_HEADER
    Bug Check Code : 0x00000019
    Parameter 1 : 0x00000020
    Parameter 2 : 0x9a9c0c00
    Parameter 3 : 0x9a9c0c00
    Parameter 4 : 0x0a000601
    Caused By Driver : ntoskrnl.exe
    Caused By Address : ntoskrnl.exe+117c4e
    File Description : NT Kernel & System
    Product Name : Microsoft® Windows® Operating System
    Company : Microsoft Corporation
    File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
    Processor : 32-bit
    Computer Name :
    Full Path : C:\Windows\Minidump\012611-24421-01.dmp
    Processors Count : 2
    Major Version : 15
    Minor Version : 7600
    Dump File Size : 139,440
    ==================================================
      My Computer


  10. Posts : 927
    windows 7 ultimate
       #10

    Hi awinterton,

    AVG is known to be a cause of BSOD's on some Win 7 systems so you need to uninstall it. Download the correct AVG Remover for your system. AVG Remover(64bit) or AVG Remover(32bit). If you have AVG ID protection installed, download the AVGID Protection Remover as well (it won't hurt to d'load and run it anyway). Download Microsoft Security Essentials as its replacement. Re-boot to Safe Mode. In Safe Mode run the AVG Removal tools. Re-boot to normal mode and install MSE. Make sure your Windows firewall is enabled!

    PC Tools is known to be a cause of BSOD's on some Windows 7 systems. Uninstall PC Tools.
    If you've already uninstalled PC Tools, go to C:\Windows\System32\Drivers and rename PCTCore64.sys to PCTCore64.old

    More to follow.
      My Computer


 
Page 1 of 4 123 ... LastLast

  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 20:27.
Find Us