Random BSOD, Stop Code 116, Sapphire Toxic Radeon HD 6950

I've had this PC for about..... Six months? The 116 BSODs started about two weeks of getting the PC up and running. As far as I can tell there is no discernable pattern to what triggers them, I only have the crash dumps and a persistent indicator that it is maybe a driver problem.

At first I thought the PC was overheating or at least the graphic card. So I downloaded and installed AIDA64 in order to monitor the temperatures. And it idles around lower 40s C and jumps to mid to high 60s under load. Well within the specs I've seen. So I gave it a nice hose down with a can of compressed air to get out what dust may be there, no dust as I try to keep it dust free.

So I kept the catalyst driver up to date currently she is running the 12.3 version. Odd thing though the problem went away briefly when 12.1 was released and showed up again about a few weeks ago.

I have all the crash dumps from my minidump folder including the one from today. If theres anything else I should include with it just let me know.

The most recent crash dump:

Code:

 
BugCheck 116, {fffffa8012f464e0, fffff880074639e0, 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+79e0 )
Followup: MachineOwner
---------
3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8012f464e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff880074639e0, 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+79e0
fffff880`074639e0 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`023fe9c8 fffff880`0750e000 : 00000000`00000116 fffffa80`12f464e0 fffff880`074639e0 00000000`00000000 : nt!KeBugCheckEx
fffff880`023fe9d0 fffff880`0750dd0a : fffff880`074639e0 fffffa80`12f464e0 fffffa80`14d47010 fffffa80`10d24410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`023fea10 fffff880`08d3af07 : fffffa80`12f464e0 00000000`00000000 fffffa80`14d47010 fffffa80`10d24410 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`023fea40 fffff880`08d64b75 : 00000000`ffffffff 00000000`000a2de6 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`023feb20 fffff880`08d632bb : 00000000`00000102 00000000`00000005 00000000`000a2de6 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`023feb50 fffff880`08d362c6 : ffffffff`ff676980 fffffa80`10d24410 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`023febf0 fffff880`08d62e7a : 00000000`00000000 fffffa80`0f0fcb50 00000000`00000080 fffffa80`10d24410 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`023fed00 fffff800`0377af7a : 00000000`fffffc32 fffffa80`0f3d7b60 fffffa80`0cd1e9e0 fffffa80`0f3d7b60 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`023fed40 fffff800`034d19c6 : fffff880`03288180 fffffa80`0f3d7b60 fffff880`03293040 fffff880`01429384 : nt!PspSystemThreadStartup+0x5a
fffff880`023fed80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
 
STACK_COMMAND:  .bugcheck ; kb
FOLLOWUP_IP: 
atikmpag+79e0
fffff880`074639e0 4883ec28        sub     rsp,28h
SYMBOL_NAME:  atikmpag+79e0
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: atikmpag
IMAGE_NAME:  atikmpag.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  4f3b14b8
FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys
BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys
Followup: MachineOwner
---------

Code:

 
 
System Manufacturer/Model Number=N/A 
OS=Windows 7 Ultimate 64 bit 
CPU=AMD Phenom 2 X6 1100T Black Edition Thuban 3.3GHz 
Motherboard=ASUS Crosshair V Formula 990FX 
Memory=Corsair Veneance 16GB DDR3 PC12800 
Graphics Card(s)=2x Sapphire Toxic Radeon HD 6950 2GB 256 bit GDDR5 PCIx 2.1 
Sound Card=Creative PCIx Sound Blaster X-FI Titanium Fatal1ty Champion 
Monitor(s) Displays=ASUS VW246H 24" 2ms(GTG) HDMI Widescreen LCD Monitor 
Hard Drives=Seagate Constellation ES STS500NM0011 500GB (Drive with OS)
HITACHI Deskstar 7K3000 HDS723020BLA642 2TB (Drive with most user files)
WDC (Western Digital) WD5000AAKS-00TMA0 500GB (Drive from previous PC) 
PSU=Thermaltake Toughpower Grand TPG-1050M 1050Watt 
Case=Cooler Master HAF X RC-942-KKN1 ATX Full Tower 
Cooling=140mm Rear Fan, 200mm Top Fan, 200mm Side Fan, 230mm Front Fan

In Looking at the three most recent BSODs (APril 4th -10th) I noticed that each one of them had an uptime of at least 60 hours with the most recent having an uptime of 100 hours.

Leads me to believe it is either a memory leak (not most likely) or heat.

To test you should try rebooting daily and see what the results are.


BTW you have at least 10 software items that can contribute to BSOD's but I dont believe they are relevant to the video issue,

zigzag3143 said:

In Looking at the three most recent BSODs (APril 4th -10th) I noticed that each one of them had an uptime of at least 60 hours with the most recent having an uptime of 100 hours.

Leads me to believe it is either a memory leak (not most likely) or heat.

To test you should try rebooting daily and see what the results are.


BTW you have at least 10 software items that can contribute to BSOD's but I dont believe they are relevant to the video issue,

@Rebootng: Will do.

What software was it? Also I just found the BSO posting instructions. You want me to post the logs and files it requires or hold off for now?

outlawstar15a2 said:

zigzag3143 said:

In Looking at the three most recent BSODs (APril 4th -10th) I noticed that each one of them had an uptime of at least 60 hours with the most recent having an uptime of 100 hours.

Leads me to believe it is either a memory leak (not most likely) or heat.

To test you should try rebooting daily and see what the results are.


BTW you have at least 10 software items that can contribute to BSOD's but I dont believe they are relevant to the video issue,

@Rebootng: Will do.

What software was it? Also I just found the BSO posting instructions. You want me to post the logs and files it requires or hold off for now?

Hold off for now.

Software includes

Daemon tools and dtsoftbus01.sys
Unknown and may be malware aa9q3721.SYS
The creative drivers
Sptd.sys
Thats all I can think of atm.

The BSODs keep continuing they keep pointing to atikmpag.sys. What' the next thing you'd like me to try?

Also I've been monitoring the temperatures thinking maybe the card was overheating the last two times it happened the GPU was hovering around the high 40s, low 50s which is my idle temp because I was staring at my wallpaper and surfing YouTube. I'm gonna try to see if I can getyou any extra info.

Go to your Control Panel >> Graphics >> Desktops and Displays,
you will see monitor or monitors. When your mouse is over the icon an arrow pointing downward will appear that will represent a drop down menu. Click that arrow then click Configure. More tabs ill be open. Click Scaling Options, then slide the bar to Overscan (0%) and click apply then ok.

Hope problem is fixed.

I think I fixed it. I downgraded the Catalyst driver to the 11.8 version which is what came on the DVD when I bought the card. It's been three days no BSODs yet.... And by Athame they'll never be hopefully....