BSODs since installing new GPU


  1. Posts : 2
    Windows 7 Professional 64bit
       #1

    BSODs since installing new GPU


    Hello all,

    Ever since I upgraded from an AMD 6950 to AMD 7970 (Gigabyte) I've been getting not only random "video driver has failed and successfully recovered" messages, but also BSODs. None have happened while playing games, ironically, but while doing non-computer intensive tasks such as browsing the internet or using MS Word.

    Here is the latest message I received today following a BSOD:

    OS Version: 6.1.7601.2.1.0.256.48
    Locale ID: 4105

    Additional information about the problem:
    BCCode: a0000001
    BCP1: 0000000000000005
    BCP2: 0000000000000000
    BCP3: 0000000000000000
    BCP4: 0000000000000000
    OS Version: 6_1_7601
    Service Pack: 1_0
    Product: 256_1


    I've updated as many drivers as I could find, as well as BIOS and firmware updates for my MOBO, GPU, and SSD. Attached is the information created using the SF Diagnostic Tool.
      My Computer


  2. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #2

    Hi rogat.

    A stop 0xA0000001 is an error inherent in ATI/AMD GPU or display driver.

    As the first try, uninstall the display driver. Then follow Drivers - Clean Left over Files after Uninstalling to clean up the leftovers.

    Then install an older version of the display driver. 13.4 WHQL is known to be a stable one.

    Let us know the results. If it continues to BSOD in the same way with that driver too, there will be only one way for you, to replace the GPU.
    Code:
    *** WARNING: Unable to verify timestamp for atikmdag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck A0000001, {5, 0, 0, 0}
    
    Probably caused by : atikmdag.sys ( atikmdag+258de )
    
    Followup: MachineOwner
    ---------
    
    9: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Unknown bugcheck code (a0000001)
    Unknown bugcheck description
    Arguments:
    Arg1: 0000000000000005
    Arg2: 0000000000000000
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    
    Debugging Details:
    ------------------
    
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    BUGCHECK_STR:  0xA0000001
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  7
    
    TAG_NOT_DEFINED_c000000f:  FFFFF88003486FB0
    
    LAST_CONTROL_TRANSFER:  from fffff8800f2748de to fffff80003c7dbc0
    
    STACK_TEXT:  
    fffff880`0347f6c8 fffff880`0f2748de : 00000000`a0000001 00000000`00000005 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
    fffff880`0347f6d0 00000000`a0000001 : 00000000`00000005 00000000`00000000 00000000`00000000 00000000`00000000 : atikmdag+0x258de
    fffff880`0347f6d8 00000000`00000005 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xa0000001
    fffff880`0347f6e0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x5
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    atikmdag+258de
    fffff880`0f2748de ??              ???
    
    SYMBOL_STACK_INDEX:  1
    
    SYMBOL_NAME:  atikmdag+258de
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: atikmdag
    
    IMAGE_NAME:  atikmdag.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  52540dc7
    
    FAILURE_BUCKET_ID:  X64_0xA0000001_atikmdag+258de
    
    BUCKET_ID:  X64_0xA0000001_atikmdag+258de
    
    Followup: MachineOwner
    ---------
    
    9: kd> lmvm atikmdag
    start             end                 module name
    fffff880`0f24f000 fffff880`0fe98000   atikmdag T (no symbols)           
        Loaded symbol image file: atikmdag.sys
        Image path: atikmdag.sys
        Image name: atikmdag.sys
        Timestamp:        Tue Oct 08 19:21:03 2013 (52540DC7)
        CheckSum:         00BFB253
        ImageSize:        00C49000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
      My Computer


  3. Posts : 2
    Windows 7 Professional 64bit
    Thread Starter
       #3

    Hi Arc,

    Sorry for the delay, but I thought I'd keep you updated.

    Since yesterday:


    • I've uninstalled the current AMD drivers, used driver sweeper to get rid of any remaining files and installed the 13.4 drivers, as you suggested.
    • I disabled CCC from running on start-up (I read somewhere that this can cause issues)
    • I also made an addition to the registry regarding TDR Delay to 10 seconds (I also read that this can cause issues)
    • Also, looking through my installed programs list, I noticed that Nvidia PhysX was installed somehow, even though this machine only ever used AMD cards, and uninstalled that
    • In addition, I recently acquired a new sound card and installed it the same day (also I disabled on board sound through BIOS, removed AMD HD sound, as well as on board Realtek drivers); I include this for the sake of being thorough

    Since yesterday, I have not encountered any BSODs after making the changes above, but I don't think I'm in the clear just yet; in the past I've been able to go a couple days without experiencing a BSOD.
      My Computer


  4. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #4

    If this BSOD comes back even with another driver version, you will need to change the GPU.
      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:30.
Find Us