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

后面我用微软的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 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 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 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 argument when starting the debugger. *

*   using .sympath and .sympath+                                    *

*********************************************************************

Probably caused by : ntoskrnl.exe

Followup: MachineOwner

---------

其中有一项Probably Caused by :ntoskrnl.exe,说明是ntoskrnl.exe造成的原因,后面在微软的网站上面,找了一下KB,在微软的Support站点上面找到了3个补丁:

此KB:975530是修复:停止错误消息正在运行 Windows Server 2008 R2 和的一个英特尔至强 5500 系列处理器的计算机上已安装的 Hyper-V 角色:"0x00000101-CLOCK_WATCHDOG_TIMEOUT"

此KB:982927修复:您会收到错误消息,指出文件系统已损坏或 Windows Server 2008 R2 中 Windows 7 的ntoskrnl.exe 。

此KB:979444修复:正在运行 Windows 7 或 Windows Server 2008 R2 的计算机上的蓝色屏幕上的错误消息:"STOP: 0x0000000A"

下图是我的打的补丁截图:

之后也没有发生过蓝屏重启事件了!!!!!!!

Windows Server 2008 R2常规安全设置及基本安全策略

这篇文章主要介绍了Windows Web Server 2008 R2服务器简单安全设置,需要的朋友可以参考下 用的腾讯云最早选购的时候悲催的只有Windows Server 2008 R2的系统,原 ...

如何在Windows Server 2008 R2没有磁盘清理工具的情况下使用系统提供的磁盘清理工具

今天,刚好碰到服务器C盘空间满的情况,首先处理了临时文件和有关的日志文件后空间还是不够用,我知道清理C盘的方法有很多,但今天只分享一下如何在Windows Server 2008 R2没有磁盘清理工具 ...

Windows Server 2008 R2 负载平衡入门篇

一.简单介绍负载均衡 负载均衡也称负载共享,它是指负载均衡是指通过对系统负载情况进行动态调整,把负荷分摊到多个操作节点上执行,以减少系统中因各个节点负载不均衡所造成的影响,从而提高系统的工作效率.在常 ...

Windows Server 2008 R2中的ASP.NET环境架设

.NET Framework的部分功能在Windows Server 2008 R2得到支持,包括:.NET 2/3/3.5的子集和ASP.NET.另外,PowerShell也在Server Core ...

Windows Server 2008 R2遗忘管理员密码后的解决方案

在日常的工作中,对于一个网络管理员来讲最悲哀的事情莫过于在没有备用管理员账户和密码恢复盘的情况下遗忘了本地管理员账户密码. 在早期的系统中,遇到这种事情可以使用目前国内的很多Windows PE光盘来 ...

Windows Server 2008 R2 64bit兼容Chrome浏览器

近日更换系统Windows Server 2008 R2 64bit系统,发现谷歌浏览器插件无法正常运行,终于找到如下解决方案: 打开桌面谷歌浏览器属性,将target目标 C:\Users\Admi ...

Windows Server 2008 R2 域控制器部署指南

一.域控制器安装步骤: 1.装 Windows Server 2008 R2并配置计算机名称和IP地址(见 附录一) 2.点击“开始”,在“搜索程序和文件”中输入Dcpromo.exe后按回车键: 3 ...

Windows Server 2008 R2 SP1 下载地址

Windows Server 2008 R2 SP1 http://download.microsoft.com/download/0/A/F/0AFB5316-3062-494A-AB78-7FB0 ...

在 Windows Server 2008 R2 上安装 IIS 7.5

原文 在 Windows Server 2008 R2 上安装 IIS 7.5 默认情况下,Windows Server(R) 2008 R2 上不安装 IIS 7.5.可以使用服务器管理器中的“添加 ...

随机推荐

JSON 与 JSONP

JSON (JavaScript Object Notation) is a lightweight data-interchange format. 即 JSON 是一种轻量级的数据交换格式. 1. ...

巧用freemarker

使用Freemarker宏进行可扩展式模块化编程 该文是转载而来,并非我本人所写,但是觉得真心不错,所以收藏一下 一.前言 今天的文章聊一下freemarker的一些特性:宏,我们将使用它写出一些模块 ...

angularJs中的隐藏和显示

