BSOD error 0xA0000001 (0x5, 0x0, 0x0, 0x0)

Page 1 of 2 12 LastLast

  1. Posts : 7
    win7 pro x64
       #1

    BSOD error 0xA0000001 (0x5, 0x0, 0x0, 0x0)


    My computer has been crashing for a a while now. I fixed most of the bugs but this last 1 is stumping me. the BSOD can happen once a week or 2 in ten minutes.

    DXdiag and SF diagnostic file uploaded.

    will upload complete mem dump apon next crash

    VRM on 290x is possibly overheating, but i have no way to check its temperature anymore.
    it seems to happen more with games that are still i beta. let me know if t would help to provide more data.
      My Computer


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

    Hi toeachtheirown.

    Stop 0xA0000001 is inherent with ATI/AMD display. It may be the display driver, or even the GPU.

    First apply any other version (better a known good WHQL) of the display driver.

    For your R9 290x GPU, you have to try any driver version 13.12 WHQL or higher.
    Arc said:
    Uninstall your installed latest version of the display driver.


    Then clean up any possible leftover.


    Then install the target version.
    Let us know the situation with any other version installed.
    ___________________________________
    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+28ece )
    
    Followup: MachineOwner
    ---------
    
    1: 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:  9
    
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
    
    DPC_STACK_BASE:  FFFFF88003122FB0
    
    LAST_CONTROL_TRANSFER:  from fffff8800f2f6ece to fffff80002cc4bc0
    
    STACK_TEXT:  
    fffff880`0311b708 fffff880`0f2f6ece : 00000000`a0000001 00000000`00000005 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
    fffff880`0311b710 00000000`a0000001 : 00000000`00000005 00000000`00000000 00000000`00000000 00000000`00000000 : atikmdag+0x28ece
    fffff880`0311b718 00000000`00000005 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`0bd93af0 : 0xa0000001
    fffff880`0311b720 00000000`00000000 : 00000000`00000000 00000000`00000000 fffffa80`0bd93af0 00000000`00000000 : 0x5
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    atikmdag+28ece
    fffff880`0f2f6ece ??              ???
    
    SYMBOL_STACK_INDEX:  1
    
    SYMBOL_NAME:  atikmdag+28ece
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: atikmdag
    
    IMAGE_NAME:  atikmdag.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  53508a3c
    
    FAILURE_BUCKET_ID:  X64_0xA0000001_atikmdag+28ece
    
    BUCKET_ID:  X64_0xA0000001_atikmdag+28ece
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:x64_0xa0000001_atikmdag+28ece
    
    FAILURE_ID_HASH:  {fe9ca8bf-417e-7edf-c2ea-22e52071137a}
    
    Followup: MachineOwner
    ---------
    
    1: kd> lmvm atikmdag
    start             end                 module name
    fffff880`0f2ce000 fffff880`101de000   atikmdag T (no symbols)           
        Loaded symbol image file: atikmdag.sys
        Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
        Image name: atikmdag.sys
        Timestamp:        Fri Apr 18 07:43:16 2014 (53508A3C)
        CheckSum:         00EAEEE6
        ImageSize:        00F10000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
      My Computer


  3. Posts : 7
    win7 pro x64
    Thread Starter
       #3

    I have repeatedly reinstall drivers, beta and normal and used driver sweeper to uninstall the driver with my try, to no avail. are you suggestng that i try each version of the graphics card driver, 13.12 to current?
      My Computer


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

    That means the issue occurs irrespective of driver versions, for sure?

    Then there is no other way but replacing the GPU.

    I was suggesting to use any other driver version which is at least 13.12 WHQL, because the earlied drivers are not supported with R9 290x.

    As you are saying that you have already tried it but nothing changed, then it is not needed anymore.
      My Computer


  5. Posts : 7
    win7 pro x64
    Thread Starter
       #5

    I do not believe it is the gpu as it came from a litecoin mining machine and had no problems for six months.
      My Computer


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

    If the issue stop 0xA000001 continues irrespective of the driver version, it is the fault from the part of the GPU. You believe it or not. Even if it came from the Mars.
      My Computer


  7. Posts : 7
    win7 pro x64
    Thread Starter
       #7

    sry if i sounded like a jerk but i rly don't WANT it to be the graphics card. I am pursuing an RMA and will post a complete mem dump if/when it happens. and thank you fr your help, this has been a problem i have been stumped by for months.
      My Computer


  8. Posts : 7
    win7 pro x64
    Thread Starter
       #8

    complete crash dump enclosed. sending card for RMA now. being thorough.
      My Computer


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

    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+28ece )
    
    Followup: MachineOwner
    ---------
    
    1: 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:  9
    
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
    
    DPC_STACK_BASE:  FFFFF88002F22FB0
    
    LAST_CONTROL_TRANSFER:  from fffff8800f0a9ece to fffff80002c85bc0
    
    STACK_TEXT:  
    fffff880`02f1b708 fffff880`0f0a9ece : 00000000`a0000001 00000000`00000005 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
    fffff880`02f1b710 00000000`a0000001 : 00000000`00000005 00000000`00000000 00000000`00000000 00000000`00000000 : atikmdag+0x28ece
    fffff880`02f1b718 00000000`00000005 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`10fc75b0 : 0xa0000001
    fffff880`02f1b720 00000000`00000000 : 00000000`00000000 00000000`00000000 fffffa80`10fc75b0 00000000`00000000 : 0x5
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    atikmdag+28ece
    fffff880`0f0a9ece ??              ???
    
    SYMBOL_STACK_INDEX:  1
    
    SYMBOL_NAME:  atikmdag+28ece
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: atikmdag
    
    IMAGE_NAME:  atikmdag.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  53508a3c
    
    FAILURE_BUCKET_ID:  X64_0xA0000001_atikmdag+28ece
    
    BUCKET_ID:  X64_0xA0000001_atikmdag+28ece
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:x64_0xa0000001_atikmdag+28ece
    
    FAILURE_ID_HASH:  {fe9ca8bf-417e-7edf-c2ea-22e52071137a}
    
    Followup: MachineOwner
    ---------
    
    1: kd> lmvm atikmdag
    start             end                 module name
    fffff880`0f081000 fffff880`0ff91000   atikmdag T (no symbols)           
        Loaded symbol image file: atikmdag.sys
        Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
        Image name: atikmdag.sys
        Timestamp:        Fri Apr 18 07:43:16 2014 (53508A3C)
        CheckSum:         00EAEEE6
        ImageSize:        00F10000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
      My Computer


  10. Posts : 7
    win7 pro x64
    Thread Starter
       #10

    so i got back a new card form the RMA but seem to be getting the same BSOD error. i think its a compatability issue of my 290x with my MBs Triple channel ram setup. SF diag info enclosed.

    EDIT: mem dump is kernel ( i think ) because this is a different OS install than b4.
      My Computer


 
Page 1 of 2 12 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 05:00.
Find Us