BSOD mostly on wake from sleep mode

Hi Stevros.

Yes, you are right ... a stop 0x116 is a display/graphics related issue. But this part of your post caught my attention:

Stevros said:

The BSOD tells me that a display driver has failed or is not responding.

Are you having any popup balloon like this?



Let us know.

You are overclocking.

Code:

CPUID:        "Intel(R) Core(TM) i7 CPU         920  @ 2.67GHz"
MaxSpeed:     2670
CurrentSpeed: 2800

As you are getting BSODs, you should stop overclocking and run all the hardware components like CPU, GPU and RAM to their default settings. See how it goes with stock hardware settings.

I see that the problem occurred with multiple versions of the display driver, latter 13.9 WHQL. Let us see how it works with this version.

Uninstall your installed latest version of the display driver.

• How-To Uninstall AMD Catalyst Drivers From A Windows Based System

Then clean up any possible leftover.

• Drivers - Clean Left over Files after Uninstalling

Then install version 13.9 WHQL only.

• Previous AMD Catalyst? Display Drivers

When the driver is applied, stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

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 the 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: Speccy - Publish Snapshot of your System Specs .
___________________________

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa8005ba64e0, fffff880048d9dac, 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+bdac )

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: fffffa8005ba64e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff880048d9dac, 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+bdac
fffff880`048d9dac 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`060a79c8 fffff880`02c65140 : 00000000`00000116 fffffa80`05ba64e0 fffff880`048d9dac 00000000`00000000 : nt!KeBugCheckEx
fffff880`060a79d0 fffff880`02c64e4a : fffff880`048d9dac fffffa80`05ba64e0 fffffa80`053dc2e0 fffffa80`07e52410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`060a7a10 fffff880`02d0bf13 : fffffa80`05ba64e0 00000000`00000000 fffffa80`053dc2e0 fffffa80`07e52410 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`060a7a40 fffff880`02d35cf1 : 00000000`ffffffff 00000000`0000bc6b 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`060a7b20 fffff880`02d34437 : 00000000`00000102 00000000`00000000 00000000`0000bc6b 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`060a7b50 fffff880`02d072d2 : ffffffff`ff676980 fffffa80`07e52410 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`060a7bf0 fffff880`02d33ff6 : 00000000`00000000 fffffa80`05ff7010 00000000`00000080 fffffa80`07e52410 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`060a7d00 fffff800`0431a73a : 00000000`fffffc32 fffffa80`07e63060 fffffa80`04eea040 fffffa80`07e63060 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`060a7d40 fffff800`0406f8e6 : fffff880`03087180 fffffa80`07e63060 fffff880`030920c0 fffffa80`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`060a7d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmpag+bdac
fffff880`048d9dac 4883ec28        sub     rsp,28h

SYMBOL_NAME:  atikmpag+bdac

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  53507abb

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
---------

0: kd> lmvm atikmpag
start             end                 module name
fffff880`048ce000 fffff880`04971000   atikmpag T (no symbols)           
    Loaded symbol image file: atikmpag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
    Image name: atikmpag.sys
    Timestamp:        Fri Apr 18 06:37:07 2014 (53507ABB)
    CheckSum:         000A6939
    ImageSize:        000A3000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4