积极答复者
BlueScreen

问题
-
问题签名:
问题事件名称: BlueScreen
OS 版本: 6.0.6002.2.2.0.256.1
区域设置 ID: 2052
有关该问题的其他信息:
BCCode: 116
BCP1: 878E2468
BCP2: 84353960
BCP3: 00000000
BCP4: 00000002
OS Version: 6_0_6002
Service Pack: 2_0
Product: 256_1
有助于描述该问题的文件:
C:\Windows\Minidump\Mini040710-01.dmp
C:\Users\ejin\AppData\Local\Temp\WER-56768-0.sysdata.xml
C:\Users\ejin\AppData\Local\Temp\WERE780.tmp.version.txt
阅读隐私声明:
http://go.microsoft.com/fwlink/?linkid=50163&clcid=0x0804Mini040710-01.dmp 下载地址!
http://u.115.com/file/t7496e7986
----------------------------------签名档
答案
-
以下是你的 DMP 文件診斷分析數據, 幫你貼上來. 從診斷信息看, 與顯卡驅動有關.
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [D:\root\dmp\Mini040710-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are availableSymbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6002.18160.x86fre.vistasp2_gdr.091208-0542
Machine Name:
Kernel base = 0x83438000 PsLoadedModuleList = 0x8354fc70
Debug session time: Wed Apr 7 19:30:53.688 2010 (UTC + 8:00)
System Uptime: 0 days 7:21:24.966
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************Use !analyze -v to get detailed debugging information.
BugCheck 116, {878e2468, 84353960, 0, 2}
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+4960 )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: 878e2468, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: 84353960, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 00000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 00000002, Optional internal context dependent data.Debugging Details:
------------------
FAULTING_IP:
atikmpag+4960
84353960 8bff mov edi,ediDEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT
CUSTOMER_CRASH_COUNT: 1
BUGCHECK_STR: 0x116
PROCESS_NAME: System
CURRENT_IRQL: 0
STACK_TEXT:
9dd88bc0 90dc9f71 00000116 878e2468 84353960 nt!KeBugCheckEx+0x1e
9dd88be4 90dcac61 84353960 00000000 00000002 dxgkrnl!TdrBugcheckOnTimeout+0x8d
9dd88c04 90d6738f 00000000 00000102 88e9b690 dxgkrnl!TdrIsRecoveryRequired+0xa1
9dd88c6c 90d83ec8 88e9b690 0019e733 00000000 dxgkrnl!VidSchiReportHwHang+0x2f5
9dd88c98 90d83c28 88e9b690 00000000 00000000 dxgkrnl!VidSchiCheckHwProgress+0x69
9dd88cc4 90d555b0 00000002 88e92460 88652e18 dxgkrnl!VidSchiWaitForSchedulerEvents+0x13f
9dd88d54 90d83f6f 88e9b690 8347c956 88e9b690 dxgkrnl!VidSchiScheduleCommandToRun+0xac
9dd88d68 90db95d1 88e9b690 00000000 88e63b78 dxgkrnl!VidSchiRun_PriorityTable+0xf
9dd88d7c 8360dc42 88e9b690 d10d1e9c 00000000 dxgkrnl!VidSchiWorkerThread+0x62
9dd88dc0 83476f4e 90db956f 88e9b690 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
STACK_COMMAND: .bugcheck ; kbFOLLOWUP_IP:
atikmpag+4960
84353960 8bff mov edi,ediSYMBOL_NAME: atikmpag+4960
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: atikmpag
IMAGE_NAME: atikmpag.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4b22a29d
FAILURE_BUCKET_ID: 0x116_IMAGE_atikmpag.sys
BUCKET_ID: 0x116_IMAGE_atikmpag.sys
Followup: MachineOwner
---------P.S. 建議使用其他網盤存放 DMP 文件, 因為 115 是那個什么木風的.
Folding@Home- 已标记为答案 哈哈大侠 2010年4月8日 6:15
全部回复
-
以下是你的 DMP 文件診斷分析數據, 幫你貼上來. 從診斷信息看, 與顯卡驅動有關.
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [D:\root\dmp\Mini040710-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are availableSymbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6002.18160.x86fre.vistasp2_gdr.091208-0542
Machine Name:
Kernel base = 0x83438000 PsLoadedModuleList = 0x8354fc70
Debug session time: Wed Apr 7 19:30:53.688 2010 (UTC + 8:00)
System Uptime: 0 days 7:21:24.966
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************Use !analyze -v to get detailed debugging information.
BugCheck 116, {878e2468, 84353960, 0, 2}
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+4960 )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: 878e2468, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: 84353960, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 00000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 00000002, Optional internal context dependent data.Debugging Details:
------------------
FAULTING_IP:
atikmpag+4960
84353960 8bff mov edi,ediDEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT
CUSTOMER_CRASH_COUNT: 1
BUGCHECK_STR: 0x116
PROCESS_NAME: System
CURRENT_IRQL: 0
STACK_TEXT:
9dd88bc0 90dc9f71 00000116 878e2468 84353960 nt!KeBugCheckEx+0x1e
9dd88be4 90dcac61 84353960 00000000 00000002 dxgkrnl!TdrBugcheckOnTimeout+0x8d
9dd88c04 90d6738f 00000000 00000102 88e9b690 dxgkrnl!TdrIsRecoveryRequired+0xa1
9dd88c6c 90d83ec8 88e9b690 0019e733 00000000 dxgkrnl!VidSchiReportHwHang+0x2f5
9dd88c98 90d83c28 88e9b690 00000000 00000000 dxgkrnl!VidSchiCheckHwProgress+0x69
9dd88cc4 90d555b0 00000002 88e92460 88652e18 dxgkrnl!VidSchiWaitForSchedulerEvents+0x13f
9dd88d54 90d83f6f 88e9b690 8347c956 88e9b690 dxgkrnl!VidSchiScheduleCommandToRun+0xac
9dd88d68 90db95d1 88e9b690 00000000 88e63b78 dxgkrnl!VidSchiRun_PriorityTable+0xf
9dd88d7c 8360dc42 88e9b690 d10d1e9c 00000000 dxgkrnl!VidSchiWorkerThread+0x62
9dd88dc0 83476f4e 90db956f 88e9b690 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
STACK_COMMAND: .bugcheck ; kbFOLLOWUP_IP:
atikmpag+4960
84353960 8bff mov edi,ediSYMBOL_NAME: atikmpag+4960
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: atikmpag
IMAGE_NAME: atikmpag.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4b22a29d
FAILURE_BUCKET_ID: 0x116_IMAGE_atikmpag.sys
BUCKET_ID: 0x116_IMAGE_atikmpag.sys
Followup: MachineOwner
---------P.S. 建議使用其他網盤存放 DMP 文件, 因為 115 是那個什么木風的.
Folding@Home- 已标记为答案 哈哈大侠 2010年4月8日 6:15