Navigation section

Windows 7 BSOD on wakeup from sleep

S

semz

New Member
Joined
May 11, 2011
Messages
2
Hi,

I'm hoping to get some help. About a month ago my pc started going to BSOD while trying to resume after being put to sleep. PC is 16 months old. I read the forums, etc and updated the ATI radeon display driver and the Realtek network driver but the problem persisted.

I also rolled back the system using restore to before the problem began but no change. I then reinstalled windows 7 64bit using the OEM CD rom and installed all the MS updates - no change. Last week, it occurred to me that it might be a monitor hw issue so I swapped out the monitor with another I had. That seemed to solve it - for 4 days - now it's doing the same thing with the second monitor.

I've attached the zipfile with the CPU-z report and minidmp. I also added a perfmon report and msinfo.

Appreciate any insight -
Bob
 


Attachments

Sort by date Sort by votes
to get an idea while i get the crash dumps debugged,

POSSIBLE CAUSE atikmpag.sys ( atikmpag+73bc

seems like a graphics card driver fault,

will get u more information shortly


have u installed the correct drivers?
 


Last edited:
Upvote 0 Downvote
As an idea also to see if its not a faulty card, try and use your on board graphics, take out the card out of the pc and see if it blue screens after sleeping
 


Upvote 0 Downvote
Further to kaos's post, make sure you have the latest drivers. There were issues with v11.4 I believe. Also when updating your drivers run Driver Sweeper in Safe Mode to make sure no remnants of old drivers remain before installing your new drivers.
You're getting a lot of Stops 116 & 117 which are all video related. This link may help you to begin troubleshooting:
 


Upvote 0 Downvote
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa8009d17010, fffff880044723bc, 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+73bc )

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

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8009d17010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff880044723bc, 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+73bc
fffff880`044723bc 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`021359c8 fffff880`04516000 : 00000000`00000116 fffffa80`09d17010 fffff880`044723bc 00000000`00000000 : nt!KeBugCheckEx
fffff880`021359d0 fffff880`04515d0a : fffff880`044723bc fffffa80`09d17010 fffffa80`0979ac00 fffffa80`09067010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`02135a10 fffff880`0513df07 : fffffa80`09d17010 00000000`00000000 fffffa80`0979ac00 fffffa80`09067010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`02135a40 fffff880`05167b75 : 00000000`ffffffff 00000000`0000072a 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`02135b20 fffff880`051662bb : 00000000`00000102 00000000`00000000 00000000`0000072a 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`02135b50 fffff880`051392c6 : ffffffff`ff676980 fffffa80`09067010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`02135bf0 fffff880`05165e7a : 00000000`00000000 00000000`0000000f 00000000`00000080 fffffa80`0963bc68 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`02135d00 fffff800`02d27cce : 00000000`04ab7453 fffffa80`09612770 fffffa80`066a5990 fffffa80`09612770 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`02135d40 fffff800`02a7bfe6 : fffff880`030a4180 fffffa80`09612770 fffff880`030af0c0 54582031`3834522c : nt!PspSystemThreadStartup+0x5a
fffff880`02135d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
atikmpag+73bc
fffff880`044723bc 4883ec28 sub rsp,28h

SYMBOL_NAME: atikmpag+73bc

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME: atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4d409c8d

FAILURE_BUCKET_ID: X64_0x116_IMAGE_atikmpag.sys

BUCKET_ID: X64_0x116_IMAGE_atikmpag.sys

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

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8009d17010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff880044723bc, 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+73bc
fffff880`044723bc 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`021359c8 fffff880`04516000 : 00000000`00000116 fffffa80`09d17010 fffff880`044723bc 00000000`00000000 : nt!KeBugCheckEx
fffff880`021359d0 fffff880`04515d0a : fffff880`044723bc fffffa80`09d17010 fffffa80`0979ac00 fffffa80`09067010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`02135a10 fffff880`0513df07 : fffffa80`09d17010 00000000`00000000 fffffa80`0979ac00 fffffa80`09067010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`02135a40 fffff880`05167b75 : 00000000`ffffffff 00000000`0000072a 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`02135b20 fffff880`051662bb : 00000000`00000102 00000000`00000000 00000000`0000072a 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`02135b50 fffff880`051392c6 : ffffffff`ff676980 fffffa80`09067010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`02135bf0 fffff880`05165e7a : 00000000`00000000 00000000`0000000f 00000000`00000080 fffffa80`0963bc68 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`02135d00 fffff800`02d27cce : 00000000`04ab7453 fffffa80`09612770 fffffa80`066a5990 fffffa80`09612770 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`02135d40 fffff800`02a7bfe6 : fffff880`030a4180 fffffa80`09612770 fffff880`030af0c0 54582031`3834522c : nt!PspSystemThreadStartup+0x5a
fffff880`02135d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
atikmpag+73bc
fffff880`044723bc 4883ec28 sub rsp,28h

SYMBOL_NAME: atikmpag+73bc

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME: atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4d409c8d

FAILURE_BUCKET_ID: X64_0x116_IMAGE_atikmpag.sys

BUCKET_ID: X64_0x116_IMAGE_atikmpag.sys
 


Upvote 0 Downvote
116 and 117, graphic driver did not respond in a timely fashion.

Possible causers:

- defective videocard
- bad or improperly installed video driver. Try reinstalling it with the use of the driver sweeper, see Elmer's post above.
- overclocked (as well as underclocked) hardware, videocard, CPU, memory, but in this case typical codes would be a combination of 124, 116, 3B. Yet, make sure everything is at stock as recommended by the manufacturer.
- overheating


CRASH DUMPS

