BSOD Stop Error 0x00000116

Page 1 of 2 12 LastLast

  1. Posts : 9
    Windows 7 Home Premium 64bit SP1
       #1

    BSOD Stop Error 0x00000116


    Hi, Im new to this forum and this whole bsod thing so dont judge me if I post something bad
    About the problem.I started getting Stop Error 0x00000116 about a month ago.I tried fixing it myself I did fix it for about a week using this method:
    Step 1: Download and install the latest ati graphic driver.

    Step 2: Then go to C:\Windows\System32\Drivers and rename atikmdag.sys to atikmdag.sys.old.

    Step 3: Go to ati directory (usually in C:\ATI) and find the file atikmdag.sy_.

    Step 4: Copy the file to your Desktop directory.

    Step 5: Open cmd.exe by going to Start -> type cmd in the search box and hit enter.

    Step 6: Change the directory to Desktop by typing chdir Desktop.

    Step 7: Then, type EXPAND.EXE atikmdag.sy_ atikmdag.sys. Or,
    expand -r atikmdag.sy_ atikmdag.sys

    Step 8: When the expansion is complete, copy the new atikmdag.sys from your Desktop to C:\Windows\System32\Drivers

    Step 9: Restart your computer and the problem should be resolved.

    After it stoped working for me I tried this and it also helped for some time:
    Open regedit then -
    Navigate to -
    H_KEY_LOCAL_MACHINE \ System \ CurrentControlSet \ Control \ Graphics Drivers.
    Right click on the open field and click on New / DWORD (32bit) Value,
    Then name it: TdrDelay -> double click it -> Set the value to 8.

    Usually this error occurs on startup.Im writing this from safe mode.I think drivers are bad or video card needs replacement.If I delete drivers laptop works in normal mode to.I tried uninstalling/installing new drivers but it doesnt seem to help.More info in the attachment.Hope I did it alright
      My Computer


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

    Welcome.

    Did you go through this thread? STOP 0x116: VIDEO_TDR_ERROR troubleshooting

    Code:
    Microsoft (R) Windows Debugger Version 6.3.9600.16384 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\YUSRA\Downloads\NAMAI-KOMPUTER-01_01_2015_191206_80\010115-28314-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    
    ************* Symbol Path validation summary **************
    Response                         Time (ms)     Location
    Deferred                                       SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
    Machine Name:
    Kernel base = 0xfffff800`03463000 PsLoadedModuleList = 0xfffff800`036a6890
    Debug session time: Thu Jan  1 20:48:22.581 2015 (UTC + 6:00)
    System Uptime: 0 days 0:02:06.829
    Loading Kernel Symbols
    .
    
    Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
    Run !sym noisy before .reload to track down problems loading symbols.
    
    ..............................................................
    ................................................................
    ..............
    Loading User Symbols
    Loading unloaded module list
    ...
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 116, {fffffa800897f010, fffff8800466a848, 0, 2}
    
    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+b848 )
    
    Followup: MachineOwner
    ---------
    
    2: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    VIDEO_TDR_FAILURE (116)
    Attempt to reset the display driver and recover from timeout failed.
    Arguments:
    Arg1: fffffa800897f010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff8800466a848, The pointer into responsible device driver module (e.g. owner tag).
    Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
    Arg4: 0000000000000002, Optional internal context dependent data.
    
    Debugging Details:
    ------------------
    
    
    FAULTING_IP: 
    atikmpag+b848
    fffff880`0466a848 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) x86fre
    
    STACK_TEXT:  
    fffff880`03f8d9c8 fffff880`104f1134 : 00000000`00000116 fffffa80`0897f010 fffff880`0466a848 00000000`00000000 : nt!KeBugCheckEx
    fffff880`03f8d9d0 fffff880`104f0e3e : fffff880`0466a848 fffffa80`0897f010 fffffa80`0810bc00 fffffa80`084f9010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
    fffff880`03f8da10 fffff880`10598f13 : fffffa80`0897f010 00000000`00000000 fffffa80`0810bc00 fffffa80`084f9010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
    fffff880`03f8da40 fffff880`105c2cf1 : 00000000`ffffffff 00000000`00001da7 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
    fffff880`03f8db20 fffff880`105c1437 : 00000000`00000102 00000000`00000001 00000000`00001da7 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
    fffff880`03f8db50 fffff880`105942d2 : ffffffff`fd9da600 fffffa80`084f9010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
    fffff880`03f8dbf0 fffff880`105c0ff6 : 00000000`00000000 00000000`0000000f 00000000`00000080 fffffa80`080a8498 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
    fffff880`03f8dd00 fffff800`0377473a : 00000000`10021876 fffffa80`082e0b50 fffffa80`03b4e040 fffffa80`082e0b50 : dxgmms1!VidSchiWorkerThread+0xba
    fffff880`03f8dd40 fffff800`034c98e6 : fffff880`031d3180 fffffa80`082e0b50 fffff880`031ddfc0 fffff880`03f8de40 : nt!PspSystemThreadStartup+0x5a
    fffff880`03f8dd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
    
    
    STACK_COMMAND:  .bugcheck ; kb
    
    FOLLOWUP_IP: 
    atikmpag+b848
    fffff880`0466a848 4883ec28        sub     rsp,28h
    
    SYMBOL_NAME:  atikmpag+b848
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: atikmpag
    
    IMAGE_NAME:  atikmpag.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  546e9eb6
    
    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
    ---------
    
    2: kd> lmvm atikmpag
    start             end                 module name
    fffff880`0465f000 fffff880`046f5000   atikmpag T (no symbols)           
        Loaded symbol image file: atikmpag.sys
        Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
        Image name: atikmpag.sys
        Timestamp:        Fri Nov 21 08:08:54 2014 (546E9EB6)
        CheckSum:         00093077
        ImageSize:        00096000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
      My Computer


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

    I did read that thread.FurMark doesnt work for me.As I understand for it to work you need AMD drivers installed but if I install then laptop only works in safe mode.And in safe mode FurMark doesnt work either.At the moment I dont have any drivers installed so laptop work normally but I cant play games and resolution is quite low.I am going to try disassemble my laptop, clean it from dust completely and change thermal grease.I seen that in most cases this helps.Also I think that I will rum memtest and HD Diagnostic.
      My Computer


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

    I just got the BSOD...


    I upgraded the CPU fan and case fans in my desktop and now I'm unable to load Windows 7 Home Premium 64 bit...

    The error code is:
    ***STOP: 0x00000116 (0xFFFFFA800790F010, 0xFFFFF880048496A0, 0x0000000000000000, 0x0000000000000002)

    *** atikmdag.sys - Address FFFFF880048496A0 base at FFFFF88004837000, DateStamp 4abaa755

    I'm checking to see if there is an updated driver I need to download for my video card. Just wondering if there was anything else going on.

    Attached is the dump file I got when I used the SF Diagnostic Tool.

    Any help you can give is very much appreciated.
      My Computer


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

    I cleaned my laptop from dust and applied new thermal grease but it didn't fix the problem.It seems my computer can only work in safe mode or without drivers :/

    Added latest crash dump file.
      My Computer


  6. Posts : 9
    Windows 7 Home Premium 64bit SP1
    Thread Starter
       #6

    I ran MemTest for 8 passes(9 hours) but it didnt find any errors.Also I ran HD Diagnostic and it also didnt find any errors.I dont know what to do now, I just ran out of ideas :/

    Latest crash dump.
      My Computer


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

    Hi residentltu.

    It is a stop 0x116, which is a display related BSOD.

    A few models of Inspiron N5010 having AMD Mobility Radeon HD 5000 Series as the integrated graphics. Is it the case for your computer?

    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 .

    Stress test the Graphics Card using Furmark. Take a screenshot of the furmark window before closing it. Upload the screenshot for us.

    Also, the latest AMD Omega driver (that you have installed) is not properly functioning and causing BSODs in a number of systems that I have noticed. You may try to roll it back to a driver that worked better previously. Try Device Manager - Roll Back Driver

    Let us know the results.
      My Computer


  8. Posts : 9
    Windows 7 Home Premium 64bit SP1
    Thread Starter
       #8

    You are completely right about my computer model and graphics.

    I replaced thermal grease and cleaned inside of laptop few days ago.So computer isnt hot.Even when running memtest for 9 hours straight temperature was about 68 degrees celsius.

    I tries many times to test graphics card with FurMark but it doesnt work.

    About that roll back.Currently I have deleted Omega drivers because with them I cant even access normal mode.I tried many difrent drivers even very old ones from Dell support but it still crashes on windows boot.

    EDIT
    About the screenshot with temperatures.Computer was running for 6 hours when screenshot was taken.
      My Computer


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

    Try an old driver as per my suggestion?

    Uninstall your installed latest version of the display driver.


    Then clean up any possible leftover.


    Then install version 13.9 WHQL only.

    Let us know how it goes. I will feel comfortable to say about this situation after seeing how it goes, because i'm not feeling comfortable to blame the hardware right now.
      My Computer


  10. Posts : 9
    Windows 7 Home Premium 64bit SP1
    Thread Starter
       #10

    I did all steps and installed those drivers and it didnt crashed but it looks like everything is same like before installing drivers.At least for me.
      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 15:11.
Find Us