Windows Server 2008 R2 ntoskrnl.exe 引起蓝屏故障,重新启动

 前不久在HP ProLiant DL360 G6的服务器上面安装了Windows Server 2008 R2,系统一到晚上凌晨就出现蓝屏、重启现象,并且在 C:\Windows\Minidump 目录下面产生一些Dump文件,如下图所示:

Windows Server 2008 R2 ntoskrnl.exe 引起蓝屏故障,重新启动

 

 

后面我用微软的Windbg程序查看了一下系统产生的Dump文件内容,分析一下文件日志,发现内容如下:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\新建文件夹\DMP\073110-13884-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 p_w_picpath \SystemRoot\system32\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 7600 MP (8 procs) Free x64 
Product: Server, suite: Enterprise TerminalServer SingleUserTS 
Built by: 7600.20655.amd64fre.win7_ldr.100226-1909 
Machine Name: 
Kernel base = 0xfffff800`0161c000 PsLoadedModuleList = 0xfffff800`01854e50 
Debug session time: Sat Jul 31 21:02:49.632 2010 (GMT+8) 
System Uptime: 2 days 10:42:35.740 
********************************************************************* 
* 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 p_w_picpath \SystemRoot\system32\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 101, {19, 0, fffff88001c5d180, 2}

***** 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

Followup: MachineOwner 
---------

上一篇:JVM调优案例


下一篇:用Python解方程