BSOD while palying, dxgkrnl.sys+5d000

[krpandrei]

Hi,

I'd really appreciate it if someone could look over these files and see if you can find the reason why my PC got a this strange BSOD's.

I consider my self a advanced user but this beats me. I suspect to be the video card ... or maybe drivers related.

what I already done:
- Memtest86+ more that 2 hours everything OK
- constant control of system and gpu temperature (and other stats) also in game paly (with MSI Kombuster + HWiNFO64) everything OK
- other minor checks including also a windows reinstall

 

[Arc]

It says that it is a stop 0x116, which is a display related issue.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa8005b3e2c0, fffff88003a078b8, 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+78b8 )

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: fffffa8005b3e2c0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88003a078b8, 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+78b8
fffff880`03a078b8 4883ec28        sub     rsp,28h

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`06fcf988 fffff880`052b5000 : 00000000`00000116 fffffa80`05b3e2c0 fffff880`03a078b8 00000000`00000000 : nt!KeBugCheckEx
fffff880`06fcf990 fffff880`052b4d0a : fffff880`03a078b8 fffffa80`05b3e2c0 fffffa80`0552ed50 fffffa80`054a8010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`06fcf9d0 fffff880`0535bf07 : fffffa80`05b3e2c0 00000000`00000000 fffffa80`0552ed50 fffffa80`054a8010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`06fcfa00 fffff880`05385b75 : 00000000`ffffffff 00000000`00000436 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`06fcfae0 fffff880`053842bb : 00000000`00000102 00000000`00000000 00000000`00000436 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`06fcfb10 fffff880`053572c6 : ffffffff`ff676980 fffffa80`054a8010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`06fcfbb0 fffff880`05383e7a : 00000000`00000000 00000000`0000000f 00000000`00000080 fffffa80`05390c58 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`06fcfcc0 fffff800`02f6d34a : 00000000`028563d6 fffffa80`054c6060 fffffa80`039cd040 fffffa80`054c6060 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`06fcfd00 fffff800`02cbd946 : fffff800`02e48e80 fffffa80`054c6060 fffff800`02e56cc0 6e326763`315a684a : nt!PspSystemThreadStartup+0x5a
fffff880`06fcfd40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmpag+78b8
fffff880`03a078b8 4883ec28        sub     rsp,28h

SYMBOL_NAME:  atikmpag+78b8

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ea760b6

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

Followup: MachineOwner
---------

0: kd> lmvm atikmpag
start             end                 module name
fffff880`03a00000 fffff880`03a55000   atikmpag T (no symbols)           
    Loaded symbol image file: atikmpag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
    Image name: atikmpag.sys
    Timestamp:        Wed Oct 26 06:51:58 2011 (4EA760B6)
    CheckSum:         0005289A
    ImageSize:        00055000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

It also says that the dispaly driver is very old here. Update your ATI/AMD display driver.
You can get it from the link in our forum, http://www.sevenforums.com/graphic-...alyst-video-driver-windows-7-a.html#post17671, 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. Then, follow the other steps described in http://www.sevenforums.com/crash-lo...op-0x116-video_tdr_error-troubleshooting.html

If you get any further BSODs during the process, upload the crash dumps. There might be something more other than graphics in your case.