Hi Nobodies.
This is not an usual situation of a BSOD. I have never seen a stop 0x116 upon wake-up. Though display crash at wake-up is most common, but it comes with a different bugcheck code. Whereas a stop 0x116 is theoretically a display failure, not a wake-up failure.
It also appears from the supplied data that your computer ASUS K43U is having AMD Radeon HD 6310, which is an integrated graphics chip in the AMD E-350 APU processor, not having any dedicated memory.
When the integrated processor graphics fails, it is not a good sign.
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 .
Follow the "Automatically Detect and Install" option in
Download Drivers, update the version of the display driver.
Let us know the results.
* I requested
essenbe to have a look at the issue, too.
_______________________________________________
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 116, {fffffa8004e694e0, fffff88003f3de5c, 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+ae5c )
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: fffffa8004e694e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88003f3de5c, 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+ae5c
fffff880`03f3de5c 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`023659c8 fffff880`11ce5140 : 00000000`00000116 fffffa80`04e694e0 fffff880`03f3de5c 00000000`00000000 : nt!KeBugCheckEx
fffff880`023659d0 fffff880`11ce4e4a : fffff880`03f3de5c fffffa80`04e694e0 fffffa80`0644dd50 fffffa80`05aee410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`02365a10 fffff880`11d8bf13 : fffffa80`04e694e0 00000000`00000000 fffffa80`0644dd50 fffffa80`05aee410 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`02365a40 fffff880`11db5cf1 : 00000000`ffffffff 00000000`000df4ac 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`02365b20 fffff880`11db4437 : 00000000`00000102 00000000`00000000 00000000`000df4ac 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`02365b50 fffff880`11d872d2 : ffffffff`ff676980 fffffa80`05aee410 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`02365bf0 fffff880`11db3ff6 : 00000000`00000000 fffffa80`04ed9950 00000000`00000080 fffffa80`05aee410 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`02365d00 fffff800`031262ea : 00000000`fffffc32 fffffa80`05963b50 fffffa80`03c9d890 fffffa80`05963b50 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`02365d40 fffff800`02e7a8e6 : fffff800`03004e80 fffffa80`05963b50 fffff800`03012cc0 fffff880`02365e40 : nt!PspSystemThreadStartup+0x5a
fffff880`02365d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
atikmpag+ae5c
fffff880`03f3de5c 4883ec28 sub rsp,28h
SYMBOL_NAME: atikmpag+ae5c
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: atikmpag
IMAGE_NAME: atikmpag.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 52211d80
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`03f33000 fffff880`03fd1000 atikmpag T (no symbols)
Loaded symbol image file: atikmpag.sys
Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
Image name: atikmpag.sys
Timestamp: Sat Aug 31 04:02:32 2013 (52211D80)
CheckSum: 0009C9D2
ImageSize: 0009E000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
