BSOD while doing random things on PC ntoskrnl.exe+6f880


  1. Posts : 3
    Windows 7 ultimate 64 bit
       #1

    BSOD while doing random things on PC ntoskrnl.exe+6f880


    I just built a new computer primarily for gaming and since this morning it has BSOD'd on me twice. I was not doing any gaming the first time and the second time it bsod was when I was playing far cry 3.

    I have attached the mini dump text file below but for some reason the actual dump file is not visible when I try to upload it.

    Any help would be greatly appreciated
      My Computer


  2. Posts : 15,026
    Windows 10 Home 64Bit
       #2

    Please follow Blue Screen of Death (BSOD) Posting Instructions to grab all and upload a report here.
      My Computer


  3. Posts : 3
    Windows 7 ultimate 64 bit
    Thread Starter
       #3

    Hey, sorry for not having uploaded the zipped file earlier on but I have attached it to this message
      My Computer


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

    Uninstall your installed version of the display driver.


    Then clean up any possible leftover.


    Then install version 13.9 WHQL only.


    Let us know the result.
    __________________________________
    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
    ---------
    
    4: 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:  a
    
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
    
    LAST_CONTROL_TRANSFER:  from fffff8800f488ece to fffff80002ecebc0
    
    STACK_TEXT:  
    fffff880`009db6b8 fffff880`0f488ece : 00000000`a0000001 00000000`00000005 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
    fffff880`009db6c0 00000000`a0000001 : 00000000`00000005 00000000`00000000 00000000`00000000 00000000`00000000 : atikmdag+0x28ece
    fffff880`009db6c8 00000000`00000005 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`0b0ba7a0 : 0xa0000001
    fffff880`009db6d0 00000000`00000000 : 00000000`00000000 00000000`00000000 fffffa80`0b0ba7a0 00000000`00000000 : 0x5
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    atikmdag+28ece
    fffff880`0f488ece ??              ???
    
    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
    ---------
    
    4: kd> lmvm atikmdag
    start             end                 module name
    fffff880`0f460000 fffff880`10370000   atikmdag T (no symbols)           
        Loaded symbol image file: atikmdag.sys
        Image path: 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


  5. Posts : 3
    Windows 7 ultimate 64 bit
    Thread Starter
       #5

    hey, im in the process of installing the 13.9 drivers now but what is going on with AMD and their drivers atm? seems like im not the only one with this problem. thanks again for helping me out! I'll update the thread some time later and confirm if i never get a bsod again
      My Computer


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

    What you have said is very true. Recently we are seeing this issue too repetitively. AMD used to code brilliant drivers and 13.9 WHQL is one of those.
      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 09:14.
Find Us