Games Crashing - BLACK SCREEN

[r5r4y]

Hello...

Since Yesterday games crash my computer, the monitor only shows black screen [there is no response from keyboard, windows etc] and there is a strange noise perhaps from the power supply, I can't figure out where the noise is from...

This only happen when I'm playing games, no particular games, all games crash this way after 5 mints MAX. My only option is to reset the computer from the button on the case.

I'm not sure there is a blue screen involved in here I've unticked Automatically restart in Startup and Recovery and didn't see any black screen when the games crashed...

I've found a crash dump in C:\Windows\LiveKernelReports\WATCHDOG, I've run a little Analysis with WinDBG, I hope it's helpful:

Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 117, {fffffa8004e804e0, fffff88003e1bc80, 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+6c80 )

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

2: 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 real bugcheck).
Arguments:
Arg1: fffffa8004e804e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88003e1bc80, 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+6c80
fffff880`03e1bc80 ??              ???

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_TIMEOUT

TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b


BUGCHECK_STR:  0x117

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`03c4c400 fffff880`041274ef : fffffa80`04e804e0 102906c9`a00038bf 00000000`00000000 fffffa80`0599b901 : watchdog!WdDbgReportRecreate+0xa3
fffff880`03c4c920 fffff880`04127e12 : fffff8a0`09dc4140 fffff8a0`09dc4140 00000000`00000008 00000000`00000000 : dxgkrnl!TdrUpdateDbgReport+0xcb
fffff880`03c4c970 fffff880`04128bda : fffffa80`04e804e0 fffffa80`04e804e0 00000000`00000000 fffffa80`0599b010 : dxgkrnl!TdrCollectDbgInfoStage1+0x7d2
fffff880`03c4ca10 fffff880`0400ff07 : fffffa80`04e804e0 00000000`00000000 00000000`00000000 fffffa80`0599b010 : dxgkrnl!TdrIsRecoveryRequired+0x17a
fffff880`03c4ca40 fffff880`04039bd4 : fffffa80`00000000 00000000`0000bdb7 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`03c4cb20 fffff880`040382bb : 00000000`00000102 00000000`00000000 00000000`0000bdb7 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0xd0
fffff880`03c4cb50 fffff880`0400b2c6 : ffffffff`ff676980 fffffa80`0599b010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`03c4cbf0 fffff880`04037e7a : 00000000`00000000 fffffa80`03a3c2a0 00000000`00000080 fffffa80`0599b010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`03c4cd00 fffff800`02d17166 : 00000000`01f72a0e fffffa80`0567ea10 fffffa80`039d4040 fffffa80`0567ea10 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`03c4cd40 fffff800`02a52486 : fffff880`02f63180 fffffa80`0567ea10 fffff880`02f6dfc0 fffff880`0121a534 : nt!PspSystemThreadStartup+0x5a
fffff880`03c4cd80 00000000`00000000 : fffff880`03c4d000 fffff880`03c47000 fffff880`085c3b60 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmpag+6c80
fffff880`03e1bc80 ??              ???

SYMBOL_NAME:  atikmpag+6c80

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4c33d53e

FAILURE_BUCKET_ID:  X64_0x117_IMAGE_atikmpag.sys

BUCKET_ID:  X64_0x117_IMAGE_atikmpag.sys

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

