Computer keeps on crashing. Possibly Video Card

My computer has been crashing lately, a lot. About a month ago, I added an LSP 550 Watt power supply and an ATI 4870 512 MB that I got on sale. Starting on May 20th, my computer has been crashing, and a lot. The video card's fan sometimes doesn't give a stable sound. I am still under warranty, so it is possible to replace it. However, I am not sure if it is the video card, so I am uploading the .dmp file. I don't know how to open this. Hopefully you can help.

Btw, this has only happened when I was playing Black Ops. I don't think it is related to the program, because if I test it (which I haven't), I think it will crash on any graphics intensive game. I do have others, but I haven't gotten around to it.

Here is the message I receive after I turn the computer back on.

This report shows up.


Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 116
BCP1: FFFFFA800CBB94E0
BCP2: FFFFF88003D9245C
BCP3: 0000000000000000
BCP4: 0000000000000002
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\052311-37892-01.dmp
C:\Users\Manu\AppData\Local\Temp\WER-51480-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

SpaceMonkey1992 said:

My computer has been crashing lately, a lot. About a month ago, I added an LSP 550 Watt power supply and an ATI 4870 512 MB that I got on sale. Starting on May 20th, my computer has been crashing, and a lot. The video card's fan sometimes doesn't give a stable sound. I am still under warranty, so it is possible to replace it. However, I am not sure if it is the video card, so I am uploading the .dmp file. I don't know how to open this. Hopefully you can help.

Btw, this has only happened when I was playing Black Ops. I don't think it is related to the program, because if I test it (which I haven't), I think it will crash on any graphics intensive game. I do have others, but I haven't gotten around to it.

Here is the message I receive after I turn the computer back on.

This report shows up.


Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 116
BCP1: FFFFFA800CBB94E0
BCP2: FFFFF88003D9245C
BCP3: 0000000000000000
BCP4: 0000000000000002
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\052311-37892-01.dmp
C:\Users\Manu\AppData\Local\Temp\WER-51480-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

Probably caused by the video driver or card. I do notice Symantec also a known cause.

I would re-install driver using this

When upgrading your graphic driver you MUST remove all traces of the current driver. In order to do that we recommend using Guru3D - Driver Sweeper

Or if the above doesnt work for you. Phyxion.net - Driver Sweeper

When it is removed then download and install the fresh copy.



I would also remove symantec and replace with Microsoft security essentials

Download and run the Norton Removal Tool to uninstall your Norton product | Norton Support

http://www.microsoft.com/security_essentials/

Code:

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


Loading Dump File [C:\Users\K\Desktop\052311-37892-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;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Machine Name:
Kernel base = 0xfffff800`03611000 PsLoadedModuleList = 0xfffff800`0384ee50
Debug session time: Tue May 24 02:26:25.529 2011 (GMT-4)
System Uptime: 0 days 0:16:37.965
Loading Kernel Symbols
...............................................................
................................................................
...............................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa800cbb94e0, fffff88003d9245c, 0, 2}

Unable to load image \SystemRoot\system32\DRIVERS\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+745c )

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

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa800cbb94e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88003d9245c, 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+745c
fffff880`03d9245c 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`0235a9c8 fffff880`046d4000 : 00000000`00000116 fffffa80`0cbb94e0 fffff880`03d9245c 00000000`00000000 : nt!KeBugCheckEx
fffff880`0235a9d0 fffff880`046d3d0a : fffff880`03d9245c fffffa80`0cbb94e0 fffffa80`0b8d9d50 fffffa80`0b8c0010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`0235aa10 fffff880`0477af07 : fffffa80`0cbb94e0 00000000`00000000 fffffa80`0b8d9d50 fffffa80`0b8c0010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`0235aa40 fffff880`047a4b75 : 00000000`ffffffff 00000000`0000f70a 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`0235ab20 fffff880`047a32bb : 00000000`00000102 00000000`00000000 00000000`0000f70a 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`0235ab50 fffff880`047762c6 : ffffffff`ff676980 fffffa80`0b8c0010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`0235abf0 fffff880`047a2e7a : 00000000`00000000 fffffa80`0b9f4810 00000000`00000080 fffffa80`0b8c0010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`0235ad00 fffff800`03924bc6 : 00000000`fffffc32 fffffa80`0b8c9210 fffffa80`06a21ae0 fffffa80`0b8c9210 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`0235ad40 fffff800`0365fbc6 : fffff880`03164180 fffffa80`0b8c9210 fffff880`0316efc0 fffff880`016672b4 : nt!PspSystemThreadStartup+0x5a
fffff880`0235ad80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmpag+745c
fffff880`03d9245c 4883ec28        sub     rsp,28h

SYMBOL_NAME:  atikmpag+745c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4dae3558

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

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

I also noticed that my fan is not speeding up under load and is reaching temperatures of 87 degrees Celsius when testing with FurMark. It gets higher. I am not sure what the temperatures are when I am playing Call of Duty Black Ops. I think the computer crashes to save the GPU from frying. I will reinstall the drivers tomorrow and hopefully the fan will speed up and be fixed. Thank you. If you have anything additional to say, please say it. I will get back to you in two days.

