询问者
WIN7 64位系统 蓝屏 ERROR: Module load completed but symbols could not be loaded for WiseTDIFw64.sys求解决方案
问题
-
以下是WinDbg中的报错信息，求解答，感谢！（现象是在刚打开Idea和Pycharm等IDE时有时会出现蓝屏）
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\112020-8312-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 19041 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff805`52200000 PsLoadedModuleList = 0xfffff805`52e2a3b0
Debug session time: Fri Nov 20 11:26:45.800 2020 (UTC + 8:00)
System Uptime: 0 days 0:05:10.531
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** 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 3B, {c0000005, fffff80563f32f50, fffff283403cca20, 0}
Unable to load image \??\C:\Windows\WiseTDIFw64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for WiseTDIFw64.sys
*** ERROR: Module load completed but symbols could not be loaded for WiseTDIFw64.sys
***** 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 ***
*** ***
*************************************************************************
Probably caused by : WiseTDIFw64.sys ( WiseTDIFw64+2f50 )
Followup: MachineOwner
---------
6: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80563f32f50, Address of the instruction which caused the bugcheck
Arg3: fffff283403cca20, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
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 ***
*** ***
*************************************************************************
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: fffff80552200000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 579ab865
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - 0x%p
FAULTING_IP:
WiseTDIFw64+2f50
fffff805`63f32f50 48395a08 cmp qword ptr [rdx+8],rbx
CONTEXT: fffff283403cca20 -- (.cxr 0xfffff283403cca20)
rax=ffffbd0e1f970000 rbx=ffffbd0e371c0dc0 rcx=00000000000004e0
rdx=0000000000060000 rsi=ffffbd0e320eeef8 rdi=ffffbd0e37750420
rip=fffff80563f32f50 rsp=fffff283403cd420 rbp=0000000000000000
r8=ffffbd0e1f15cd20 r9=fffff80552200000 r10=fffff80563f32700
r11=ffffe00824c6e500 r12=fffff283403cd638 r13=ffffbd0e2a31ef10
r14=ffffbd0e37789640 r15=0000000000000008
iopl=0 nv up ei pl nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050206
WiseTDIFw64+0x2f50:
fffff805`63f32f50 48395a08 cmp qword ptr [rdx+8],rbx ds:002b:00000000`00060008=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x3B
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff80563f32f50
STACK_TEXT:
fffff283`403cd420 00000000`00000000 : fffff805`524cd707 00000000`00000002 00000000`00000004 fffff283`403cd460 : WiseTDIFw64+0x2f50
FOLLOWUP_IP:
WiseTDIFw64+2f50
fffff805`63f32f50 48395a08 cmp qword ptr [rdx+8],rbx
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: WiseTDIFw64+2f50
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: WiseTDIFw64
IMAGE_NAME: WiseTDIFw64.sys
STACK_COMMAND: .cxr 0xfffff283403cca20 ; kb
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
全部回复
-
你好，
看您提供的信息，首先是由WiseTDIFw64.sys这个文件引起的系统崩溃。应该还是软件的兼容性和系统出现问题。
似乎是和您安装了wise care 365这个软件有关，如果安装了，可以先在控制面板中卸载。
同时这个文件路径应该在C:\Windows\WiseTdiFw64.sys和WiseTDIFw.sys。
找到可以删除，然后重新换一个其他版本的wise care 365再安装。
如果回答是有帮助的, 请将其标记为答案, 可以帮助其他有相同问题的社区成员, 并快速找到有用的答复。
针对Windows 2008/2008R2的扩展支持将于2020年结束，之后微软将不再为其提供安全更新。点击此处或扫描二维码获取《在 Azure 上运行 Windows Server 的终极指南》，把握良机完成云迁移并实现业务现代化。
