Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD happen every turn on my laptop from sleep 15 - 30 minutes

23 Feb 2014   #1
Nobodies

Windows 7 Professional x64
 
 
BSOD happen every turn on my laptop from sleep 15 - 30 minutes

I'm using laptop ASUS X43U and VGA ATI Radeon HD 6310M. My BSOD usually appear when i make my laptop sleep for 15 - 20 minutes. Then after turn on, first black windows with only cursor appear and then BSOD started. I just saw atikmpag.sys and time calculated until 100 then restart and after restart i got information "Your Windows is not shutdown normally. There is 3 option : 1. Start Windows normally. 2 and 3 i forgot but i see there is option "Safe Mode". Any solution what happen with my laptop ? For information i always use this laptop for 3 hours. Every 3 hours i make sleep 15 minutes and use this laptop 3 - 6 hours. I guess i must update driver VGA but when i go web AMD and i choose software Automatically and Detect and use it, that software didn't download which right driver VGA for me.


My System SpecsSystem Spec
.
24 Feb 2014   #2
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

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

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
My System SpecsSystem Spec
24 Feb 2014   #3
essenbe

Windows 7 Enterprise X64/Windows 10 Enterprise X64/Windows 10 Pro X64/Linux Mint
 
 

Hello Nobodies, I am far from a laptop expert, although I do own 2 of them. I am more of a desktop person. I would like to ask a couple of questions. How do you put your laptop to sleep? How do you wake it up? What USB devices do you have plugged in when you have this problem? As Arc said, it is not an uncommon problem of being unable to wake up from sleep. Some have found that it is a USB problem and some have found that it is the method you use to wake it. It is a trial and error thing, usually. The bios version you are running can be a factor too. Do you have the latest bios version and are you using the latest display driver from Asus?

The issue with switchable graphics is a very tricky one. The AMD or Nvidia site (depending on which card you have), AMD in your case, make drivers for switchable graphics and the most recent driver can be found there usually. However, most manufacturers change the implementation of exactly how the switchable graphics work. So, with my Nvidia Optimus graphics, I have found that the manufacturers' drivers work much better than the Nvidia drivers because the manufacturer modifies the drivers to use their implementation of switchable graphics.

What I would like you to try is to update to the latest bios from Asus web site and the latest graphics drivers from Asus, and then try different ways of putting it to sleep and different ways of waking it up. Before putting it to sleep, unplug any USB devices. You can usually wake it up by, using the track pad, using the left click button or hitting a key on the keyboard. Some use the power button. See if any of those ways of waking it makes a difference. Sometimes if your laptop goes into sleep mode by simply closing the lid, opening the lid will wake it, you just have to give it a few seconds to respond. Let us know if any of the different ways of putting it to sleep or waking it makes any difference.
My System SpecsSystem Spec
.

25 Feb 2014   #4
Nobodies

Windows 7 Professional x64
 
 

Quote   Quote: Originally Posted by Arc View Post
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: Speccy - Publish Snapshot of your System Specs .

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
OK i'll answer ur question :
1. Is the computer hot?
My Speccy64.exe(because i use win7 x64) said this :
http://speccy.piriform.com/results/A...ENVEGRflSqvbHH
tab Graphics sometimes show 60 - 65 degree but i just browsing and sometimes play game
i test in 3 - 5 hours.


Quote   Quote: Originally Posted by essenbe View Post
Hello Nobodies, I am far from a laptop expert, although I do own 2 of them. I am more of a desktop person. I would like to ask a couple of questions. How do you put your laptop to sleep? How do you wake it up? What USB devices do you have plugged in when you have this problem? As Arc said, it is not an uncommon problem of being unable to wake up from sleep. Some have found that it is a USB problem and some have found that it is the method you use to wake it. It is a trial and error thing, usually. The bios version you are running can be a factor too. Do you have the latest bios version and are you using the latest display driver from Asus?

The issue with switchable graphics is a very tricky one. The AMD or Nvidia site (depending on which card you have), AMD in your case, make drivers for switchable graphics and the most recent driver can be found there usually. However, most manufacturers change the implementation of exactly how the switchable graphics work. So, with my Nvidia Optimus graphics, I have found that the manufacturers' drivers work much better than the Nvidia drivers because the manufacturer modifies the drivers to use their implementation of switchable graphics.

