Windows 8 and 8.1 Forums


BSOD - Computer freezes with black screen

  1. #1


    Posts : 9
    Windows 8.1

    BSOD - Computer freezes with black screen


    Hi guys,

    I have a PC with a AMD 7790 graphics card. The system competely freezes, the music or games stops and the mouse and keyboard are stuck. You have to hard reset the PC to fix it. Mostly after crashing, there is no BSOD dump or something so it's not easy to fit it. I installed all the newest drivers and updated all software.

    Specs:
    - AMD FX-6300
    - ASRock 970 Pro3 R2.0
    - ASUS HD7790-DC2OC-1GD5
    - Be quiet! Pure Power L8 430W CM
    - Kingston ValueRam 8 GB DDR3-1600 CL11
    - Seagate Barracuda 7200.14 1 TB
    - Windows 7 Ultimate x64

    You can find the BSOD report here:
    https://onedrive.live.com/?cid=868f9...D5I3JXmOIC9z6M

    What I did:
    - Updated all drivers
    - Updated all software
    - Did a Memtest
    - Did a chkdsk
    - ...

    At the beginning, the problems where a lot worser. The AMD OverDrive software overclocked the card automatically which was crashing the PC. With the new driver, it looks like that problem is fixed. The PC crashed after 15 minutes playing or something. I also uninstalled AMD Fuel. The PC now crashes after 2/3 hours of playing iRacing or listening to music, so it's a big improvement.

    I think it's the graphics card. What do you think?

    Regards,

    WindowsPro

      My System SpecsSystem Spec

  2. #2


    Posts : 660
    windows 8.1


    The dumpfile is a BugCheck 117 Probably caused by : atikmpag.sys with VIDEO_TDR_TIMEOUT_DETECTED (117)
    The display driver failed to respond in timely fashion.

    This is related to your graphic Card.

    Possible reasons are overclocking, overheating, driverversion sometimes going back to earlier versions helps, changing the TDR, faulty hardware.
    Troubleshooting steps for this kind of error are located here: Video TDR Timeout - 0x116 + 0x117 - Sysnative Forums.
    Also this windows KB can help you "Display driver stopped responding and has recovered" error in Windows 7 or Windows Vista .



    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    Use !analyze -v to get detailed debugging information.
    BugCheck 117, {fffffa800761c4e0, fffff8800480ae80, 0, 0}
    Unable to load image 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+ae80 )
    Followup: MachineOwner
    ---------
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    VIDEO_TDR_TIMEOUT_DETECTED (117)
    The display driver failed to respond in timely fashion.
    (This code can never be used for a real bugcheck.)
    Arguments:
    Arg1: fffffa800761c4e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff8800480ae80, The pointer into responsible device driver module (e.g owner tag).
    Arg3: 0000000000000000, The secondary driver specific bucketing key.
    Arg4: 0000000000000000, Optional internal context dependent data.
    Debugging Details:
    ------------------
    
    FAULTING_IP: 
    atikmpag+ae80
    fffff880`0480ae80 ??              ???
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_TIMEOUT
    TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b
    
    CUSTOMER_CRASH_COUNT:  1
    BUGCHECK_STR:  0x117
    PROCESS_NAME:  System
    CURRENT_IRQL:  0
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
    STACK_TEXT:  
    fffff880`064b1050 fffff880`02d30737 : fffffa80`0761c4e0 00000000`00000024 fffffa80`098dfd50 fffff880`02d303d8 : watchdog!WdDbgReportRecreate+0xa3
    fffff880`064b1570 fffff880`02d30b6e : 00000000`00001000 fffff8a0`035af7a0 00000000`00000008 00000000`00004000 : dxgkrnl!TdrUpdateDbgReport+0xcb
    fffff880`064b15c0 fffff880`02d31e22 : fffffa80`0761c4e0 fffffa80`0761c4e0 fffffa80`098dfd50 fffffa80`094f2410 : dxgkrnl!TdrCollectDbgInfoStage1+0x2e6
    fffff880`064b1660 fffff880`02c0ff13 : fffffa80`0761c4e0 00000000`00000000 fffffa80`098dfd50 fffffa80`094f2410 : dxgkrnl!TdrIsRecoveryRequired+0x17a
    fffff880`064b1690 fffff880`02c3ded6 : fffff8a0`ffffffff 00000000`000219ad fffff880`064b17f0 fffffa80`094f2410 : dxgmms1!VidSchiReportHwHang+0x40b
    fffff880`064b1770 fffff880`02c39e21 : fffffa80`095e3000 ffffffff`feced300 fffffa80`0999d010 fffff880`111e8eb1 : dxgmms1!VidSchWaitForCompletionEvent+0x196
    fffff880`064b17b0 fffff880`02c39fd9 : fffffa80`095e3000 fffffa80`094f2410 000000ff`02440000 fffff880`05b50000 : dxgmms1!VidSchiWaitForCompletePreemption+0x7d
    fffff880`064b18a0 fffff880`02c38eb8 : 00000000`00000040 00000000`00007c0a fffffa80`0999d010 fffffa80`094f2410 : dxgmms1!VidSchiSendToExecutionQueueWithWait+0x171
    fffff880`064b19a0 fffff880`02c38514 : fffff880`0308df00 fffff880`02c37f00 fffffa80`00000000 fffffa80`00000120 : dxgmms1!VidSchiSubmitRenderCommand+0x920
    fffff880`064b1b90 fffff880`02c38012 : 00000000`00000000 fffffa80`098dfd50 00000000`00000080 fffffa80`094f2410 : dxgmms1!VidSchiSubmitQueueCommand+0x50
    fffff880`064b1bc0 fffff800`0316c2ea : 00000000`034521ce fffffa80`091d9a00 fffffa80`06cde6f0 fffffa80`091d9a00 : dxgmms1!VidSchiWorkerThread+0xd6
    fffff880`064b1c00 fffff800`02ec08e6 : fffff880`03089180 fffffa80`091d9a00 fffff880`03094040 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
    fffff880`064b1c40 00000000`00000000 : fffff880`064b2000 fffff880`064ac000 fffff880`064afc50 00000000`00000000 : nt!KxStartSystemThread+0x16
    
    STACK_COMMAND:  .bugcheck ; kb
    FOLLOWUP_IP: 
    atikmpag+ae80
    fffff880`0480ae80 ??              ???
    SYMBOL_NAME:  atikmpag+ae80
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: atikmpag
    IMAGE_NAME:  atikmpag.sys
    DEBUG_FLR_IMAGE_TIMESTAMP:  5253fa42
    FAILURE_BUCKET_ID:  X64_0x117_IMAGE_atikmpag.sys
    BUCKET_ID:  X64_0x117_IMAGE_atikmpag.sys
    ANALYSIS_SOURCE:  KM
    FAILURE_ID_HASH_STRING:  km:x64_0x117_image_atikmpag.sys
    FAILURE_ID_HASH:  {fa4b6286-8c4a-e9c2-c89f-5612619e000e}
    Followup: MachineOwner
    ---------
      My System SpecsSystem Spec

  3. #3


    Posts : 9
    Windows 8.1


    Quote Originally Posted by lifetec View Post
    The dumpfile is a BugCheck 117 Probably caused by : atikmpag.sys with VIDEO_TDR_TIMEOUT_DETECTED (117)
    The display driver failed to respond in timely fashion.

    This is related to your graphic Card.

    Possible reasons are overclocking, overheating, driverversion sometimes going back to earlier versions helps, changing the TDR, faulty hardware.
    Troubleshooting steps for this kind of error are located here: Video TDR Timeout - 0x116 + 0x117 - Sysnative Forums.
    Also this windows KB can help you "Display driver stopped responding and has recovered" error in Windows 7 or Windows Vista .



    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    Use !analyze -v to get detailed debugging information.
    BugCheck 117, {fffffa800761c4e0, fffff8800480ae80, 0, 0}
    Unable to load image 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+ae80 )
    Followup: MachineOwner
    ---------
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    VIDEO_TDR_TIMEOUT_DETECTED (117)
    The display driver failed to respond in timely fashion.
    (This code can never be used for a real bugcheck.)
    Arguments:
    Arg1: fffffa800761c4e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff8800480ae80, The pointer into responsible device driver module (e.g owner tag).
    Arg3: 0000000000000000, The secondary driver specific bucketing key.
    Arg4: 0000000000000000, Optional internal context dependent data.
    Debugging Details:
    ------------------
    
    FAULTING_IP: 
    atikmpag+ae80
    fffff880`0480ae80 ??              ???
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_TIMEOUT
    TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b
    
    CUSTOMER_CRASH_COUNT:  1
    BUGCHECK_STR:  0x117
    PROCESS_NAME:  System
    CURRENT_IRQL:  0
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
    STACK_TEXT:  
    fffff880`064b1050 fffff880`02d30737 : fffffa80`0761c4e0 00000000`00000024 fffffa80`098dfd50 fffff880`02d303d8 : watchdog!WdDbgReportRecreate+0xa3
    fffff880`064b1570 fffff880`02d30b6e : 00000000`00001000 fffff8a0`035af7a0 00000000`00000008 00000000`00004000 : dxgkrnl!TdrUpdateDbgReport+0xcb
    fffff880`064b15c0 fffff880`02d31e22 : fffffa80`0761c4e0 fffffa80`0761c4e0 fffffa80`098dfd50 fffffa80`094f2410 : dxgkrnl!TdrCollectDbgInfoStage1+0x2e6
    fffff880`064b1660 fffff880`02c0ff13 : fffffa80`0761c4e0 00000000`00000000 fffffa80`098dfd50 fffffa80`094f2410 : dxgkrnl!TdrIsRecoveryRequired+0x17a
    fffff880`064b1690 fffff880`02c3ded6 : fffff8a0`ffffffff 00000000`000219ad fffff880`064b17f0 fffffa80`094f2410 : dxgmms1!VidSchiReportHwHang+0x40b
    fffff880`064b1770 fffff880`02c39e21 : fffffa80`095e3000 ffffffff`feced300 fffffa80`0999d010 fffff880`111e8eb1 : dxgmms1!VidSchWaitForCompletionEvent+0x196
    fffff880`064b17b0 fffff880`02c39fd9 : fffffa80`095e3000 fffffa80`094f2410 000000ff`02440000 fffff880`05b50000 : dxgmms1!VidSchiWaitForCompletePreemption+0x7d
    fffff880`064b18a0 fffff880`02c38eb8 : 00000000`00000040 00000000`00007c0a fffffa80`0999d010 fffffa80`094f2410 : dxgmms1!VidSchiSendToExecutionQueueWithWait+0x171
    fffff880`064b19a0 fffff880`02c38514 : fffff880`0308df00 fffff880`02c37f00 fffffa80`00000000 fffffa80`00000120 : dxgmms1!VidSchiSubmitRenderCommand+0x920
    fffff880`064b1b90 fffff880`02c38012 : 00000000`00000000 fffffa80`098dfd50 00000000`00000080 fffffa80`094f2410 : dxgmms1!VidSchiSubmitQueueCommand+0x50
    fffff880`064b1bc0 fffff800`0316c2ea : 00000000`034521ce fffffa80`091d9a00 fffffa80`06cde6f0 fffffa80`091d9a00 : dxgmms1!VidSchiWorkerThread+0xd6
    fffff880`064b1c00 fffff800`02ec08e6 : fffff880`03089180 fffffa80`091d9a00 fffff880`03094040 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
    fffff880`064b1c40 00000000`00000000 : fffff880`064b2000 fffff880`064ac000 fffff880`064afc50 00000000`00000000 : nt!KxStartSystemThread+0x16
    
    STACK_COMMAND:  .bugcheck ; kb
    FOLLOWUP_IP: 
    atikmpag+ae80
    fffff880`0480ae80 ??              ???
    SYMBOL_NAME:  atikmpag+ae80
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: atikmpag
    IMAGE_NAME:  atikmpag.sys
    DEBUG_FLR_IMAGE_TIMESTAMP:  5253fa42
    FAILURE_BUCKET_ID:  X64_0x117_IMAGE_atikmpag.sys
    BUCKET_ID:  X64_0x117_IMAGE_atikmpag.sys
    ANALYSIS_SOURCE:  KM
    FAILURE_ID_HASH_STRING:  km:x64_0x117_image_atikmpag.sys
    FAILURE_ID_HASH:  {fa4b6286-8c4a-e9c2-c89f-5612619e000e}
    Followup: MachineOwner
    ---------
    Hi Lifetec,

    Thank you for your response. I will try to install the driver without all the Catalyst software. When that's still not working, I'm going to RMA the card.
      My System SpecsSystem Spec