2: 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 real bugcheck).
Arguments:
Arg1: fffffa8004e804e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88003e1bc80, 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+6c80
fffff880`03e1bc80 ??              ???

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_TIMEOUT

TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b


BUGCHECK_STR:  0x117

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`03c4c400 fffff880`041274ef : fffffa80`04e804e0 102906c9`a00038bf 00000000`00000000 fffffa80`0599b901 : watchdog!WdDbgReportRecreate+0xa3
fffff880`03c4c920 fffff880`04127e12 : fffff8a0`09dc4140 fffff8a0`09dc4140 00000000`00000008 00000000`00000000 : dxgkrnl!TdrUpdateDbgReport+0xcb
fffff880`03c4c970 fffff880`04128bda : fffffa80`04e804e0 fffffa80`04e804e0 00000000`00000000 fffffa80`0599b010 : dxgkrnl!TdrCollectDbgInfoStage1+0x7d2
fffff880`03c4ca10 fffff880`0400ff07 : fffffa80`04e804e0 00000000`00000000 00000000`00000000 fffffa80`0599b010 : dxgkrnl!TdrIsRecoveryRequired+0x17a
fffff880`03c4ca40 fffff880`04039bd4 : fffffa80`00000000 00000000`0000bdb7 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`03c4cb20 fffff880`040382bb : 00000000`00000102 00000000`00000000 00000000`0000bdb7 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0xd0
fffff880`03c4cb50 fffff880`0400b2c6 : ffffffff`ff676980 fffffa80`0599b010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`03c4cbf0 fffff880`04037e7a : 00000000`00000000 fffffa80`03a3c2a0 00000000`00000080 fffffa80`0599b010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`03c4cd00 fffff800`02d17166 : 00000000`01f72a0e fffffa80`0567ea10 fffffa80`039d4040 fffffa80`0567ea10 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`03c4cd40 fffff800`02a52486 : fffff880`02f63180 fffffa80`0567ea10 fffff880`02f6dfc0 fffff880`0121a534 : nt!PspSystemThreadStartup+0x5a
fffff880`03c4cd80 00000000`00000000 : fffff880`03c4d000 fffff880`03c47000 fffff880`085c3b60 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmpag+6c80
fffff880`03e1bc80 ??              ???

SYMBOL_NAME:  atikmpag+6c80

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4c33d53e

FAILURE_BUCKET_ID:  X64_0x117_IMAGE_atikmpag.sys

BUCKET_ID:  X64_0x117_IMAGE_atikmpag.sys

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

2: 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 real bugcheck).
Arguments:
Arg1: fffffa8004e804e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88003e1bc80, 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+6c80
fffff880`03e1bc80 ??              ???

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_TIMEOUT

TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b


BUGCHECK_STR:  0x117

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`03c4c400 fffff880`041274ef : fffffa80`04e804e0 102906c9`a00038bf 00000000`00000000 fffffa80`0599b901 : watchdog!WdDbgReportRecreate+0xa3
fffff880`03c4c920 fffff880`04127e12 : fffff8a0`09dc4140 fffff8a0`09dc4140 00000000`00000008 00000000`00000000 : dxgkrnl!TdrUpdateDbgReport+0xcb
fffff880`03c4c970 fffff880`04128bda : fffffa80`04e804e0 fffffa80`04e804e0 00000000`00000000 fffffa80`0599b010 : dxgkrnl!TdrCollectDbgInfoStage1+0x7d2
fffff880`03c4ca10 fffff880`0400ff07 : fffffa80`04e804e0 00000000`00000000 00000000`00000000 fffffa80`0599b010 : dxgkrnl!TdrIsRecoveryRequired+0x17a
fffff880`03c4ca40 fffff880`04039bd4 : fffffa80`00000000 00000000`0000bdb7 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`03c4cb20 fffff880`040382bb : 00000000`00000102 00000000`00000000 00000000`0000bdb7 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0xd0
fffff880`03c4cb50 fffff880`0400b2c6 : ffffffff`ff676980 fffffa80`0599b010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`03c4cbf0 fffff880`04037e7a : 00000000`00000000 fffffa80`03a3c2a0 00000000`00000080 fffffa80`0599b010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`03c4cd00 fffff800`02d17166 : 00000000`01f72a0e fffffa80`0567ea10 fffffa80`039d4040 fffffa80`0567ea10 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`03c4cd40 fffff800`02a52486 : fffff880`02f63180 fffffa80`0567ea10 fffff880`02f6dfc0 fffff880`0121a534 : nt!PspSystemThreadStartup+0x5a
fffff880`03c4cd80 00000000`00000000 : fffff880`03c4d000 fffff880`03c47000 fffff880`085c3b60 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmpag+6c80
fffff880`03e1bc80 ??              ???

