none
Windows 7 蓝屏 代码:0x00000034 RRS feed

  • 问题

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


    Loading Dump File [F:\Users\Hello\Desktop\dmp\011411-19718-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 ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Windows 7 Kernel Version 7600 MP (2 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Machine Name:
    Kernel base = 0xfffff800`0461d000 PsLoadedModuleList = 0xfffff800`0485ae50
    Debug session time: Fri Jan 14 15:44:48.785 2011 (GMT+8)
    System Uptime: 0 days 0:00:51.783
    *********************************************************************
    * 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 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 34, {50830, fffff88008753198, fffff88008752a00, fffff8000490cddd}

    ***** 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                                     ***
    ***                                                                   ***
    *************************************************************************
    Unable to load image pffilter.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for pffilter.sys
    *** ERROR: Module load completed but symbols could not be loaded for pffilter.sys
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    *                                                                   *
    * The Symbol Path can be set by:                                    *
    *   using the _NT_SYMBOL_PATH environment variable.                 *
    *   using the -y <symbol_path> argument when starting the debugger. *
    *   using .sympath and .sympath+                                    *
    *********************************************************************
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    *                                                                   *
    * The Symbol Path can be set by:                                    *
    *   using the _NT_SYMBOL_PATH environment variable.                 *
    *   using the -y <symbol_path> argument when starting the debugger. *
    *   using .sympath and .sympath+                                    *
    *********************************************************************
    Probably caused by : pffilter.sys ( pffilter+3a58 )

    Followup: MachineOwner
    ---------
    我也搜索了pffilter.sys 压根就没有这个驱动文件啊。
    T T 大家帮帮忙~

    34是网络重名么?我是在家里的上的,有4台电脑,他们计算机名我也都看过我跟我不一样。

    2011年1月15日 7:08

答案

全部回复

  • 之前是否安装过什么游戏软件?
    如果您的问题得到解答,请进行标注。http://goxia.maytide.net
    2011年1月15日 9:48
    版主
  • 请问您是否在您的电脑上可以找到pffilter.sys这个文件?如果可以找到,它在哪个文件夹?

    谢谢。


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    2011年1月19日 2:13
  • 1、请在DEBUG前正确设置Symbol Path

    2、您是否曾使用过IObit Information Technology出品的Password Folder?

    2011年1月19日 9:00
  • 这个还真过用 Password Folder,难道这个软件有问题?
    2011年2月11日 2:08
  • 没有~ 一怒之下把杀毒软件都卸载了
    2011年2月11日 2:09
  • 找不到这个文件,我在 driver 文件夹里面找都不到~
    2011年2月11日 2:09
  • 请问您是否在您的电脑上可以找到pffilter.sys这个文件?如果可以找到,它在哪个文件夹?

    谢谢。


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    我找到了,确实是像 smalllion 所说的 IObit Information Technology出品的Password Folder软件文件夹里面找到了这个文件。T T 感谢大家 Dmp附件
    • 已编辑 What0o0 2011年2月11日 3:09 添加附件
    2011年2月11日 2:54
  • 1、请在DEBUG前正确设置Symbol Path

    2、您是否曾使用过IObit Information Technology出品的Password Folder?


    谢谢,终于在Password Folder找到这个pffilter.sys了,请教一下Symbol Path怎么设置?Password Folder为什么会引起 34 代码的蓝屏?

    Dmp附件

    2011年2月11日 3:08
  • 1、请在DEBUG前正确设置Symbol Path

    2、您是否曾使用过IObit Information Technology出品的Password Folder?


    谢谢,终于在Password Folder找到这个pffilter.sys了,请教一下Symbol Path怎么设置?Password Folder为什么会引起 34 代码的蓝屏?

    Dmp附件

    设置Symbol Path主要是为了提高DMP文件分析的准确性,其方法是在Windbg的File——Symbol File Path下输入路径,如以下则为一种常用的设置方式,它将从http://msdl.microsoft.com/download/symbols获取symbols到C:\Program Files\Debugging Tools for Windows (x64)\symbols以供使用:

    srv*C:\Program Files\Debugging Tools for Windows (x64)\symbols*http://msdl.microsoft.com/download/symbols

    至于Password Folder为何会引发蓝屏,由于我并非这款产品的使用者,因而不能给您以准确的答复。您可联系软件提供商以获取进阶技术支持。现阶段则可尝试将此软件移除或进行更新。

    关于0x34错误的信息,请参见:http://msdn.microsoft.com/library/ff557491

    2011年2月11日 6:54
  • 1、请在DEBUG前正确设置Symbol Path

    2、您是否曾使用过IObit Information Technology出品的Password Folder?


    谢谢,终于在Password Folder找到这个pffilter.sys了,请教一下Symbol Path怎么设置?Password Folder为什么会引起 34 代码的蓝屏?

    Dmp附件

    设置Symbol Path主要是为了提高DMP文件分析的准确性,其方法是在Windbg的File——Symbol File Path下输入路径,如以下则为一种常用的设置方式,它将从http://msdl.microsoft.com/download/symbols 获取symbols到C:\Program Files\Debugging Tools for Windows (x64)\symbols以供使用:

     

    srv*C:\Program Files\Debugging Tools for Windows (x64)\symbols*http://msdl.microsoft.com/download/symbols

     

    至于Password Folder为何会引发蓝屏,由于我并非这款产品的使用者,因而不能给您以准确的答复。您可联系软件提供商以获取进阶技术支持。现阶段则可尝试将此软件移除或进行更新。

    关于0x34错误的信息,请参见:http://msdn.microsoft.com/library/ff557491

    谢谢您~自从卸载了Password Folder这个软件之后就不会出现 34 蓝屏了~非常感谢~
    2011年2月24日 12:25