none
vista开机运行后 总是出现蓝屏又迅速自动重启 RRS feed

  • 问题

  • vista开机运行后  总是出现蓝屏又迅速自动重启
    每次蓝屏后代码总是不一样
    昨天蓝屏两次
    记下了蓝屏代码
    0x0000008e
    0x00000050
    不知道是哪里出的问题
    刚刚装了系统
    还刷新了最新的bois
    也重装了显卡驱动
    还是会出现
    蓝屏代码
    0x0000008e
    0x00000050
    诊断文件:
    问题签名:
      问题事件名称: BlueScreen
      OS 版本: 6.0.6000.2.0.0.768.2
      区域设置 ID: 2052

    有关该问题的其他信息:
      BCCode: 1000008e
      BCP1: C0000005
      BCP2: 81CE752B
      BCP3: 9EC4477C
      BCP4: 00000000
      OS Version: 6_0_6000
      Service Pack: 0_0
      Product: 768_1

    有助于描述该问题的文件:
      C:\Windows\Minidump\Mini071709-01.dmp
      C:\Users\love5201314\AppData\Local\Temp\WER-118435-0.sysdata.xml
      C:\Users\love5201314\AppData\Local\Temp\WER2B53.tmp.version.txt

    阅读隐私声明:
      http://go.microsoft.com/fwlink/?linkid=50163&clcid=0x0804

     

     

    问题签名:
      问题事件名称: BlueScreen
      OS 版本: 6.0.6000.2.0.0.768.2
      区域设置 ID: 2052

    有关该问题的其他信息:
      BCCode: 1000008e
      BCP1: C0000005
      BCP2: 81E01E8C
      BCP3: 9DC0F644
      BCP4: 00000000
      OS Version: 6_0_6000
      Service Pack: 0_0
      Product: 768_1

    有助于描述该问题的文件:
      C:\Windows\Minidump\Mini071709-03.dmp
      C:\Users\love5201314\AppData\Local\Temp\WER-94864-0.sysdata.xml
      C:\Users\love5201314\AppData\Local\Temp\WERA83F.tmp.version.txt

    阅读隐私声明:
      http://go.microsoft.com/fwlink/?linkid=50163&clcid=0x0804








    都是诊断的信息


    问题签名
    问题事件名称: WINDOWS_WCP_OTHER_FAILURE2
    OsVersion: 6.0.6000
    File: base\xml\udom_microdom.cpp
    Function: RtlCreateMicrodom
    Line: 4493
    Status: c000a083
    OS 版本: 6.0.6000.2.0.0.768.2
    区域设置 ID: 2052

    帮助描述问题的文件
    poqexec.log
    Cbs.log
    memory.hdmp
    minidump.mdmp


    问题签名
    问题事件名称: BlueScreen
    OS 版本: 6.0.6000.2.0.0.768.2
    区域设置 ID: 2052

    帮助描述问题的文件
    Mini071709-01.dmp
    sysdata.xml
    Version.txt

     查看这些文件的临时副本
    警告: 如果是病毒或其他安全威胁导致了该问题,打开文件副本可能会损害计算

    机。

    关于该问题的额外信息
    BCCode: 1000008e
    BCP1: C0000005
    BCP2: 81CE752B
    BCP3: 9EC4477C
    BCP4: 00000000
    OS Version: 6_0_6000
    Service Pack: 0_0
    Product: 768_1

     

    问题签名
    问题事件名称: BlueScreen
    OS 版本: 6.0.6000.2.0.0.768.2
    区域设置 ID: 2052

    帮助描述问题的文件
    Mini071709-03.dmp
    sysdata.xml
    Version.txt

     查看这些文件的临时副本
    警告: 如果是病毒或其他安全威胁导致了该问题,打开文件副本可能会损害计算

    机。

    关于该问题的额外信息
    BCCode: 1000008e
    BCP1: C0000005
    BCP2: 81E01E8C
    BCP3: 9DC0F644
    BCP4: 00000000
    OS Version: 6_0_6000
    Service Pack: 0_0
    Product: 768_1

     


    问题签名
    问题事件名称: BlueScreen
    OS 版本: 6.0.6000.2.0.0.768.2
    区域设置 ID: 2052

    帮助描述问题的文件
    Mini071709-02.dmp
    sysdata.xml
    Version.txt

     查看这些文件的临时副本
    警告: 如果是病毒或其他安全威胁导致了该问题,打开文件副本可能会损害计算

    机。

    关于该问题的额外信息
    BCCode: 24
    BCP1: 001904AB
    BCP2: 9B43A9E8
    BCP3: 9B43A6E4
    BCP4: 81DD3973
    OS Version: 6_0_6000
    Service Pack: 0_0
    Product: 768_1

    2009年7月18日 3:11

答案

