积极答复者
Windows Server 2008 r2 Enterprise sp1无故重启

问题
-
贴出dump文件内容 请给于一下分析!~
Microsoft (R) Windows Debugger Version 6.10.0003.233 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [\\192.168.2.74\共享数据it\IT专用\2222\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is 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+ *
*********************************************************************
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -
Windows 7 Kernel Version 7601 (Service Pack 1) MP (16 procs) Free x64
Product: Server, suite: Enterprise TerminalServer SingleUserTS
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`0164e000 PsLoadedModuleList = 0xfffff800`01893e90
Debug session time: Thu Jun 28 23:17:56.589 2018 (GMT+8)
System Uptime: 0 days 0:02:31.151
*********************************************************************
* 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+ *
*********************************************************************
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -
Loading Kernel Symbols
...............................................................
................................................................
......
Loading User Symbols
Loading unloaded module list
....
The context is partially valid. Only x86 user-mode context is available.
The wow64exts extension must be loaded to access 32-bit state.
.load wow64exts will do this if you haven't loaded it already.
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {28, 2, 0, fffff88000e5fd0b}
***** 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 ***
*** ***
*************************************************************************
*** ERROR: Symbol file could not be found. Defaulted to export symbols for NETIO.SYS -
*************************************************************************
*** ***
*** ***
*** 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 : NETIO.SYS ( NETIO!FsbFree+2b )
Followup: MachineOwner
---------
答案
-
您好!
感谢您回复。
我给您的那个版本Windows2008R2也可以用。您可以点击System Requirements看下,
初步判断看,看到最后一行可能是由于srv.sys这个系统文件出错导致,您到下面的官方链接下载针对文件的最新KB并安装更新您的系统来尝试修复。
https://support.microsoft.com/en-sg/help/4284842/windows-7-update-kb4284842
希望以上信息能帮助您解决这个问题。
Best regards,
Please remember to mark the replies as an answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com- 已标记为答案 小生无奈 2018年10月10日 7:47
-
你好!
很抱歉由于周末休息,未能及时回复您。根据您的DUMP文件中,看到“ Your debugger is not using the correct symbols ”,显示您的debug时设置的symbol不正确。
请您在此官方链接(https://www.microsoft.com/en-us/download/details.aspx?displaylang=en&id=8279)下载适用于您系统的SDK工具集安装debugging tools,然后参照以下链接来设置symbols参数。
Symbol path for Windows debuggers
https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/symbol-path
另外,这里有一篇中文博客关于如何设置symbols,您也可以同时参照下:
https://blog.csdn.net/epluguo/article/details/9219395
另外,还有以下链接供您作参考:
Debugging Tools for Windows (WinDbg, KD, CDB, NTSD)
https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/
希望以上信息可以帮助到您。
如还需帮助,可随时在论坛回复我。
祝工作愉快!
Best regards,
Michael
Please remember to mark the replies as an answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com- 已标记为答案 小生无奈 2018年10月10日 7:47
-
另外今天又重启了!~蓝屏代码 dump 分析结果是!~~ Probably caused by : srv.sys ( srv+6d585 )
*************************************************************************
*** ***
*** ***
*** 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 : srv.sys ( srv+6d585 )
Followup: MachineOwner
---------- 已标记为答案 小生无奈 2018年10月10日 7:47
全部回复
-
你好!
很抱歉由于周末休息,未能及时回复您。根据您的DUMP文件中,看到“ Your debugger is not using the correct symbols ”,显示您的debug时设置的symbol不正确。
请您在此官方链接(https://www.microsoft.com/en-us/download/details.aspx?displaylang=en&id=8279)下载适用于您系统的SDK工具集安装debugging tools,然后参照以下链接来设置symbols参数。
Symbol path for Windows debuggers
https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/symbol-path
另外,这里有一篇中文博客关于如何设置symbols,您也可以同时参照下:
https://blog.csdn.net/epluguo/article/details/9219395
另外,还有以下链接供您作参考:
Debugging Tools for Windows (WinDbg, KD, CDB, NTSD)
https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/
希望以上信息可以帮助到您。
如还需帮助,可随时在论坛回复我。
祝工作愉快!
Best regards,
Michael
Please remember to mark the replies as an answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com- 已标记为答案 小生无奈 2018年10月10日 7:47
-
另外今天又重启了!~蓝屏代码 dump 分析结果是!~~ Probably caused by : srv.sys ( srv+6d585 )
*************************************************************************
*** ***
*** ***
*** 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 : srv.sys ( srv+6d585 )
Followup: MachineOwner
---------- 已标记为答案 小生无奈 2018年10月10日 7:47
-
您好!
感谢您回复。
我给您的那个版本Windows2008R2也可以用。您可以点击System Requirements看下,
初步判断看,看到最后一行可能是由于srv.sys这个系统文件出错导致,您到下面的官方链接下载针对文件的最新KB并安装更新您的系统来尝试修复。
https://support.microsoft.com/en-sg/help/4284842/windows-7-update-kb4284842
希望以上信息能帮助您解决这个问题。
Best regards,
Please remember to mark the replies as an answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com- 已标记为答案 小生无奈 2018年10月10日 7:47
-
你好!
请问您的这个事件进展如何?解决了吗?
Best regards,
Michael
Please remember to mark the replies as an answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com -
你好!
您可以参照这篇博客,打开windbg工具,点击 File,找到“Symbol Search Path”,在窗口中添加“srv*c:\MyServerSymbols*https://msdl.microsoft.com/download/symbols
”,(请确保C盘存在目录MyServerSymbol,如果没有需要手动创建),请参照下图。https://blog.csdn.net/epluguo/article/details/9219395
设置好后,直接将收集到的DUMP文件拖进工具窗口中进行分析。
希望以上信息可以帮助解决这个问题。
Best regards,
Michael
Please remember to mark the replies as an answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com- 已编辑 Michael HxyMicrosoft contingent staff, Moderator 2018年7月11日 16:03
-
你好!
请问您的这个事件进展如何? 有解决吗?
Best regards,
Michael
Please remember to mark the replies as an answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com -
你好!
请问您的这个事件进展如何? 有解决吗?
如还需帮助或还有疑问,可随时在论坛回复。
Best regards,
Michael
Please remember to mark the replies as an answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com- 已编辑 Michael HxyMicrosoft contingent staff, Moderator 2018年7月18日 14:42
-
你好!
很高兴您的问题可以成功得到解决。
您可以标记一个您觉得有用的答案,这样也可以给论坛中遇到类似问题的其他会员作一个参考。
感谢您的分享和支持。
祝工作愉快!
Best regards,
Michael
Please remember to mark the replies as an answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com