SYMBOL_NAME:  atikmpag+6c80

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4c33d53e

FAILURE_BUCKET_ID:  X64_0x117_IMAGE_atikmpag.sys

BUCKET_ID:  X64_0x117_IMAGE_atikmpag.sys

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

My Hardware is:ATI HD4890 GIGABYTE 1GB, MSI K9A2 CF, Aspire 550W, 4GB memory DDR2 866, AMD Phantom 9950 Quad-Core black edition, windows 7 is full retail and 64 Bit...

This never happened before, started only yesterday. Also I did format my system today to see if the problem is in one of my installed programs, but even with a clean system the problem still appears. Latest drivers on everything, tried 10.6 Catylast and 10.5, problem still exists.

Do I have a hardware issue? Can you help me?

 

[osholt]

Hello...

Since Yesterday games crash my computer, the monitor only shows black screen [there is no response from keyboard, windows etc] and there is a strange noise perhaps from the power supply, I can't figure out where the noise is from...

This only happen when I'm playing games, no particular games, all games crash this way after 5 mints MAX. My only option is to reset the computer from the button on the case.

I'm not sure there is a blue screen involved in here I've unticked Automatically restart in Startup and Recovery and didn't see any black screen when the games crashed...

I've found a crash dump in C:\Windows\LiveKernelReports\WATCHDOG, I've run a little Analysis with WinDBG, I hope it's helpful:

Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 117, {fffffa8004e804e0, fffff88003e1bc80, 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+6c80 )

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

2: 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 real bugcheck).
Arguments:
Arg1: fffffa8004e804e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88003e1bc80, 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+6c80
fffff880`03e1bc80 ??              ???

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_TIMEOUT

TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b


BUGCHECK_STR:  0x117

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`03c4c400 fffff880`041274ef : fffffa80`04e804e0 102906c9`a00038bf 00000000`00000000 fffffa80`0599b901 : watchdog!WdDbgReportRecreate+0xa3
fffff880`03c4c920 fffff880`04127e12 : fffff8a0`09dc4140 fffff8a0`09dc4140 00000000`00000008 00000000`00000000 : dxgkrnl!TdrUpdateDbgReport+0xcb
fffff880`03c4c970 fffff880`04128bda : fffffa80`04e804e0 fffffa80`04e804e0 00000000`00000000 fffffa80`0599b010 : dxgkrnl!TdrCollectDbgInfoStage1+0x7d2
fffff880`03c4ca10 fffff880`0400ff07 : fffffa80`04e804e0 00000000`00000000 00000000`00000000 fffffa80`0599b010 : dxgkrnl!TdrIsRecoveryRequired+0x17a
fffff880`03c4ca40 fffff880`04039bd4 : fffffa80`00000000 00000000`0000bdb7 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`03c4cb20 fffff880`040382bb : 00000000`00000102 00000000`00000000 00000000`0000bdb7 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0xd0
fffff880`03c4cb50 fffff880`0400b2c6 : ffffffff`ff676980 fffffa80`0599b010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`03c4cbf0 fffff880`04037e7a : 00000000`00000000 fffffa80`03a3c2a0 00000000`00000080 fffffa80`0599b010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`03c4cd00 fffff800`02d17166 : 00000000`01f72a0e fffffa80`0567ea10 fffffa80`039d4040 fffffa80`0567ea10 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`03c4cd40 fffff800`02a52486 : fffff880`02f63180 fffffa80`0567ea10 fffff880`02f6dfc0 fffff880`0121a534 : nt!PspSystemThreadStartup+0x5a
fffff880`03c4cd80 00000000`00000000 : fffff880`03c4d000 fffff880`03c47000 fffff880`085c3b60 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmpag+6c80
fffff880`03e1bc80 ??              ???