全部回复

  • 請首先嘗試安全模式啟動.
    Folding@Home
    2009年7月18日 3:14
  • 也請閱讀一下這個帖子, 依據裏面的方法, 把診斷信息貼上來.

    如何獲取轉儲文件詳細診斷信息:
    http://social.microsoft.com/Forums/vistazhchs/windowsserversystemzhchs/thread/48d50269-adb8-43b9-a74d-ccf1914eb72f
    Folding@Home
    2009年7月18日 3:14
  • 易宝典:Windows常见蓝屏故障分析(MVP 撰稿)
    http://support.microsoft.com/kb/972602/zh-cn

    其他相關鏈接:

    如何判断我的计算机是否存在内存问题?
    http://windowshelp.microsoft.com/Windows/zh-CN/help/4edd5f80-def2-4d32-965c-116d49fb98722052.mspx

    Folding@Home
    2009年7月18日 3:24
  • 请尝试以下方法:打开控制面板中问题报告和解决方案,选择检查新的解决方案(N),然后提交,如果你的VISTA并不是VISTA SP2的话,把它升级VISTA SP2试试,另外安装Everest观察各硬件工作时温度,尤其长时间工作后,看是否正常范围内。
    2009年7月18日 4:38
  • 因為你目前的系統是 Windows Vista RTM 版(OS Version: 6_0_6000  Service Pack: 0_0). 可以嘗試從其他計算機下載, 并在本機安裝 Windows Vista Service Pack 1 .  SP2 可以暫緩安裝, 然後視情況看, 是否重新安裝驅動程序.

    不過在具體的藍屏原因沒有查明情況下, 我仍然建議你先用 windbg 進行診斷分析. 如果藍屏原因是硬件造成的, 升級為 SP1 不會對此問題有所改善.

    下载详细信息: Windows Vista Service Pack 1 所有语言单行版本(KB936330)
    http://www.microsoft.com/downloads/details.aspx?FamilyID=F559842A-9C9B-4579-B64A-09146A0BA746&displaylang=zh-cn

    Windows Server 2008 Service Pack 2 和 Windows Vista Service Pack 2 的所有语言单行版本 (KB948465)
    http://www.microsoft.com/downloads/details.aspx?FamilyID=891AB806-2431-4D00-AFA3-99FF6F22448D&displaylang=zh-cn

    注: 如要安裝 SP2, 必須先安裝 SP1.


    Folding@Home
    • 已编辑 repl 2009年7月18日 4:53
    2009年7月18日 4:48
  • 我刚才已经提交了
    我昨天在打补丁的时候
    打到一半也突然蓝屏了

    2009年7月18日 4:53
  • 不知是因為不斷藍屏, 才嘗試進行 SP1 升級, 還是由於升級 SP1 失敗, 才造成不斷藍屏?


    Folding@Home
    2009年7月18日 4:55
  • 診斷信息, 需要用 windbg 分析像 C:\Windows\Minidump\Mini071709-01.dmp 這些文件.
    Folding@Home
    2009年7月18日 4:56
  • 你試試在安全模式下能否安裝 windbg, 如果可以請首先用 windbg 分析 dmp 文件.


    Folding@Home
    2009年7月18日 4:58
  • 如果安裝 windbg 失敗, 那么你可以用 U 盤將那些 dmp 文件導出, 然後在其他機器上進行分析, 并把結果貼上來.



    嘗試在安全模式下安裝 SP1, 看能否改善藍屏問題.


    P.S. 請用跟貼方式進行補充, 以便大家能及時看到你的回覆.
    Folding@Home
    2009年7月18日 5:00
  • 没有升级也会蓝屏
    我没有连接网络
    有时装软件都会蓝屏
    后来又重装了系统
    索性什么软件都不装了
    有时浏览网页都会蓝屏
    2009年7月18日 5:01
  • 看來問題還沒有到完全進入不了正常模式的地步, 請下下載并安裝 windbg 進行分析.
    Folding@Home
    2009年7月18日 5:02
  • 既然什麽軟件都沒裝也會藍屏, 那硬件有問題的可能性較大, 也不排除因為沒有安裝防病毒軟件導致系統中毒的可能.
    Folding@Home
    2009年7月18日 5:06
  • 请问下我之前已经有360打了一些补丁
    现在从另外的计算机下载sp1拷贝过来安装
    会不会有冲突
    2009年7月18日 5:09
  • 请问下我之前已经有360打了一些补丁
    现在从另外的计算机下载sp1拷贝过来安装
    会不会有冲突

    可以安装,没有问题的,你发生蓝屏以后有没有进行过病毒查杀?
    2009年7月18日 5:12
  • 我刚才用用 windbg 分析像 C:\Windows\Minidump\Mini071709-01.dmp 這些文件.
    提示没有权限打开
    2009年7月18日 5:17
  • 刚才安装成功了
    但是在打开那些文件的时候
    提示拒绝访问...
    2009年7月18日 5:18
  • 要以管理員身份運行 windbg , 然後在 File 菜單選擇 Open Crash Dump...
    Folding@Home
    2009年7月18日 5:19
  • 下载并安装成功
    但是在打开那些文件时
    提示拒绝访问
    2009年7月18日 5:20
  • 用360在安全模式下查杀了 没有问题
    2009年7月18日 5:20
  • 我检查了内存
    但是没有看见报告
    检测完之后
    重启
    什么都没有出现
    也没有提示
    2009年7月18日 5:22
  • 截圖示意:


    Folding@Home
    • 已编辑 repl 2009年7月18日 5:36
    2009年7月18日 5:23
  • 按你的方法】管理員身份運行 windbg , 然後在 File 菜單選擇 Open Crash Dump...
    弹出一个对话框
    我点了yes
    出来的结果全部的乱码
    2009年7月18日 5:26
  • 出来的结果全部是乱码
    2009年7月18日 5:27
  • 是否打開的是 C:\Windows\Minidump\ 文件夾下的文件?


    Folding@Home
    2009年7月18日 5:28
  • 请问下怎样查看内存检查结果啊
    内存检查结束没有任何提示
    2009年7月18日 5:30
  • 是的
    结果是乱码
    2009年7月18日 5:32
  • 內存診斷結果, 我是很久之前用過, 忘記是否會生成 LOG 文件, 如果在界面上沒有提示有錯, 就可以不管它了.

    現在主要是看 dmp 文件的診斷結果.


    Folding@Home
    2009年7月18日 5:33
  • 你要不截圖貼上來, 我看看到底是什麽樣的情況?

    正常情況如下圖所示:


    Folding@Home

    • 已编辑 repl 2009年7月18日 5:46
    2009年7月18日 5:34
  • 不好意思
    那次机子现在没有联网
    我等下看能不能把图截上来
    2009年7月18日 5:41
  • 还有我试了一下
    机子开在那么
    什么都不动
    就不会蓝屏
    只要不上网
    不装软件
    不打补丁
    好像都正常
    2009年7月18日 5:44
  • 还有我试了一下
    机子开在那么
    什么都不动
    就不会蓝屏
    只要不上网
    不装软件
    不打补丁
    好像都正常

    你回憶一下, 藍屏在上網時候的次數多不.?
    Folding@Home
    2009年7月18日 5:50
  • 还有我试了一下
    机子开在那么
    什么都不动
    就不会蓝屏
    只要不上网
    不装软件
    不打补丁
    好像都正常

    你回憶一下, 藍屏在上網時候的次數多不.?
    Folding@Home

    不多  在浏览网页的时候
    2009年7月18日 5:56
  • 了解, 因為你說在本機用 windbg 打開 dmp 文件有亂碼, 建議你把那些 dmp 文件以管理員權限複製到 U 盤, 在其他電腦上進行診斷分析.


    Folding@Home
    2009年7月18日 6:00
  • 了解, 因為你說在本機用 windbg 打開 dmp 文件有亂碼, 建議你把那些 dmp 文件以管理員權限複製到 U 盤, 在其他電腦上進行診斷分析.


    Folding@Home

    我试试
    2009年7月18日 6:02
  • 你要不截圖貼上來, 我看看到底是什麽樣的情況?

    正常情況如下圖所示:


    Folding@Home

     


    [url=http://tu.6.cn/pic/show/id/4014308][img]http://i3.6.cn/cvbnm/f3/e8/39/27d4cf4f87cdd0d4f804e78cb568bf53.jpg[/img][/url]
    [url=http://tu.6.cn/pic/show/id/4014311][img]http://i3.6.cn/cvbnm/cb/31/44/bef0b5f1ace792bcb2f1b100c22b98bd.jpg[/img][/url]
    [url=http://tu.6.cn/pic/show/id/4014313][img]http://i3.6.cn/cvbnm/81/98/45/e57b5210fc72c02c844c09f3a309789e.jpg[/img][/url]
    2009年7月18日 6:10
  • 怎么截图不显示
    2009年7月18日 6:12

  • 你看看之前那個帖子, 後面幾個回覆是最新貼圖方法.
    Folding@Home
    2009年7月18日 6:13
  •  

    你選錯了, 是用 File -  Open Crash Dump... 菜單打開, 不是 File - Open Source File... 打開.

    Folding@Home
    2009年7月18日 6:16
  • 你要不截圖貼上來, 我看看到底是什麽樣的情況?

    正常情況如下圖所示:


    Folding@Home

     


    [url=http://tu.6.cn/pic/show/id/4014308][img]http://i3.6.cn/cvbnm/f3/e8/39/27d4cf4f87cdd0d4f804e78cb568bf53.jpg[/img][/url]
    
    [url=http://tu.6.cn/pic/show/id/4014311][img]http://i3.6.cn/cvbnm/cb/31/44/bef0b5f1ace792bcb2f1b100c22b98bd.jpg[/img][/url]
    
    [url=http://tu.6.cn/pic/show/id/4014313][img]http://i3.6.cn/cvbnm/81/98/45/e57b5210fc72c02c844c09f3a309789e.jpg[/img][/url]

    <a href="http://tu.6.cn/pic/show/id/4014308"><img src="http://i3.6.cn/cvbnm/f3/e8/39/27d4cf4f87cdd0d4f804e78cb568bf53.jpg" alt="" /></a>
    2009年7月18日 6:18
  • <a href="http://tu.6.cn/pic/show/id/4014308"><img src="http://i3.6.cn/cvbnm/f3/e8/39/27d4cf4f87cdd0d4f804e78cb568bf53.jpg" alt="" /></a>
    要用 HTML 視圖插入, 或者複製要貼的圖像, 粘貼到帖子裏.
    Folding@Home
    2009年7月18日 6:19
  • [url=http://tu.6.cn/pic/show/id/4014308][img]http://i3.6.cn/cvbnm/f3/e8/39/27d4cf4f87cdd0d4f804e78cb568bf53.jpg[/img][/url]
    [url=http://tu.6.cn/pic/show/id/4014311][img]http://i3.6.cn/cvbnm/cb/31/44/bef0b5f1ace792bcb2f1b100c22b98bd.jpg[/img][/url]
    [url=http://tu.6.cn/pic/show/id/4014313][img]http://i3.6.cn/cvbnm/81/98/45/e57b5210fc72c02c844c09f3a309789e.jpg[/img][/url]
    2009年7月18日 6:21
  • 就先不貼圖了, 你試試用 Open Crash Dump... 打開 dmp 文件看是否還是會有亂碼.


    Folding@Home
    2009年7月18日 6:22
  • [url=http://tu.6.cn/pic/show/id/4014311][img]http://i3.6.cn/cvbnm/cb/31/44/bef0b5f1ace792bcb2f1b100c22b98bd.jpg[/img][/url]
    2009年7月18日 6:23

  • 單擊 HTML 按鈕 把下面的代碼貼上去, 用 <br /> 進行回車換行.
    <a href="http://tu.6.cn/pic/show/id/4014308"><img src="http://i3.6.cn/cvbnm/f3/e8/39/27d4cf4f87cdd0d4f804e78cb568bf53.jpg" alt="" /></a>
    Folding@Home
    2009年7月18日 6:24
  •  

    你選錯了, 是用 File -  Open Crash Dump... 菜單打開, 不是 File - Open Source File... 打開.

    Folding@Home


    现在好像可以了
    2009年7月18日 6:31
  • 在輸入 !analyze -v 命令後, 把結果複製上來, 用文字的即可.


    Folding@Home
    2009年7月18日 6:32

  • Microsoft (R) Windows Debugger  Version 6.6.0007.5
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [I:\Minidump\Mini071809-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\ntkrnlpa.exe, Win32 error 2
    *** WARNING: Unable to verify timestamp for ntkrnlpa.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
    Windows Vista Kernel Version 6000 MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Kernel base = 0x82000000 PsLoadedModuleList = 0x82111e10
    Debug session time: Sat Jul 18 11:35:39.681 2009 (GMT+8)
    System Uptime: 0 days 0:12:27.589
    *********************************************************************
    * 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\ntkrnlpa.exe, Win32 error 2
    *** WARNING: Unable to verify timestamp for ntkrnlpa.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
    Loading Kernel Symbols
    .........................................................................................................................................................
    Loading User Symbols
    Loading unloaded module list
    ..................
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000008E, {c0000005, 821ee0bb, 982cea04, 0}

    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.

    ***** 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                                     ***
    ***                                                                   ***
    *************************************************************************
    *** WARNING: Unable to verify timestamp for Hookport.sys
    *** ERROR: Module load completed but symbols could not be loaded for Hookport.sys
    Probably caused by : Hookport.sys ( Hookport+15b8 )

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

    1: kd>  !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
    This is a very common bugcheck.  Usually the exception address pinpoints
    the driver/function that caused the problem.  Always note this address
    as well as the link date of the driver/image that contains this address.
    Some common problems are exception code 0x80000003.  This means a hard
    coded breakpoint or assertion was hit, but this system was booted
    /NODEBUG.  This is not supposed to happen as developers should never have
    hardcoded breakpoints in retail code, but ...
    If this happens, make sure a debugger gets connected, and the
    system is booted /DEBUG.  This will let us see why this breakpoint is
    happening.
    Arguments:
    Arg1: c0000005, The exception code that was not handled
    Arg2: 821ee0bb, The address that the exception occurred at
    Arg3: 982cea04, Trap Frame
    Arg4: 00000000

    Debugging Details:
    ------------------

    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.

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

    FAULTING_MODULE: 82000000 nt

    DEBUG_FLR_IMAGE_TIMESTAMP:  4a569ddb

    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - "0x%08lx"

    FAULTING_IP:
    nt+1ee0bb
    821ee0bb 394608          cmp     dword ptr [esi+8],eax

    TRAP_FRAME:  982cea04 -- (.trap ffffffff982cea04)
    ErrCode = 00000000
    eax=3ed09189 ebx=8360f5c4 ecx=00000011 edx=00000021 esi=030c6b02 edi=00740073
    eip=821ee0bb esp=982cea78 ebp=982cea9c iopl=0         nv up ei pl nz na po nc
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010202
    nt+0x1ee0bb:
    821ee0bb 394608          cmp     dword ptr [esi+8],eax ds:0023:030c6b0a=????????
    Resetting default scope

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  WRONG_SYMBOLS

    BUGCHECK_STR:  0x8E

    LAST_CONTROL_TRANSFER:  from 821eed56 to 821ee0bb

    STACK_TEXT: 
    WARNING: Stack unwind information not available. Following frames may be wrong.
    982cea9c 821eed56 8360f598 982ceb10 00000000 nt+0x1ee0bb
    982ceb18 821ec6a5 00000000 982ceb70 00000040 nt+0x1eed56
    982ceb7c 821839d4 014ffa24 00000000 00000001 nt+0x1ec6a5
    982cebf0 8218ec82 014ffa48 00100001 014ffa24 nt+0x1839d4
    982cec3c 8061b5b8 014ffa48 00100001 014ffa24 nt+0x18ec82
    982ced30 8208caea 014ffa48 00100001 014ffa24 Hookport+0x15b8
    982ced64 77da0f34 badb0d00 014ff9e8 00000000 nt+0x8caea
    982ced68 badb0d00 014ff9e8 00000000 00000000 0x77da0f34
    982ced6c 014ff9e8 00000000 00000000 00000000 0xbadb0d00
    982ced70 00000000 00000000 00000000 00000000 0x14ff9e8


    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    Hookport+15b8
    8061b5b8 ??              ???

    SYMBOL_STACK_INDEX:  5

    SYMBOL_NAME:  Hookport+15b8

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: Hookport

    IMAGE_NAME:  Hookport.sys

    BUCKET_ID:  WRONG_SYMBOLS

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

     

    2009年7月18日 6:35
  • 我这是检测今天蓝屏的  昨天的用不用检测  因为每次蓝屏代码都不一样
    2009年7月18日 6:36
  • 你可以檢查, 貼上來之前如果都有這句話, Probably caused by : Hookport.sys ( Hookport+15b8 ) 就不用貼了

    Hookport.sys 導致藍屏的可能性很大.
    Folding@Home
    2009年7月18日 6:38
  • 請參看一下這個帖子:

    又是蓝屏,又是360的某个文件引起的
    http://bbs.360.cn/3229787/27094709.html
    Folding@Home
    2009年7月18日 6:39

  • Microsoft (R) Windows Debugger  Version 6.6.0007.5
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [I:\Minidump\Mini071709-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\ntkrnlpa.exe, Win32 error 2
    *** WARNING: Unable to verify timestamp for ntkrnlpa.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
    Windows Vista Kernel Version 6000 MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Kernel base = 0x81c00000 PsLoadedModuleList = 0x81d11e10
    Debug session time: Fri Jul 17 13:45:28.015 2009 (GMT+8)
    System Uptime: 0 days 0:17:06.729
    *********************************************************************
    * 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\ntkrnlpa.exe, Win32 error 2
    *** WARNING: Unable to verify timestamp for ntkrnlpa.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
    Loading Kernel Symbols
    ...........................................................................................................................................................
    Loading User Symbols
    Loading unloaded module list
    ......
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000008E, {c0000005, 81ce752b, 9ec4477c, 0}

    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.

    ***** 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                                     ***
    ***                                                                   ***
    *************************************************************************
    *** WARNING: Unable to verify timestamp for Hookport.sys
    *** ERROR: Module load completed but symbols could not be loaded for Hookport.sys
    *** WARNING: Unable to verify timestamp for win32k.sys
    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
    Probably caused by : Hookport.sys ( Hookport+dbf )

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

     

    2009年7月18日 6:43

  • Microsoft (R) Windows Debugger  Version 6.6.0007.5
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [I:\Minidump\Mini071709-02.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\ntkrnlpa.exe, Win32 error 2
    *** WARNING: Unable to verify timestamp for ntkrnlpa.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
    Windows Vista Kernel Version 6000 MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Kernel base = 0x81c00000 PsLoadedModuleList = 0x81d11e10
    Debug session time: Fri Jul 17 20:27:59.842 2009 (GMT+8)
    System Uptime: 0 days 1:10:58.725
    *********************************************************************
    * 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\ntkrnlpa.exe, Win32 error 2
    *** WARNING: Unable to verify timestamp for ntkrnlpa.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
    Loading Kernel Symbols
    ..........................................................................................................................................................
    Loading User Symbols
    Loading unloaded module list
    ..............................
    Unable to load image \SystemRoot\System32\Drivers\Ntfs.sys, Win32 error 2
    *** WARNING: Unable to verify timestamp for Ntfs.sys
    *** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 24, {1904ab, 9b43a9e8, 9b43a6e4, 81dd3973}

    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.

    ***** 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                                     ***
    ***                                                                   ***
    *************************************************************************
    Probably caused by : Ntfs.sys ( Ntfs+d6f2 )

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

     

    2009年7月18日 6:44
  • 補充一下, 如果診斷信息裏有  KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e) 和 Probably caused by : Hookport.sys ( Hookport+15b8 ) 就不用貼了. 其他的可以貼上來.


    Folding@Home
    2009年7月18日 6:44

  • Microsoft (R) Windows Debugger  Version 6.6.0007.5
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [I:\Minidump\Mini071709-03.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\ntkrnlpa.exe, Win32 error 2
    *** WARNING: Unable to verify timestamp for ntkrnlpa.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
    Windows Vista Kernel Version 6000 MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Kernel base = 0x81c00000 PsLoadedModuleList = 0x81d11e10
    Debug session time: Fri Jul 17 21:02:54.332 2009 (GMT+8)
    System Uptime: 0 days 0:33:41.237
    *********************************************************************
    * 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\ntkrnlpa.exe, Win32 error 2
    *** WARNING: Unable to verify timestamp for ntkrnlpa.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
    Loading Kernel Symbols
    ..........................................................................................................................................................
    Loading User Symbols
    Loading unloaded module list
    ......
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000008E, {c0000005, 81e01e8c, 9dc0f644, 0}

    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.

    ***** 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                                     ***
    ***                                                                   ***
    *************************************************************************
    *** WARNING: Unable to verify timestamp for fileinfo.sys
    *** ERROR: Module load completed but symbols could not be loaded for fileinfo.sys
    *** WARNING: Unable to verify timestamp for fltmgr.sys
    *** ERROR: Module load completed but symbols could not be loaded for fltmgr.sys
    *** WARNING: Unable to verify timestamp for AsDsm.sys
    *** ERROR: Module load completed but symbols could not be loaded for AsDsm.sys
    *** WARNING: Unable to verify timestamp for Hookport.sys
    *** ERROR: Module load completed but symbols could not be loaded for Hookport.sys
    Probably caused by : fileinfo.sys ( fileinfo+5e9a )

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

     

    2009年7月18日 6:44

  • Microsoft (R) Windows Debugger  Version 6.6.0007.5
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [I:\Minidump\Mini071709-04.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\ntkrnlpa.exe, Win32 error 2
    *** WARNING: Unable to verify timestamp for ntkrnlpa.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
    Windows Vista Kernel Version 6000 MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Kernel base = 0x82000000 PsLoadedModuleList = 0x82111e10
    Debug session time: Fri Jul 17 21:09:13.562 2009 (GMT+8)
    System Uptime: 0 days 0:05:33.466
    *********************************************************************
    * 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\ntkrnlpa.exe, Win32 error 2
    *** WARNING: Unable to verify timestamp for ntkrnlpa.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
    Loading Kernel Symbols
    .........................................................................................................................................................
    Loading User Symbols
    Loading unloaded module list
    .....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 50, {c7cedc99, 0, 821ee0bb, 2}

    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.

    ***** 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                                     ***
    ***                                                                   ***
    *************************************************************************
    Probably caused by : ntkrnlpa.exe ( nt+1ee0bb )

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

     

    2009年7月18日 6:46
  • 還有這個帖子

    求助!电脑蓝屏听说是和卡巴有关,真是这样吗?有谁能解答
    http://bbs.360.cn/3217044/27326444.html

    如果你沒有安裝卡巴, 就把 360 暫時卸載了, 這個和之前的那個帖子都是最近的
    Folding@Home
    2009年7月18日 6:46
  • 還有你最好加載 symbol 文件, 這樣診斷結果更準確.
    Folding@Home
    2009年7月18日 6:50
  • 我之前装过卡巴了  但是今天又装了系统
    卡巴还在电脑里
    但是没有去重装
    或者去修复
    要不要删去卡巴
    那我现在卸了360
    主要是感觉360打补丁不windows  update
    而且360打的补丁文件我都知道在哪里
    一般都是手动安装
    比较快
    windows  update打补丁特慢
    安装也慢
    2009年7月18日 6:51
  • 又一個提到了 Hookport.sys 的帖子, 也是最近的.

    [求助] 联想y450蓝屏问题
    http://bbs.cfan.com.cn/viewthread.php?tid=948843&page=1&authorid=845714
    Folding@Home
    2009年7月18日 6:52
  • 如果卡巴還在先卸載卡巴, 因為有網友說卸載卡巴後, 不再藍屏, 若還不行, 再卸載 360.

    雖然提到 Hookport.sys 但不一定就是藍屏的直接原因, 不排除是與卡巴有衝突.
    Folding@Home
    2009年7月18日 6:53
  • 還有你最好加載 symbol 文件, 這樣診斷結果更準確.
    Folding@Home

    怎么加载
    2009年7月18日 6:54
  • 請參見之前那個帖子, 谢依村的第7步.


    Folding@Home
    2009年7月18日 6:55
  • 我再看看你後來貼的診斷信息.
    Folding@Home
    2009年7月18日 6:56
  • 卡巴刚刚直接删了
    2009年7月18日 6:59
  • 請參見之前那個帖子, 谢依村的第7步.


    Folding@Home

    哪个帖子
    2009年7月18日 6:59
  • 直接刪除? 是用卸載程序刪除嗎?

    如果不是就麻煩了, 因為有些組件就不能清除了


    Folding@Home
    2009年7月18日 7:00
  • 如果是正常刪除卡巴, 那么請觀察系統的運行情況, 因為你後面幾個藍屏, 雖然沒有運行 !analyze -v 命令, 但是從程序自動返回的結果看涉及到文件系統的驅動程序有問題, 比如 ntfs.sys 和 fileinfo.sys. 如果仍然出現藍屏, 請用 sfc /scannow 嘗試修復系統文件, 或者重裝系統, 如果要重裝系統最好安裝完成以後, 升級到 SP1, 如運行正常, 再考慮升級到 SP2 .
    Folding@Home
    2009年7月18日 7:03
  • 我今天刚装的系统
    卡巴都没有装啊
    控制面板里面也没有卸载卡巴的方式啊
    所以直接删了卡巴以前的安装文件夹
    2009年7月18日 7:08
  • 是 Program Files 文件夾下面的嗎?

    如果是, 你有系統還原的話, 進行系統還原.

    如果不是則比較麻煩了, 用清楚工具清理不乾淨, 後面的使用是會出大問題的.


    Folding@Home
    2009年7月18日 7:10
  • 如果是正常刪除卡巴, 那么請觀察系統的運行情況, 因為你後面幾個藍屏, 雖然沒有運行 !analyze -v 命令, 但是從程序自動返回的結果看涉及到文件系統的驅動程序有問題, 比如 ntfs.sys 和 fileinfo.sys. 如果仍然出現藍屏, 請用 sfc /scannow 嘗試修復系統文件, 或者重裝系統, 如果要重裝系統最好安裝完成以後, 升級到 SP1, 如運行正常, 再考慮升級到 SP2 .
    Folding@Home

    我按那种方式进行到第9步
    弹出了
    2009年7月18日 7:13
  • 加載 symbol 文件需要接入網絡, 所以速度不是很快.
    Folding@Home
    2009年7月18日 7:14
  • 是 Program Files 文件夾下面的嗎?

    如果是, 你有系統還原的話, 進行系統還原.

    如果不是則比較麻煩了, 用清楚工具清理不乾淨, 後面的使用是會出大問題的.


    Folding@Home

    我卡巴以前装的
    今天重新装了系统
    今天没有装卡巴
    和没有修复卡巴
    也没有去用卡巴
    也会出现吗
    2009年7月18日 7:19
  • 加載 symbol 文件需要接入網絡, 所以速度不是很快.
    Folding@Home

    那是不是现在要接入网络
    然后再从第七步开始吗
    2009年7月18日 7:20
  • 只要這次安裝系統後, 沒有安裝卡巴就不會.

    那請暫時把 360 進行卸載. 看看是否由於這個造成的.

    至於用 360 升級系統補丁, 之後再想辦法.
    Folding@Home
    2009年7月18日 7:21
  • 可以不用, 接入網絡即可.
    Folding@Home
    2009年7月18日 7:21
  • 可以不用, 接入網絡即可.
    Folding@Home

    那我等下接入网络 再从第七步开始 
    我现在来卸载360
    对了
    可以把360里已经下载好的系统补丁复制过来吧
    防止等下如果装系统
    再重新下载补丁
    2009年7月18日 7:24
  • 可以把 hotfix 文件夾下的補丁全部複製出來, 建議因為你想目前不穩定, 如果 U 盤空間足夠的話, 也複製到 U 盤作為備份.
    Folding@Home
    2009年7月18日 7:27
  • 可以把 hotfix 文件夾下的補丁全部複製出來, 建議因為你想目前不穩定, 如果 U 盤空間足夠的話, 也複製到 U 盤作為備份.
    Folding@Home

    卡巴删了
    360卸了
    我现在来连接网络
    看会不会有提示
    打开9. 打开例如C:\Windows\Minidump\Mini122208-01.dmp后,等待提示
    当出现 Use !analyze -v to get detailed debugging information. 字样后,在下面输入框
    2009年7月18日 7:29
  • 其實 "当出现 Use !analyze -v to get detailed debugging information. 字样后" 直接用鼠標單擊 !analyze -v 即可.


    Folding@Home
    2009年7月18日 7:31
  • 其實 "当出现 Use !analyze -v to get detailed debugging information. 字样后" 直接用鼠標單擊 !analyze -v 即可.


    Folding@Home

    问题是没有出现 Use !analyze -v to get detailed debugging information. 字样
    2009年7月18日 7:32
  • 其實 "当出现 Use !analyze -v to get detailed debugging information. 字样后" 直接用鼠標單擊 !analyze -v 即可.


    Folding@Home

    问题是没有出现 Use !analyze -v to get detailed debugging information. 字样
    2009年7月18日 7:33
  • 你看看文件夾 C:\Temp 裏面有無文件, 你的 symbol 文件從之前的截圖看是放在那裏的.
    Folding@Home
    2009年7月18日 7:34
  • 你看看文件夾 C:\Temp 裏面有無文件, 你的 symbol 文件從之前的截圖看是放在那裏的.
    Folding@Home

    有文件
    2009年7月18日 7:38
  • 沒有看到 windbg 不能在 Windows XP 下調試更高版本 Windows 的說明. 你等等, 我找找 Debuggee not connected 的說明.


    Folding@Home
    2009年7月18日 7:41
  • 沒有看到 windbg 不能在 Windows XP 下調試更高版本 Windows 的說明. 你等等, 我找找 Debuggee not connected 的說明.


    Folding@Home

    哦  还是出现那样的提示啊
    没有没有出现 Use !analyze -v to get detailed debugging information. 字样
    2009年7月18日 7:47
  • 這樣你重新運行 windbg 試試, 如果還是不行就把 symbol 去掉, 反正可用的診斷內容也只有寄存器和堆棧跟蹤.
    Folding@Home
    2009年7月18日 7:56
  • 你那些 dmp 文件是不是只有幾百KB?


    Folding@Home
    2009年7月18日 7:59
  • 這樣你重新運行 windbg 試試, 如果還是不行就把 symbol 去掉, 反正可用的診斷內容也只有寄存器和堆棧跟蹤.
    Folding@Home

    我试试
    2009年7月18日 8:01
  • 這樣你重新運行 windbg 試試, 如果還是不行就把 symbol 去掉, 反正可用的診斷內容也只有寄存器和堆棧跟蹤.
    Folding@Home

    我试试

    我在其他的电脑上运行都没有区别吧
    2009年7月18日 8:03
  • 這個我沒試過, 不過 windbg 是可以調試比當前系統高的版本, 加載 symbol 也沒問題. 比如我幫別人調試的 Windows 7 dmp 文件.

    截圖:

    Folding@Home
    2009年7月18日 8:08
  • 你那些 dmp 文件是不是只有幾百KB?


    Folding@Home

    都是100多
    2009年7月18日 8:17
  • 這個我沒試過, 不過 windbg 是可以調試比當前系統高的版本, 加載 symbol 也沒問題. 比如我幫別人調試的 Windows 7 dmp 文件.

    截圖:

    Folding@Home


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


    Loading Dump File [C:\Windows\Minidump\Mini071809-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is:

    SRV*c:\temp*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 2
    *** WARNING: Unable to verify timestamp for ntkrnlpa.exe
    *** ERROR: Module load completed but symbols could not be loaded for

    ntkrnlpa.exe
    Windows Vista Kernel Version 6000 MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Kernel base = 0x82000000 PsLoadedModuleList = 0x82111e10
    Debug session time: Sat Jul 18 11:35:39.681 2009 (GMT+8)
    System Uptime: 0 days 0:12:27.589
    Map \SystemRoot\system32\ntkrnlpa.exe:
      Image region f2c00:180400 does not fit in mapping
    *** WARNING: Unable to verify timestamp for ntkrnlpa.exe
    *** ERROR: Module load completed but symbols could not be loaded for

    ntkrnlpa.exe
    Loading Kernel Symbols
    ......................................................................

    ......................................................................

    .............
    Loading User Symbols
    Loading unloaded module list
    ..................
    **********************************************************************

    *********
    *                                                                     

           *
    *                        Bugcheck Analysis                            

           *
    *                                                                     

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

    *********

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000008E, {c0000005, 821ee0bb, 982cea04, 0}

    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.

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

    ***
    ***                                                                  

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

    ***
    *** WARNING: Unable to verify timestamp for Hookport.sys
    *** ERROR: Module load completed but symbols could not be loaded for

    Hookport.sys
    Probably caused by : Hookport.sys ( Hookport+15b8 )

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

    1: kd> !analyze -v
    **********************************************************************

    *********
    *                                                                     

           *
    *                        Bugcheck Analysis                            

           *
    *                                                                     

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

    *********

    KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
    This is a very common bugcheck.  Usually the exception address

    pinpoints
    the driver/function that caused the problem.  Always note this address
    as well as the link date of the driver/image that contains this

    address.
    Some common problems are exception code 0x80000003.  This means a hard
    coded breakpoint or assertion was hit, but this system was booted
    /NODEBUG.  This is not supposed to happen as developers should never

    have
    hardcoded breakpoints in retail code, but ...
    If this happens, make sure a debugger gets connected, and the
    system is booted /DEBUG.  This will let us see why this breakpoint is
    happening.
    Arguments:
    Arg1: c0000005, The exception code that was not handled
    Arg2: 821ee0bb, The address that the exception occurred at
    Arg3: 982cea04, Trap Frame
    Arg4: 00000000

    Debugging Details:
    ------------------

    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.

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

    ***
    ***                                                                  

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

    ***

    FAULTING_MODULE: 82000000 nt

    DEBUG_FLR_IMAGE_TIMESTAMP:  4a569ddb

    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - 0x%08lx

    FAULTING_IP:
    nt+1ee0bb
    821ee0bb 394608          cmp     dword ptr [esi+8],eax

    TRAP_FRAME:  982cea04 -- (.trap ffffffff982cea04)
    ErrCode = 00000000
    eax=3ed09189 ebx=8360f5c4 ecx=00000011 edx=00000021 esi=030c6b02

    edi=00740073
    eip=821ee0bb esp=982cea78 ebp=982cea9c iopl=0         nv up ei pl nz

    na po nc
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000            

    efl=00010202
    nt+0x1ee0bb:
    821ee0bb 394608          cmp     dword ptr [esi+8],eax

    ds:0023:030c6b0a=????????
    Resetting default scope

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  WRONG_SYMBOLS

    BUGCHECK_STR:  0x8E

    LAST_CONTROL_TRANSFER:  from 821eed56 to 821ee0bb

    STACK_TEXT: 
    WARNING: Stack unwind information not available. Following frames may

    be wrong.
    982cea9c 821eed56 8360f598 982ceb10 00000000 nt+0x1ee0bb
    982ceb18 821ec6a5 00000000 982ceb70 00000040 nt+0x1eed56
    982ceb7c 821839d4 014ffa24 00000000 00000001 nt+0x1ec6a5
    982cebf0 8218ec82 014ffa48 00100001 014ffa24 nt+0x1839d4
    982cec3c 8061b5b8 014ffa48 00100001 014ffa24 nt+0x18ec82
    982ced30 8208caea 014ffa48 00100001 014ffa24 Hookport+0x15b8
    982ced64 77da0f34 badb0d00 014ff9e8 00000000 nt+0x8caea
    982ced68 badb0d00 014ff9e8 00000000 00000000 0x77da0f34
    982ced6c 014ff9e8 00000000 00000000 00000000 0xbadb0d00
    982ced70 00000000 00000000 00000000 00000000 0x14ff9e8


    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    Hookport+15b8
    8061b5b8 ??              ???

    SYMBOL_STACK_INDEX:  5

    SYMBOL_NAME:  Hookport+15b8

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: Hookport

    IMAGE_NAME:  Hookport.sys

    BUCKET_ID:  WRONG_SYMBOLS

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

     

     

    2009年7月18日 8:19
  • 這個我沒試過, 不過 windbg 是可以調試比當前系統高的版本, 加載 symbol 也沒問題. 比如我幫別人調試的 Windows 7 dmp 文件.

    截圖:

    Folding@Home


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


    Loading Dump File [C:\Windows\Minidump\Mini071809-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is:

    SRV*c:\temp*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 2
    *** WARNING: Unable to verify timestamp for ntkrnlpa.exe
    *** ERROR: Module load completed but symbols could not be loaded for

    ntkrnlpa.exe
    Windows Vista Kernel Version 6000 MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Kernel base = 0x82000000 PsLoadedModuleList = 0x82111e10
    Debug session time: Sat Jul 18 11:35:39.681 2009 (GMT+8)
    System Uptime: 0 days 0:12:27.589
    Map \SystemRoot\system32\ntkrnlpa.exe:
      Image region f2c00:180400 does not fit in mapping
    *** WARNING: Unable to verify timestamp for ntkrnlpa.exe
    *** ERROR: Module load completed but symbols could not be loaded for

    ntkrnlpa.exe
    Loading Kernel Symbols
    ......................................................................

    ......................................................................

    .............
    Loading User Symbols
    Loading unloaded module list
    ..................
    **********************************************************************

    *********
    *                                                                     

           *
    *                        Bugcheck Analysis                            

           *
    *                                                                     

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

    *********

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000008E, {c0000005, 821ee0bb, 982cea04, 0}

    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.

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

    ***
    ***                                                                  

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

    ***
    *** WARNING: Unable to verify timestamp for Hookport.sys
    *** ERROR: Module load completed but symbols could not be loaded for

    Hookport.sys
    Probably caused by : Hookport.sys ( Hookport+15b8 )

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

    1: kd> !analyze -v
    **********************************************************************

    *********
    *                                                                     

           *
    *                        Bugcheck Analysis                            

           *
    *                                                                     

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

    *********

    KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
    This is a very common bugcheck.  Usually the exception address

    pinpoints
    the driver/function that caused the problem.  Always note this address
    as well as the link date of the driver/image that contains this

    address.
    Some common problems are exception code 0x80000003.  This means a hard
    coded breakpoint or assertion was hit, but this system was booted
    /NODEBUG.  This is not supposed to happen as developers should never

    have
    hardcoded breakpoints in retail code, but ...
    If this happens, make sure a debugger gets connected, and the
    system is booted /DEBUG.  This will let us see why this breakpoint is
    happening.
    Arguments:
    Arg1: c0000005, The exception code that was not handled
    Arg2: 821ee0bb, The address that the exception occurred at
    Arg3: 982cea04, Trap Frame
    Arg4: 00000000

    Debugging Details:
    ------------------

    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.

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

    ***
    ***                                                                  

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

    ***

    FAULTING_MODULE: 82000000 nt

    DEBUG_FLR_IMAGE_TIMESTAMP:  4a569ddb

    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - 0x%08lx

    FAULTING_IP:
    nt+1ee0bb
    821ee0bb 394608          cmp     dword ptr [esi+8],eax

    TRAP_FRAME:  982cea04 -- (.trap ffffffff982cea04)
    ErrCode = 00000000
    eax=3ed09189 ebx=8360f5c4 ecx=00000011 edx=00000021 esi=030c6b02

    edi=00740073
    eip=821ee0bb esp=982cea78 ebp=982cea9c iopl=0         nv up ei pl nz

    na po nc
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000            

    efl=00010202
    nt+0x1ee0bb:
    821ee0bb 394608          cmp     dword ptr [esi+8],eax

    ds:0023:030c6b0a=????????
    Resetting default scope

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  WRONG_SYMBOLS

    BUGCHECK_STR:  0x8E

    LAST_CONTROL_TRANSFER:  from 821eed56 to 821ee0bb

    STACK_TEXT: 
    WARNING: Stack unwind information not available. Following frames may

    be wrong.
    982cea9c 821eed56 8360f598 982ceb10 00000000 nt+0x1ee0bb
    982ceb18 821ec6a5 00000000 982ceb70 00000040 nt+0x1eed56
    982ceb7c 821839d4 014ffa24 00000000 00000001 nt+0x1ec6a5
    982cebf0 8218ec82 014ffa48 00100001 014ffa24 nt+0x1839d4
    982cec3c 8061b5b8 014ffa48 00100001 014ffa24 nt+0x18ec82
    982ced30 8208caea 014ffa48 00100001 014ffa24 Hookport+0x15b8
    982ced64 77da0f34 badb0d00 014ff9e8 00000000 nt+0x8caea
    982ced68 badb0d00 014ff9e8 00000000 00000000 0x77da0f34
    982ced6c 014ff9e8 00000000 00000000 00000000 0xbadb0d00
    982ced70 00000000 00000000 00000000 00000000 0x14ff9e8


    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    Hookport+15b8
    8061b5b8 ??              ???

    SYMBOL_STACK_INDEX:  5

    SYMBOL_NAME:  Hookport+15b8

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: Hookport

    IMAGE_NAME:  Hookport.sys

    BUCKET_ID:  WRONG_SYMBOLS

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

     

     


    刚刚在哪台电脑上加载的
    2009年7月18日 8:22
  • 這個不影響什麽, 就是可供分析的內容較少.

    建議你在 Windows Vista 上建立一個受限用戶, 然後用這個受限用戶登錄系統後上網, 只訪問受信任的網站, 用一段時間看是否還會藍屏.

    如果還有再用 windbg 進行分析.

    沒有的話, 你可以再次嘗試安裝 SP1.

    也可以直接在 Windows Vista 上進行對之前那些 dmp 文件診斷分析, 同時加載 symbol 文件.
    Folding@Home
    2009年7月18日 8:26
  • 這個不影響什麽, 就是可供分析的內容較少.

    建議你在 Windows Vista 上建立一個受限用戶, 然後用這個受限用戶登錄系統後上網, 只訪問受信任的網站, 用一段時間看是否還會藍屏.

    如果還有再用 windbg 進行分析.

    沒有的話, 你可以再次嘗試安裝 SP1.

    也可以直接在 Windows Vista 上進行對之前那些 dmp 文件診斷分析, 同時加載 symbol 文件.
    Folding@Home

    刚才那个就是我在那台电脑上加载的
    我要不全部加载发上来
    2009年7月18日 8:30
  • 先不用, 如果有新的藍屏發生, 再把 dmp 文件的診斷分析內容貼上來.
    Folding@Home
    2009年7月18日 8:33
  • 先不用, 如果有新的藍屏發生, 再把 dmp 文件的診斷分析內容貼上來.
    Folding@Home

    那请问下
    现在检测出原因了没有
    就怕
    等下又是蓝屏频繁
    2009年7月18日 8:36
  • 請不要貼診斷結果了, 因為這個帖子已經太長了. 也不要對已貼的診斷內容加以引用進行回覆.


    Folding@Home
    2009年7月18日 8:41
  • 先不用, 如果有新的藍屏發生, 再把 dmp 文件的診斷分析內容貼上來.
    Folding@Home

    那请问下
    现在检测出原因了没有
    就怕
    等下又是蓝屏频繁

    那5个系统诊断
    现在查出原因了没
    2009年7月18日 8:44
  • 如果是正常刪除卡巴, 那么請觀察系統的運行情況, 因為你後面幾個藍屏, 雖然沒有運行 !analyze -v 命令, 但是從程序自動返回的結果看涉及到文件系統的驅動程序有問題, 比如 ntfs.sys 和 fileinfo.sys. 如果仍然出現藍屏, 請用 sfc /scannow 嘗試修復系統文件, 或者重裝系統, 如果要重裝系統最好安裝完成以後, 升級到 SP1, 如運行正常, 再考慮升級到 SP2 .

    這個是之前一個回覆, 因為帖子太多, 可能你沒有看到. 至少目前看來軟件衝突的可能性大於硬件有問題, 因為你的系統是 Windows Vista RTM 版, 而那些軟件版本都比較新, 不能保證它們不會有衝突. 總之先觀察幾天, 如果還有藍屏發生, 再貼上來也不遲.



    Folding@Home
    2009年7月18日 8:47
  • 請不要貼診斷結果了, 因為這個帖子已經太長了. 也不要對已貼的診斷內容加以引用進行回覆.


    Folding@Home

    我想问下
    装sp1
    是在其他的电脑上下载下来
    然后拷到电脑上装好
    还是直接用update装好
    我在网上看到
    Windows Vista Service Pack 1 — 下载须知

    发布时间:2008 年 3 月 18 日

    • Windows Vista SP1 提供了英语、法语、德语、西班牙语和日语五种语言版本。其他语言版本也即将推出。
    • Microsoft 强烈建议在单台 PC 上使用 Windows Update 下载和安装 Windows Vista SP1:
      • Windows Update 提供的针对 x86 的 Windows Vista SP1 的下载大小为 65 MB(与之相比,Microsoft 下载中心提供的下载大小要大得多,为 450 MB)。
      • Windows Update 提供的针对 x64 的 Windows Vista SP1 的下载大小为 125 MB(与之相比,Microsoft 下载中心提供的下载大小为 745 MB)。
      • Windows Update 能够识别出其驱动程序存在已知问题的 PC,并在该 PC 更新驱动程序或应用其他适用更新后才下载 Windows Vista SP1。使用 Windows Update 有助于确保您获得尽可能完美的更新体验。
      • 某些 Windows Vista 用户在将 Windows Vista PC 更新到 Windows Vista SP1 后,一小部分硬件设备可能无法正常工作。此问题是由于在 Windows Vista SP1 更新过程中重新安装设备驱动程序导致的,但这些驱动程序本身并没有问题,它们在 Windows Vista RTM 和 Windows Vista SP1 上都能正常工作。通常,卸载并重新安装驱动程序即可解决此问题。我们正在与这些设备的制造商合作,以更新存在已知问题的驱动程序及其安装程序。同时,我们也在共同开发其他解决方案,以确保客户在使用 Windows Update 更新到 Windows Vista SP1 时获得完美的客户体验。预先配置了 Windows Vista SP1 的新 PC 不存在此问题。
    2009年7月18日 8:48
  • 你在其他電腦下載好, 因為 SP1 文件較大, 在其他電腦手動下載速度會比較快. 下載地址在最前面一個回覆裏.

    還有在安裝 SP1 之前, 請對系統卷 C: 進行磁盤檢查, 注意不是扇區檢查.
    Folding@Home
    2009年7月18日 8:50
  • 你在其他電腦下載好, 因為 SP1 文件較大, 在其他電腦手動下載速度會比較快. 下載地址在最前面一個回覆裏.

    還有在安裝 SP1 之前, 請對系統卷 C: 進行磁盤檢查, 注意不是扇區檢查.
    Folding@Home

    谢谢啦
    如果再蓝屏
    那就只好再麻烦你啦
    能告诉我你的qq吗
    以后如果蓝屏了
    就不用在这上面发这么长的帖子啊
    谢谢啦
    2009年7月18日 8:56
  • 用郵箱吧 uid1434@163.com .
    Folding@Home
    • 已编辑 repl 2009年7月18日 9:03
    2009年7月18日 9:03
  • 我刚刚在安装sp1的时候提示
    出现内部错误
    错误代码:0x80073712
    请问怎么解决
    是直接在别的电脑上面下载
    然后拷过来安装的

    2009年7月18日 12:11
  • 下載并運行 系统更新准备工具, 運行之前請仔細閱讀該 KB .

    Windows Vista、Windows Server 2008、Windows Server 2008 R2 候选发布版本和 Windows 7 候选发布版本的系统更新准备工具说明
    http://support.microsoft.com/kb/947821/zh-cn


    Folding@Home
    2009年7月18日 12:14
  • 一個 Microsoft 幫助和支持

    尝试为 Windows Vista Service Pack 1、Windows Vista Service Pack 2 或 Windows Server 2008 Service Pack 2 安装独立程序包时会出现错误消息:“Installation was not successful”(安装未成功)或“An internal error occurred while installing the service pack”(安装 Service Pack 时出现内部错误)
    http://support.microsoft.com/kb/947366/zh-cn
    Folding@Home
    2009年7月18日 12:19
  • 下載并運行 系统更新准备工具, 運行之前請仔細閱讀該 KB .

    Windows Vista、Windows Server 2008、Windows Server 2008 R2 候选发布版本和 Windows 7 候选发布版本的系统更新准备工具说明
    http://support.microsoft.com/kb/947821/zh-cn


    Folding@Home


    用update更新时
    总是提示错误
    部分没有更新
    总是提示
    2009年7月18日 12:20
  • 要不這樣你用郵件, 一這個帖子已經很長. 二來你的問題發生了變更.
    Folding@Home
    2009年7月18日 12:22
  • 要不這樣你用郵件, 一這個帖子已經很長. 二來你的問題發生了變更.
    Folding@Home

    可不可以单独去网上下载系统更新准备工具
    用update下载老是提示错误
    下载不了
    发了邮件给你了
    2009年7月18日 13:04
  • 郵件已發送
    Folding@Home
    2009年7月18日 13:07
  • 默认情况下,系统出现错误时会自动重新启动。将该功能关闭方便查看故障的详细信息:

    在桌面上右键点击“我的电脑”,在弹出的右键菜单中选择“属性”,弹出“系统属性”窗口,点选“高级”选项卡,点击“启动和故障恢复”栏目中的“设置”按钮,弹出“启动和故障恢复”窗口。在“系统失败”栏目中将“自动重新启动”选项前的对勾去掉,点“确定”按钮。


    Yog Li - MSFT
    2009年7月22日 11:15
    版主
  • 后来解决了吗?
    2019年8月13日 3:27