BSOD Code:0x00000116


  1. Posts : 3
    Windows 7 Home Premium 64bit
       #1

    Random BSOD While playing games Code:0x00000116


    Windows Version: Microsoft Windows 7 Home Premium Edition (build 7600), 64-bit

    Processor: Intel(R) Pentium(R) CPU G2120 @ 3.10GHz

    Graphics Card: AMD Radeon HD 7700 Series

    Total RAM: 4.0 GB
    You could say my PC is new (1 yr old) and i started having this problem about 4-5 months ago. Since i was using a 32bit OS at the time i thought that was the problem so i installed a 64bit Windows but the problem still was present. For some games it occurs more frequent than others and for some it doesn't occur at all. I searched around the web for answers but nothing worked - updating graphic drivers , windows...

    Thank you in advance
      My Computer


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

    Hi redrac.

    A stop 0x116 is a Display/graphics related issue.

    Uninstall your installed latest version of the display driver.


    Then clean up any possible leftover.


    Then install version 13.9 WHQL only.


    Lately we have seen a lot of issues with the latest 13.12 WHQL AMD Catalyst.

    Also, Stress test the Graphics Card using Furmark.
    Video Card - Stress Test with Furmark

    Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
    eXtreme Power Supply Calculator
    Let us know the wattage of the PSU too.

    Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy. Alternatively, you can publish a Speccy snapshot too: Speccy - Publish Snapshot of your System Specs .

    Let us know the results.
    _________________________________________________________________________________________
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 116, {fffffa8006a324e0, fffff88006c9dd88, 0, d}
    
    Unable to load image \SystemRoot\system32\DRIVERS\atikmpag.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for atikmpag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
    Probably caused by : atikmpag.sys ( atikmpag+bd88 )
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    VIDEO_TDR_FAILURE (116)
    Attempt to reset the display driver and recover from timeout failed.
    Arguments:
    Arg1: fffffa8006a324e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff88006c9dd88, The pointer into responsible device driver module (e.g. owner tag).
    Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
    Arg4: 000000000000000d, Optional internal context dependent data.
    
    Debugging Details:
    ------------------
    
    
    FAULTING_IP: 
    atikmpag+bd88
    fffff880`06c9dd88 4883ec28        sub     rsp,28h
    
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
    
    CUSTOMER_CRASH_COUNT:  1
    
    BUGCHECK_STR:  0x116
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
    
    STACK_TEXT:  
    fffff880`07beb988 fffff880`06f1b000 : 00000000`00000116 fffffa80`06a324e0 fffff880`06c9dd88 00000000`00000000 : nt!KeBugCheckEx
    fffff880`07beb990 fffff880`06f1ad87 : fffff880`06c9dd88 fffffa80`06a324e0 fffffa80`042bdd50 fffffa80`036a5410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
    fffff880`07beb9d0 fffff880`06fc1f07 : fffffa80`06a324e0 00000000`00000000 fffffa80`042bdd50 fffffa80`036a5410 : dxgkrnl!TdrIsRecoveryRequired+0x21f
    fffff880`07beba00 fffff880`06febb75 : 00000000`ffffffff 00000000`00183ad4 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
    fffff880`07bebae0 fffff880`06fea2bb : 00000000`00000102 00000000`00000000 00000000`00183ad4 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
    fffff880`07bebb10 fffff880`06fbd2c6 : ffffffff`ff676980 fffffa80`036a5410 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
    fffff880`07bebbb0 fffff880`06fe9e7a : 00000000`00000000 fffffa80`05130950 00000000`00000080 fffffa80`036a5410 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
    fffff880`07bebcc0 fffff800`0315f47a : 00000000`fffffc32 fffffa80`050e38c0 fffffa80`0369bb30 fffffa80`050e38c0 : dxgmms1!VidSchiWorkerThread+0xba
    fffff880`07bebd00 fffff800`02e9eda6 : fffff800`0303ae80 fffffa80`050e38c0 fffff800`03048c40 75654173`69366d37 : nt!PspSystemThreadStartup+0x5a
    fffff880`07bebd40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
    
    
    STACK_COMMAND:  .bugcheck ; kb
    
    FOLLOWUP_IP: 
    atikmpag+bd88
    fffff880`06c9dd88 4883ec28        sub     rsp,28h
    
    SYMBOL_NAME:  atikmpag+bd88
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: atikmpag
    
    IMAGE_NAME:  atikmpag.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  52a231d9
    
    FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys
    
    BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:x64_0x116_image_atikmpag.sys
    
    FAILURE_ID_HASH:  {83e844bc-fe68-2042-4230-7f5d3e90b48a}
    
    Followup: MachineOwner
    ---------
    
    0: kd> lmvm atikmpag
    start             end                 module name
    fffff880`06c92000 fffff880`06d32000   atikmpag T (no symbols)           
        Loaded symbol image file: atikmpag.sys
        Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
        Image name: atikmpag.sys
        Timestamp:        Sat Dec 07 01:51:45 2013 (52A231D9)
        CheckSum:         0009FEFF
        ImageSize:        000A0000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
      My Computer


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

    Wasn't sure about how long should i let the Fulmark test go on so i stoped it when the temperature was at a standstill

    About the wattage - 279W and my PSU can support up to 400W


    Also i am about to test if the BSOD is gone
    EDIT: It didnt work, same error
    Last edited by redrac; 08 Feb 2014 at 18:27.
      My Computer


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

    You need to change the GPU as per the Furmark screenshot; which is totlly a mess. And you also need to get a bigger PSU, of at least 600 watts.
      My Computer


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

    I don't understand. I get that i need to get a more powerful PSU but change the GPU? Is it defected or insufficient for the system i have ? Could therе be dust involved as in i need to open my PC and clean it (i haven't opened it yet since i bought it because my warranty will no longer be valid)
    Last edited by redrac; 03 Feb 2014 at 18:45.
      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 17:56.
Find Us