locked
Win 7 ultimate 64, green screen of death? RRS feed

  • Question

  • Hey all,

    Just got a weird green screen with horizontal lines, never seen a green screen just a blue on. I have tried to read the DUMP file myself to no avail. i can't even open the correct path in the command line!

    Can someone do me a big big favour and check my dump file?

    http://www.mediafire.com/?57r85wn21vv308k

    Many Many thanks

    Wednesday, June 1, 2011 6:54 PM

Answers

  • It's a TDR problem, by the description, it reads like the video card is bad.

    I'll try to debug the dump now.

    The debugger blames the ATI graphics drivers, you could try updating them from the  AMD website.


    *******************************************************************************
    *                                       *
    *            Bugcheck Analysis                  *
    *                                       *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 116, {fffffa800efca010, fffff88004243408, 0, 2}
    
    *** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
    Probably caused by : atikmpag.sys ( atikmpag+7408 )
    
    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: fffffa800efca010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff88004243408, 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+7408
    fffff880`04243408 4883ec28    sub   rsp,28h
    
    DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT
    
    BUGCHECK_STR: 0x116
    
    PROCESS_NAME: System
    
    CURRENT_IRQL: 0
    
    STACK_TEXT: 
    fffff880`061bf9c8 fffff880`044bf000 : 00000000`00000116 fffffa80`0efca010 fffff880`04243408 00000000`00000000 : nt!KeBugCheckEx
    fffff880`061bf9d0 fffff880`044bed0a : fffff880`04243408 fffffa80`0efca010 fffffa80`0a3edd50 fffffa80`09fd7010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
    fffff880`061bfa10 fffff880`04565f07 : fffffa80`0efca010 00000000`00000000 fffffa80`0a3edd50 fffffa80`09fd7010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
    fffff880`061bfa40 fffff880`0458fb75 : 00000000`ffffffff 00000000`000f6575 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
    fffff880`061bfb20 fffff880`0458e2bb : 00000000`00000102 00000000`00000000 00000000`000f6575 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
    fffff880`061bfb50 fffff880`045612c6 : ffffffff`ff676980 fffffa80`09fd7010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
    fffff880`061bfbf0 fffff880`0458de7a : 00000000`00000000 fffffa80`0a6f0930 00000000`00000080 fffffa80`09fd7010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
    fffff880`061bfd00 fffff800`02f2fbc6 : 00000000`fffffc32 fffffa80`0a066b60 fffffa80`06d055f0 fffffa80`0a066b60 : dxgmms1!VidSchiWorkerThread+0xba
    fffff880`061bfd40 fffff800`02c6abc6 : fffff880`02f64180 fffffa80`0a066b60 fffff880`02f6f0c0 2c307830`2c307830 : nt!PspSystemThreadStartup+0x5a
    fffff880`061bfd80 00000000`00000000 : fffff880`061c0000 fffff880`061ba000 fffff880`067a6b70 00000000`00000000 : nt!KiStartSystemThread+0x16
    
    
    STACK_COMMAND: .bugcheck ; kb
    
    FOLLOWUP_IP: 
    atikmpag+7408
    fffff880`04243408 4883ec28    sub   rsp,28h
    
    SYMBOL_NAME: atikmpag+7408
    
    FOLLOWUP_NAME: MachineOwner
    
    MODULE_NAME: atikmpag
    
    IMAGE_NAME: atikmpag.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP: 4d9bc027
    
    FAILURE_BUCKET_ID: X64_0x116_IMAGE_atikmpag.sys
    
    BUCKET_ID: X64_0x116_IMAGE_atikmpag.sys
    
    Followup: MachineOwner
    ---------
    
    
    • Proposed as answer by Arthur Xie Friday, June 3, 2011 9:12 AM
    • Marked as answer by Arthur Xie Thursday, June 16, 2011 5:34 AM
    Wednesday, June 1, 2011 7:40 PM
  • Many of this kind of issues are caused by overheating. I suspect that the released driver for your video card does not supports overheating well.
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”
    • Marked as answer by Arthur Xie Thursday, June 16, 2011 5:34 AM
    Friday, June 3, 2011 9:14 AM

All replies

  • It's a TDR problem, by the description, it reads like the video card is bad.

    I'll try to debug the dump now.

    The debugger blames the ATI graphics drivers, you could try updating them from the  AMD website.


    *******************************************************************************
    *                                       *
    *            Bugcheck Analysis                  *
    *                                       *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 116, {fffffa800efca010, fffff88004243408, 0, 2}
    
    *** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
    Probably caused by : atikmpag.sys ( atikmpag+7408 )
    
    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: fffffa800efca010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff88004243408, 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+7408
    fffff880`04243408 4883ec28    sub   rsp,28h
    
    DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT
    
    BUGCHECK_STR: 0x116
    
    PROCESS_NAME: System
    
    CURRENT_IRQL: 0
    
    STACK_TEXT: 
    fffff880`061bf9c8 fffff880`044bf000 : 00000000`00000116 fffffa80`0efca010 fffff880`04243408 00000000`00000000 : nt!KeBugCheckEx
    fffff880`061bf9d0 fffff880`044bed0a : fffff880`04243408 fffffa80`0efca010 fffffa80`0a3edd50 fffffa80`09fd7010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
    fffff880`061bfa10 fffff880`04565f07 : fffffa80`0efca010 00000000`00000000 fffffa80`0a3edd50 fffffa80`09fd7010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
    fffff880`061bfa40 fffff880`0458fb75 : 00000000`ffffffff 00000000`000f6575 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
    fffff880`061bfb20 fffff880`0458e2bb : 00000000`00000102 00000000`00000000 00000000`000f6575 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
    fffff880`061bfb50 fffff880`045612c6 : ffffffff`ff676980 fffffa80`09fd7010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
    fffff880`061bfbf0 fffff880`0458de7a : 00000000`00000000 fffffa80`0a6f0930 00000000`00000080 fffffa80`09fd7010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
    fffff880`061bfd00 fffff800`02f2fbc6 : 00000000`fffffc32 fffffa80`0a066b60 fffffa80`06d055f0 fffffa80`0a066b60 : dxgmms1!VidSchiWorkerThread+0xba
    fffff880`061bfd40 fffff800`02c6abc6 : fffff880`02f64180 fffffa80`0a066b60 fffff880`02f6f0c0 2c307830`2c307830 : nt!PspSystemThreadStartup+0x5a
    fffff880`061bfd80 00000000`00000000 : fffff880`061c0000 fffff880`061ba000 fffff880`067a6b70 00000000`00000000 : nt!KiStartSystemThread+0x16
    
    
    STACK_COMMAND: .bugcheck ; kb
    
    FOLLOWUP_IP: 
    atikmpag+7408
    fffff880`04243408 4883ec28    sub   rsp,28h
    
    SYMBOL_NAME: atikmpag+7408
    
    FOLLOWUP_NAME: MachineOwner
    
    MODULE_NAME: atikmpag
    
    IMAGE_NAME: atikmpag.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP: 4d9bc027
    
    FAILURE_BUCKET_ID: X64_0x116_IMAGE_atikmpag.sys
    
    BUCKET_ID: X64_0x116_IMAGE_atikmpag.sys
    
    Followup: MachineOwner
    ---------
    
    
    • Proposed as answer by Arthur Xie Friday, June 3, 2011 9:12 AM
    • Marked as answer by Arthur Xie Thursday, June 16, 2011 5:34 AM
    Wednesday, June 1, 2011 7:40 PM
  • Many of this kind of issues are caused by overheating. I suspect that the released driver for your video card does not supports overheating well.
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”
    • Marked as answer by Arthur Xie Thursday, June 16, 2011 5:34 AM
    Friday, June 3, 2011 9:14 AM