BSOD after resume from sleep

Hi,

I'm hoping to get some help. About a month ago my pc started going to BSOD while trying to resume after being put to sleep. PC is 16 months old. I read the forums, etc and updated the ATI radeon display driver and the Realtek network driver but the problem persisted.

I also rolled back the system using restore to before the problem began but no change. I then reinstalled windows 7 64bit using the OEM CD rom and installed all the MS updates - no change. Last week, it occurred to me that it might be a monitor hw issue so I swapped out the monitor with another I had. That seemed to solve it - for 4 days - now it's doing the same thing with the second monitor.

I've attached the zipfile with the minidmp and perfmon.

Appreciate any insight - Bob

Basically this is a sign of a defective graphic card/RAM
STOP 0x116: VIDEO_TDR_ERROR troubleshooting
RAM - Test with Memtest86+

Remove Avira antivirus and use MSE
Remove IObit Smart Defrag, it is known to cause issues on Windows 7
Are you overclocking?

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa8007464010, fffff8800447d408, 0, 2}

*** 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+7408 )


VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8007464010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800447d408, 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`0447d408 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`065eb9c8 fffff880`04522000 : 00000000`00000116 fffffa80`07464010 fffff880`0447d408 00000000`00000000 : nt!KeBugCheckEx
fffff880`065eb9d0 fffff880`04521d0a : fffff880`0447d408 fffffa80`07464010 fffffa80`09cd1c00 fffffa80`09cc6010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`065eba10 fffff880`051c1f07 : fffffa80`07464010 00000000`00000000 fffffa80`09cd1c00 fffffa80`09cc6010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`065eba40 fffff880`051ebb75 : 00000000`ffffffff 00000000`002e707f 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`065ebb20 fffff880`051ea2bb : 00000000`00000102 00000000`00000000 00000000`002e707f 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`065ebb50 fffff880`051bd2c6 : ffffffff`ff676980 fffffa80`09cc6010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`065ebbf0 fffff880`051e9e7a : 00000000`00000000 fffffa80`06b1c010 00000000`00000080 fffffa80`09cc6010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`065ebd00 fffff800`02d6832e : 00000000`fffffc32 fffffa80`09cf68c0 fffffa80`066a5990 fffffa80`09cf68c0 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`065ebd40 fffff800`02abd666 : fffff800`02c3ee80 fffffa80`09cf68c0 fffff800`02c4ccc0 6f704330`526d354a : nt!PspSystemThreadStartup+0x5a
fffff880`065ebd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmpag+7408
fffff880`0447d408 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
---------

Thanks for the reply.

Not overclocking at all. Removed Avira and Defrag. Was already using MS security essentials.

When you say defective video card, do you mean the GPU itself, the video RAM, the I/O between the card and the motherboard, the motherboard RAM or possibly some combination of these ?

I've begun investigating temperature as a possibility, but nothing conclusive yet. Would this type of issue typically cause irreparable damage to a connected monitor ? If it is temperature, is it likely the video card is now permanently damaged or could it be fine if allowed to breath better ? Any ideas why a machine would work for 16 months and then develop a temperature issue (if that is what the problem turns out to be) ?

When you say defective video card, do you mean the GPU itself, the video RAM, the I/O between the card and the motherboard, the motherboard RAM or possibly some combination of these ?

It can one of these or a combination

I've begun investigating temperature as a possibility, but nothing conclusive yet. Would this type of issue typically cause irreparable damage to a connected monitor ?

Monitors are unaffected

If it is temperature, is it likely the video card is now permanently damaged or could it be fine if allowed to breath better ?

If the video card was overheating for long periods of time the heat may have damaged the card itself, however check its temps. It should not go beyond 80C under normal conditions

Any ideas why a machine would work for 16 months and then develop a temperature issue (if that is what the problem turns out to be) ?

Thermal compound/paste may be the cause, you may want to apply new paste. Keep in mind that every component of a computer has a limited lifetime and may fail anytime