none
经常蓝屏怎么办,烦死了 RRS feed

  • 问题

  • win10专业版

    -------------------------------------------------------------------------------------------------------------

    系统日志还每次报这个错误

    应用程序-特定 权限设置并未向在应用程序容器 不可用 SID (不可用)中运行的地址 LocalHost (使用 LRPC) 中的用户 NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19)授予针对 CLSID 为 
    {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52}
    、APPID 为 
    {4839DDB7-58C2-48F5-8283-E1D1807D0D7D}
     的 COM 服务器应用程序的 本地 激活 权限。此安全权限可以使用组件服务管理工具进行修改。

    --------------------------------------------------------------------------------------------------------------------

    蓝屏代码的分析

    --------------------------------------------------------------------------------------------

    Microsoft (R) Windows Debugger Version 10.0.16299.15 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\081018-8734-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: srv* 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 10 Kernel Version 16299 MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Machine Name: Kernel base = 0xfffff802`d3092000 PsLoadedModuleList = 0xfffff802`d33f3ff0 Debug session time: Fri Aug 10 19:50:41.722 2018 (UTC + 8:00) System Uptime: 0 days 23:54:46.440 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 ........... ************* Symbol Loading Error Summary ************** Module name Error ntoskrnl The system cannot find the file specified You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded. You should also verify that your symbol search path (.sympath) is correct. Unable to add extension DLL: kdexts Unable to add extension DLL: kext Unable to add extension DLL: exts The call to LoadLibrary(ext) failed, Win32 error 0n2 "系统找不到指定的文件。" Please check your debugger configuration and/or network access. No .natvis files found at C:\WINDOWS\SYSTEM32\Visualizers. No .natvis files found at C:\Users\Administrator\AppData\Local\Dbg\Visualizers. The call to LoadLibrary(ext) failed, Win32 error 0n2 "系统找不到指定的文件。" Please check your debugger configuration and/or network access. ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Bugcheck code 000000C2 Arguments 00000000`00000004 00000000`620cf527 00000000`094b4062 ffffb58d`329af518 RetAddr : Args to Child : Call Site fffff802`d3339eea : 00000000`000000c2 00000000`00000004 00000000`620cf527 00000000`094b4062 : nt+0x1640e0 00000000`000000c2 : 00000000`00000004 00000000`620cf527 00000000`094b4062 ffffb58d`329af518 : nt+0x2a7eea 00000000`00000004 : 00000000`620cf527 00000000`094b4062 ffffb58d`329af518 fffff80d`a7f3128e : 0xc2 00000000`620cf527 : 00000000`094b4062 ffffb58d`329af518 fffff80d`a7f3128e ffffb58d`2dc4c030 : 0x4 00000000`094b4062 : ffffb58d`329af518 fffff80d`a7f3128e ffffb58d`2dc4c030 00000000`00000000 : 0x620cf527 ffffb58d`329af518 : fffff80d`a7f3128e ffffb58d`2dc4c030 00000000`00000000 00000000`00000000 : 0x94b4062 *** WARNING: Unable to verify timestamp for fwpkclnt.sys *** ERROR: Module load completed but symbols could not be loaded for fwpkclnt.sys fffff80d`a7f3128e : ffffb58d`2dc4c030 00000000`00000000 00000000`00000000 fffff80d`00000001 : 0xffffb58d`329af518 ffffb58d`2dc4c030 : 00000000`00000000 00000000`00000000 fffff80d`00000001 ffffb58d`31868a30 : fwpkclnt+0x128e 00000000`00000000 : 00000000`00000000 fffff80d`00000001 ffffb58d`31868a30 fffff80d`a7bb6a6b : 0xffffb58d`2dc4c030

    2018年8月10日 14:28

全部回复

  • 建议先做好备份,然后重装系统  O.O
    2018年8月10日 14:33
  • Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\081018-8437-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 16299 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Machine Name:
    Kernel base = 0xfffff803`6d499000 PsLoadedModuleList = 0xfffff803`6d7faff0
    Debug session time: Fri Aug 10 22:09:25.512 2018 (UTC + 8:00)
    System Uptime: 0 days 2:18:26.230
    *********************************************************************
    * 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
    ............
    Cannot read PEB32 from WOW64 TEB32 0000f867 - Win32 error 0n30
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck C2, {4, 0, 0, ffffd606ae756238}
    
    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.
    
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!KPRCB                                      ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!KPRCB                                      ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    Probably caused by : hardware_ram ( PAGE_NOT_ZERO )
    
    Followup: MachineOwner
    ---------
    
     *** Memory manager detected 63591 instance(s) of page corruption, target is likely to have memory corruption.
    
    

    2018年8月10日 14:44
  • 0x000000C2 错误表示内核程序或硬件设备驱动程序试图进行错误的内存操作。这个错误一般是因为应用软件或硬件设备驱动程序存在 BUG 引起的。

    关于 FWPKClnt.SYS 的蓝屏故障,有一篇相似案例可以参考:

    http://www.utosee.com/post/fwpkclnt.sys.html


    Alexis Zhang

    http://mvp.microsoft.com/zh-cn/mvp/Jie%20Zhang-4000545
    http://blogs.itecn.net/blogs/alexis

    推荐以 NNTP Bridge 桥接新闻组方式访问论坛。

    本帖是回复帖,原帖作者是楼上的 <pangolin_>;
    | Bugcheck code 000000C2: 0x94b4062
    | * WARNING: Unable to verify timestamp for fwpkclnt.sys

    2018年8月12日 13:03
    版主
  • 一般是硬件错误,USB口最近有没有新插入硬件,拔出来换一个USB口,或是重装下驱动程序。


    专注于.NET ERP/CRM开发框架,C/S架构,SQL Server + ORM(LLBL Gen Pro) + Infragistics WinForms

    2018年8月13日 0:19