至强服务器装2003系统蓝屏,Windows Server 2008 R2 ntoskrnl.exe 引起蓝屏故障,重新启动...相关推荐

  1. 一台服务器多人远程桌面连接,Windows Server 2008 R2多用户远程桌面连接授权

    这篇文章主要介绍了Server 2008 R2多用户远程桌面连接授权,解决120天过期问题,具有一定的参考价值,感兴趣的小伙伴们可以参考一下 在工作中,我们往往需要远程服务器,经常会遇到以下这两个麻烦 ...

  2. Windows Server 2003 AD域升级至Windows Server 2008 R2实战案例

    某公司2003AD升级为2008R2AD过程 域名是:testad.com DC1:AD004(windows 2003 AD,DNS.GC.五大角色) DC2:AD005(windows 2003 ...

  3. 服务器装2008系统蓝屏,Windows Server 2008 R2 Enterprise 服务器蓝屏 代码0x00000124 - Microsoft Community...

    Microsoft (R) Windows Debugger Version 6.12.0002.633 X86 Copyright (c) Microsoft Corporation. All ri ...

  4. windows服务器迁到_将文件服务器及域控制器从2003迁移至Windows Server 2008 R2

    (一)背景环境: 当前,多数小企业仍然使用windows server2003 系统做域控制器及文件服务器,由于windows server 2003在多年使用之后变得卡顿,且存在异常的系统错误及诟病 ...

  5. windows多个服务器之间共享文件夹,windows server 2008 R2 部署NFS,实现多台服务器间、客户端间的共享目录。...

    如何通过Windows Server 2008 R2建立NFS存储服务? 通过Windows Server 2008 R2,我们可以很容易地将其作为一台NFS存储服务器,得到一个NFS软存储,轻松解决 ...

  6. 2008系统更改计算机名,用Windows server 2008 R2更改计算机名的方法

    用Windows server 2008 R2更改计算机名的方法 腾讯视频/爱奇艺/优酷/外卖 充值4折起 Windows Server 2008 R2是第一个只提供64位版本的服务器操作系统,在其使 ...

  7. 联想服务器引导盘制作工具,制作支持UEFI引导的U盘在System x服务器上安装Windows Server 2008 R2操作系统...

    操作步骤: 本例是在System x3550 M5 5463型上通过U盘安装Windows Server 2008 R2操作系统,其他机型以U盘方式安装系统或者以刻录DVD光盘方式安装系统,也可参考本 ...

  8. 浪潮服务器安装windows2008系统,浪潮NF5280M3安装Windows Server 2008 R2注意事项

    近期某单位购买了几台浪潮英信NF5280M3服务器,每台服务器配置有2个E5-2630的CPU.16GB内存.5块2.5寸的600GB的SAS硬盘.服务器到位之后,在安装Windows Server ...

  9. DELL服务器装2003系统

    DELL第12代服务器装2003系统 首先说明DELL官方不支持12代服务器集成S110RAID卡装2003 32位系统. 本人支持S110 固件版本 3.0.0-XXXX 以下的卡, 不支持S110 ...

最新文章

  1. html5 网页游戏 开源,HTML5 网页游戏,基于 WebGL 打造
  2. oracle linux内存推荐分配,浅析Oracle 的体系架构及内存分配机制
  3. 关于listview上下滑动imageview图片混乱问题
  4. 【图像处理】——图像灰度直方图的绘制(直接调用函数和自定义函数)
  5. UIKit应用 - Swift 版本: 3.让UITableViewCell的背景色渐变
  6. 【转】文件各种上传,离不开的表单
  7. Ubuntu Quickbuild 安装配置
  8. ucinet网络分析使用总结
  9. xy轴坐标图数字表示_cad图纸上的X、Y坐标是什么意思? 丫坐标和x坐标图纸上的数...
  10. Java多线程篇--concurrentHashMap
  11. 单片机数码管显示程序c语言,基于STC89C52单片机的动态数码管显示C语言程序
  12. 海洋表面洋流数据可视化
  13. Excel中两表数据核对方法
  14. 2020长三角(上海)区块链应用创新大赛复赛评审圆满结束
  15. 1-编程基础及Python环境部署
  16. 不平衡学习(Imbalanced learning)
  17. 视频压制参数设置详细说明(转)
  18. Django企业it资产管理系统
  19. tmux还有这种操作,我在这边的窗口上操作,你那边可以实时的看到我的操作,厉害了...
  20. Android 蓝牙开发(一) -- 传统蓝牙聊天室

热门文章

  1. photoshop第十一章:人物照片脸部的处理
  2. 1996亚特兰大奥运会歌曲《Reach》铃声 1996亚特兰大奥运会歌曲...
  3. 视角FOV测试—imatest
  4. 神雕侠侣服务器维修时间,《神雕侠侣》2021年1月21日更新维护新服开启公告
  5. wxWidgets 简介
  6. GB28181视频监控管理平台LiveGBS如何指定获取摄像头子码流或者主码流
  7. jsp百度贴吧_JSP【java吧】_百度贴吧
  8. 微信小程序获取微信头像、微信昵称
  9. css 设置变量,通过refs的style.setProperty直接设置变量的值
  10. 布兰特原油飙升至多年高位