BSOD - Computer freezes with black screen
Related Threads
Hi, I hoping that somebody can help me with the problem i have. It all started yesterday when i turned my computer on and signed in to my normal account. This then sent me to a tempory account desktop. I did some research on this and apparntly my user profile had become corrupt. I ran SFC...
how do I keep my screen from going black after only a few minutes if I don't move the mouse, windows 8.1 Dell inspiron 350, originally came with win7... TIA GaryD..
Hi guys, A couple of weeks ago my old PSU blew up. It did kind of like a explosion sound and some flashing, very impressive. I inspected the motherboard and I could not find any damage whatsoever. Only the PSU seemed affected. After that I bought a new PSU (Tacens MP700 - 700W), an...
Hello! Finally found an issue to make an account about. Anyways, so I just recently installed a new anti-virus software (Kaskersky Anti-Virus 2013) and it runs perfectly (or so I thought). The only problem that was plaguing my computer was after I restarted it (via the Sidebar and pressing...
I upgraded from Windows 7 Home Premium to Windows 8.1 Pro about a week ago. Everything seems fine, unless I leave the computer idle for a long time. What happens is I get a black screen, with no cursor, when I return to the computer after leaving it idle overnight. It is not asleep. It is also not...
Hi there, I am using Windows 8 on Dell Inspiron N5110 15R laptop. I had to upgrade my BIOS so as to install and use the most recent operating system, Windows 8. I was Windows 7 user and had to clean install Windows 8. In Windows 7, I was very much familiar with safe mode, but today,...
I just recently bought a new 64gb SSD and installed it into my computer as the case manufacturer said in the instructions. I did everything as planned, then plugged my computer back in, to turn it on and get a black screen. No bios or anything. I tried plugging it into my alternate display to see...
Eight Forums Android App Eight Forums IOS App Follow us on Facebook