系统蓝屏问题常规处理步骤

匿名
2010-02-21T00:25:15+00:00

出现蓝屏了怎么办

蓝屏（Blue Screen）错误可能是Windows系统中比较常见的一种错误。而且对于我们大多数人来说，发生蓝屏之后可能就束手无策了。这里介绍一些发生蓝屏错误时的一些办法。办法很多，但是今天这部分，主要介绍如何用Windows Debugging Tool，或者叫Windbg，结合微软的论坛来处理问题的办法。

首先，要用WinDBG处理蓝屏问题，要确保系统有生成内存转储文件。

确认存在内存转储文件

默认配置的Windows 7，生成的可能是核心转储文件（Kernal Memory Dump）或是小内存转储文件（Minidump）。如果是核心转储文件，默认会存为C:\Windows\Memory.dmp，如果是小内存转储文件，相关文件会保存在C:\Windows\MiniDump目录下面。

所以，出现蓝屏后，请检查系统中有没有C:\Windows\Memory.dmp这个文件，或者是C:\Windows\MiniDump目录下面按照日期命名的文件。比如，Mini010810-01.dmp就是2010年1月8日的第一个小内存转储文件。

如果没有相应的内存转储文件，请参考有关文档。

安装Windows Debugging Tool （WinDBG）

接下来，我们要安装Windbg了。WinDBG可以在微软网站下载，32位的地址是http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx ，64位的地址是http://www.microsoft.com/whdc/devtools/debugging/install64bit.mspx 。注意WinDBG只有英文版的。你只要到这两个地方找一个最新的版本下载安装就可以了。如果你不是很懂英语，那就直接到这两个地址下载：32位：http://msdl.microsoft.com/download/symbols/debuggers/dbg_x86_6.11.1.404.msi，64位：

http://msdl.microsoft.com/download/symbols/debuggers/dbg_amd64_6.11.1.404.msi

http://msdl.microsoft.com/download/symbols/debuggers/dbg_ia64_6.11.1.404.msi。然后一路Next安转就可以了。WinDBG安转文件大小，大概在15-30兆左右。

配置Windows Debugging Tool （WinDBG）

在用WinDBG分析内存转储文件之前，我们要配置一下WinDBG。

首先，选一个临时目录存放Symbol文件。比如，建立一个目录叫C:\Temp

然后，打开WinDBG，在File菜单-〉选择Symbol File Path。在打开的对话框里输入：

SRV*c:\temp*http://msdl.microsoft.com/download/symbols

选择OK确定。WinDBG就配置好了。

用Windows Debugging Tool （WinDBG）分析内存转储文件

在WinDBG里面，在File菜单，选择Open Crash Dump，然后找到前面说的那个核心内存转储文件或者小内存转储文件，选择打开。等待一会儿，如果需要从微软网站下载Symbole文件的话，时间可能会比较长。如果不出现大量Warning，就说明设置是成功的。如果出现Your debugger is not using the correct symbols                之类的信息，说明配置有问题，到上一步再仔细检查一下。

一直等到出现Use !analyze -v to get detailed debugging information.字样和0: kd>提示符。

按照提示，输入!analyze -v命令。等待命令执行完成。

分析Windows Debugging Tool（WinDBG）结果

如果你的英文有一定基础，!analyze -v命令可能就告诉你很多信息了。如果看的不是很明白，就把结果贴出来让热心的网友给你分析一下吧。

http://shower-thunder.spaces.live.com/blog/cns!250DE47BD119587C!131.entry

Windows 家庭版 | 以前的 Windows 版本 | Windows 更新

锁定的问题。 此问题已从 Microsoft 支持社区迁移。 你可投票决定它是否有用，但不能添加评论或回复，也不能关注问题。

0 个注释
问题作者接受的答案
匿名
2014-09-12T06:03:21+00:00

您好，

从您提供的蓝屏信息中可以查看到是由于EagleX64.sys、KartRider.exe文件导致的。

错误代码: 0x00000019，表示磁盘驱动器在磁盘找不到持定的扇区或磁道。

Eaglex64.sys 是安博士杀毒软件，可能是游戏自带的安全软件也有可能是您安装的该软件。

