none
最近蓝屏,用 Debugging Tools 查出后,请帮忙看看 什么原因 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\Mini011209-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 XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Machine Name:
    Kernel base = 0x804d8000 PsLoadedModuleList = 0x8055b6a0
    Debug session time: Mon Jan 12 12:14:06.218 2009 (GMT+8)
    System Uptime: 0 days 0:58:44.828
    *********************************************************************
    * 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
    ..................
    Unable to load image raspppoe.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for raspppoe.sys
    *** ERROR: Module load completed but symbols could not be loaded for raspppoe.sys
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 100000D1, {dbcfbe6, 2, 0, dbcfbe6}

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

    *** WARNING: Unable to verify timestamp for NDIS.sys
    *** ERROR: Module load completed but symbols could not be loaded for NDIS.sys
    *** WARNING: Unable to verify timestamp for ndiswan.sys
    *** ERROR: Module load completed but symbols could not be loaded for ndiswan.sys
    *** WARNING: Unable to verify timestamp for psched.sys
    *** ERROR: Module load completed but symbols could not be loaded for psched.sys
    *** WARNING: Unable to verify timestamp for wanarp.sys
    *** ERROR: Module load completed but symbols could not be loaded for wanarp.sys
    *** WARNING: Unable to verify timestamp for tcpip.sys
    *** ERROR: Module load completed but symbols could not be loaded for tcpip.sys
    *** WARNING: Unable to verify timestamp for afd.sys
    *** ERROR: Module load completed but symbols could not be loaded for afd.sys
    *** WARNING: Unable to verify timestamp for 360webpro.sys
    *** ERROR: Module load completed but symbols could not be loaded for 360webpro.sys
    *** WARNING: Unable to verify timestamp for safeboxkrnl.sys
    *** ERROR: Module load completed but symbols could not be loaded for safeboxkrnl.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 : raspppoe.sys ( raspppoe+1103 )

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

     

    2009年1月12日 5:32

答案

  • 内存无问题!网络驱动要有问题也只是ndis.sys的版本不对,我想应该不会,估计是vs这个平台的设计问题!设计不符合xp运行的网络协议规范!可能换个版本会有改善!

    2009年1月12日 9:53