Code: 
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [F:\DMP\050211-59514-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02a0d000 PsLoadedModuleList = 0xfffff800`02c52e90
Debug session time: Mon May  2 10:17:45.034 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:57.829
Loading Kernel Symbols
...............................................................
.............................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 117, {fffffa8009883010, fffff880042633bc, 0, 0}

*** 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+73bc )

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

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

VIDEO_TDR_TIMEOUT_DETECTED (117)
The display driver failed to respond in timely fashion.
(This code can never be used for real bugcheck).
Arguments:
Arg1: fffffa8009883010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff880042633bc, The pointer into responsible device driver module (e.g owner tag).
Arg3: 0000000000000000, The secondary driver specific bucketing key.
Arg4: 0000000000000000, Optional internal context dependent data.

Debugging Details:
------------------


FAULTING_IP: 
atikmpag+73bc
fffff880`042633bc ??              ???

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_TIMEOUT

TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b


CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x117

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`03ef04a0 fffff880`043055f7 : fffffa80`09883010 fffff880`043053d8 fffffa80`09460950 fffff880`04305061 : watchdog!WdDbgReportRecreate+0xa3
fffff880`03ef09c0 fffff880`04306c87 : fffffa80`09883010 fffffa80`09883010 fffffa80`09460950 00000000`00000000 : dxgkrnl!TdrUpdateDbgReport+0xcb
fffff880`03ef0a10 fffff880`0516df07 : fffffa80`09883010 00000000`00000e75 fffffa80`09460950 fffffa80`06722410 : dxgkrnl!TdrIsRecoveryRequired+0x11f
fffff880`03ef0a40 fffff880`05197b75 : 00000000`ffffffff 00000000`00000bb4 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`03ef0b20 fffff880`051962bb : 00000000`00000102 00000000`00000000 00000000`00000bb4 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`03ef0b50 fffff880`051692c6 : ffffffff`ff676980 fffffa80`06722410 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`03ef0bf0 fffff880`05195e7a : 00000000`00000000 00000000`0000000f 00000000`00000080 fffffa80`093cdb38 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`03ef0d00 fffff800`02d2acce : 00000000`07ad1a1d fffffa80`0979bb60 fffffa80`066a5990 fffffa80`0979bb60 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`03ef0d40 fffff800`02a7efe6 : fffff880`009e8180 fffffa80`0979bb60 fffff880`009f30c0 fffff880`0125e384 : nt!PspSystemThreadStartup+0x5a
fffff880`03ef0d80 00000000`00000000 : fffff880`03ef1000 fffff880`03eeb000 fffff880`03eef860 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmpag+73bc
fffff880`042633bc ??              ???

SYMBOL_NAME:  atikmpag+73bc

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d409c8d

FAILURE_BUCKET_ID:  X64_0x117_IMAGE_atikmpag.sys

BUCKET_ID:  X64_0x117_IMAGE_atikmpag.sys

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




Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [F:\DMP\050211-59561-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02a54000 PsLoadedModuleList = 0xfffff800`02c99e90
Debug session time: Mon May  2 10:20:04.597 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:57.503
Loading Kernel Symbols
...............................................................
.............................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 117, {fffffa80096e2010, fffff88002ec53bc, 0, 0}

*** 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+73bc )

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

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

VIDEO_TDR_TIMEOUT_DETECTED (117)
The display driver failed to respond in timely fashion.
(This code can never be used for real bugcheck).
Arguments:
Arg1: fffffa80096e2010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88002ec53bc, The pointer into responsible device driver module (e.g owner tag).
Arg3: 0000000000000000, The secondary driver specific bucketing key.
Arg4: 0000000000000000, Optional internal context dependent data.

Debugging Details:
------------------


FAULTING_IP: 
atikmpag+73bc
fffff880`02ec53bc ??              ???

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_TIMEOUT

TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b


CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x117

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`042f04a0 fffff880`02f675f7 : fffffa80`096e2010 fffff880`02f673d8 fffffa80`095a8d50 fffff880`02f67061 : watchdog!WdDbgReportRecreate+0xa3
fffff880`042f09c0 fffff880`02f68c87 : fffffa80`096e2010 fffffa80`096e2010 fffffa80`095a8d50 00000000`00000000 : dxgkrnl!TdrUpdateDbgReport+0xcb
fffff880`042f0a10 fffff880`0534af07 : fffffa80`096e2010 00000000`00000e5f fffffa80`095a8d50 fffffa80`08ca6410 : dxgkrnl!TdrIsRecoveryRequired+0x11f
fffff880`042f0a40 fffff880`05374b75 : 00000000`ffffffff 00000000`00000b9e 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`042f0b20 fffff880`053732bb : 00000000`00000102 00000000`00000000 00000000`00000b9e 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`042f0b50 fffff880`053462c6 : ffffffff`ff676980 fffffa80`08ca6410 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`042f0bf0 fffff880`05372e7a : 00000000`00000000 00000000`0000000f 00000000`00000080 fffffa80`095a9c68 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`042f0d00 fffff800`02d71cce : 00000000`07a07e46 fffffa80`0929ab60 fffffa80`066a5890 fffffa80`0929ab60 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`042f0d40 fffff800`02ac5fe6 : fffff800`02c46e80 fffffa80`0929ab60 fffff800`02c54cc0 fffff880`01224384 : nt!PspSystemThreadStartup+0x5a
fffff880`042f0d80 00000000`00000000 : fffff880`042f1000 fffff880`042eb000 fffff880`042ef860 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmpag+73bc
fffff880`02ec53bc ??              ???

SYMBOL_NAME:  atikmpag+73bc

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d409c8d

FAILURE_BUCKET_ID:  X64_0x117_IMAGE_atikmpag.sys