SYMBOL_NAME:  atikmpag+6c80

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4c33d53e

FAILURE_BUCKET_ID:  X64_0x117_IMAGE_atikmpag.sys

BUCKET_ID:  X64_0x117_IMAGE_atikmpag.sys

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

2: 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 real bugcheck).
Arguments:
Arg1: fffffa8004e804e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88003e1bc80, 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+6c80
fffff880`03e1bc80 ??              ???

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_TIMEOUT

TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b


BUGCHECK_STR:  0x117

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`03c4c400 fffff880`041274ef : fffffa80`04e804e0 102906c9`a00038bf 00000000`00000000 fffffa80`0599b901 : watchdog!WdDbgReportRecreate+0xa3
fffff880`03c4c920 fffff880`04127e12 : fffff8a0`09dc4140 fffff8a0`09dc4140 00000000`00000008 00000000`00000000 : dxgkrnl!TdrUpdateDbgReport+0xcb
fffff880`03c4c970 fffff880`04128bda : fffffa80`04e804e0 fffffa80`04e804e0 00000000`00000000 fffffa80`0599b010 : dxgkrnl!TdrCollectDbgInfoStage1+0x7d2
fffff880`03c4ca10 fffff880`0400ff07 : fffffa80`04e804e0 00000000`00000000 00000000`00000000 fffffa80`0599b010 : dxgkrnl!TdrIsRecoveryRequired+0x17a
fffff880`03c4ca40 fffff880`04039bd4 : fffffa80`00000000 00000000`0000bdb7 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`03c4cb20 fffff880`040382bb : 00000000`00000102 00000000`00000000 00000000`0000bdb7 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0xd0
fffff880`03c4cb50 fffff880`0400b2c6 : ffffffff`ff676980 fffffa80`0599b010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`03c4cbf0 fffff880`04037e7a : 00000000`00000000 fffffa80`03a3c2a0 00000000`00000080 fffffa80`0599b010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`03c4cd00 fffff800`02d17166 : 00000000`01f72a0e fffffa80`0567ea10 fffffa80`039d4040 fffffa80`0567ea10 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`03c4cd40 fffff800`02a52486 : fffff880`02f63180 fffffa80`0567ea10 fffff880`02f6dfc0 fffff880`0121a534 : nt!PspSystemThreadStartup+0x5a
fffff880`03c4cd80 00000000`00000000 : fffff880`03c4d000 fffff880`03c47000 fffff880`085c3b60 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmpag+6c80
fffff880`03e1bc80 ??              ???

SYMBOL_NAME:  atikmpag+6c80

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4c33d53e

FAILURE_BUCKET_ID:  X64_0x117_IMAGE_atikmpag.sys

BUCKET_ID:  X64_0x117_IMAGE_atikmpag.sys

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

2: 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 real bugcheck).
Arguments:
Arg1: fffffa8004e804e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88003e1bc80, 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+6c80
fffff880`03e1bc80 ??              ???

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_TIMEOUT

TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b


BUGCHECK_STR:  0x117

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`03c4c400 fffff880`041274ef : fffffa80`04e804e0 102906c9`a00038bf 00000000`00000000 fffffa80`0599b901 : watchdog!WdDbgReportRecreate+0xa3
fffff880`03c4c920 fffff880`04127e12 : fffff8a0`09dc4140 fffff8a0`09dc4140 00000000`00000008 00000000`00000000 : dxgkrnl!TdrUpdateDbgReport+0xcb
fffff880`03c4c970 fffff880`04128bda : fffffa80`04e804e0 fffffa80`04e804e0 00000000`00000000 fffffa80`0599b010 : dxgkrnl!TdrCollectDbgInfoStage1+0x7d2
fffff880`03c4ca10 fffff880`0400ff07 : fffffa80`04e804e0 00000000`00000000 00000000`00000000 fffffa80`0599b010 : dxgkrnl!TdrIsRecoveryRequired+0x17a
fffff880`03c4ca40 fffff880`04039bd4 : fffffa80`00000000 00000000`0000bdb7 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`03c4cb20 fffff880`040382bb : 00000000`00000102 00000000`00000000 00000000`0000bdb7 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0xd0
fffff880`03c4cb50 fffff880`0400b2c6 : ffffffff`ff676980 fffffa80`0599b010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`03c4cbf0 fffff880`04037e7a : 00000000`00000000 fffffa80`03a3c2a0 00000000`00000080 fffffa80`0599b010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`03c4cd00 fffff800`02d17166 : 00000000`01f72a0e fffffa80`0567ea10 fffffa80`039d4040 fffffa80`0567ea10 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`03c4cd40 fffff800`02a52486 : fffff880`02f63180 fffffa80`0567ea10 fffff880`02f6dfc0 fffff880`0121a534 : nt!PspSystemThreadStartup+0x5a
fffff880`03c4cd80 00000000`00000000 : fffff880`03c4d000 fffff880`03c47000 fffff880`085c3b60 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmpag+6c80
fffff880`03e1bc80 ??              ???

