Computer Randomly Restarts Only When Playing Certain Games

[Prototype661]

You did good
There were about 12 files and all consistent

 Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\Richard\AppData\Local\Temp\Temp1_Prototype661 BSOD Files.zip\Prototype661 BSOD Files\Mini030913-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6001.22777.x86fre.vistasp1_ldr.101014-0432
Machine Name:
Kernel base = 0x82010000 PsLoadedModuleList = 0x82128c70
Debug session time: Sat Mar  9 22:47:49.380 2013 (UTC - 4:00)
System Uptime: 0 days 5:20:41.559
Loading Kernel Symbols
...............................................................
................................................................
..............
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 116, {87089008, 8df1b62c, 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+662c )
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: 87089008, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: 8df1b62c, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 00000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 00000002, Optional internal context dependent data.
Debugging Details:
------------------

FAULTING_IP: 
atikmpag+662c
8df1b62c 8bff            mov     edi,edi
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
CUSTOMER_CRASH_COUNT:  1
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
CURRENT_IRQL:  0
STACK_TEXT:  
93614bc0 8f3a9d76 00000116 87089008 8df1b62c nt!KeBugCheckEx+0x1e
93614be4 8f3aaa68 8df1b62c 00000000 00000002 dxgkrnl!TdrBugcheckOnTimeout+0x8d
93614c04 8f347ed1 00000000 00000102 882616d8 dxgkrnl!TdrIsRecoveryRequired+0xa1
93614c6c 8f358ef4 882616d8 0012cf3e 00000000 dxgkrnl!VidSchiReportHwHang+0x2f5
93614c98 8f358c54 882616d8 00000000 00000000 dxgkrnl!VidSchiCheckHwProgress+0x69
93614cc4 8f335a4c 00000002 885aaae0 8823c070 dxgkrnl!VidSchiWaitForSchedulerEvents+0x13f
93614d54 8f358f9b 882616d8 820617bf 882616d8 dxgkrnl!VidSchiScheduleCommandToRun+0xac
93614d68 8f396053 882616d8 00000000 85787788 dxgkrnl!VidSchiRun_PriorityTable+0xf
93614d7c 821e6fd2 882616d8 795b059e 00000000 dxgkrnl!VidSchiWorkerThread+0x62
93614dc0 8203ea8e 8f395ff1 882616d8 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16

STACK_COMMAND:  .bugcheck ; kb
FOLLOWUP_IP: 
atikmpag+662c
8df1b62c 8bff            mov     edi,edi
SYMBOL_NAME:                     c+662c
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: atikmpag
IMAGE_NAME:  [B]atikmpag.sys[/B]
DEBUG_FLR_IMAGE_TIMESTAMP:  4f597fae
FAILURE_BUCKET_ID:  0x116_IMAGE_atikmpag.sys
BUCKET_ID:  0x116_IMAGE_atikmpag.sys
Followup: MachineOwner
---------

The problem seems to be the AMD driver or the actual card. Go to the web site and update driver, to start

	AMD driver
	AMD multi-vendor Miniport Driver
	Advanced Micro Devices, Inc.
	Various

[TD="align: right"] Productname: [/TD]

[TD="align: right"] Description: [/TD]

[TD="align: right"] Company: [/TD]

[TD="align: right"] File size: [/TD]

My drivers are updated to the latest version, so it must be the card itself.

 

[richc46]

It could be the actual card, but lets see what happens with the driver.

 

[richc46]

Your BC code is 116.
We have this great write up from our affilated forum on 116
STOP 0x116: VIDEO_TDR_ERROR troubleshooting - Windows 7 Help Forums

 

[Prototype661]

It could be the actual card, but lets see what happens with the driver.

A few weeks ago I did a factory reset, to see if that would fix my problem in any way, and since the hard drive was completely erased, I had to re-download the latest driver. So I am almost 100% certain that I have the latest driver.

 

[richc46]

I gave you a link to BC 116 troubleshooting, give that a shot.
Your reports were consisent, I am certain the problem is tied into graphics.

 

[Prototype661]

Your BC code is 116.
We have this great write up from our affilated forum on 116
STOP 0x116: VIDEO_TDR_ERROR troubleshooting - Windows 7 Help Forums

I've cleaned the computer out multiple times, made sure all the fans were working, and pulled the computer out from under my desk to give it the most air possible. I have also put my hand by the fan a few times while playing a game, and it wasn't hot at all. I also played Skyrim with CPU-Z on, to see what temps I was hitting, and cores never went over 65c.

 

[richc46]

Here is the most pertinent portion of the article that I gave you
How to troubleshoot

 

[Prototype661]

Here is the most pertinent portion of the article that I gave you
How to troubleshoot

This is exactly what is happening to me.

 

[Prototype661]

I'm still not completely sure about what to do to try and fix this, but thanks very much for that link. I have a friend whose brother is an expert with computers. I'll call him and see if he can help. Thanks again for the help!

 

[Prototype661]

I'm still not completely sure about what to do to try and fix this, but thanks very much for that link. I have a friend whose brother is an expert with computers. I'll call him and see if he can help. Thanks again for the help!

My problem isn't fixed yet, but I think we found the problem: Issue Cause:
The issue occurs when the Timeout Detection and Recovery (TDR) feature available in Windows Vista® and Windows 7 detects that the graphics card (GPU) has not responded within a predetermined period of time and reinitializes it with the Windows Display Driver Model (WDDM) to prevent the need to reboot. There is no single cause for a TDR event to be triggered.

 

[richc46]

I hate to tell you but code 116 is the most difficult to solve. It seems that you have a good start. Follow the instructions, between the Forum, you friend and you, we should get it solved.

 

[townsbg]

I agree about the heat; too much and it would shut off. It sounds like you are getting a kernel exception causing the recycle. If you disable automatic restarts you'd probably have a blue screen which can be quite useful and informative however the memory dumps contain just as much if not more information. I think that you are on the right track with Rich.

 

[Prototype661]

I hate to tell you but code 116 is the most difficult to solve. It seems that you have a good start. Follow the instructions, between the Forum, you friend and you, we should get it solved.

I did notice that the computer only restarts during certain events in a game, such as an explosion, or lots of visual effects like motion blur and stuff. One thing did seem to keep it from restarting though: Windowed Mode. I could just play my games in windowed mode. I'd rather have no fullscreen than restarting.

 

[Patonb]

By using windows mode, you are not pushing your card to it's fullest.

I'm still banking a bad power supply AND running IBT and furmark together will usually find this out.

 

[Prototype661]

I ran the Furmark test for about 10 minutes, and the GPU got up to 86°C. I highly doubt that my GPU should be at this temperature. So far, I think the problem with my computer is that the GPU is overheating. 14 more degrees, and my GPU will be hot enough to boil water.I wasn't even running the test at max settings. My screen resolution is 1680x1050, and I was running the test at 1280x720. I was also only using 2 samples of anti-aliasing.

 

[Patonb]

86C is finer for a gpu, I run mine 24/7 At 83C. In fact my desktop runs 100% load 24/7 at cpu of 73C and gpu at 83C

Gpu's are not like cpu's they're designed to crap out at 110C.

You really need to max it out.. But I do not believe you are heat related though.

Btw, you can't really hurt things as they throttle back and shut off to keep damage from occurring.

 

[richc46]

Follow the BC code 116 instructions, the answer is there (somewhere)