Solved BSOD playing all games, dxgkrnl/atikmpag/dxgmms1

[Hextall27]

I get a BSOD during every game I play (Napoleon TW, Rome 2 TW, Mirror's Edge, Just Cause 2 single player) It takes longer in some games than others. I can play for an hour in JC2, for example, but only a few minutes of Napoleon before I crash.

I have updated my GPU drivers and motherboard bios, expanded atikmdag/pag.sy_ via the CMD console, and run Furmark with no problems for 20 minutes. I even plugged my computer directly into the wall to rule out my surge protector. I have deleted every trace of my old AMD drivers through the registry editor and downloaded the latest drivers from the website. I also ran memtest86+ for two hours without any errors. I would greatly appreciate any help.

System specs:

I built my computer in August of 2013 with all new hardware.
MSI B-75A-G43 motherboard
Intel i5 3350p processor
AMD Radeon 7770 GPU
XFX 550watt power supply
MEM 4Gx2|CORSAIR CML8GX3M2A1600C9 R

 

[Arc]

Hi Hextall27.

You are having stop 0x116 BSODs (display/graphics related) irrespective of the display driver version. So apparently the reason is not the driver.

Are you overclocking? As you are getting BSODs, you should stop overclocking and run all the hardware components like CPU, GPU and RAM to their default settings.

Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
eXtreme Power Supply Calculator
Also let us know the wattage of your PSU.

Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy. Alternatively, you can publish a Speccy snapshot too: http://www.sevenforums.com/tutorials/311593-speccy-publish-snapshot-your-system-specs.html .

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Let us know the results.
__________________________________________________________________________________________

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa80078b24e0, fffff88002c3ad88, 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+bd88 )

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

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa80078b24e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88002c3ad88, 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+bd88
fffff880`02c3ad88 4883ec28        sub     rsp,28h

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

STACK_TEXT:  
fffff880`03ee8888 fffff880`02d2c140 : 00000000`00000116 fffffa80`078b24e0 fffff880`02c3ad88 00000000`00000000 : nt!KeBugCheckEx
fffff880`03ee8890 fffff880`02d2be4a : fffff880`02c3ad88 fffffa80`078b24e0 fffffa80`07804450 fffffa80`0907d010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`03ee88d0 fffff880`0fdc4f13 : fffffa80`078b24e0 00000000`00000000 fffffa80`07804450 fffffa80`0907d010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`03ee8900 fffff880`0fdeecf1 : 00000000`ffffffff 00000000`0001764a 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`03ee89e0 fffff880`0fded437 : 00000000`00000102 00000000`00000000 00000000`0001764a 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`03ee8a10 fffff880`0fdc02d2 : ffffffff`ff676980 fffffa80`0907d010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`03ee8ab0 fffff880`0fdecff6 : 00000000`00000000 fffffa80`07932a70 00000000`00000080 fffffa80`0907d010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`03ee8bc0 fffff800`031142ea : 00000000`fffffc32 fffffa80`0812fb50 fffffa80`066a5040 fffffa80`0812fb50 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`03ee8c00 fffff800`02e688e6 : fffff800`02ff2e80 fffffa80`0812fb50 fffff800`03000cc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03ee8c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmpag+bd88
fffff880`02c3ad88 4883ec28        sub     rsp,28h

SYMBOL_NAME:  atikmpag+bd88

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  52a231d9

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x116_image_atikmpag.sys

FAILURE_ID_HASH:  {83e844bc-fe68-2042-4230-7f5d3e90b48a}

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

2: kd> lmvm atikmpag
start             end                 module name
fffff880`02c2f000 fffff880`02ccf000   atikmpag T (no symbols)           
    Loaded symbol image file: atikmpag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
    Image name: atikmpag.sys
    Timestamp:        Sat Dec 07 01:51:45 2013 (52A231D9)
    CheckSum:         0009FEFF
    ImageSize:        000A0000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

http://pcsupport.about.com/od/fixtheproblem/tp/clearcmos.htm

 

[Hextall27]

Thank you for your reply.

1. I am not overclocking any components of my PC, so that isn't the issue.

2. I have a 550 watt XFX power supply. eXtreme Power Supply Calculator recommends 278 watts for my PC, so I don't think that is the problem.

3. The computer is not running hot. Using speedfan and speccy on separate occasions, my components run between 20-30C at idle, and between 30-38C during normal usage. My GPU goes up to between 50 and 60C during gaming, so I don't think that heat is the problem.

4. I ran furmark for 20 minutes a few days ago and again for an hour today. My GPU did not exceed 70C and it did not crash.

I am at a complete loss. The crashes only come a few minutes into playing any game. I can watch videos or run furmark without issue. Is there anything else you can suggest? I would gladly format my hard drive, but according to the following post a fresh install doesn't help the problem. (Annoying BSOD and driver crash (dxgkrnl.sys+5d140) - Radeon - Graphics & Displays)

 

[Arc]

Screenshot of Speccy and Furmark is needed to support your statements.

 

[Hextall27]

The forum wouldn't allow me to upload the Speccy files, but I have jpg screenshots of furmark, speccy, and speedfan. They confirm the temps I posted previously.

Speccy claims that my gpu is receiving .825 Volts, could this cause my problem?

 

[Arc]

Can you run the 15 minutes full resolution benchmark test?

View attachment 304055