What I would like you to try is to update to the latest bios from Asus web site and the latest graphics drivers from Asus, and then try different ways of putting it to sleep and different ways of waking it up. Before putting it to sleep, unplug any USB devices. You can usually wake it up by, using the track pad, using the left click button or hitting a key on the keyboard. Some use the power button. See if any of those ways of waking it makes a difference. Sometimes if your laptop goes into sleep mode by simply closing the lid, opening the lid will wake it, you just have to give it a few seconds to respond. Let us know if any of the different ways of putting it to sleep or waking it makes any difference.
OK i'll answer ur question :
1. How do you put your laptop to sleep?
I just press Fn + F1 or sometimes Menu Start > Tab Shutdown > Sleep
but sometimes after 1 - 2 second after sleep, my laptop automatically wake up so i must put to sleep again
2. How do you wake it up?
Only press Enter
3. What USB devices do you have plugged in when you have this problem?
Ah, i forgot to said, i think my BSOD always happen together with my plugged modem USB to connect online. so when i put my laptop to sleep, my modem USB still plugged in to my laptop.
this is my modem :

4. Do you have the latest bios version and are you using the latest display driver from Asus?
When i check my support in ASUSTeK Computer Inc. -Support- Drivers and Download X43U i saw BIOS version 223 (newer 2012.05.18 update), 221, 217 and file size is only 1.4 MBytes. Did i must download all version or just newer version.
When i check my BIOS version on System Information (msinfo32.exe) i found my BIOS version : American Megatrends Inc.223, 10-Apr-12
so my BIOS is up-to-date, right?
I didn't found any driver VGA on ASUS support so i download manual from web AMD. I just download 13-12_mobility_win7_win8_64_dd_ccc_whql.exe from AMD from this thread Latest AMD Catalyst Video Driver for Windows 7
so my driver is up-to-date, right?

The issue with switchable graphics is a very tricky one. The AMD or Nvidia site (depending on which card you have), AMD in your case, make drivers for switchable graphics and the most recent driver can be found there usually. However, most manufacturers change the implementation of exactly how the switchable graphics work. So, with my Nvidia Optimus graphics, I have found that the manufacturers' drivers work much better than the Nvidia drivers because the manufacturer modifies the drivers to use their implementation of switchable graphics.

What I would like you to try is to update to the latest bios from Asus web site and the latest graphics drivers from Asus, and then try different ways of putting it to sleep and different ways of waking it up. Before putting it to sleep, unplug any USB devices. You can usually wake it up by, using the track pad, using the left click button or hitting a key on the keyboard. Some use the power button. See if any of those ways of waking it makes a difference. Sometimes if your laptop goes into sleep mode by simply closing the lid, opening the lid will wake it, you just have to give it a few seconds to respond. Let us know if any of the different ways of putting it to sleep or waking it makes any difference.
My System SpecsSystem Spec
25 Feb 2014   #5
essenbe

Windows 7 Enterprise X64/Windows 10 Enterprise X64/Windows 10 Pro X64/Linux Mint
 
 

I didn't see any graphics drivers on Asus site either, which is strange unless they are incorporated into the chipset driver. You can experiment with different ways of waking the laptop from sleep to see if any make a difference. I would try unplugging the USB Modem before putting it to sleep and re attaching it after wake up and see if that helps. I would just experiment with it to find a way around this problem. This is not an uncommon problem with laptops and the manufacturers know about it. I would think it should be reasonable to expect them to come up with a solution to the problem, but they don't. It is not only Asus, it is most manufacturers.
My System SpecsSystem Spec
07 Mar 2014   #6
Nobodies

Windows 7 Professional x64
 
 

problem solved, thank you. looks like my USB modem make BSOD
My System SpecsSystem Spec
07 Mar 2014   #7
essenbe

Windows 7 Enterprise X64/Windows 10 Enterprise X64/Windows 10 Pro X64/Linux Mint
 
 

I'm glad you have it fixed and hope it stays fixed. Good job, well done.
My System SpecsSystem Spec
13 Mar 2014   #8
Nobodies

Windows 7 Professional x64
 
 

Quote   Quote: Originally Posted by essenbe View Post
Hello Nobodies, I am far from a laptop expert, although I do own 2 of them. I am more of a desktop person. I would like to ask a couple of questions. How do you put your laptop to sleep? How do you wake it up? What USB devices do you have plugged in when you have this problem? As Arc said, it is not an uncommon problem of being unable to wake up from sleep. Some have found that it is a USB problem and some have found that it is the method you use to wake it. It is a trial and error thing, usually. The bios version you are running can be a factor too. Do you have the latest bios version and are you using the latest display driver from Asus?
today i got 2 BSOD again -_-"
i bold ur quote.
how can be any USB plugged in and method i use to wake up can make BSOD?

my first BSOD came again same with my first problem :
i didn't unplug USB mouse and i press button sleep by Start Menu then after i press Enter to wake up, BSOD come again

my second BSOD came when i didn't use laptop for 20 minutes and automatic sleep. I press Enter to wake it, then blank screen with cursor appear. I can't move that cursor and then after 1 minutes, BSOD come again
My System SpecsSystem Spec
13 Mar 2014   #9
essenbe

