18,141
社区成员
发帖
与我相关
我的任务
分享Lenovo Rescuer-15ISK蓝屏故障 有知道的帮忙看看
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
VIDEO_DXGKRNL_FATAL_ERROR (113)
The dxgkrnl has detected that a violation has occurred. This resulted
in a condition that dxgkrnl can no longer progress. By crashing, dxgkrnl
is attempting to get enough information into the minidump such that somebody
can pinpoint the crash cause. Any other values after parameter 1 must be
individually examined according to the subtype.
Arguments:
Arg1: 0000000000000019, The subtype of the bugcheck:
Arg2: 0000000000000002
Arg3: 00000000000010de
Arg4: 000000000000139b
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
SYSTEM_MANUFACTURER: LENOVO
SYSTEM_PRODUCT_NAME: 80RQ
SYSTEM_SKU: LENOVO_MT_80RQ_BU_idea_FM_Lenovo Rescuer-15ISK
SYSTEM_VERSION: Lenovo Rescuer-15ISK
BIOS_VENDOR: LENOVO
BIOS_VERSION: 0KCN30WW
BIOS_DATE: 04/29/2015
BASEBOARD_MANUFACTURER: LENOVO
BASEBOARD_PRODUCT: SuperX 5B
BASEBOARD_VERSION: SDK0K09938 WIN
DUMP_TYPE: 2
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
BUGCHECK_P1: 19
BUGCHECK_P2: 2
BUGCHECK_P3: 10de
BUGCHECK_P4: 139b
CPU_COUNT: 8
CPU_MHZ: a20
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 5e
CPU_STEPPING: 3
CPU_MICROCODE: 6,5e,3,0 (F,M,S,R) SIG: 74'00000000 (cache) 74'00000000 (init)
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x113
PROCESS_NAME: System
CURRENT_IRQL: 0
ANALYSIS_SESSION_HOST: WIN10-703182154
ANALYSIS_SESSION_TIME: 08-15-2017 11:02:28.0482
ANALYSIS_VERSION: 10.0.15063.468 amd64fre
LAST_CONTROL_TRANSFER: from fffff8087d0a355e to fffff800cf7fc550
STACK_TEXT:
ffffae00`2674f7d8 fffff808`7d0a355e : 00000000`00000113 00000000`00000019 00000000`00000002 00000000`000010de : nt!KeBugCheckEx
ffffae00`2674f7e0 fffff808`7d22af2c : ffffd800`1fbf4180 ffffffff`c000000e ffffd800`1fbf4180 00000000`00000000 : watchdog!WdLogEvent5_WdCriticalError+0xce
ffffae00`2674f820 fffff808`7d1b416b : ffffd800`2046cb00 ffffd800`1fbf4100 ffffd800`2046cb80 00000000`ff030000 : dxgkrnl!DpiFdoHandleDevicePower+0x768cc
ffffae00`2674f8b0 fffff808`7f6c8a93 : 00000000`00000001 ffffae00`2674fa59 00000000`00000001 ffffd800`223c8000 : dxgkrnl!DpiDispatchPower+0x8b
ffffae00`2674f9d0 00000000`00000001 : ffffae00`2674fa59 00000000`00000001 ffffd800`223c8000 ffffae00`2674fad8 : nvlddmkm+0x168a93
ffffae00`2674f9d8 ffffae00`2674fa59 : 00000000`00000001 ffffd800`223c8000 ffffae00`2674fad8 00000000`00000004 : 0x1
ffffae00`2674f9e0 00000000`00000001 : ffffd800`223c8000 ffffae00`2674fad8 00000000`00000004 00000000`00000000 : 0xffffae00`2674fa59
ffffae00`2674f9e8 ffffd800`223c8000 : ffffae00`2674fad8 00000000`00000004 00000000`00000000 ffffae00`2674fa01 : 0x1
ffffae00`2674f9f0 ffffae00`2674fad8 : 00000000`00000004 00000000`00000000 ffffae00`2674fa01 ffffd800`1fce3000 : 0xffffd800`223c8000
ffffae00`2674f9f8 00000000`00000004 : 00000000`00000000 ffffae00`2674fa01 ffffd800`1fce3000 fffff800`cf6c2d78 : 0xffffae00`2674fad8
ffffae00`2674fa00 00000000`00000000 : ffffae00`2674fa01 ffffd800`1fce3000 fffff800`cf6c2d78 ffffd800`1fbf4030 : 0x4
STACK_COMMAND: kb
THREAD_SHA1_HASH_MOD_FUNC: 522fff5ea38323f8cf6fd33b40a8a5ff09335789
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: a699a317be4bd01ac8fa83cb14e02c668c3259dc
THREAD_SHA1_HASH_MOD: 75c5edb9820b07db07645796a7ba91c81e006f7c
FOLLOWUP_IP:
dxgkrnl!DpiFdoHandleDevicePower+768cc
fffff808`7d22af2c 488b5730 mov rdx,qword ptr [rdi+30h]
FAULT_INSTR_CODE: 30578b48
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: dxgkrnl!DpiFdoHandleDevicePower+768cc
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgkrnl
IMAGE_NAME: dxgkrnl.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 0
IMAGE_VERSION: 10.0.15063.481
BUCKET_ID_FUNC_OFFSET: 768cc
FAILURE_BUCKET_ID: 0x113_dxgkrnl!DpiFdoHandleDevicePower
BUCKET_ID: 0x113_dxgkrnl!DpiFdoHandleDevicePower
PRIMARY_PROBLEM_CLASS: 0x113_dxgkrnl!DpiFdoHandleDevicePower
TARGET_TIME: 2017-08-07T08:55:24.000Z
OSBUILD: 15063
OSSERVICEPACK: 502
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 272
PRODUCT_TYPE: 1
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: 2017-07-28 12:07:59
ANALYSIS_SESSION_ELAPSED_TIME: 4f0
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x113_dxgkrnl!dpifdohandledevicepower
FAILURE_ID_HASH: {d602ffad-dbab-56f7-4cf4-fd87d40aefc6}
Followup: MachineOwner
---------
* *
* Bugcheck Analysis *
* *
*******************************************************************************
VIDEO_DXGKRNL_FATAL_ERROR (113)
The dxgkrnl has detected that a violation has occurred. This resulted
in a condition that dxgkrnl can no longer progress. By crashing, dxgkrnl
is attempting to get enough information into the minidump such that somebody
can pinpoint the crash cause. Any other values after parameter 1 must be
individually examined according to the subtype.
Arguments:
Arg1: 0000000000000019, The subtype of the bugcheck:
Arg2: 0000000000000002
Arg3: 00000000000010de
Arg4: 000000000000139b
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
SYSTEM_MANUFACTURER: LENOVO
SYSTEM_PRODUCT_NAME: 80RQ
SYSTEM_SKU: LENOVO_MT_80RQ_BU_idea_FM_Lenovo Rescuer-15ISK
SYSTEM_VERSION: Lenovo Rescuer-15ISK
BIOS_VENDOR: LENOVO
BIOS_VERSION: 0KCN30WW
BIOS_DATE: 04/29/2015
BASEBOARD_MANUFACTURER: LENOVO
BASEBOARD_PRODUCT: SuperX 5B
BASEBOARD_VERSION: SDK0K09938 WIN
DUMP_TYPE: 2
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
BUGCHECK_P1: 19
BUGCHECK_P2: 2
BUGCHECK_P3: 10de
BUGCHECK_P4: 139b
CPU_COUNT: 8
CPU_MHZ: a20
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 5e
CPU_STEPPING: 3
CPU_MICROCODE: 6,5e,3,0 (F,M,S,R) SIG: 74'00000000 (cache) 74'00000000 (init)
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x113
PROCESS_NAME: System
CURRENT_IRQL: 0
ANALYSIS_SESSION_HOST: WIN10-703182154
ANALYSIS_SESSION_TIME: 08-15-2017 11:02:28.0482
ANALYSIS_VERSION: 10.0.15063.468 amd64fre
LAST_CONTROL_TRANSFER: from fffff8087d0a355e to fffff800cf7fc550
STACK_TEXT:
ffffae00`2674f7d8 fffff808`7d0a355e : 00000000`00000113 00000000`00000019 00000000`00000002 00000000`000010de : nt!KeBugCheckEx
ffffae00`2674f7e0 fffff808`7d22af2c : ffffd800`1fbf4180 ffffffff`c000000e ffffd800`1fbf4180 00000000`00000000 : watchdog!WdLogEvent5_WdCriticalError+0xce
ffffae00`2674f820 fffff808`7d1b416b : ffffd800`2046cb00 ffffd800`1fbf4100 ffffd800`2046cb80 00000000`ff030000 : dxgkrnl!DpiFdoHandleDevicePower+0x768cc
ffffae00`2674f8b0 fffff808`7f6c8a93 : 00000000`00000001 ffffae00`2674fa59 00000000`00000001 ffffd800`223c8000 : dxgkrnl!DpiDispatchPower+0x8b
ffffae00`2674f9d0 00000000`00000001 : ffffae00`2674fa59 00000000`00000001 ffffd800`223c8000 ffffae00`2674fad8 : nvlddmkm+0x168a93
ffffae00`2674f9d8 ffffae00`2674fa59 : 00000000`00000001 ffffd800`223c8000 ffffae00`2674fad8 00000000`00000004 : 0x1
ffffae00`2674f9e0 00000000`00000001 : ffffd800`223c8000 ffffae00`2674fad8 00000000`00000004 00000000`00000000 : 0xffffae00`2674fa59
ffffae00`2674f9e8 ffffd800`223c8000 : ffffae00`2674fad8 00000000`00000004 00000000`00000000 ffffae00`2674fa01 : 0x1
ffffae00`2674f9f0 ffffae00`2674fad8 : 00000000`00000004 00000000`00000000 ffffae00`2674fa01 ffffd800`1fce3000 : 0xffffd800`223c8000
ffffae00`2674f9f8 00000000`00000004 : 00000000`00000000 ffffae00`2674fa01 ffffd800`1fce3000 fffff800`cf6c2d78 : 0xffffae00`2674fad8
ffffae00`2674fa00 00000000`00000000 : ffffae00`2674fa01 ffffd800`1fce3000 fffff800`cf6c2d78 ffffd800`1fbf4030 : 0x4
STACK_COMMAND: kb
THREAD_SHA1_HASH_MOD_FUNC: 522fff5ea38323f8cf6fd33b40a8a5ff09335789
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: a699a317be4bd01ac8fa83cb14e02c668c3259dc
THREAD_SHA1_HASH_MOD: 75c5edb9820b07db07645796a7ba91c81e006f7c
FOLLOWUP_IP:
dxgkrnl!DpiFdoHandleDevicePower+768cc
fffff808`7d22af2c 488b5730 mov rdx,qword ptr [rdi+30h]
FAULT_INSTR_CODE: 30578b48
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: dxgkrnl!DpiFdoHandleDevicePower+768cc
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgkrnl
IMAGE_NAME: dxgkrnl.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 0
IMAGE_VERSION: 10.0.15063.481
BUCKET_ID_FUNC_OFFSET: 768cc
FAILURE_BUCKET_ID: 0x113_dxgkrnl!DpiFdoHandleDevicePower
BUCKET_ID: 0x113_dxgkrnl!DpiFdoHandleDevicePower
PRIMARY_PROBLEM_CLASS: 0x113_dxgkrnl!DpiFdoHandleDevicePower
TARGET_TIME: 2017-08-07T08:55:24.000Z
OSBUILD: 15063
OSSERVICEPACK: 502
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 272
PRODUCT_TYPE: 1
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: 2017-07-28 12:07:59
ANALYSIS_SESSION_ELAPSED_TIME: 4f0
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x113_dxgkrnl!dpifdohandledevicepower
FAILURE_ID_HASH: {d602ffad-dbab-56f7-4cf4-fd87d40aefc6}
Followup: MachineOwner
---------
...全文
请发表友善的回复…
发表回复
夜鹰 2017-08-15
- 打赏
- 举报
应该是NV显卡驱动造成，或者说显卡驱动和某款应用不兼容引起的故障。
解决方法：
1.安装具有微软WHQL认证的硬件驱动，建议从联想官网下载，强烈不建议使用第三方工具安装驱动程序；
2.运行dxdiag命令检查DirectX版本，Windows 10系统下目前最新版本是12，如果不是进行系统更新即可；
3.全盘查杀木马和病毒
4.检查机器散热是否正常，过高的显卡温度也会导致设备异常。
尝试上述方法后请在此贴引用此回复进行反馈，谢谢！
