BSOD when playing games after getting new monitor

Page 1 of 2 12 LastLast

  1. Posts : 8
    Windows 7 Ultimate x64
       #1

    BSOD when playing games after getting new monitor


    So 2 days ago I got a new monitor and since then I've been having BSODs when playing games for about 20 minutes, at first the game will crash and then when I open it again after about 1 minute I will get a BSOD saying "Attempt to reset display driver and recover from time out failed".
      My Computer


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

    Hi SpongeSquid.

    The monitor is just an output device. It has nothing to do with a stop 0x116 BSOD.

    You Uninstall your installed latest version of the display driver.


    Then clean up any possible leftover.


    Then install any other version of the display driver which either 13.12 WHQL or higher (because your GPU will not support a driver below that one).

    When the driver is applied, 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
    Also let us know the wattage of the PSU.

    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 .

    Are you overclocking?
    As you are getting BSODs, you should stop overclocking and run all the hardware components like CPU, GPU and RAM to their default settings.

    And, the most important thing is, install Service pack 1 and all other windows updates. Otherwise the system will remain vulnerable to threats.
    Code:
    Windows 7 Kernel Version 7600 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Learn how to install Windows 7 Service Pack 1 (SP1)
    Service Pack and Update Center - Microsoft Windows

    Let us know the results.
    ___________________________
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 116, {fffffa8009210110, fffff8800800bdac, 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+bdac )
    
    Followup: MachineOwner
    ---------
    
    3: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    VIDEO_TDR_FAILURE (116)
    Attempt to reset the display driver and recover from timeout failed.
    Arguments:
    Arg1: fffffa8009210110, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff8800800bdac, 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+bdac
    fffff880`0800bdac 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`03a47a18 fffff880`06d32cbc : 00000000`00000116 fffffa80`09210110 fffff880`0800bdac 00000000`00000000 : nt!KeBugCheckEx
    fffff880`03a47a20 fffff880`06d329c6 : fffff880`0800bdac fffffa80`09210110 fffffa80`0ed94780 fffffa80`0c6ee410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
    fffff880`03a47a60 fffff880`06c0ff07 : fffffa80`09210110 00000000`00000000 fffffa80`0ed94780 fffffa80`0c6ee410 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
    fffff880`03a47a90 fffff880`06c3dd7e : fffffa80`ffffffff 00000000`0018a760 fffff880`03a47bf0 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
    fffff880`03a47b70 fffff880`06c0b29e : fffffa80`0c6ee410 ffffffff`feced300 fffffa80`0ed94780 00000000`00000000 : dxgmms1!VidSchWaitForCompletionEvent+0x196
    fffff880`03a47bb0 fffff880`06c37e7a : 00000000`00000000 fffffa80`0a3b6450 00000000`00000080 fffffa80`0c6ee410 : dxgmms1!VidSchiScheduleCommandToRun+0x1b2
    fffff880`03a47cc0 fffff800`02f1b166 : fffff880`fffffc32 fffffa80`068c2760 fffffa80`066a6740 fffff800`02c6fd87 : dxgmms1!VidSchiWorkerThread+0xba
    fffff880`03a47d00 fffff800`02c56486 : fffff880`02f71180 fffffa80`068c2760 fffff880`02f7bfc0 fffff880`0123da90 : nt!PspSystemThreadStartup+0x5a
    fffff880`03a47d40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
    
    
    STACK_COMMAND:  .bugcheck ; kb
    
    FOLLOWUP_IP: 
    atikmpag+bdac
    fffff880`0800bdac 4883ec28        sub     rsp,28h
    
    SYMBOL_NAME:  atikmpag+bdac
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: atikmpag
    
    IMAGE_NAME:  atikmpag.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  53507abb
    
    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
    ---------
    
    3: kd> lmvm atikmpag
    start             end                 module name
    fffff880`08000000 fffff880`080a3000   atikmpag T (no symbols)           
        Loaded symbol image file: atikmpag.sys
        Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
        Image name: atikmpag.sys
        Timestamp:        Fri Apr 18 06:37:07 2014 (53507ABB)
        CheckSum:         000A6939
        ImageSize:        000A3000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
      My Computer


  3. Posts : 8
    Windows 7 Ultimate x64
    Thread Starter
       #3

    Thanks, I managed to fix it. I uninstalled my current drivers, used that driver sweeper thing and installed the beta drivers and now it works fine, played for about 2 hours with no bluescreen.
      My Computer


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

    Good news. :)

    Now observe the situation for some more days and let us know how it is running.
      My Computer


  5. Posts : 8
    Windows 7 Ultimate x64
    Thread Starter
       #5

    So, today I fired up euro truck simulator 2 like i do every morning, played for about 3 hours without a problem. Had a 2 hour break, decided to play the game again, 10 minutes in the game crashes - I thought it was because I had installed a mod and I was just having problems with that, but no. I open up the game again and... the same bluescreen. My GPU couldn't have overheated, it was at about 38C at the time of the crash.
      My Computer


  6. Posts : 8
    Windows 7 Ultimate x64
    Thread Starter
       #6

    I think this might actually be a problem with the game itself, it hasn't happened in any other game so far. Sometimes I can play for as long as I want but sometimes it will just bluescreen. I don't know why it would suddenly start happening, I haven't downloaded any updates for anything or the game.
      My Computer


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

    In that situation you need to contract the game developer. They must have custom settings or patches that will work for your system.
      My Computer


  8. Posts : 8
    Windows 7 Ultimate x64
    Thread Starter
       #8

    Well I got the BSOD again but it happened in a different game. It's gotten really bad now and I can't play anything without it crashing.
      My Computer


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

    SpongeSquid said:
    Well I got the BSOD again but it happened in a different game. It's gotten really bad now and I can't play anything without it crashing.
    Now follow the other things of post #2.
      My Computer


  10. Posts : 8
    Windows 7 Ultimate x64
    Thread Starter
       #10

    Okay, I tried older drivers but it didn't help so I installed the latest drivers back. I ran furmark for about 20 minutes and nothing happened, the GPU went up to about 80C. That website with the PSU calculation thing is too complicated, but my PSU is 620W and I had no problems before, it just suddenly started happening. I also installed all the windows updates (took a really long time) and it didn't help. I'm not overclocking anything.
      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 00:56.
Find Us