Solved BSOD help reading .dmp files

[kinjacob]

Hi guys, as the title says can someone help me read these crash dumps it would be really helpful!

 

[ICIT2LOL]

Hmm Jacob sorry about the wait - but the dumps are reading graphic issues and are suggesting you uninstall the Catalyst Contro, Centre for starters

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
[COLOR=red]VIDEO_TDR_FAILURE (116)[/COLOR]
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa800c830010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88004025cec, 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+ccec
fffff880`04025cec 4883ec28        sub     rsp,28h
DEFAULT_BUCKET_ID:  [COLOR=red]GRAPHICS_DRIVER_TDR_FAULT[/COLOR]
CUSTOMER_CRASH_COUNT:  1
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
CURRENT_IRQL:  0
ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
STACK_TEXT:  
fffff880`03ebf928 fffff880`0411e134 : 00000000`00000116 fffffa80`0c830010 fffff880`04025cec 00000000`00000000 : nt!KeBugCheckEx
fffff880`03ebf930 fffff880`0411de3e : fffff880`04025cec fffffa80`0c830010 fffffa80`0d131d50 fffffa80`0b671010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`03ebf970 fffff880`1075ef13 : fffffa80`0c830010 00000000`00000000 fffffa80`0d131d50 fffffa80`0b671010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`03ebf9a0 fffff880`10788cf1 : fffffa80`ffffffff 00000000`0000da02 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`03ebfa80 fffff880`1075a2e1 : fffffa80`0b671010 fffffa80`00000008 00000000`0000da02 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`03ebfab0 fffff880`10786ff6 : 00000000`00000000 fffffa80`09bd81b0 00000000`00000080 fffffa80`0b671010 : dxgmms1!VidSchiScheduleCommandToRun+0x1e9
fffff880`03ebfbc0 fffff800`0351a456 : 00000000`fffffc32 fffffa80`0b27da00 fffffa80`066f0720 fffffa80`0b27da00 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`03ebfc00 fffff800`032722c6 : fffff800`033ffe80 fffffa80`0b27da00 fffff800`0340dcc0 fffffa80`0b272c10 : nt!PspSystemThreadStartup+0x5a
fffff880`03ebfc40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16

STACK_COMMAND:  .bugcheck ; kb
FOLLOWUP_IP: 
atikmpag+ccec
fffff880`04025cec 4883ec28        sub     rsp,28h
SYMBOL_NAME:  atikmpag+ccec
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: atikmpag
IMAGE_NAME:  [COLOR=red]atikmpag.sys[/COLOR]
DEBUG_FLR_IMAGE_TIMESTAMP:  5588b21b
FAILURE_BUCKET_ID:  [COLOR=red]X64_0x116_IMAGE_atikmpag.sys[/COLOR]
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

Do this first and then lets see if anything changes.

 

[kinjacob]

Hmm Jacob sorry about the wait - but the dumps are reading graphic issues and are suggesting you uninstall the Catalyst Contro, Centre for starters

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
[COLOR=red]VIDEO_TDR_FAILURE (116)[/COLOR]
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa800c830010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88004025cec, 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+ccec
fffff880`04025cec 4883ec28        sub     rsp,28h
DEFAULT_BUCKET_ID:  [COLOR=red]GRAPHICS_DRIVER_TDR_FAULT[/COLOR]
CUSTOMER_CRASH_COUNT:  1
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
CURRENT_IRQL:  0
ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
STACK_TEXT:  
fffff880`03ebf928 fffff880`0411e134 : 00000000`00000116 fffffa80`0c830010 fffff880`04025cec 00000000`00000000 : nt!KeBugCheckEx
fffff880`03ebf930 fffff880`0411de3e : fffff880`04025cec fffffa80`0c830010 fffffa80`0d131d50 fffffa80`0b671010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`03ebf970 fffff880`1075ef13 : fffffa80`0c830010 00000000`00000000 fffffa80`0d131d50 fffffa80`0b671010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`03ebf9a0 fffff880`10788cf1 : fffffa80`ffffffff 00000000`0000da02 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`03ebfa80 fffff880`1075a2e1 : fffffa80`0b671010 fffffa80`00000008 00000000`0000da02 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`03ebfab0 fffff880`10786ff6 : 00000000`00000000 fffffa80`09bd81b0 00000000`00000080 fffffa80`0b671010 : dxgmms1!VidSchiScheduleCommandToRun+0x1e9
fffff880`03ebfbc0 fffff800`0351a456 : 00000000`fffffc32 fffffa80`0b27da00 fffffa80`066f0720 fffffa80`0b27da00 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`03ebfc00 fffff800`032722c6 : fffff800`033ffe80 fffffa80`0b27da00 fffff800`0340dcc0 fffffa80`0b272c10 : nt!PspSystemThreadStartup+0x5a
fffff880`03ebfc40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16

STACK_COMMAND:  .bugcheck ; kb
FOLLOWUP_IP: 
atikmpag+ccec
fffff880`04025cec 4883ec28        sub     rsp,28h
SYMBOL_NAME:  atikmpag+ccec
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: atikmpag
IMAGE_NAME:  [COLOR=red]atikmpag.sys[/COLOR]
DEBUG_FLR_IMAGE_TIMESTAMP:  5588b21b
FAILURE_BUCKET_ID:  [COLOR=red]X64_0x116_IMAGE_atikmpag.sys[/COLOR]
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

Do this first and then lets see if anything changes.

Thanks for looking in to it for me, i was really curious to see what was being flagged.

allthough now it seems the problem is solved after trying everything, i started by decreasing the gpu clock while testing different programs to stress the card a bit. and it seemed like everytime the gpu reached 100% usage it would fail and crash. I was then worried that the hardware was damaged, so i opened the case, inspected the card, put it back correctly and then tried again without success. I then did a driver sweep (for the second time). But this time i installed a more stable driver (13.12) i dont think that worked either, but after toying around with catalyst control center, i changed the "wait for vertical refresh" under "gaming"> "3D applications" to "always on" instead of "always off" and this actually fixed it! At least the card is working like it used to before.

But thanks again for sending the bugcheck analysis since it was very important for me, im very grateful for the help!

 

[ICIT2LOL]

Well done Jacob - good lateral thinking I would have gione on researching that oother stuff first mate before cracking onto that.
Personally I OC a bit on my main desktop - just to see what it will do but to be brutally honest I think this OC stuff is either for the money bags who can afford new gear, the foolhardy who think it will be ok and the others like me who sometime tend to overdo it.