Windows 7 Enterprise X64/Windows 10 Enterprise X64/Windows 10 Pro X64/Linux Mint
 
 

Nobodies, I can't tell you why it happens. But, in reading on the problem, those are common solutions I have found, where solutions are found. The problem itself is not uncommon, but solutions vary. USB seems to be the most frequent cause in what I have read.
My System SpecsSystem Spec
13 Mar 2014   #10
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

But the crash dumps are not going with the expressions. Those point it to be a display issue. As like earlier.
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa8004079010, fffff880042bad88, 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+bd88 )

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: fffffa8004079010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff880042bad88, 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`042bad88 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`02359898 fffff880`03a88140 : 00000000`00000116 fffffa80`04079010 fffff880`042bad88 00000000`00000000 : nt!KeBugCheckEx
fffff880`023598a0 fffff880`03a87e4a : fffff880`042bad88 fffffa80`04079010 fffffa80`05b31d50 fffffa80`05b502c0 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`023598e0 fffff880`03b2ef13 : fffffa80`04079010 00000000`00000000 fffffa80`05b31d50 fffffa80`05b502c0 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`02359910 fffff880`03b5ced6 : 00000000`ffffffff 00000000`0002da4d fffff880`02359a70 fffffa80`05b502c0 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`023599f0 fffff880`03b5882b : fffffa80`05b502c0 ffffffff`feced300 00000000`00000002 00005dd6`00000003 : dxgmms1!VidSchWaitForCompletionEvent+0x196
fffff880`02359a30 fffff880`03b5719f : fffffa80`05b502c0 00000000`00000002 fffff880`03b56f3c 00000000`00000000 : dxgmms1!VidSchiWaitForEmptyHwQueue+0x8f
fffff880`02359b20 fffff880`03b5747a : 00000000`00000000 00000000`00000002 00000000`00000002 00000000`00000000 : dxgmms1!VidSchiHandleControlEvent+0x3b
fffff880`02359b50 fffff880`03b2a2d2 : ffffffff`ff676980 fffffa80`05b502c0 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x23e
fffff880`02359bf0 fffff880`03b56ff6 : 00000000`00000000 fffffa80`05b31d50 00000000`00000080 fffffa80`05b502c0 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`02359d00 fffff800`031632ea : 00000000`fffffc32 fffffa80`059c54c0 fffffa80`03c9d890 fffffa80`059c54c0 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`02359d40 fffff800`02eb78e6 : fffff880`009eb180 fffffa80`059c54c0 fffff880`009f5f40 6f635174`37786251 : nt!PspSystemThreadStartup+0x5a
fffff880`02359d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmpag+bd88
fffff880`042bad88 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
---------

0: kd> lmvm atikmpag
start             end                 module name
fffff880`042af000 fffff880`0434f000   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
My System SpecsSystem Spec
Reply

 BSOD happen every turn on my laptop from sleep 15 - 30 minutes




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
Laptop extremely slow to wake up from sleep mode, 5+ minutes to wake
Hi, I am new here. Hoping someone can help me out with this issue. I work in IT so am not a complete computer bonehead and am at my wits end with this. My laptop is about 4 years old, it's a toshiba. For whatever reason, it started taking 5+ minutes to wake up from sleeping. If it sleeps...
Performance & Maintenance
Windows shuts off but laptop wont turn off or go to sleep.
Hi, I Have Hp Pavilion dv6-6120us and recently I notice that windows 7 shuts off but my computer stays on, the fan hard disc and lights stay on also, if I put my computer to sleep it wont wake up i have to hold the power button off for 10 seconds and restart the computer. I uninstalled all...
General Discussion
BSOD 5 minutes after startup from sleep or shutdown every day
I am having some trouble out of my Windows 7 Pro computer. I use my computer continuously throughout every day. When I wake it up the next morning from sleep (or even from a shutdown state) mode everything works fine for about 5-10 minutes then I receive the BSOD almost on schedule! Once it...
BSOD Help and Support
BSOD a few minutes after wake from sleep
Hi, I have a new machine built almost three months ago and I've occasionally gotten BSODs but they've increased in the past couple of weeks usually a few minutes after I wake the machine from sleep. One BSOD error said something about USBScan.sys with error 0x0000000A. Thanks very much. my...
BSOD Help and Support
Laptop doesnt turn off when going into sleep/hibernate
Hello, My laptop is an MSI Gx660, running windows 7 64bit with 12gb ram. The laptop is only 1-2months old and My harddisk has very little files with about 205gb free on the C drive. After using for a long period of time like 6-7hours, I would usually put my laptop into hibernate mode. When...
General Discussion
BSOD every time I turn on my comp after about 5 minutes
I had 6 dumps within 20 minutes (each time my laptop reboots). I have attached them all in a zip file. Please help me! Thanks so much.
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 13:41.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App