KartRider.exe是跑跑卡丁车这款游戏的进程，可能是该软件不兼容当前系统或与电脑上安装的应用软件存在冲突（特别是杀毒软件）。

建议您暂时卸载掉电脑上的安全防护类软件再确认问题（您安装了360和迅雷之类的应用了）。

此答案是否有帮助?

6 个人认为此答案很有帮助。
0 个注释

80 个其他答案

排序依据： 最新
非常有帮助 最新 最早
  1. 匿名
    2014-09-12T01:11:35+00:00

    兄弟没有结局问题还是蓝屏了T T 

    麻烦您了。给看下原因我有按不走找存在C：\Users\Administrator\AppData\Local\Temp\WER-86939-0.sysdata.xml

    问题签名:

      问题事件名称: BlueScreen

      OS 版本: 6.1.7601.2.1.0.256.1

      区域设置 ID: 2052

    有关该问题的其他信息:

      BCCode: 19

      BCP1: 0000000000000020

      BCP2: FFFFF80005044860

      BCP3: FFFFF80005044CE0

      BCP4: 000000008548C38B

      OS Version: 6_1_7601

      Service Pack: 1_0

      Product: 256_1

    有助于描述该问题的文件:

      C:\Windows\Minidump\091214-27237-01.dmp

      C:\Users\Administrator\AppData\Local\Temp\WER-86939-0.sysdata.xml

    联机阅读隐私声明:

      http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0804

    如果无法获取联机隐私声明，请脱机阅读我们的隐私声明:

      C:\windows\system32\zh-CN\erofflps.txt

    我win7，64位戴尔的机子灵越系列17R，拜托了，我喜欢玩单机游戏下了好多单机，会不会是下的单机太多导致的？我电脑里有使命召唤4-10，我怀疑是下载单机时候进入的不干净软件导致的？麻烦了！大神。求解决。

    此答案是否有帮助?

    0 个注释
  2. 匿名
    2014-09-12T00:51:40+00:00

    Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64

    Copyright (c) Microsoft Corporation. All rights reserved.

    Loading Dump File [C:\Windows\Minidump\091214-25521-01.dmp]

    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: SRV*c:\symbol*http://msdl.microsoft.com/download/symbols

    Executable search path is:

    Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64

    Product: WinNt, suite: TerminalServer SingleUserTS

    Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144

    Machine Name:

    Kernel base = 0xfffff80004c08000 PsLoadedModuleList = 0xfffff80004e4b890

    Debug session time: Fri Sep 12 08:22:07.761 2014 (GMT+8)

    System Uptime: 0 days 0:26:32.266

    Loading Kernel Symbols

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

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

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

    Loading User Symbols

    Loading unloaded module list

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

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

    *                                                                             *

    *                        Bugcheck Analysis                                    *

    *                                                                             *

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

    Use !analyze -v to get detailed debugging information.

    BugCheck 19, {20, fffff8000504c860, fffff8000504cce0, 8548c38b}

    Unable to load image EagleX64.sys, Win32 error 0n2

    *** WARNING: Unable to verify timestamp for EagleX64.sys

    *** ERROR: Module load completed but symbols could not be loaded for EagleX64.sys

    Probably caused by : memory_corruption

    Followup: memory_corruption

    0: kd> !analyze -v

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

    *                                                                             *

    *                        Bugcheck Analysis                                    *

    *                                                                             *

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

    BAD_POOL_HEADER (19)

    The pool is already corrupt at the time of the current request.

    This may or may not be due to the caller.

    The internal pool links must be walked to figure out a possible cause of

    the problem, and then special pool applied to the suspect tags or the driver

    verifier to a suspect driver.

    Arguments:

    Arg1: 0000000000000020, a pool block header size is corrupt.

    Arg2: fffff8000504c860, The pool entry we were looking for within the page.

    Arg3: fffff8000504cce0, The next pool entry.

    Arg4: 000000008548c38b, (reserved)

    Debugging Details:

    BUGCHECK_STR:  0x19_20

    POOL_ADDRESS: GetPointerFromAddress: unable to read from fffff80004eb5100

     fffff8000504c860

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  CODE_CORRUPTION

    PROCESS_NAME:  KartRider.exe

    CURRENT_IRQL:  0

    LAST_CONTROL_TRANSFER:  from fffff80004db0cae to fffff80004c7dbc0

    STACK_TEXT: 

    fffff8800e604248 fffff80004db0cae : 0000000000000019 0000000000000020 fffff8000504c860 fffff8000504cce0 : nt!KeBugCheckEx

    fffff8800e604250 fffff80004c81ce3 : 00000000a0000003 fffffa800d5ad8a0 00000000435b30c4 0000000000000000 : nt!ExDeferredFreePool+0x12da

    fffff8800e604300 fffff8800c7dbb6e : fffffa8010884a40 fffffa800ea15a00 fffffa800e891ee0 0000000000000000 : nt!IopfCompleteRequest+0xa53

    fffff8800e6043f0 fffffa8010884a40 : fffffa800ea15a00 fffffa800e891ee0 0000000000000000 fffff88004765180 : EagleX64+0x13b6e

    fffff8800e6043f8 fffffa800ea15a00 : fffffa800e891ee0 0000000000000000 fffff88004765180 fffff8800c7e08ff : 0xfffffa80`10884a40

    fffff8800e604400 fffffa800e891ee0 : 0000000000000000 fffff88004765180 fffff8800c7e08ff 0000000000000000 : 0xfffffa80`0ea15a00

    fffff8800e604408 0000000000000000 : fffff88004765180 fffff8800c7e08ff 0000000000000000 fffff8a0177a0c90 : 0xfffffa80`0e891ee0

    STACK_COMMAND:  kb

    CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt

        fffff8000504c863 - nt!EtwpUpdateFileInfoDriverState+c3

     [ 83:85 ]

    1 error : !nt (fffff8000504c863)

    MODULE_NAME: memory_corruption

    IMAGE_NAME:  memory_corruption

    FOLLOWUP_NAME:  memory_corruption

    DEBUG_FLR_IMAGE_TIMESTAMP:  0

    MEMORY_CORRUPTOR:  ONE_BYTE

    FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BYTE

    BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BYTE

    Followup: memory_corruption

    这是我按您的不走一直走下来的。我也不知道什么时候发生的问题，大概就是半个月前左右我使用中国银行网上支付控件的时候只要输入数字就会蓝屏，很苦恼，希望能决绝蓝屏问题，现在居然开启一款很久没玩的游戏跑跑卡丁车也会蓝屏，而且游戏无法运行，我英语极其不好，谢谢你这样的好心人。不敢我电脑解决没解决都谢谢你！麻烦了！

    此答案是否有帮助?

    0 个注释
  3. 匿名
    2013-07-25T03:59:30+00:00

    Microsoft (R) Windows Debugger Version 6.11.0001.404 X86

    Copyright (c) Microsoft Corporation. All rights reserved.

    Loading Dump File [d:\Desktop\蓝屏\ZHOU-SHI\072413-47627-01.dmp]

    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: SRV*D:\temp* http://msdl.microsoft.com/download/symbols

    Executable search path is:

    Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible

    Product: WinNt, suite: TerminalServer SingleUserTS

    Built by: 7601.18113.x86fre.win7sp1_gdr.130318-1533

    Machine Name:

    Kernel base = 0x83e3f000 PsLoadedModuleList = 0x83f884d0

    Debug session time: Wed Jul 24 09:56:31.861 2013 (GMT+8)

    System Uptime: 0 days 2:02:12.284

    Loading Kernel Symbols

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

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

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

    Loading User Symbols

    Loading unloaded module list

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

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

    *                                                                             *

    *                        Bugcheck Analysis                                    *

    *                                                                             *

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

    Use !analyze -v to get detailed debugging information.

    BugCheck A, {78, 2, 0, 83ef8444}

    Probably caused by : CLASSPNP.SYS ( CLASSPNP!DestroyTransferPacket+53 )

    Followup: MachineOwner

    请帮我分析下啊！上面一个，下面一个，都是同一部电脑同一天发生的蓝屏。

    Microsoft (R) Windows Debugger Version 6.11.0001.404 X86

    Copyright (c) Microsoft Corporation. All rights reserved.

    Loading Dump File [d:\Desktop\蓝屏\ZHOU-SHI\072413-43617-01.dmp]

    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: SRV*D:\temp* http://msdl.microsoft.com/download/symbols

    Executable search path is:

    Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible

    Product: WinNt, suite: TerminalServer SingleUserTS

    Built by: 7601.18113.x86fre.win7sp1_gdr.130318-1533

    Machine Name:

    Kernel base = 0x83e3b000 PsLoadedModuleList = 0x83f844d0

    Debug session time: Wed Jul 24 16:01:29.844 2013 (GMT+8)

    System Uptime: 0 days 6:04:19.781

    Loading Kernel Symbols

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

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

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

    Loading User Symbols

    Loading unloaded module list

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

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

    *                                                                             *

    *                        Bugcheck Analysis                                    *

    *                                                                             *

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

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000008E, {c0000005, 83ef4444, b66e098c, 0}

    Probably caused by : ntkrpamp.exe ( nt!ExpReleasePoolQuota+21 )

    Followup: MachineOwner

    此答案是否有帮助?

    0 个注释
  4. 匿名
    2013-07-17T08:46:40+00:00

    Microsoft (R) Windows Debugger Version 6.11.0001.404 X86

    Copyright (c) Microsoft Corporation. All rights reserved.

    Loading Dump File [C:\Windows\Minidump\071713-39812-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:

    Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible

    Product: WinNt, suite: TerminalServer SingleUserTS

    Built by: 7601.18147.x86fre.win7sp1_gdr.130505-1534

    Machine Name:

    Kernel base = 0x84009000 PsLoadedModuleList = 0x841524d0

    Debug session time: Wed Jul 17 13:37:47.987 2013 (GMT+8)

    System Uptime: 0 days 1:44:41.627

    Loading Kernel Symbols

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

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

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

    Loading User Symbols

    Loading unloaded module list

    .......

    0: kd> !analyze -v

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

    *                                                                             *

    *                        Bugcheck Analysis                                    *

    *                                                                             *

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

    VIDEO_TDR_FAILURE (116)

    Attempt to reset the display driver and recover from timeout failed.

    Arguments:

    Arg1: b0ba8008, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).

    Arg2: 93c1ff20, The pointer into responsible device driver module (e.g. owner tag).

    Arg3: 00000000, Optional error code (NTSTATUS) of the last failed operation.

    Arg4: 0000000d, Optional internal context dependent data.

    Debugging Details:

    *** WARNING: Unable to verify timestamp for igdkmd32.sys

    *** ERROR: Module load completed but symbols could not be loaded for igdkmd32.sys

    FAULTING_IP:

    igdkmd32+11f20

    93c1ff20 55              push    ebp

    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

    CUSTOMER_CRASH_COUNT:  1

    BUGCHECK_STR:  0x116

    PROCESS_NAME:  iexplore.exe

    CURRENT_IRQL:  0

    STACK_TEXT: 

    8b863898 941a407f 00000116 b0ba8008 93c1ff20 nt!KeBugCheckEx+0x1e

    8b8638bc 941989e2 93c1ff20 00000000 0000000d dxgkrnl!TdrBugcheckOnTimeout+0x8d

    8b8638e0 93b1d92c 00000000 00000000 8b8639a4 dxgkrnl!TdrIsRecoveryRequired+0xb8

    8b863958 93b44d55 fffffcfb 000621d8 00000000 dxgmms1!VidSchiReportHwHang+0x3c0

    8b863984 93b2e471 87275008 8b8639a4 00000102 dxgmms1!VidSchWaitForCompletionEvent+0x16f

    8b863a1c 93b2fb0f b74f7310 00000001 00000000 dxgmms1!VIDMM_GLOBAL::xWaitForAllEngines+0x181

    8b863a34 93b32432 cbed6dc8 8738df08 8b863b94 dxgmms1!VIDMM_GLOBAL::WaitForAllPagingOperations+0x1b

    8b863a9c 93b32ef8 8b863be0 8b863b6c 8b863b9c dxgmms1!VIDMM_GLOBAL::ProcessDeferredCommand+0x338

    8b863ab4 93b483b9 8b863b94 8738df08 8738df08 dxgmms1!VidMmiProcessSystemCommand+0x20

    8b863ad0 93b49293 87274438 87275008 8b863b10 dxgmms1!VidSchiSubmitSystemCommand+0x33

    8b863ae0 93b246dc 8738df08 8738df08 8738b8b8 dxgmms1!VidSchiSubmitQueueCommand+0x7b

    8b863b10 93b49466 87282000 8b863b34 8738b8b8 dxgmms1!VidSchiSubmitQueueCommandDirect+0x1ae

    8b863b38 93b447f1 0138df08 878c9000 cbed6dc8 dxgmms1!VidSchiSubmitCommandPacketToQueue+0x180

    8b863b50 93b32f5f 87275008 93b32ed8 8b863b94 dxgmms1!VidSchSubmitSystemCommand+0xab

    8b863b80 93b32fc6 8b863b94 ceac9328 86a625f0 dxgmms1!VIDMM_GLOBAL::QueueSystemCommandAndWait+0x41

    8b863bb8 93b35ee0 8b863be0 bd2c25b0 8b863cac dxgmms1!VIDMM_GLOBAL::QueueDeferredCommandAndWait+0x3c

    8b863c14 93b1843b 01ac9328 00000008 0000004d dxgmms1!VIDMM_GLOBAL::BeginCPUAccess+0xa18

    8b863c34 9411a329 878c9000 ceac9328 00000000 dxgmms1!VidMmBeginCPUAccess+0x1f

    8b863c58 94142106 87178778 878c9000 ceac9328 dxgkrnl!VIDMM_EXPORT::VidMmBeginCPUAccess+0x23

    8b863c90 9414275b 0000004d 1f9529b9 03c4cf18 dxgkrnl!DXGDEVICE::Lock+0x24f

    8b863d28 840468a6 03c4cf18 03c4cf40 77c57094 dxgkrnl!DxgkLock+0x17b

    8b863d28 77c57094 03c4cf18 03c4cf40 77c57094 nt!KiSystemServicePostCall

    WARNING: Frame IP not in any known module. Following frames may be wrong.

    03c4cf40 00000000 00000000 00000000 00000000 0x77c57094

    STACK_COMMAND:  .bugcheck ; kb

    FOLLOWUP_IP:

    igdkmd32+11f20

    93c1ff20 55              push    ebp

    SYMBOL_NAME:  igdkmd32+11f20

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: igdkmd32

    IMAGE_NAME:  igdkmd32.sys

    DEBUG_FLR_IMAGE_TIMESTAMP:  4aba7471

    FAILURE_BUCKET_ID:  0x116_IMAGE_igdkmd32.sys

    BUCKET_ID:  0x116_IMAGE_igdkmd32.sys

    Followup: MachineOwner

    0: kd> analyze -v

    *** WARNING: Unable to verify timestamp for amdsata.sys

    *** ERROR: Module load completed but symbols could not be loaded for amdsata.sys

    *** WARNING: Unable to verify timestamp for nvraid.sys

    *** ERROR: Module load completed but symbols could not be loaded for nvraid.sys

    *** WARNING: Unable to verify timestamp for Hookport.sys

    *** ERROR: Module load completed but symbols could not be loaded for Hookport.sys

    *** ERROR: Module load completed but symbols could not be loaded for intelide.sys

    *** WARNING: Unable to verify timestamp for amdxata.sys

    *** ERROR: Module load completed but symbols could not be loaded for amdxata.sys

    *** WARNING: Unable to verify timestamp for amd_xata.sys

    *** ERROR: Module load completed but symbols could not be loaded for amd_xata.sys

    *** WARNING: Unable to verify timestamp for spldr.sys

    *** ERROR: Module load completed but symbols could not be loaded for spldr.sys

    *** WARNING: Unable to verify timestamp for iaStorF.sys

    *** ERROR: Module load completed but symbols could not be loaded for iaStorF.sys

    *** WARNING: Unable to verify timestamp for 360Box.sys

    *** ERROR: Module load completed but symbols could not be loaded for 360Box.sys

    *** WARNING: Unable to verify timestamp for QQProtect.sys

    *** ERROR: Module load completed but symbols could not be loaded for QQProtect.sys

    *** WARNING: Unable to verify timestamp for 360SelfProtection.sys

    *** ERROR: Module load completed but symbols could not be loaded for 360SelfProtection.sys

    *** WARNING: Unable to verify timestamp for 360netmon.sys

    *** ERROR: Module load completed but symbols could not be loaded for 360netmon.sys

    *** WARNING: Unable to verify timestamp for snp2uvc.sys

    *** ERROR: Module load completed but symbols could not be loaded for snp2uvc.sys

    *** WARNING: Unable to verify timestamp for sncduvc.SYS

    *** ERROR: Module load completed but symbols could not be loaded for sncduvc.SYS

    *** WARNING: Unable to verify timestamp for qutmipc.sys

    *** ERROR: Module load completed but symbols could not be loaded for qutmipc.sys

    *** WARNING: Unable to verify timestamp for qutmdrv.sys

    *** ERROR: Module load completed but symbols could not be loaded for qutmdrv.sys

    *** WARNING: Unable to verify timestamp for ProtectorA.sys

    *** ERROR: Module load completed but symbols could not be loaded for ProtectorA.sys

    *** WARNING: Unable to verify timestamp for Protector.sys

    *** ERROR: Module load completed but symbols could not be loaded for Protector.sys

    *** WARNING: Unable to verify timestamp for Efimon.sys

    *** ERROR: Module load completed but symbols could not be loaded for Efimon.sys

    *** WARNING: Unable to verify timestamp for 360AntiHacker.sys

    *** ERROR: Module load completed but symbols could not be loaded for 360AntiHacker.sys

    *** WARNING: Unable to verify timestamp for 360Camera.sys

    *** ERROR: Module load completed but symbols could not be loaded for 360Camera.sys

    *** WARNING: Unable to verify timestamp for BAPIDRV.SYS

    *** ERROR: Module load completed but symbols could not be loaded for BAPIDRV.SYS

    *** WARNING: Unable to verify timestamp for intelppm.sys

    *** ERROR: Module load completed but symbols could not be loaded for intelppm.sys

    *** WARNING: Unable to verify timestamp for e1e6232.sys

    *** ERROR: Module load completed but symbols could not be loaded for e1e6232.sys

    *** WARNING: Unable to verify timestamp for TenpayKeyboard.SYS

    *** ERROR: Module load completed but symbols could not be loaded for TenpayKeyboard.SYS

    *** WARNING: Unable to verify timestamp for smccard.sys

    *** ERROR: Module load completed but symbols could not be loaded for smccard.sys

    *** WARNING: Unable to verify timestamp for Chip_smc.sys

    *** ERROR: Module load completed but symbols could not be loaded for Chip_smc.sys

    *** WARNING: Unable to verify timestamp for TSDDD.dll

    *** ERROR: Module load completed but symbols could not be loaded for TSDDD.dll

    *** WARNING: Unable to verify timestamp for ATMFD.DLL

    *** ERROR: Module load completed but symbols could not be loaded for ATMFD.DLL

    *** WARNING: Unable to verify timestamp for peauth.sys

    *** ERROR: Module load completed but symbols could not be loaded for peauth.sys

    *** WARNING: Unable to verify timestamp for PECKP.SYS

    *** ERROR: Module load completed but symbols could not be loaded for PECKP.SYS

    *** WARNING: Unable to verify timestamp for secdrv.SYS

    *** ERROR: Module load completed but symbols could not be loaded for secdrv.SYS

    *** WARNING: Unable to verify timestamp for RTKVHDA.sys

    *** ERROR: Module load completed but symbols could not be loaded for RTKVHDA.sys

    *** WARNING: Unable to verify timestamp for drmk.sys

    *** ERROR: Module load completed but symbols could not be loaded for drmk.sys

    *** WARNING: Unable to verify timestamp for DgSafe.sys

    *** ERROR: Module load completed but symbols could not be loaded for DgSafe.sys

    *** WARNING: Unable to verify timestamp for ksapi.sys

    *** ERROR: Module load completed but symbols could not be loaded for ksapi.sys

    *** WARNING: Unable to verify timestamp for 360AvFlt.sys

    *** ERROR: Module load completed but symbols could not be loaded for 360AvFlt.sys

    Couldn't resolve error at 'nalyze -v'

    此答案是否有帮助?

    0 个注释