Bsod when playing games/videos VIDEO_TDR_ERROR

Page 1 of 2 12 LastLast

  1. Posts : 6
    windows 7 professional 32bit
       #1

    Bsod when playing games/videos VIDEO_TDR_ERROR


    Hello everyone and thank you for your time. First of all I am a bit of a newb when it comes to PC's, your patience is appreciated. I have a Lenovo notebook thinkpad 2847-6qg, and I've been experiencing BSODS for about two months now. I've checked hundreds of posts, read a lot but I came up with no solution. The game that I play is dota 2. The crash is something like: screen freezes, I can still hear sounds for 2-3 seconds, after that the screen goes black flashes a bit and the pc restarts.
    Potential useful info:
    1. Originally I had 2x2gb RAM cards, I removed one which eventually broke, so now I only have 1 x 2gb ram.(Ran memtest for 12 passes 0 fails.)
    2.My video card is an Ati mobility radeon hd 4500/5100 or 4500 or 545v depending on the driver I install.
    3.On everest I cannot acces "gpu" , PCI/AGP video (from display) as well as SPD and Chipset(from Motherboard)
    4.EVEREST: On motherboard details I get : Motherboard name: Unknown
    5.EVEREST: On computer/sensor: my only temperatures readings are:CPU 38 C,Samsung HM250JI 39 C.
    6. When I enter bios, which seems to be up to date (2012) I don't have any graphic options, on "display".
    The only thing I have is the Monitor.
    7.If I install GPU-Z it detects the GPU temperature at 42 C when in Windows, speed fan 30%, speedfan (RPM) --RPM , GPU load 0%
    8.After a bsod sometimes, not always, I get artifacts on windows loading screen, from the 1st second the restart happens until it actually loads windows.
    9.Sometimes I can play without getting bsod(rarely) 1-2-3 days. after the laptop sleeps it sometimes restarts after trying to wake up. after that blue screens occur again.
    Note: I use driver fusion + ccleaner after uninstalling a driver.
    I've been trying for the last two months to fix it but no success.(installed dozens of different drivers, cleaned the fan-I get decent
    I also run TPFanControl at level 7 all the time, so I can make sure its not a heating issue.

    I will now post the analysis from WhoCrashed:
    Crash Dump Analysis
    Crash dump directory: C:\Windows\Minidump

    Crash dumps are enabled on your computer.

    On Sat 1/26/2013 6:05:00 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\012613-18969-01.dmp
    This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x8D07B)
    Bugcheck code: 0x116 (0xFFFFFFFF85692008, 0xFFFFFFFF891D31A0, 0x0, 0x2)
    Error: VIDEO_TDR_ERROR
    file path: C:\Windows\system32\drivers\dxgkrnl.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: DirectX Graphics Kernel
    Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



    On Sat 1/26/2013 6:05:00 PM GMT your computer crashed
    crash dump file: C:\Windows\memory.dmp
    This was probably caused by the following module: dxgkrnl.sys (dxgkrnl!TdrIsTimeoutForcedFlip+0xF4)
    Bugcheck code: 0x116 (0xFFFFFFFF85692008, 0xFFFFFFFF891D31A0, 0x0, 0x2)
    Error: VIDEO_TDR_ERROR
    file path: C:\Windows\system32\drivers\dxgkrnl.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: DirectX Graphics Kernel
    Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



    On Fri 1/25/2013 11:13:08 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\012513-43305-01.dmp
    This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x8D07B)
    Bugcheck code: 0x116 (0xFFFFFFFF82D8F510, 0xFFFFFFFF8ED3B576, 0x0, 0x2)
    Error: VIDEO_TDR_ERROR
    file path: C:\Windows\system32\drivers\dxgkrnl.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: DirectX Graphics Kernel
    Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



    On Fri 1/25/2013 9:47:08 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\012513-46987-01.dmp
    This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x8D07B)
    Bugcheck code: 0x116 (0xFFFFFFFF86EFE4A8, 0xFFFFFFFF918D1C0A, 0x0, 0x2)
    Error: VIDEO_TDR_ERROR
    file path: C:\Windows\system32\drivers\dxgkrnl.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: DirectX Graphics Kernel
    Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



    On Fri 1/25/2013 7:07:22 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\012513-14898-01.dmp
    This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x8D07B)
    Bugcheck code: 0x116 (0xFFFFFFFF84D5E008, 0xFFFFFFFF9111C86E, 0x0, 0x2)
    Error: VIDEO_TDR_ERROR
    file path: C:\Windows\system32\drivers\dxgkrnl.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: DirectX Graphics Kernel
    Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



    On Fri 1/25/2013 9:05:57 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\012513-15849-01.dmp
    This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x8D07B)
    Bugcheck code: 0x116 (0xFFFFFFFF881B1510, 0xFFFFFFFF90B2E86E, 0x0, 0x2)
    Error: VIDEO_TDR_ERROR
    file path: C:\Windows\system32\drivers\dxgkrnl.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: DirectX Graphics Kernel
    Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



    On Thu 1/24/2013 11:58:16 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\012413-14664-01.dmp
    This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x8D07B)
    Bugcheck code: 0x116 (0xFFFFFFFF84AFA118, 0xFFFFFFFF9142386E, 0x0, 0x2)
    Error: VIDEO_TDR_ERROR
    file path: C:\Windows\system32\drivers\dxgkrnl.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: DirectX Graphics Kernel
    Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



    On Thu 1/24/2013 11:18:59 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\012413-15069-01.dmp
    This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x8D07B)
    Bugcheck code: 0x116 (0xFFFFFFFF84CDE008, 0xFFFFFFFF8DF1A86E, 0x0, 0x2)
    Error: VIDEO_TDR_ERROR
    file path: C:\Windows\system32\drivers\dxgkrnl.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: DirectX Graphics Kernel
    Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



    On Thu 1/24/2013 8:59:41 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\012413-14726-01.dmp
    This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x8D07B)
    Bugcheck code: 0x116 (0xFFFFFFFF87A7D510, 0xFFFFFFFF9133686E, 0x0, 0x2)
    Error: VIDEO_TDR_ERROR
    file path: C:\Windows\system32\drivers\dxgkrnl.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: DirectX Graphics Kernel
    Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



    On Thu 1/24/2013 8:40:28 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\012413-15865-01.dmp
    This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x8D07B)
    Bugcheck code: 0x116 (0xFFFFFFFF85276008, 0xFFFFFFFF9182386E, 0x0, 0x2)
    Error: VIDEO_TDR_ERROR
    file path: C:\Windows\system32\drivers\dxgkrnl.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: DirectX Graphics Kernel
    Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



    Conclusion
    27 crash dumps have been found and analyzed. Only 15 are included in this report. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

    Please help me, and thank you very much for your potential efforts.
      My Computer


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

    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 116, {82d8f510, 8ed3b576, 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+6576 )
    
    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: 82d8f510, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: 8ed3b576, The pointer into responsible device driver module (e.g. owner tag).
    Arg3: 00000000, Optional error code (NTSTATUS) of the last failed operation.
    Arg4: 00000002, Optional internal context dependent data.
    
    Debugging Details:
    ------------------
    
    
    FAULTING_IP: 
    atikmpag+6576
    8ed3b576 8bff            mov     edi,edi
    
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
    
    CUSTOMER_CRASH_COUNT:  1
    
    BUGCHECK_STR:  0x116
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    STACK_TEXT:  
    829c7b74 920ad07b 00000116 82d8f510 8ed3b576 nt!KeBugCheckEx+0x1e
    829c7b98 920a1937 8ed3b576 00000000 00000002 dxgkrnl!TdrBugcheckOnTimeout+0x8d
    829c7bbc 920dd92c 00000000 00000102 82c57788 dxgkrnl!TdrIsRecoveryRequired+0xb8
    829c7c34 92107944 fffffcfb 00009783 00000000 dxgmms1!VidSchiReportHwHang+0x3c0
    829c7c5c 92108065 00000000 00000000 00000000 dxgmms1!VidSchiCheckHwProgress+0x68
    829c7c98 920e48f0 829c7c90 88c856f8 88c8b5c0 dxgmms1!VidSchiWaitForSchedulerEvents+0x1b1
    829c7d28 921093c9 82c57788 8308cbb9 82c57788 dxgmms1!VidSchiScheduleCommandToRun+0xaa
    829c7d3c 92109485 82c57788 00000000 88c94538 dxgmms1!VidSchiRun_PriorityTable+0xf
    829c7d50 8326007a 82c57788 a2db0297 00000000 dxgmms1!VidSchiWorkerThread+0x7f
    829c7d90 83106819 92109406 82c57788 00000000 nt!PspSystemThreadStartup+0x9e
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
    
    
    STACK_COMMAND:  .bugcheck ; kb
    
    FOLLOWUP_IP: 
    atikmpag+6576
    8ed3b576 8bff            mov     edi,edi
    
    SYMBOL_NAME:  atikmpag+6576
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: atikmpag
    
    IMAGE_NAME:  atikmpag.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4f3b14a0
    
    FAILURE_BUCKET_ID:  0x116_IMAGE_atikmpag.sys
    
    BUCKET_ID:  0x116_IMAGE_atikmpag.sys
    
    Followup: MachineOwner
    ---------
    
    0: kd> lmvm atikmpag
    start    end        module name
    8ed35000 8ed7a000   atikmpag T (no symbols)           
        Loaded symbol image file: atikmpag.sys
        Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
        Image name: atikmpag.sys
        Timestamp:        Wed Feb 15 07:42:48 2012 (4F3B14A0)
        CheckSum:         00044CB7
        ImageSize:        00045000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Stop 0x116 is a display related error. And, your display driver is kinda old. Update your ATI/AMD display driver.
    You can get it from the link in our forum, Latest AMD Catalyst Video Driver for Windows 7, or you may go to AMD Graphics Driver and Software and opt for Automatically Detect and Install the appropriate driver for your card.


    During installation, you may opt for advanced installation, and install the display driver only, not the Catalyst Control Center.

    If problems persist, follow STOP 0x116: VIDEO_TDR_ERROR troubleshooting
      My Computer


  3. Posts : 6
    windows 7 professional 32bit
    Thread Starter
       #3

    I already did that about 5 times already...The reason why you see it as old is because I just uninstalled it to try something different or whatever you suggest. Also, what can you tell me about the "misssing" gpu page on everest/temperature. ? Also the bios's lack of graphic options ? Thank you.
    I've read the link you posted. I did a test with atitool to see if any artifacts show up when gpu is stressed: nothing. It worked fine.
      My Computer


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

    As suggested by NoelDP:

    Post a report following the Windows Update Posting Instructions.
      My Computer


  5. Posts : 6
    windows 7 professional 32bit
    Thread Starter
       #5

    Update:
    I have installed

    System Update Readiness Tool for Windows 7 (KB947821), it installed successfully.
    After that I had two new windows updates ready which I tried to install but failed:
    One was a driver update for ati mobility radeon hd 4500 and the other was a security update:
    Code 800B0100
    Code 80070103
      My Computer


  6. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #6

    We need the data from the log to be able to help- the tool often only points out failures.
      My Computer


  7. Posts : 6
    windows 7 professional 32bit
    Thread Starter
       #7

    Update:
    I ran the sfc scannow in cmd, no integrity errors shown.
    I'm attaching the CBS folder
      My Computer


  8. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #8

    Your problems with Windows Update originate from these errors....
    Code:
     Line 8699: 2013-01-27 17:00:02, Error                 CBS    Failed to verify if mum file \\?\C:\Windows\SoftwareDistribution\Download\35886d0ea6a9e82821dd05aad9d81833\update.mum is vouched for by catalog \\?\C:\Windows\SoftwareDistribution\Download\35886d0ea6a9e82821dd05aad9d81833\update.cat. [HRESULT = 0x800b0100 - TRUST_E_NOSIGNATURE]
     Line 8701: 2013-01-27 17:00:02, Error                 CBS    Failed to create internal package [HRESULT = 0x800b0100 - TRUST_E_NOSIGNATURE]
    You'll need to clear the SoftwareDistribution folder - but if you're willing to do a test or two, I'd like to try doing it selectively, rather that the more usual wholesale deletion.

    If you're OK with that, please follow these instructions.

    Open an Elevated Command Prompt, and run the following commands..

    NET STOP WUAUSERV
    DIR C:\Windows\SoftwareDistribution\Download /S >>"%userprofile%"\desktop\npsdfiles.log
    NET START WUAUSERV

    That will create a file npsdfiles.log on your desktop - please attach that to a reply.
    Then I'll see what I can do about a repair, rather than a deletion.
      My Computer


  9. Posts : 6
    windows 7 professional 32bit
    Thread Starter
       #9

    Thank you Noel for your help so far. I did what you instructed me.I dont know what an Elevated Command Prompt is but I ran Command Prompt as administrator. here is the file.
    Once again, thank you.
      My Computer


  10. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #10

    Interesting - the referenced folder doesn't exist in the SoftwareDistribution folder.

    In that case, there's not a lot I can do except recommend the usual solution of renaming the folder

    Please open an Elevated (Admin) Command Prompt, and run the following commands.

    NET STOP WUAUSERV
    REN C:\WINDOWS\SOFTWAREDISTRIBUTION SDOLD
    NET START WUAUSERV

    Then WAIT 15 minutes. before rebooting and waiting a further 15 minutes.
    Then run another SFC /SCANNOW and post the new CBS.log
      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 03:20.
Find Us