BUCKET_ID:  X64_0x117_IMAGE_atikmpag.sys

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




Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [F:\DMP\050211-60325-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02a4f000 PsLoadedModuleList = 0xfffff800`02c94e90
Debug session time: Mon May  2 10:24:45.315 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:58.220
Loading Kernel Symbols
...............................................................
.............................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 117, {fffffa80098254e0, fffff88002eef3bc, 0, 0}

Unable to load image 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+73bc )

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

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

VIDEO_TDR_TIMEOUT_DETECTED (117)
The display driver failed to respond in timely fashion.
(This code can never be used for real bugcheck).
Arguments:
Arg1: fffffa80098254e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88002eef3bc, The pointer into responsible device driver module (e.g owner tag).
Arg3: 0000000000000000, The secondary driver specific bucketing key.
Arg4: 0000000000000000, Optional internal context dependent data.

Debugging Details:
------------------


FAULTING_IP: 
atikmpag+73bc
fffff880`02eef3bc ??              ???

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_TIMEOUT

TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b


CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x117

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`045294a0 fffff880`03ee35f7 : fffffa80`098254e0 fffff880`03ee33d8 fffffa80`0935db10 fffff880`03ee3061 : watchdog!WdDbgReportRecreate+0xa3
fffff880`045299c0 fffff880`03ee4c87 : fffffa80`098254e0 fffffa80`098254e0 fffffa80`0935db10 00000000`00000000 : dxgkrnl!TdrUpdateDbgReport+0xcb
fffff880`04529a10 fffff880`03f8bf07 : fffffa80`098254e0 00000000`00000e8e fffffa80`0935db10 fffffa80`094c9010 : dxgkrnl!TdrIsRecoveryRequired+0x11f
fffff880`04529a40 fffff880`03fb5b75 : 00000000`ffffffff 00000000`00000bcd 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`04529b20 fffff880`03fb42bb : 00000000`00000102 00000000`00000000 00000000`00000bcd 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`04529b50 fffff880`03f872c6 : ffffffff`ff676980 fffffa80`094c9010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`04529bf0 fffff880`03fb3e7a : 00000000`00000000 00000000`0000000f 00000000`00000080 fffffa80`090d3c68 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`04529d00 fffff800`02d6ccce : 00000000`07bf476d fffffa80`0946fb60 fffffa80`066a5890 fffffa80`0946fb60 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`04529d40 fffff800`02ac0fe6 : fffff800`02c41e80 fffffa80`0946fb60 fffff800`02c4fcc0 fffff880`0124b384 : nt!PspSystemThreadStartup+0x5a
fffff880`04529d80 00000000`00000000 : fffff880`0452a000 fffff880`04524000 fffff880`04528860 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmpag+73bc
fffff880`02eef3bc ??              ???

SYMBOL_NAME:  atikmpag+73bc

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d409c8d

FAILURE_BUCKET_ID:  X64_0x117_IMAGE_atikmpag.sys

BUCKET_ID:  X64_0x117_IMAGE_atikmpag.sys

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




Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [F:\DMP\050911-32136-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02a62000 PsLoadedModuleList = 0xfffff800`02ca7e90
Debug session time: Mon May  9 18:09:36.815 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:38.720
Loading Kernel Symbols
...............................................................
................................................................

Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa8009e49010, fffff880046b4408, 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+7408 )

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

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8009e49010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff880046b4408, 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+7408
fffff880`046b4408 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`06beb9c8 fffff880`04759000 : 00000000`00000116 fffffa80`09e49010 fffff880`046b4408 00000000`00000000 : nt!KeBugCheckEx
fffff880`06beb9d0 fffff880`04758d0a : fffff880`046b4408 fffffa80`09e49010 fffffa80`0982c950 fffffa80`0671a410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`06beba10 fffff880`04a0ff07 : fffffa80`09e49010 00000000`00000000 fffffa80`0982c950 fffffa80`0671a410 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`06beba40 fffff880`04a39b75 : 00000000`ffffffff 00000000`00000699 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`06bebb20 fffff880`04a382bb : 00000000`00000102 00000000`00000000 00000000`00000699 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`06bebb50 fffff880`04a0b2c6 : ffffffff`ff676980 fffffa80`0671a410 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`06bebbf0 fffff880`04a37e7a : 00000000`00000000 00000000`0000000f 00000000`00000080 fffffa80`09805c68 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`06bebd00 fffff800`02d7fcce : 00000000`04473589 fffffa80`09826b60 fffffa80`066a5890 fffffa80`09826b60 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`06bebd40 fffff800`02ad3fe6 : fffff880`032a4180 fffffa80`09826b60 fffff880`032af0c0 6d6f6d62`356a3875 : nt!PspSystemThreadStartup+0x5a
fffff880`06bebd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmpag+7408
fffff880`046b4408 4883ec28        sub     rsp,28h

