none
蓝屏死机的Dump文件贴上来了.请高手帮帮忙啊.看看是什么问题.救命啊. RRS feed

  • 问题

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


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

    Symbol search path is: SRV*DownstreamStore*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Unable to load image ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Machine Name:
    Kernel base = 0x804d8000 PsLoadedModuleList = 0x8055e720
    Debug session time: Thu Dec 25 21:36:11.953 2008 (GMT+8)
    System Uptime: 0 days 2:33:52.694
    Unable to load image ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Loading Kernel Symbols
    ...............................................................
    .........................................................
    Loading User Symbols
    Loading unloaded module list
    .............
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1A, {781, c0615138, 0, e290a000}

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

    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!KPRCB                                      ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!KPRCB                                      ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    Probably caused by : ntoskrnl.exe ( nt+22f43 )

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

    2008年12月25日 18:01

答案

  • 楼上的理解错了,Probably caused by NTOSKRNL.EXE 并不是表示 NTOSKRNL.EXE 受到了损坏。

     

    这是一个典型的内存管理错误,往往是由硬件问题引起的。请检查最近有没有安装过新的硬件设备或驱动程序,重点在更换的设备及驱动中查找问题。

    2008年12月26日 12:02
    版主

全部回复

  • ntoskrnl.exe丢失或损坏了。

     

    ntoskrnl.exe是保护性的进程,在你计算机反复启动的情况下出现。在正常情况下,在任务管理器是不会有该进程的ntoskrnl.exe也可能是w32.bolzano病毒。

     

    这里有一些解决方法你参考一下。

     

    http://baike.baidu.com/view/449849.htm

    2008年12月26日 2:04
    版主
  • 如果安全模式能进的话,并且不蓝屏的话一般可以判断为病毒,你进行杀毒进行了。如果都不能进说明你的系统被破坏了,重装或修复安装吧。

    2008年12月26日 4:48
    版主
  •  

    谢谢。我装有瑞星最新版本的杀毒软件与瑞星个人防火墙。还有卡上网安全助手。这些东西都是随时更新起的。说是病毒引起这样的蓝,自认为不太可能发生,如果说是因为文件丢失也不可能。因为我重启之后也能进入系统。我昨天晚上就是蓝屏之后再次进入本机系统,进行发贴的。实在是一头雾水啊。谢谢版主的帮助。不过我还想问一下版主是不是其他什么原因啊?!
    2008年12月26日 11:01
  •  

    哦。我试试看。谢谢。
    2008年12月26日 11:09
  • 楼上的理解错了,Probably caused by NTOSKRNL.EXE 并不是表示 NTOSKRNL.EXE 受到了损坏。

     

    这是一个典型的内存管理错误,往往是由硬件问题引起的。请检查最近有没有安装过新的硬件设备或驱动程序,重点在更换的设备及驱动中查找问题。

    2008年12月26日 12:02
    版主
  •  

    以前,我装有俩台光驱,后面因为老是出现光驱启动问题所以撤了一台下来。现在只用了一台光驱,刻录的那种。在这之前呢因为把刻录机的所有软件都装上去了的。所以出现了一次蓝屏。后来找到原因是刻录机自带的播放器与系统用户名有冲突所以才蓝屏,必须把系统用户名改为英文的才行。后来我没有改变用户名。只删除了刻录机的全部软件。这样就再也没出现因为这个原因而蓝屏的故障。那么如今看来是不是我撤换了一台光驱到致系统蓝屏故障呢?请 Alexis Zhang帮我分析一下吧。求您了!
    2008年12月27日 6:05