BSOD: Suddenly occurs after 4 years out of the Blue


  1. Posts : 2
    Windows7 64bit
       #1

    BSOD: Suddenly occurs after 4 years out of the Blue


    Hi there,

    my Computer is almost 4 years old, and I never had any problems. I didn't update any drivers recently or installed any new software.

    For the last couple of days I get some BSOD randomly. Mostly while watching/listening something on YouTube.

    I have attached the Dump Files to this post.

    Thank for you any help.
      My Computer


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

    Dont use a BETA display driver.

    Uninstall the installed display driver using DDU. Then install the CCC 14.4 WHQL only.

    Let us know for any further BSOD after doing it.

    When done, stress test the Graphics Card using Furmark.Take a screenshot of the furmark window before closing it. Upload the screenshot for us. Also let us know if you have experienced any crash/BSOD and/or artifacts during the test.
    ______________________________________________
    Code:
    BugCheck 100000EA, {fffffa8008377060, 0, 0, 0}
    
    *** WARNING: Unable to verify timestamp for atikmdag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
    Probably caused by : dxgkrnl.sys ( dxgkrnl!TdrTimedOperationBugcheckOnTimeout+37 )
    
    Followup: MachineOwner
    ---------
    
    2: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    THREAD_STUCK_IN_DEVICE_DRIVER_M (100000ea)
    The device driver is spinning in an infinite loop, most likely waiting for
    hardware to become idle. This usually indicates problem with the hardware
    itself or with the device driver programming the hardware incorrectly.
    If the kernel debugger is connected and running when watchdog detects a
    timeout condition then DbgBreakPoint() will be called instead of KeBugCheckEx()
    and detailed message including bugcheck arguments will be printed to the
    debugger. This way we can identify an offending thread, set breakpoints in it,
    and hit go to return to the spinning code to debug it further. Because
    KeBugCheckEx() is not called the .bugcheck directive will not return bugcheck
    information in this case. The arguments are already printed out to the kernel
    debugger. You can also retrieve them from a global variable via
    "dd watchdog!g_WdBugCheckData l5" (use dq on NT64).
    On MP machines it is possible to hit a timeout when the spinning thread is
    interrupted by hardware interrupt and ISR or DPC routine is running at the time
    of the bugcheck (this is because the timeout's work item can be delivered and
    handled on the second CPU and the same time). If this is the case you will have
    to look deeper at the offending thread's stack (e.g. using dds) to determine
    spinning code which caused the timeout to occur.
    Arguments:
    Arg1: fffffa8008377060, Pointer to a stuck thread object.  Do .thread then kb on it to find
        the hung location.
    Arg2: 0000000000000000, Pointer to a DEFERRED_WATCHDOG object.
    Arg3: 0000000000000000, Pointer to offending driver name.
    Arg4: 0000000000000000, Number of times "intercepted" bugcheck 0xEA was hit (see notes).
    
    Debugging Details:
    ------------------
    
    
    FAULTING_THREAD:  fffffa8008377060
    
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_FAULT
    
    CUSTOMER_CRASH_COUNT:  1
    
    BUGCHECK_STR:  0xEA
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre
    
    LAST_CONTROL_TRANSFER:  from fffff880048f9f63 to fffff800032d5bc0
    
    STACK_TEXT:  
    fffff880`059f8598 fffff880`048f9f63 : 00000000`000000ea fffffa80`08377060 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
    fffff880`059f85a0 fffff880`048fa112 : fffff880`059f8678 fffff880`13125698 fffff880`059f8678 00000000`00000246 : dxgkrnl!TdrTimedOperationBugcheckOnTimeout+0x37
    fffff880`059f8610 fffff880`13135bcf : fffffa80`0760d000 00000000`00000000 fffffa80`0760d000 fffff880`13125670 : dxgkrnl!TdrTimedOperationDelay+0xbe
    fffff880`059f8650 fffffa80`0760d000 : 00000000`00000000 fffffa80`0760d000 fffff880`13125670 00000000`01c9c380 : atikmdag+0x41bcf
    fffff880`059f8658 00000000`00000000 : fffffa80`0760d000 fffff880`13125670 00000000`01c9c380 fffff880`13120028 : 0xfffffa80`0760d000
    
    
    STACK_COMMAND:  .thread 0xfffffa8008377060 ; kb
    
    FOLLOWUP_IP: 
    dxgkrnl!TdrTimedOperationBugcheckOnTimeout+37
    fffff880`048f9f63 cc              int     3
    
    SYMBOL_STACK_INDEX:  1
    
    SYMBOL_NAME:  dxgkrnl!TdrTimedOperationBugcheckOnTimeout+37
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: dxgkrnl
    
    IMAGE_NAME:  dxgkrnl.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  539e411c
    
    IMAGE_VERSION:  6.1.7601.18510
    
    FAILURE_BUCKET_ID:  X64_0xEA_IMAGE_dxgkrnl.sys
    
    BUCKET_ID:  X64_0xEA_IMAGE_dxgkrnl.sys
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:x64_0xea_image_dxgkrnl.sys
    
    FAILURE_ID_HASH:  {b58a0dfd-90f3-63cd-1b07-7ce1b53744cb}
    
    Followup: MachineOwner
    ---------
    
    2: kd> lmvm atikmpag
    start             end                 module name
    fffff880`0485d000 fffff880`048f3000   atikmpag   (deferred)             
        Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
        Image name: atikmpag.sys
        Timestamp:        Fri Nov 21 07:38:54 2014 (546E9EB6)
        CheckSum:         00093077
        ImageSize:        00096000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
      My Computer


  3. Posts : 2
    Windows7 64bit
    Thread Starter
       #3

    Thank you!

    I've used the program you provided here to uninstall the AMD drivers and reinstalled the WHQL drivers and everything seems to be running smooth for hours now without any problems.

    I also ran a Furmark test for 15mins with no artifacts, the GPU temperature never went above 68% so I canceled the test early because I needed the computer.

    I'll let you guys know if anything strange occurs again.

    Thanks again! Great forum ...
      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 03:39.
Find Us