SYMBOL_NAME:  atikmpag+7408

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d9bc027

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

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




Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [F:\DMP\050911-32931-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02a09000 PsLoadedModuleList = 0xfffff800`02c4ee90
Debug session time: Mon May  9 18:08:05.910 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:37.831
Loading Kernel Symbols
...............................................................
................................................................
..
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa8009734010, fffff88004407408, 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+7408 )

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

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8009734010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88004407408, 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+7408
fffff880`04407408 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`023569c8 fffff880`044ac000 : 00000000`00000116 fffffa80`09734010 fffff880`04407408 00000000`00000000 : nt!KeBugCheckEx
fffff880`023569d0 fffff880`044abd0a : fffff880`04407408 fffffa80`09734010 fffffa80`09847c00 fffffa80`0984a010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`02356a10 fffff880`05387f07 : fffffa80`09734010 00000000`00000000 fffffa80`09847c00 fffffa80`0984a010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`02356a40 fffff880`053b1b75 : 00000000`ffffffff 00000000`00000619 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`02356b20 fffff880`053b02bb : 00000000`00000102 00000000`00000000 00000000`00000619 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`02356b50 fffff880`053832c6 : ffffffff`ff676980 fffffa80`0984a010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`02356bf0 fffff880`053afe7a : 00000000`00000000 00000000`0000000f 00000000`00000080 fffffa80`097227c8 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`02356d00 fffff800`02d26cce : 00000000`03ef972b fffffa80`0984b620 fffffa80`066a5890 fffffa80`0984b620 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`02356d40 fffff800`02a7afe6 : fffff880`032a4180 fffffa80`0984b620 fffff880`032af0c0 fffff880`0123ca20 : nt!PspSystemThreadStartup+0x5a
fffff880`02356d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmpag+7408
fffff880`04407408 4883ec28        sub     rsp,28h

SYMBOL_NAME:  atikmpag+7408

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d9bc027

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys

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




Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [F:\DMP\051111-30903-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0xfffff800`02a4c000 PsLoadedModuleList = 0xfffff800`02c91650
Debug session time: Wed May 11 08:38:04.970 2011 (UTC - 4:00)
System Uptime: 0 days 13:11:29.875
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
..................................................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa8007464010, fffff8800447d408, 0, 2}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!KPRCB                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!KPRCB                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.

Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.

Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.

Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.

Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.

Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.

Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.

Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.

Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.

Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.

Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.

Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.

Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.

Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.

Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.

Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.

Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.

Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.

Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
Probably caused by : atikmpag.sys ( atikmpag+7408 )

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

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8007464010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800447d408, 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:
------------------

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!KPRCB                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!KPRCB                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.

Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.

Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.

Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.

Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.

Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.

Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.

Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.

Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.

Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.

Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.

Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.

Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.

Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.

Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.

Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.

Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.

Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.

Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************

ADDITIONAL_DEBUG_TEXT:  
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

FAULTING_MODULE: fffff80002a4c000 nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4d9bc027

FAULTING_IP: 
atikmpag+7408
fffff880`0447d408 4883ec28        sub     rsp,28h

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`065eb9c8 fffff880`04522000 : 00000000`00000116 fffffa80`07464010 fffff880`0447d408 00000000`00000000 : nt+0x7fd00
fffff880`065eb9d0 fffff880`04521d0a : fffff880`0447d408 fffffa80`07464010 fffffa80`09cd1c00 fffffa80`09cc6010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`065eba10 fffff880`051c1f07 : fffffa80`07464010 00000000`00000000 fffffa80`09cd1c00 fffffa80`09cc6010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`065eba40 fffff880`051ebb75 : 00000000`ffffffff 00000000`002e707f 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`065ebb20 fffff880`051ea2bb : 00000000`00000102 00000000`00000000 00000000`002e707f 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`065ebb50 fffff880`051bd2c6 : ffffffff`ff676980 fffffa80`09cc6010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`065ebbf0 fffff880`051e9e7a : 00000000`00000000 fffffa80`06b1c010 00000000`00000080 fffffa80`09cc6010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`065ebd00 fffff800`02d6832e : 00000000`fffffc32 fffffa80`09cf68c0 fffffa80`066a5990 fffffa80`09cf68c0 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`065ebd40 00000000`fffffc32 : fffffa80`09cf68c0 fffffa80`066a5990 fffffa80`09cf68c0 fffffa80`066a5990 : nt+0x31c32e
fffff880`065ebd48 fffffa80`09cf68c0 : fffffa80`066a5990 fffffa80`09cf68c0 fffffa80`066a5990 00000000`00000000 : 0xfffffc32
fffff880`065ebd50 fffffa80`066a5990 : fffffa80`09cf68c0 fffffa80`066a5990 00000000`00000000 00000000`00000000 : 0xfffffa80`09cf68c0
fffff880`065ebd58 fffffa80`09cf68c0 : fffffa80`066a5990 00000000`00000000 00000000`00000000 fffff800`02abd666 : 0xfffffa80`066a5990
fffff880`065ebd60 fffffa80`066a5990 : 00000000`00000000 00000000`00000000 fffff800`02abd666 fffff800`02c3ee80 : 0xfffffa80`09cf68c0
fffff880`065ebd68 00000000`00000000 : 00000000`00000000 fffff800`02abd666 fffff800`02c3ee80 fffffa80`09cf68c0 : 0xfffffa80`066a5990


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmpag+7408
fffff880`0447d408 4883ec28        sub     rsp,28h

SYMBOL_NAME:  atikmpag+7408

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

BUCKET_ID:  WRONG_SYMBOLS

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





DRIVERS

Code: 
start             end                 module name
fffff880`0531c000 fffff880`0535a000   1394ohci 1394ohci.sys Sat Nov 20 05:44:56 2010 (4CE7A6A8)
fffff880`00f7d000 fffff880`00fd4000   ACPI     ACPI.sys     Sat Nov 20 04:19:16 2010 (4CE79294)
fffff880`03e4c000 fffff880`03ed5000   afd      afd.sys      Sat Nov 20 04:23:27 2010 (4CE7938F)
fffff880`05376000 fffff880`0538c000   AgileVpn AgileVpn.sys Mon Jul 13 20:10:24 2009 (4A5BCCF0)
fffff880`00de0000 fffff880`00deb000   amdxata  amdxata.sys  Fri Mar 19 12:18:18 2010 (4BA3A3CA)
fffff880`06976000 fffff880`06981000   asyncmac asyncmac.sys Mon Jul 13 20:10:13 2009 (4A5BCCE5)
fffff880`00cda000 fffff880`00ce3000   atapi    atapi.sys    Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`00db6000 fffff880`00de0000   ataport  ataport.SYS  Sat Nov 20 04:19:15 2010 (4CE79293)
fffff880`0487c000 fffff880`051b2000   atikmdag atikmdag.sys Tue Apr 05 21:50:36 2011 (4D9BC6EC)
fffff880`04476000 fffff880`044c5000   atikmpag atikmpag.sys Tue Apr 05 21:21:43 2011 (4D9BC027)
fffff960`008d0000 fffff960`00931000   ATMFD    ATMFD.DLL    unavailable (00000000)
fffff880`04850000 fffff880`0486d000   avgntflt avgntflt.sys Thu Nov 11 10:59:48 2010 (4CDC12F4)
fffff880`01022000 fffff880`01044000   avipbb   avipbb.sys   Mon Feb 22 05:08:50 2010 (4B8257B2)
fffff880`019f1000 fffff880`019f8000   Beep     Beep.SYS     Mon Jul 13 20:00:13 2009 (4A5BCA8D)
fffff880`01211000 fffff880`01222000   blbdrive blbdrive.sys Mon Jul 13 19:35:59 2009 (4A5BC4DF)
fffff880`038c9000 fffff880`038e7000   bowser   bowser.sys   Tue Feb 22 23:55:04 2011 (4D649328)
fffff960`00630000 fffff960`00657000   cdd      cdd.dll      unavailable (00000000)
fffff880`019be000 fffff880`019e8000   cdrom    cdrom.sys    Sat Nov 20 04:19:20 2010 (4CE79298)
fffff880`00c00000 fffff880`00cc0000   CI       CI.dll       Sat Nov 20 08:12:36 2010 (4CE7C944)
fffff880`01958000 fffff880`01988000   CLASSPNP CLASSPNP.SYS Sat Nov 20 04:19:23 2010 (4CE7929B)
fffff880`00d58000 fffff880`00db6000   CLFS     CLFS.SYS     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`01154000 fffff880`011c6000   cng      cng.sys      Sat Nov 20 05:08:45 2010 (4CE79E2D)
fffff880`05366000 fffff880`05376000   CompositeBus CompositeBus.sys Sat Nov 20 05:33:17 2010 (4CE7A3ED)
fffff880`0599e000 fffff880`059ac000   crashdmp crashdmp.sys Mon Jul 13 20:01:01 2009 (4A5BCABD)
fffff880`03e26000 fffff880`03e44000   dfsc     dfsc.sys     Sat Nov 20 04:26:31 2010 (4CE79447)
fffff880`03e17000 fffff880`03e26000   discache discache.sys Mon Jul 13 19:37:18 2009 (4A5BC52E)
fffff880`01942000 fffff880`01958000   disk     disk.sys     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`05976000 fffff880`05998000   drmk     drmk.sys     Mon Jul 13 21:01:25 2009 (4A5BD8E5)
fffff880`059b8000 fffff880`059c1000   dump_atapi dump_atapi.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`059ac000 fffff880`059b8000   dump_dumpata dump_dumpata.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`059c1000 fffff880`059d4000   dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F)
fffff880`059d4000 fffff880`059e0000   Dxapi    Dxapi.sys    Mon Jul 13 19:38:28 2009 (4A5BC574)
fffff880`044c5000 fffff880`045b9000   dxgkrnl  dxgkrnl.sys  Sat Nov 20 04:50:50 2010 (4CE799FA)
fffff880`051b2000 fffff880`051f8000   dxgmms1  dxgmms1.sys  Sat Nov 20 04:49:53 2010 (4CE799C1)
fffff880`03939000 fffff880`0396f000   fastfat  fastfat.SYS  Mon Jul 13 19:23:28 2009 (4A5BC1F0)
fffff880`010e2000 fffff880`010f6000   fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481)
fffff880`01096000 fffff880`010e2000   fltmgr   fltmgr.sys   Sat Nov 20 04:19:24 2010 (4CE7929C)
fffff880`013f2000 fffff880`013fc000   Fs_Rec   Fs_Rec.sys   Mon Jul 13 19:19:45 2009 (4A5BC111)
fffff880`01908000 fffff880`01942000   fvevol   fvevol.sys   Sat Nov 20 04:24:06 2010 (4CE793B6)
fffff880`0180e000 fffff880`01858000   fwpkclnt fwpkclnt.sys Sat Nov 20 04:21:37 2010 (4CE79321)
fffff800`02a03000 fffff800`02a4c000   hal      hal.dll      Sat Nov 20 08:00:25 2010 (4CE7C669)
fffff880`04800000 fffff880`04824000   HDAudBus HDAudBus.sys Sat Nov 20 05:43:42 2010 (4CE7A65E)
fffff880`058dd000 fffff880`05939000   HdAudio  HdAudio.sys  Sat Nov 20 05:44:23 2010 (4CE7A687)
fffff880`0760e000 fffff880`07627000   HIDCLASS HIDCLASS.SYS Sat Nov 20 05:43:49 2010 (4CE7A665)
fffff880`05819000 fffff880`05821080   HIDPARSE HIDPARSE.SYS Mon Jul 13 20:06:17 2009 (4A5BCBF9)
fffff880`07600000 fffff880`0760e000   hidusb   hidusb.sys   Sat Nov 20 05:43:49 2010 (4CE7A665)
fffff880`03800000 fffff880`038c9000   HTTP     HTTP.sys     Sat Nov 20 04:24:30 2010 (4CE793CE)
fffff880`018ff000 fffff880`01908000   hwpolicy hwpolicy.sys Sat Nov 20 04:18:54 2010 (4CE7927E)
fffff880`0106a000 fffff880`01080000   intelppm intelppm.sys Mon Jul 13 19:19:25 2009 (4A5BC0FD)
fffff880`05256000 fffff880`05265000   kbdclass kbdclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116)
fffff880`0772a000 fffff880`07738000   kbdhid   kbdhid.sys   Sat Nov 20 05:33:25 2010 (4CE7A3F5)
fffff800`00ba0000 fffff800`00baa000   kdcom    kdcom.dll    Sat Feb 05 11:52:49 2011 (4D4D8061)
fffff880`045b9000 fffff880`045fc000   ks       ks.sys       Sat Nov 20 05:33:23 2010 (4CE7A3F3)
fffff880`013c6000 fffff880`013e1000   ksecdd   ksecdd.sys   Sat Nov 20 04:21:15 2010 (4CE7930B)
fffff880`015b3000 fffff880`015de000   ksecpkg  ksecpkg.sys  Sat Nov 20 05:10:34 2010 (4CE79E9A)
fffff880`05998000 fffff880`0599d200   ksthunk  ksthunk.sys  Mon Jul 13 20:00:19 2009 (4A5BCA93)
fffff880`0390c000 fffff880`03921000   lltdio   lltdio.sys   Mon Jul 13 20:08:50 2009 (4A5BCC92)
fffff880`01988000 fffff880`019ab000   luafv    luafv.sys    Mon Jul 13 19:26:13 2009 (4A5BC295)
fffff880`00cf5000 fffff880`00d44000   mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Sat Nov 20 08:03:51 2010 (4CE7C737)
fffff880`04842000 fffff880`04850000   monitor  monitor.sys  Mon Jul 13 19:38:52 2009 (4A5BC58C)
fffff880`05265000 fffff880`05274000   mouclass mouclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116)
fffff880`077e3000 fffff880`077f0000   mouhid   mouhid.sys   Mon Jul 13 20:00:20 2009 (4A5BCA94)
fffff880`00cc0000 fffff880`00cda000   mountmgr mountmgr.sys Sat Nov 20 04:19:21 2010 (4CE79299)
fffff880`01400000 fffff880`01431000   MpFilter MpFilter.sys Tue Sep 14 20:19:28 2010 (4C901110)
fffff880`06ef3000 fffff880`06f03000   MpNWMon  MpNWMon.sys  Tue Sep 14 20:19:30 2010 (4C901112)
fffff880`0396f000 fffff880`03987000   mpsdrv   mpsdrv.sys   Mon Jul 13 20:08:25 2009 (4A5BCC79)
fffff880`03987000 fffff880`039b4000   mrxsmb   mrxsmb.sys   Tue Feb 22 23:56:22 2011 (4D649376)
fffff880`06e82000 fffff880`06ecf000   mrxsmb10 mrxsmb10.sys Tue Feb 22 23:55:12 2011 (4D649330)
fffff880`06ecf000 fffff880`06ef3000   mrxsmb20 mrxsmb20.sys Tue Feb 22 23:55:12 2011 (4D649330)
fffff880`015e7000 fffff880`015f2000   Msfs     Msfs.SYS     Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`00fdd000 fffff880`00fe7000   msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE)
fffff880`010f6000 fffff880`01154000   msrpc    msrpc.sys    Sat Nov 20 04:21:56 2010 (4CE79334)
fffff880`03e0c000 fffff880`03e17000   mssmbios mssmbios.sys Mon Jul 13 19:31:10 2009 (4A5BC3BE)
fffff880`018ed000 fffff880`018ff000   mup      mup.sys      Mon Jul 13 19:23:45 2009 (4A5BC201)
fffff880`01460000 fffff880`01553000   ndis     ndis.sys     Sat Nov 20 04:23:30 2010 (4CE79392)
fffff880`053b0000 fffff880`053bc000   ndistapi ndistapi.sys Mon Jul 13 20:10:00 2009 (4A5BCCD8)
fffff880`053bc000 fffff880`053eb000   ndiswan  ndiswan.sys  Sat Nov 20 05:52:32 2010 (4CE7A870)
fffff880`058c8000 fffff880`058dd000   NDProxy  NDProxy.SYS  Sat Nov 20 05:52:20 2010 (4CE7A864)
fffff880`03f49000 fffff880`03f58000   netbios  netbios.sys  Mon Jul 13 20:09:26 2009 (4A5BCCB6)
fffff880`03ed5000 fffff880`03f1a000   netbt    netbt.sys    Sat Nov 20 04:23:18 2010 (4CE79386)
fffff880`01553000 fffff880`015b3000   NETIO    NETIO.SYS    Sat Nov 20 04:23:13 2010 (4CE79381)
fffff880`07708000 fffff880`0771d000   NisDrvWFP NisDrvWFP.sys Tue Sep 14 20:20:25 2010 (4C901149)
fffff880`01200000 fffff880`01211000   Npfs     Npfs.SYS     Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`03e00000 fffff880`03e0c000   nsiproxy nsiproxy.sys Mon Jul 13 19:21:02 2009 (4A5BC15E)
fffff800`02a4c000 fffff800`03035000   nt       ntoskrnl.exe Sat Apr 09 00:15:23 2011 (4D9FDD5B)
fffff880`01223000 fffff880`013c6000   Ntfs     Ntfs.sys     Thu Mar 10 22:39:39 2011 (4D79997B)
fffff880`019e8000 fffff880`019f1000   Null     Null.SYS     Mon Jul 13 19:19:37 2009 (4A5BC109)
fffff880`03f23000 fffff880`03f49000   pacer    pacer.sys    Sat Nov 20 05:52:18 2010 (4CE7A862)
fffff880`00e40000 fffff880`00e55000   partmgr  partmgr.sys  Sat Nov 20 04:20:00 2010 (4CE792C0)
fffff880`00e00000 fffff880`00e33000   pci      pci.sys      Sat Nov 20 04:19:11 2010 (4CE7928F)
fffff880`00fe7000 fffff880`00fee000   pciide   pciide.sys   Mon Jul 13 19:19:49 2009 (4A5BC115)
fffff880`00fee000 fffff880`00ffe000   PCIIDEX  PCIIDEX.SYS  Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`013e1000 fffff880`013f2000   pcw      pcw.sys      Mon Jul 13 19:19:27 2009 (4A5BC0FF)
fffff880`06f03000 fffff880`06fa9000   peauth   peauth.sys   Mon Jul 13 21:01:19 2009 (4A5BD8DF)
fffff880`077f0000 fffff880`07800000   point64  point64.sys  Fri Apr 08 18:58:14 2011 (4D9F9306)
fffff880`05939000 fffff880`05976000   portcls  portcls.sys  Mon Jul 13 20:06:27 2009 (4A5BCC03)
fffff880`00d44000 fffff880`00d58000   PSHED    PSHED.dll    Mon Jul 13 21:32:23 2009 (4A5BE027)
fffff880`0538c000 fffff880`053b0000   rasl2tp  rasl2tp.sys  Sat Nov 20 05:52:34 2010 (4CE7A872)
fffff880`05200000 fffff880`0521b000   raspppoe raspppoe.sys Mon Jul 13 20:10:17 2009 (4A5BCCE9)
fffff880`0521b000 fffff880`0523c000   raspptp  raspptp.sys  Sat Nov 20 05:52:31 2010 (4CE7A86F)
fffff880`0523c000 fffff880`05256000   rassstp  rassstp.sys  Mon Jul 13 20:10:25 2009 (4A5BCCF1)
fffff880`03fa4000 fffff880`03ff5000   rdbss    rdbss.sys    Sat Nov 20 04:27:51 2010 (4CE79497)
fffff880`01600000 fffff880`01609000   RDPCDD   RDPCDD.sys   Mon Jul 13 20:16:34 2009 (4A5BCE62)
fffff880`0144f000 fffff880`01458000   rdpencdd rdpencdd.sys Mon Jul 13 20:16:34 2009 (4A5BCE62)
fffff880`015de000 fffff880`015e7000   rdprefmp rdprefmp.sys Mon Jul 13 20:16:35 2009 (4A5BCE63)
fffff880`018b3000 fffff880`018ed000   rdyboost rdyboost.sys Sat Nov 20 04:43:10 2010 (4CE7982E)
fffff880`03921000 fffff880`03939000   rspndr   rspndr.sys   Mon Jul 13 20:08:50 2009 (4A5BCC92)
fffff880`052ac000 fffff880`0531c000   Rt64win7 Rt64win7.sys Mon Mar 21 09:20:32 2011 (4D8750A0)
fffff880`06fa9000 fffff880`06fb4000   secdrv   secdrv.SYS   Wed Sep 13 09:18:38 2006 (4508052E)
fffff880`0535a000 fffff880`05366000   serenum  serenum.sys  Mon Jul 13 20:00:33 2009 (4A5BCAA1)
fffff880`03f58000 fffff880`03f75000   serial   serial.sys   Mon Jul 13 20:00:40 2009 (4A5BCAA8)
fffff880`018ac000 fffff880`018b3000   SmartDefragDriver SmartDefragDriver.sys Wed Feb 23 03:37:56 2011 (4D64C764)
fffff880`018a4000 fffff880`018ac000   spldr    spldr.sys    Mon May 11 12:56:27 2009 (4A0858BB)
fffff880`068dd000 fffff880`0694e000   spsys    spsys.sys    Mon May 11 13:20:58 2009 (4A085E7A)
fffff880`07670000 fffff880`07708000   srv      srv.sys      Tue Feb 22 23:56:21 2011 (4D649375)
fffff880`06e00000 fffff880`06e6a000   srv2     srv2.sys     Tue Feb 22 23:56:00 2011 (4D649360)
fffff880`06fb4000 fffff880`06fe5000   srvnet   srvnet.sys   Tue Feb 22 23:55:44 2011 (4D649350)
fffff880`05274000 fffff880`05275480   swenum   swenum.sys   Mon Jul 13 20:00:18 2009 (4A5BCA92)
fffff880`0160a000 fffff880`0180e000   tcpip    tcpip.sys    Sat Nov 20 04:25:52 2010 (4CE79420)
fffff880`06fe5000 fffff880`06ff7000   tcpipreg tcpipreg.sys Sat Nov 20 05:51:48 2010 (4CE7A844)
fffff880`015f2000 fffff880`015ff000   TDI      TDI.SYS      Sat Nov 20 04:22:06 2010 (4CE7933E)
fffff880`01000000 fffff880`01022000   tdx      tdx.sys      Sat Nov 20 04:21:54 2010 (4CE79332)
fffff880`03f90000 fffff880`03fa4000   termdd   termdd.sys   Sat Nov 20 06:03:40 2010 (4CE7AB0C)
fffff960`004e0000 fffff960`004ea000   TSDDD    TSDDD.dll    unavailable (00000000)
fffff880`01044000 fffff880`0106a000   tunnel   tunnel.sys   Sat Nov 20 05:51:50 2010 (4CE7A846)
fffff880`05276000 fffff880`05288000   umbus    umbus.sys    Sat Nov 20 05:44:37 2010 (4CE7A695)
fffff880`0775f000 fffff880`0777c000   usbccgp  usbccgp.sys  Thu Mar 24 23:29:14 2011 (4D8C0C0A)
fffff880`07786000 fffff880`07787f00   USBD     USBD.SYS     Thu Mar 24 23:28:59 2011 (4D8C0BFB)
fffff880`0774e000 fffff880`0775f000   usbehci  usbehci.sys  Thu Mar 24 23:29:04 2011 (4D8C0C00)
fffff880`0586e000 fffff880`058c8000   usbhub   usbhub.sys   Thu Mar 24 23:29:25 2011 (4D8C0C15)
fffff880`04400000 fffff880`04456000   USBPORT  USBPORT.SYS  Mon Jul 13 20:06:31 2009 (4A5BCC07)
fffff880`07653000 fffff880`0765f000   usbprint usbprint.sys Mon Jul 13 20:38:18 2009 (4A5BD37A)
fffff880`07642000 fffff880`07653000   usbscan  usbscan.sys  Mon Jul 13 20:35:32 2009 (4A5BD2D4)
fffff880`07627000 fffff880`07642000   USBSTOR  USBSTOR.SYS  Thu Mar 10 23:37:16 2011 (4D79A6FC)
fffff880`0771d000 fffff880`0772a000   usbuhci  usbuhci.sys  Thu Mar 24 23:29:03 2011 (4D8C0BFF)
fffff880`00e33000 fffff880`00e40000   vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB)
fffff880`01431000 fffff880`0143f000   vga      vga.sys      Mon Jul 13 19:38:47 2009 (4A5BC587)
fffff880`011c6000 fffff880`011eb000   VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:38:51 2009 (4A5BC58B)
fffff880`00e55000 fffff880`00e6a000   volmgr   volmgr.sys   Sat Nov 20 04:19:28 2010 (4CE792A0)
fffff880`00e6a000 fffff880`00ec6000   volmgrx  volmgrx.sys  Sat Nov 20 04:20:43 2010 (4CE792EB)
fffff880`01858000 fffff880`018a4000   volsnap  volsnap.sys  Sat Nov 20 04:20:08 2010 (4CE792C8)
fffff880`03f75000 fffff880`03f90000   wanarp   wanarp.sys   Sat Nov 20 05:52:36 2010 (4CE7A874)
fffff880`0143f000 fffff880`0144f000   watchdog watchdog.sys Mon Jul 13 19:37:35 2009 (4A5BC53F)
fffff880`00eca000 fffff880`00f6e000   Wdf01000 Wdf01000.sys Mon Jul 13 19:22:07 2009 (4A5BC19F)
fffff880`00f6e000 fffff880`00f7d000   WDFLDR   WDFLDR.SYS   Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`03f1a000 fffff880`03f23000   wfplwf   wfplwf.sys   Mon Jul 13 20:09:26 2009 (4A5BCCB6)
fffff960`000c0000 fffff960`003d2000   win32k   win32k.sys   unavailable (00000000)
fffff880`00fd4000 fffff880`00fdd000   WMILIB   WMILIB.SYS   Mon Jul 13 19:19:51 2009 (4A5BC117)
fffff880`038eb000 fffff880`0390c000   WudfPf   WudfPf.sys   Sat Nov 20 05:42:44 2010 (4CE7A624)
fffff880`07796000 fffff880`077c7000   WUDFRd   WUDFRd.sys   Sat Nov 20 05:43:32 2010 (4CE7A654)