SYMBOL_NAME:  atikmpag+6c80

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4c33d53e

FAILURE_BUCKET_ID:  X64_0x117_IMAGE_atikmpag.sys

BUCKET_ID:  X64_0x117_IMAGE_atikmpag.sys

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

My Hardware is:ATI HD4890 GIGABYTE 1GB, MSI K9A2 CF, Aspire 550W, 4GB memory DDR2 866, AMD Phantom 9950 Quad-Core black edition, windows 7 is full retail and 64 Bit...

This never happened before, started only yesterday. Also I did format my system today to see if the problem is in one of my installed programs, but even with a clean system the problem still appears. Latest drivers on everything, tried 10.6 Catylast and 10.5, problem still exists.

Do I have a hardware issue? Can you help me?

Due to all the timing issues I am wonder whether or not your graphics card is making full contact with its connector on the Motherboard.

If possible unplug your computer and earth it and yourself; then open the case and check if the GPU is making full contact.

It is either this, a driver issue or a hardware issue.

You seam to have ruled out it being a software issue so it's either this or a hardware issue.

It may be that your Graphics card is heating up extremely, check using CPU-Z (CPUID - System & hardware benchmark, monitoring, reporting) or another utility of your choice.

Oli

 

[r5r4y]

Thanks for the answer...

I'm quite sure now that's a hardware problem...
I've controlled the fan speed via ATI CCC and It didn't do so much improvement although the gpu isn't very high... Around 65-69...

Without controlling the fan speed It's goes very easily to 80... That's a shame...
And I'm quite sure the noise came from the the video card now...

But tell me this before I go to my pc vendor Is my PSU good enough for this system?

My Hardware is:ATI HD4890 GIGABYTE 1GB, MSI K9A2 CF, Aspire 550W, 4GB memory DDR2 866, AMD Phantom 9950 Quad-Core black edition

 

[CarlTR6]

You can try this free video stress test: FurMark: Graphics Card Stability and Stress Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net[FONT=&quot]. Also if you could upload the dump file, I would be glad to take a look.

[/FONT] http://www.sevenforums.com/tutorials/83172-dump-files-upload-seven-forums.html

I would like to know the date of your atikmpag.sys driver.

[FONT=&quot]
[/FONT]

 

[r5r4y]

I would like to know the date of your atikmpag.sys driver.

What do you mean? How can I check it out? I've updated my drivers just recently, both north bridge and video card...

I'll run the test Also I've already posted the dump files in CODE tag, but here you go if you could get more from it:


Thanks for the help.
EDIT: I've added the FurMark results, I've got those just after a couple of seconds.
Also the dump file is the newts one I've got from yesterday, not everytime the games crashes It creates a dump file..

 

[CarlTR6]

Thank you for uploading the dump file. Your atikmpag.sys driver is up to date. Older versions of this driver have caused BSOD's along with atikmdag.sys which is also up to date.