全部回复

  • 用于debug的Symbol file没有正确导入!分析也是白搭!

    请按照下面步骤:

     

     

    首先下载windebug

     

    http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx

    说下debug方法
    1.
    我的电脑,属性->高级->启动,最下面的内存调试选最后一项的全部,确定后重新启动
    2.
    蓝屏后不要急着重启,系统会保存整个内存内容,然后会自动重启
    3.
    找到C:\Windows\Minidump\

    4. 下载安装windwos debug tools, 我这有下载地址,或微软网站
    http://public.hshh.org/SysTools/debug/dbg_x86_6.6.07.5.exe
    5.
    安装后创建一个临时目录,例如 c:\temp
    6.
    启动 windbg
    7. windbg
    界面: file->symbol file path (ctrl+s) 输入:
    SRV*c:\temp*http://msdl.microsoft.com/download/symbols
    然后确定
    8. windbg
    界面: file->open crash dump(ctrl+d),打开9. 打开例如C:\Windows\Minidump\Mini122208-01.dmp后,等待提示
    当出现 Use !analyze -v to get detailed debugging information. 字样后,在下面输入框
    !analyze -v
    10.
    等待分析完毕,可以知道什么导致的出错
    11. windbg
    使用中需要网上下载调试内容,这个速度嘛,取决于你的网络了。

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

     

    你把敲完!analyze -v后的信息发上来!

     

    2009年1月12日 6:13
  •  


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


    Loading Dump File [C:\WINDOWS\Minidump\Mini011209-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 XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 2600.xpsp_sp2_gdr.080814-1233
    Kernel base = 0x804d8000 PsLoadedModuleList = 0x8055b6a0
    Debug session time: Mon Jan 12 12:14:06.218 2009 (GMT+8)
    System Uptime: 0 days 0:58:44.828
    Loading Kernel Symbols
    ...............................................................................................................
    Loading User Symbols
    Loading unloaded module list
    ..................
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 100000D1, {dbcfbe6, 2, 0, dbcfbe6}

    Unable to load image 360webpro.sys, Win32 error 2
    *** WARNING: Unable to verify timestamp for 360webpro.sys
    *** ERROR: Module load completed but symbols could not be loaded for 360webpro.sys
    *** WARNING: Unable to verify timestamp for safeboxkrnl.sys
    *** ERROR: Module load completed but symbols could not be loaded for safeboxkrnl.sys
    Probably caused by : hardware

    Followup: MachineOwner
    ---------
     *** Possible invalid call from f85780fe ( raspppoe!MpWanSend+0x11e )
     *** Expected target f8579be6 ( raspppoe!PacketFree+0x0 )

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

    DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high.  This is usually
    caused by drivers using improper addresses.
    If kernel debugger is available get stack backtrace.
    Arguments:
    Arg1: 0dbcfbe6, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000000, value 0 = read operation, 1 = write operation
    Arg4: 0dbcfbe6, address which referenced memory

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


    READ_ADDRESS:  0dbcfbe6

    CURRENT_IRQL:  2

    FAULTING_IP:
    +dbcfbe6
    0dbcfbe6 ??              ???

    PROCESS_NAME:  cstrike.exe

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  DRIVER_FAULT

    BUGCHECK_STR:  0xD1

    LAST_CONTROL_TRANSFER:  from f8578103 to 0dbcfbe6

    FAILED_INSTRUCTION_ADDRESS:
    +dbcfbe6
    0dbcfbe6 ??              ???

    POSSIBLE_INVALID_CONTROL_TRANSFER:  from f85780fe to f8579be6

    STACK_TEXT: 
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    b935d040 f8578103 fe399b38 82243780 00040000 0xdbcfbe6
    b935d060 f82ce204 fe3cfad0 00000001 8140453c raspppoe!MpWanSend+0x123
    b935d084 f75fe1ae 0023e330 00000001 8140453c NDIS!ndisMWanSend+0xe2
    b935d0b0 f75fe866 fe3ced94 fe3b24d0 00000001 ndiswan!SendOnLegacyLink+0xd2
    b935d10c f75feaa1 fe3b24d0 00000046 814044e0 ndiswan!FramePacket+0x255
    b935d144 f75fec72 fe3b24d0 fe397dc0 b935d178 ndiswan!SendFromProtocol+0xb5
    b935d184 f75ff14d 013b24d0 81832208 00000000 ndiswan!SendPacketOnBundle+0x116
    b935d1a8 f75fabde 8227f440 00000000 00000103 ndiswan!NdisWanQueueSend+0x297
    b935d1bc f82b9f86 8227f440 b935d1f0 00000001 ndiswan!MPSendPackets+0x20
    b935d1e4 f75e6f31 8223da28 81832228 822d4ad0 NDIS!ndisMSendX+0x1bd
    b935d220 f82cf424 821a5ab8 81832228 00000002 psched!MpSend+0x10f
    b935d254 f85fc404 81bc8888 00000000 00000001 NDIS!ndisMSendPacketsX+0x1d5
    b935d270 f85fc707 81bbb7e8 814b5260 814475f0 wanarp!WanpSendPackets+0xfc
    b935d2b4 f527670a 81bbb7e8 b935d2f4 00000001 wanarp!WanIpTransmit+0x14f
    b935d2e4 f52764a9 fe3c2548 c88555da 81832228 tcpip!SendIPPacket+0x18e
    b935d430 f527a994 f52b4834 fe34a230 814ca07c tcpip!IPTransmit+0x287f
    b935d4d0 f527a75b fd38c618 fe34a230 fd83dda0 tcpip!UDPSend+0x41b
    b935d4f4 f527a7c1 0035d518 fd83df00 814ca0bc tcpip!TdiSendDatagram+0xd5
    b935d52c f5279119 fd83dda0 fd83de58 fd83df00 tcpip!UDPSendDatagram+0x4f
    b935d548 804e47f7 81c21730 fd83dda0 814da1f0 tcpip!TCPDispatchInternalDeviceControl+0xff
    b935d558 f5213787 b935d648 00000008 b935d5bc nt!IopfCallDriver+0x31
    b935d5b0 f520ab5e 805600b4 0012dbb4 f520ab5e afd!AfdFastDatagramSend+0x2fd
    b935d6fc b9ecb99f 813d95c8 00000001 0012da84 afd!AfdFastIoDeviceControl+0x2a7
    b935d770 8057e378 813d95c8 00000001 0012da84 360webpro+0x199f
    b935d820 8057e30b 000006c4 0000059c 00000000 nt!IopXxxControlFile+0x261
    b935d854 f51de7fb 000006c4 0000059c 00000000 nt!NtDeviceIoControlFile+0x2a
    b935dd30 804df7ec 0012da70 000006c4 0000059c safeboxkrnl+0xa7fb
    b935dd30 7c92eb94 0012da70 000006c4 0000059c nt!KiFastCallEntry+0xf8
    0012db74 00000000 00000000 00000000 00000000 0x7c92eb94


    STACK_COMMAND:  kb

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: hardware

    IMAGE_NAME:  hardware

    DEBUG_FLR_IMAGE_TIMESTAMP:  0

    BUCKET_ID:  CPU_CALL_ERROR

    Followup: MachineOwner
    ---------
     *** Possible invalid call from f85780fe ( raspppoe!MpWanSend+0x11e )
     *** Expected target f8579be6 ( raspppoe!PacketFree+0x0 )

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

    DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high.  This is usually
    caused by drivers using improper addresses.
    If kernel debugger is available get stack backtrace.
    Arguments:
    Arg1: 0dbcfbe6, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000000, value 0 = read operation, 1 = write operation
    Arg4: 0dbcfbe6, address which referenced memory

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


    READ_ADDRESS:  0dbcfbe6

    CURRENT_IRQL:  2

    FAULTING_IP:
    +dbcfbe6
    0dbcfbe6 ??              ???

    PROCESS_NAME:  cstrike.exe

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  DRIVER_FAULT

    BUGCHECK_STR:  0xD1

    LAST_CONTROL_TRANSFER:  from f8578103 to 0dbcfbe6

    FAILED_INSTRUCTION_ADDRESS:
    +dbcfbe6
    0dbcfbe6 ??              ???

    POSSIBLE_INVALID_CONTROL_TRANSFER:  from f85780fe to f8579be6

    STACK_TEXT: 
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    b935d040 f8578103 fe399b38 82243780 00040000 0xdbcfbe6
    b935d060 f82ce204 fe3cfad0 00000001 8140453c raspppoe!MpWanSend+0x123
    b935d084 f75fe1ae 0023e330 00000001 8140453c NDIS!ndisMWanSend+0xe2
    b935d0b0 f75fe866 fe3ced94 fe3b24d0 00000001 ndiswan!SendOnLegacyLink+0xd2
    b935d10c f75feaa1 fe3b24d0 00000046 814044e0 ndiswan!FramePacket+0x255
    b935d144 f75fec72 fe3b24d0 fe397dc0 b935d178 ndiswan!SendFromProtocol+0xb5
    b935d184 f75ff14d 013b24d0 81832208 00000000 ndiswan!SendPacketOnBundle+0x116
    b935d1a8 f75fabde 8227f440 00000000 00000103 ndiswan!NdisWanQueueSend+0x297
    b935d1bc f82b9f86 8227f440 b935d1f0 00000001 ndiswan!MPSendPackets+0x20
    b935d1e4 f75e6f31 8223da28 81832228 822d4ad0 NDIS!ndisMSendX+0x1bd
    b935d220 f82cf424 821a5ab8 81832228 00000002 psched!MpSend+0x10f
    b935d254 f85fc404 81bc8888 00000000 00000001 NDIS!ndisMSendPacketsX+0x1d5
    b935d270 f85fc707 81bbb7e8 814b5260 814475f0 wanarp!WanpSendPackets+0xfc
    b935d2b4 f527670a 81bbb7e8 b935d2f4 00000001 wanarp!WanIpTransmit+0x14f
    b935d2e4 f52764a9 fe3c2548 c88555da 81832228 tcpip!SendIPPacket+0x18e
    b935d430 f527a994 f52b4834 fe34a230 814ca07c tcpip!IPTransmit+0x287f
    b935d4d0 f527a75b fd38c618 fe34a230 fd83dda0 tcpip!UDPSend+0x41b
    b935d4f4 f527a7c1 0035d518 fd83df00 814ca0bc tcpip!TdiSendDatagram+0xd5
    b935d52c f5279119 fd83dda0 fd83de58 fd83df00 tcpip!UDPSendDatagram+0x4f
    b935d548 804e47f7 81c21730 fd83dda0 814da1f0 tcpip!TCPDispatchInternalDeviceControl+0xff
    b935d558 f5213787 b935d648 00000008 b935d5bc nt!IopfCallDriver+0x31
    b935d5b0 f520ab5e 805600b4 0012dbb4 f520ab5e afd!AfdFastDatagramSend+0x2fd
    b935d6fc b9ecb99f 813d95c8 00000001 0012da84 afd!AfdFastIoDeviceControl+0x2a7
    b935d770 8057e378 813d95c8 00000001 0012da84 360webpro+0x199f
    b935d820 8057e30b 000006c4 0000059c 00000000 nt!IopXxxControlFile+0x261
    b935d854 f51de7fb 000006c4 0000059c 00000000 nt!NtDeviceIoControlFile+0x2a
    b935dd30 804df7ec 0012da70 000006c4 0000059c safeboxkrnl+0xa7fb
    b935dd30 7c92eb94 0012da70 000006c4 0000059c nt!KiFastCallEntry+0xf8
    0012db74 00000000 00000000 00000000 00000000 0x7c92eb94


    STACK_COMMAND:  kb

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: hardware

    IMAGE_NAME:  hardware

    DEBUG_FLR_IMAGE_TIMESTAMP:  0

    BUCKET_ID:  CPU_CALL_ERROR

    Followup: MachineOwner
    ---------
     *** Possible invalid call from f85780fe ( raspppoe!MpWanSend+0x11e )
     *** Expected target f8579be6 ( raspppoe!PacketFree+0x0 )

    2009年1月12日 9:03
  • 你是否在连接一个vpn来打cs?而发生的蓝屏?

    2009年1月12日 9:18
  •  

    vpn?我是adsl拨号上网,应该是把,上次是在vs平台上玩魔兽争霸时也发生了蓝屏。
    2009年1月12日 9:25
  • 尝试换一个版本的cs或者vs!

    2009年1月12日 9:46
  • 那我的驱动,内存什么的都没问题是把。

    2009年1月12日 9:50
  • 内存无问题!网络驱动要有问题也只是ndis.sys的版本不对,我想应该不会,估计是vs这个平台的设计问题!设计不符合xp运行的网络协议规范!可能换个版本会有改善!

    2009年1月12日 9:53
  • 不排除 ADSL 相关设备驱动问题(包括网卡、ADSL Modem)。

     

    是否只有在运行特定程序时出现问题?平时一般的 ADSL 上网操作会不会有问题?

    2009年1月12日 9:55
    版主
  •  

    水落石出了。。谢谢啊,,
    2009年1月12日 9:57
  • 水落石出了。。谢谢你的帮忙了。。谢谢。。。
    2009年1月12日 9:59
  • 还是要测试一下为好!不要高兴太早了,换个vs版本!

    2009年1月12日 10:01
  • 如果还有现象发生,请及时更新帖子!

    2009年1月12日 10:04
  • 对了,问下,我朋友什么的也是用同样的 vs版本。cs也是,为什么他们都没发生 蓝屏的现象呢、??

    2009年1月13日 3:00
  • 是否是同样的硬件配置?是否在同样的网络环境?如果不是,就没有可比性!

    2009年1月13日 4:34
  •  

    啊 原来这样。明白了,我在去玩下游戏,试验下,,
    2009年1月13日 4:46
  • 我测出来的蓝屏信息如下,请帮忙看看是什么原因引起我电脑蓝屏的:
    Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Windows\Minidump\Mini091409-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 0n2
    *** WARNING: Unable to verify timestamp for ntkrnlpa.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
    Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Machine Name:
    Kernel base = 0x81e47000 PsLoadedModuleList = 0x81f5ec70
    Debug session time: Mon Sep 14 22:22:33.211 2009 (GMT+8)
    System Uptime: 0 days 0:38:02.997
    *********************************************************************
    * 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 0n2
    *** 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 FC, {40020, a7f847, 81f3ca8c, 0}

    *** WARNING: Unable to verify timestamp for kl1.sys
    *** ERROR: Module load completed but symbols could not be loaded for kl1.sys
    ***** 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                                     ***
    ***                                                                   ***
    *************************************************************************
    *********************************************************************
    * 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 : kl1.sys ( kl1+28cc0 )

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

    2009年9月15日 4:54
  • 你帮帮我啊!我测到的代码如下,请你帮我分析一下我电脑蓝屏的原因:
    Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
    Copyright (c) Microsoft Corporation. All rights reserved.


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

    Symbol search path is: SRV*D:\programs\test*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 6002.18005.x86fre.lh_sp2rtm.090410-1830
    Machine Name:
    Kernel base = 0x81e43000 PsLoadedModuleList = 0x81f5ac70
    Debug session time: Sun Sep 13 13:03:09.427 2009 (GMT+8)
    System Uptime: 0 days 2:25:06.390
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ..............................
    Loading User Symbols
    Loading unloaded module list
    ...............
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck FC, {40020, 43e19005, 8059dd2c, 0}

    Unable to load image \SystemRoot\system32\DRIVERS\kl1.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for kl1.sys
    *** ERROR: Module load completed but symbols could not be loaded for kl1.sys
    *** WARNING: Unable to verify timestamp for Rtlh86.sys
    *** ERROR: Module load completed but symbols could not be loaded for Rtlh86.sys
    Probably caused by : kl1.sys ( kl1+267b8 )

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

    2009年9月15日 5:19