- 积分
- 718
- 最后登录
- 2022-3-13
- 精华
- 0
- 阅读权限
- 40
- 主题
- 47
- UID
- 1002003
- 帖子
- 851
- PB币
- 341
- 威望
- 63
- 贡献
- 0
- 技术
- 544
- 活跃
- 462
远景特工
- UID
- 1002003
- 帖子
- 851
- PB币
- 341
- 贡献
- 0
- 技术
- 544
- 活跃
- 462
|
发表于 2014-4-2 13:06:15
IP属地重庆
|显示全部楼层
本帖最后由 payne.huang 于 2014-4-2 23:50 编辑
- Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
- Copyright (c) Microsoft Corporation. All rights reserved.
- Loading Dump File [C:\Users\浩\Desktop\040214-7593-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 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 9600 MP (4 procs) Free x64
- Product: WinNt, suite: TerminalServer SingleUserTS
- Machine Name:
- Kernel base = 0xfffff802`d1486000 PsLoadedModuleList = 0xfffff802`d174a990
- Debug session time: Wed Apr 2 12:42:20.976 2014 (GMT+8)
- System Uptime: 5 days 11:37:44.859
- *********************************************************************
- * 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 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 133, {0, 501, 500, 0}
- ***** 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 ***
- *** ***
- *************************************************************************
- *************************************************************************
- *** ***
- *** ***
- *** 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 ***
- *** ***
- *************************************************************************
- *********************************************************************
- * 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+ *
- *********************************************************************
- *********************************************************************
- * 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+ *
- *********************************************************************
- Probably caused by : ntoskrnl.exe ( nt+14dca0 )
- Followup: MachineOwner
- ---------
复制代码
台式机
状态是屏幕突然不动(鼠标键盘全部无响应),过几秒就蓝屏了。
上面的信息我是查看系统蓝屏事件的记录文件获得的。
使用久了就来这么一次。
|
|