You do have two drivers that needs to be updated. The second one is badly out of date and may be the cause of the crash. Win 7 does not like obsolete drivers. As a general rule (there are exceptions) drivers dated before July 13, 2009 are obsolete.

AtiPcie.sys Tue May 05 11:00:22 2009
RivaTuner64.sys Tue Jul 17 15:13:42 2007

RivaTuner64.sys - I cannot find the company that produced this driver. I am guessing it is a TV tuner? At any rate, the software and driver are obsolete. I suggest that you uninstall the software and see if this stops the BSOD's. As an alternative, you can rename the file from RivaTuner64.sys to RivaTuner64.bak. Reboot and it will not load. This will break your program, though.

AtiPcie.sys - ATI PCIE Driver for ATI PCIE chipsetGlobal Provider of Innovative Graphics, Processors and Media Solutions | AMD If there is not an update for this driver. Let it ride for the time being.

After you have gotten rid of the RivaTuner driver, run your system and see if you get any more BSOD's. Let us know.

 

[r5r4y]

RivaTuner64.sys is part of RivaTuner, I've installed it but didn't use it... It's for testing benchmarks.

Hmm.. I've searched the AMD ATI site but didn't find a link to AtiPcie.sys, Isn't that file a part of CCC? I've got 10.7...

 

[CarlTR6]

I believe it is a part of CCC and it may be OK even though it is a little out of date. We will look at that one further if you have more BSOD's.

I couldn't find the FurMark results. Was everything OK?

 

[r5r4y]

Hmm... No... Still games keep crashing my computer even after deleting RivaTuner...

 

[CarlTR6]

What did FurMark show?

 

[r5r4y]

What did FurMark show?

I don't understand... I already post the FurMark results... you mean what did it show when the game crashed? How can I know this? does the program keep logs if I run it in the background?

 

[CarlTR6]

I did not see the FurMark results; I must have missed them. Where are they?

You definitely have a video problem.

STOP 0x00000117: VIDEO_TDR_TIMEOUT_DETECTED

Usual causes: Video driver/sub-system

Note that the cause can be in subsystem. Do yo have another video card you can try?

 

[r5r4y]

No.. I do not have another video card I can try...

Any other suggestions? Thanks for the help so far.

 

[CarlTR6]

Where did you post your FurMark results. I must be blind; I did not see them. Do you have any additional mini dumps later than the one you uploaded? If so, please upload them. Have you tried to reseat your graphics card?

 

[r5r4y]

Right above your post but since you say you can't see them I've uploaded them to external site: http://i37.tinypic.com/2uzcxtz.jpg

I do not have anymore mini dumps, the last one was from 14/08/2010 which I've already uploaded...


Also I've googled for half hour and couldn't find updated AtiPcie.sys, last one I found was from 2007 which isn't good at all...

One more thing, When I looked at Event Viewer I see alot [Really, alot] of messages about amdkmdag:

External link: http://i36.tinypic.com/52gh8j.jpg

And It goes on, 13/8, 14/8 etc...
There isn't any details about this information just Binary data...
This isn't normal... right?

 

[CarlTR6]

I don't think there is an update available for AtiPcie.sys. Don't worry about it for now.

The event viewer items are information items. They are not errors. You can right click on any of them, select properties, and read the information.

I am thinking your problem is either your graphics card or possibly your power supply. I don't know a way to check either of these possibilities short of trying another graphics card and another power supply. Remember the dump definitely pointed to a graphics card error. A faulty or failing power supply can trigger all kinds of errors.

 

[r5r4y]

Here is another crash dump from five minutes ago...

Another thing when the games crash the computer does not restart automatically I hear some noise and than the screen goes black, I have to press the restart button on the case for the computer to restart completely.

 

[CarlTR6]

STOP 0x00000117: VIDEO_TDR_TIMEOUT_DETECTED

Usual causes: Video driver/sub-system