Unloaded modules:
fffff880`06981000 fffff880`0698d000   hiber_atapor
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0000C000
fffff880`0698d000 fffff880`06996000   hiber_atapi.
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00009000
fffff880`06996000 fffff880`069a9000   hiber_dumpfv
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00013000
fffff880`0694e000 fffff880`0695a000   hiber_atapor
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0000C000
fffff880`0695a000 fffff880`06963000   hiber_atapi.
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00009000
fffff880`06963000 fffff880`06976000   hiber_dumpfv
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00013000
fffff880`0765f000 fffff880`0766d000   kbdhid.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0000E000
fffff880`077d5000 fffff880`077e3000   kbdhid.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0000E000
fffff880`0772a000 fffff880`07736000   usbprint.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0000C000
fffff880`0765f000 fffff880`07670000   usbscan.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00011000
fffff880`0764f000 fffff880`0765f000   point64.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00010000
fffff880`07642000 fffff880`0764f000   mouhid.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0000D000
fffff880`077c7000 fffff880`077d5000   kbdhid.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0000E000
fffff880`07788000 fffff880`07796000   kbdhid.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0000E000
fffff880`077ce000 fffff880`077ff000   WUDFRd.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00031000
fffff880`077c2000 fffff880`077ce000   usbprint.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0000C000
fffff880`077b1000 fffff880`077c2000   usbscan.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00011000
fffff880`07796000 fffff880`077b1000   USBSTOR.SYS
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0001B000
fffff880`0772a000 fffff880`0773a000   point64.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00010000
fffff880`07627000 fffff880`07634000   mouhid.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0000D000
fffff880`07635000 fffff880`07666000   WUDFRd.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00031000
fffff880`07788000 fffff880`077a3000   USBSTOR.SYS
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0001B000
fffff880`077a3000 fffff880`077c0000   usbccgp.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0001D000
fffff880`077ee000 fffff880`077fa000   usbprint.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0000C000
fffff880`077dd000 fffff880`077ee000   usbscan.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00011000
fffff880`0773a000 fffff880`07748000   kbdhid.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0000E000
fffff880`0775f000 fffff880`07778000   HIDCLASS.SYS
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00019000
fffff880`0772a000 fffff880`07738000   hidusb.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0000E000
fffff880`077c0000 fffff880`077d0000   point64.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00010000
fffff880`07778000 fffff880`07785000   mouhid.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0000D000
fffff880`04824000 fffff880`04831000   usbuhci.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0000D000
fffff880`0760e000 fffff880`07627000   HIDCLASS.SYS
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00019000
fffff880`07600000 fffff880`0760e000   hidusb.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0000E000
fffff880`07627000 fffff880`07635000   kbdhid.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0000E000
fffff880`0776d000 fffff880`07786000   HIDCLASS.SYS
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00019000
fffff880`0775f000 fffff880`0776d000   hidusb.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0000E000
fffff880`077cd000 fffff880`077dd000   point64.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00010000
fffff880`077c0000 fffff880`077cd000   mouhid.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0000D000
fffff880`05822000 fffff880`05824000   USBD.SYS
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00002000
fffff880`05800000 fffff880`05819000   HIDCLASS.SYS
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00019000
fffff880`059e0000 fffff880`059ee000   hidusb.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0000E000
fffff880`05831000 fffff880`05841000   point64.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00010000
fffff880`05824000 fffff880`05831000   mouhid.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0000D000
fffff880`05288000 fffff880`052a5000   usbccgp.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0001D000
fffff880`053eb000 fffff880`053f9000   kbdhid.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0000E000
fffff880`0771d000 fffff880`0774e000   WUDFRd.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00031000
fffff880`04831000 fffff880`04842000   usbehci.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00011000
fffff880`05841000 fffff880`0585c000   USBSTOR.SYS
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0001B000
fffff880`059ee000 fffff880`059fa000   usbprint.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  0000C000
fffff880`0585c000 fffff880`0586d000   usbscan.sys
    Timestamp: unavailable (00000000)
    Checksum:  00000000
    ImageSize:  00011000
 


Upvote 0 Downvote
You must log in or register to reply here.

Similar threads

L
  • Solved
Sound pauses every time monitor goes to or wakes from sleep
Replies
2
Views
843
Lars B
L
RodBarnes
  • Solved
Windows 10 Windows 10 system keeps waking up from sleep
Replies
9
Views
5K
CodeB434
C
S
  • Solved
Windows 10 PC unable to wake up from sleep
Replies
2
Views
916
Neemobeer
Neemobeer
T
  • Solved
Windows 10 Laptop won't wake from sleep; chkdsk fixes problem, temporarily
Replies
1
Views
968
ChatGPT
ChatGPT
olat
  • Solved
Windows 10 Sound pauses every time monitor goes to or wakes from sleep
Replies
1
Views
1K
olat
olat
Back
Top