Games Crashing - BLACK SCREEN

r5r4y said:

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:

Code:

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

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

https://www.sevenforums.com/tutorials...en-forums.html

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

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.

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?

What did FurMark show?