This is obviously a video error. The dumps blames atikmpag.sys. For more information on TDR errors, read this post:

http://www.sevenforums.com/graphic-...ing-display-driver-ati-hd5870.html#post821652

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_WD-20100817-2227.zip\WD-20100817-2227.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*[URL="http://msdl.microsoft.com/download/symbols"]Symbol information[/URL]

Debug session time: Tue Aug 17 15:27:10.167 2010 (GMT-4)
System Uptime: 1 days 22:53:27.792
Loading Kernel Symbols
...............................................................
................................................................
................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 117, {fffffa8004a7b4e0, fffff88003eb9c80, 0, 0}

*** 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+6c80 )

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

3: 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 real bugcheck).
Arguments:
Arg1: fffffa8004a7b4e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88003eb9c80, 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+6c80
fffff880`03eb9c80 ??              ???

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_TIMEOUT

TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b


BUGCHECK_STR:  0x117

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`031d44a0 fffff880`03f544ef : fffffa80`04a7b4e0 fffff8a0`0e55d8b7 00000000`00000000 fffff880`03f54234 : watchdog!WdDbgReportRecreate+0xa3
fffff880`031d49c0 fffff880`03f54f6d : fffff8a0`0e6b4ffc fffff8a0`09b1ae10 fffff8a0`0e55d8b7 00000000`00157745 : dxgkrnl!TdrUpdateDbgReport+0xcb
fffff880`031d4a10 fffff880`03f55bda : fffffa80`04a7b4e0 fffffa80`04a7b4e0 fffffa80`0469c010 fffffa80`04f50410 : dxgkrnl!TdrCollectDbgInfoStage1+0x92d
fffff880`031d4ab0 fffff880`0460ff07 : fffffa80`04a7b4e0 00000000`00000000 fffffa80`0469c010 fffffa80`04f50410 : dxgkrnl!TdrIsRecoveryRequired+0x17a
fffff880`031d4ae0 fffff880`04639b75 : fffff8a0`ffffffff 00000000`00a4d6d8 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`031d4bc0 fffff880`0460b2d5 : fffffa80`04f50410 fffffa80`00000000 00000000`00a4d6d8 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`031d4bf0 fffff880`04637e7a : 00000000`00000000 fffffa80`0469c010 00000000`00000080 fffffa80`04f50410 : dxgmms1!VidSchiScheduleCommandToRun+0x1e9
fffff880`031d4d00 fffff800`02d78c06 : 00000000`01fccafd fffffa80`055efa10 fffffa80`03973890 fffffa80`055efa10 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`031d4d40 fffff800`02ab2c26 : fffff800`02c4ee80 fffffa80`055efa10 fffff800`02c5cc40 fffff880`0122c534 : nt!PspSystemThreadStartup+0x5a
fffff880`031d4d80 00000000`00000000 : fffff880`031d5000 fffff880`031cf000 fffff880`08c7db60 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmpag+6c80
fffff880`03eb9c80 ??              ???

SYMBOL_NAME:  atikmpag+6c80

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4c33d53e

FAILURE_BUCKET_ID:  X64_0x117_IMAGE_atikmpag.sys

BUCKET_ID:  X64_0x117_IMAGE_atikmpag.sys

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

 

[r5r4y]

Finally, The problem is solved... I took the computer to my PC vendor, the problem was the PSU overheating and that made the graphic card fail... I'm not sure why the crash dumps blamed ATI.

Also my computer case is not big enough for all this big hardware and there is a lot of heat I need to find a new case now that will help me with cooling down my hardware... any suggestions?

 

[osholt]

Finally, The problem is solved... I took the computer to my PC vendor, the problem was the PSU overheating and that made the graphic card fail... I'm not sure why the crash dumps blamed ATI.

Also my computer case is not big enough for all this big hardware and there is a lot of heat I need to find a new case now that will help me with cooling down my hardware... any suggestions?

While you're at it you may want to invest in a water cooling system or a good fan.

Oli