I reinstalled the older drivers and completely got rid of the new ones with driver sweeper, but still got a blue screen. Here is the error report copy:


Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 116
BCP1: FFFFFA8006E81280
BCP2: FFFFF8800440745C
BCP3: 0000000000000000
BCP4: 0000000000000002
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\053111-32151-01.dmp
C:\Users\Manu\AppData\Local\Temp\WER-46987-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

SpaceMonkey1992 said:

I reinstalled the older drivers and completely got rid of the new ones with driver sweeper, but still got a blue screen. Here is the error report copy:


Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 116
BCP1: FFFFFA8006E81280
BCP2: FFFFF8800440745C
BCP3: 0000000000000000
BCP4: 0000000000000002
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\053111-32151-01.dmp
C:\Users\Manu\AppData\Local\Temp\WER-46987-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

"It's not a true crash, in the sense that the bluescreen was initiated only because the combination of video driver and video hardware was being unresponsive, and not because of any synchronous processing exception.

Since Vista, the "Timeout Detection and Recovery" (TDR) components of the OS video subsystem have been capable of doing some truly impressive things to try to recover from issues which would have caused earlier OSs like XP to crash.

As a last resort, the TDR subsystem sends the video driver a "please restart yourself now!" command and waits a few seconds.

If there's no response, the OS concludes that the video driver/hardware combo has truly collapsed in a heap, and it fires off that stop 0x116 BSOD.

If playing with video driver versions hasn't helped, make sure the box is not overheating.

Try removing a side panel and aiming a big mains fan straight at the motherboard and GPU.

Run it like that for a few hours or days - long enough to ascertain whether cooler temperatures make a difference.

If so, it might be as simple as dust buildup and subsequently inadequate cooling.

I would download cpu-z and gpu-z (both free) and keep an eye on the video temps Let us know if you need help STOP 0x116: VIDEO_TDR_ERROR troubleshooting - Windows 7 Forums

I bought this Visiontek AMD 4870 512MB refurbished from Tigerdirect.com. Since it is still under warranty, I will probably get it replaced within the next three weeks. I switched back to the AMD 4350 512MB, a great few lunges down. Also, I don't see a blue screen. All I see is a band that looks like a distorted checkerboard. I notice that the fan doesn't spin up, even to 60% before failing. At a manual 100%, it sounds like a loud vacuum cleaner. It is a really loud fan at full speed. However, it rarely gets over 30-40%. It is receiving full power from an LSP 550, which is a very good power supply (or so I hear). It may not be modular, but it gets the job done. The temps get up to 91-95 degrees Celsius, which I think is very high. It probably shuts off to keep the GPU from frying. When idle, temperatures are around 75 degrees Celsius. Either way, I don't think drivers will fix this problem, because I tried the factory drivers that come with the factory disk and I have tried the latest drivers. I still get crashes. Also, I don't actually see a blue screen before a crash. I only see that checkerboard band and after the GPU cool for a couple minutes, the computer automatically restarts. I should have bought the factory overclocked one with two fans at the same price. Oh well, what is done, is done.

zigzag3143 said:

SpaceMonkey1992 said:

I reinstalled the older drivers and completely got rid of the new ones with driver sweeper, but still got a blue screen. Here is the error report copy:


Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 116
BCP1: FFFFFA8006E81280
BCP2: FFFFF8800440745C
BCP3: 0000000000000000
BCP4: 0000000000000002
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\053111-32151-01.dmp
C:\Users\Manu\AppData\Local\Temp\WER-46987-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

"It's not a true crash, in the sense that the bluescreen was initiated only because the combination of video driver and video hardware was being unresponsive, and not because of any synchronous processing exception.

Since Vista, the "Timeout Detection and Recovery" (TDR) components of the OS video subsystem have been capable of doing some truly impressive things to try to recover from issues which would have caused earlier OSs like XP to crash.

As a last resort, the TDR subsystem sends the video driver a "please restart yourself now!" command and waits a few seconds.

If there's no response, the OS concludes that the video driver/hardware combo has truly collapsed in a heap, and it fires off that stop 0x116 BSOD.

If playing with video driver versions hasn't helped, make sure the box is not overheating.

Try removing a side panel and aiming a big mains fan straight at the motherboard and GPU.

Run it like that for a few hours or days - long enough to ascertain whether cooler temperatures make a difference.

If so, it might be as simple as dust buildup and subsequently inadequate cooling.

I would download cpu-z and gpu-z (both free) and keep an eye on the video temps Let us know if you need help STOP 0x116: VIDEO_TDR_ERROR troubleshooting - Windows 7 Forums

When you referred to the dust buildup and inadequate cooling, were you referring to the video card or the case? I assume you were referring to the case. Also the 4350 runs at about 55 degrees Celsius, around 60-70 degrees Celsius under load.

I also had another question: Could the power supply be at fault? The power supply is 550W (Ultra LSP550), but emits a very low pitch whine whenever on. It has been doing this since the day I received it. However, I have only had the video card problems since recently. Is this normal? Could the power supply be defective? Could I find out if this is a power supply problem using some software? This way I could find out how many watts the video card is actually getting. I don't have an extra power supply lying around, so I can't switch it out with anything and troubleshoot it that way. Both the card and the power supply have a lifetime warranty, but replacement parts do cost money, so before I RMA the card, I just want to make sure it is actually the card that is not working and not the power supply.