none
系统不断蓝屏。。。。。蓝屏代码不固定。。。。。 RRS feed

  • 问题

  • 大家好。。。

    最近我的电脑经常蓝屏。。。。。

    我系统换了。。。硬盘换了。。。。内存换了。。。。显卡换了。。。。

    却还是一直蓝屏。。。。

    是不定时蓝屏的。。。。

    一天都有几次。。。。

    这是我电脑的配置信息。。。

    --------[ 鲁大师 ]--------------------------------------------------------------------------------

      版本:             鲁大师 2.76.11.103
      主页:             http://www.ludashi.com
      操作系统:         Windows XP 专业版 ( 32位 / SP3 / DirectX 9.0c )

    --------[ 概览 ]----------------------------------------------------------------------------------

      电脑:             联想 ThinkCentre Mini Tower
      处理器:           英特尔 2140 @ 1.60GHz
      主板:             联想 LENOVO
      芯片组:           英特尔 946GZ/PL/GL - ICH7 Family
      内存:             1 GB ( 记忆科技 DDR2 533MHz )
      主硬盘:           西数 WDC WD5000AADS-00S9B0 ( 500 GB )
      主显卡:           Nvidia GeForce 7300 LE ( 128 MB / 宝龙达 )
      显示器:           冠捷 AOC1780 TFT1780 ( 17.1 英寸 )
      主光驱:           日立-LG RW/DVD GCC-H20N 康宝
      主声卡:           Analog Devices AD1986 @ 英特尔 82801G(ICH7) 高保真音频
      主网卡:           博通 BCM5786 NetLink Gigabit Ethernet / 联想

    接下来是蓝屏文件。。。。。

     

    第一次。。。


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


    Loading Dump File [C:\WINDOWS\Minidump\Mini011811-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 3) MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Kernel base = 0x804d8000 PsLoadedModuleList = 0x8055e720
    Debug session time: Tue Jan 18 11:02:17.218 2011 (GMT+8)
    System Uptime: 0 days 0:32:19.908
    *********************************************************************
    * 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 1000000A, {c2e0d784, 1, 0, 80506f37}

    *** WARNING: Unable to verify timestamp for mssmbios.sys
    *** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.

    Probably caused by : ntoskrnl.exe ( nt+2ef37 )

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

     

     

    第二次

     


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


    Loading Dump File [C:\WINDOWS\Minidump\Mini011811-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 ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Kernel base = 0x804d8000 PsLoadedModuleList = 0x8055e720
    Debug session time: Tue Jan 18 13:03:02.109 2011 (GMT+8)
    System Uptime: 0 days 1:41:02.805
    *********************************************************************
    * 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 afd.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for afd.sys
    *** ERROR: Module load completed but symbols could not be loaded for afd.sys
    Unable to load image 360netmon.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for 360netmon.sys
    *** ERROR: Module load completed but symbols could not be loaded for 360netmon.sys
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000007F, {d, 0, 0, 0}

    *** WARNING: Unable to verify timestamp for mssmbios.sys
    *** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.

    *** 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 NDIS.sys
    *** ERROR: Module load completed but symbols could not be loaded for NDIS.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 b57xp32.sys
    *** ERROR: Module load completed but symbols could not be loaded for b57xp32.sys
    Probably caused by : 360netmon.sys ( 360netmon+6f5 )

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

     

     

     

    第三次

     


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


    Loading Dump File [C:\WINDOWS\Minidump\Mini011911-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 3) MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Kernel base = 0x804d8000 PsLoadedModuleList = 0x8055e720
    Debug session time: Wed Jan 19 09:16:10.781 2011 (GMT+8)
    System Uptime: 0 days 0:04:03.371
    *********************************************************************
    * 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 1A, {41284, c5881001, 3b54, c0e00000}

    *** WARNING: Unable to verify timestamp for mssmbios.sys
    *** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.

    Probably caused by : ntoskrnl.exe ( nt+22f43 )

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

     

     

    希望大家可以帮下。。。。

    谢谢了。。。

    2011年1月19日 2:03

全部回复

  • 360 的网络监控模块驱动程序文件引起的,请暂时卸载 360 看看能否解决。
     
    --
    Alexis Zhang
     
    http://mvp.support.microsoft.com/profile/jie
    http://blogs.itecn.net/blogs/alexis
     
    推荐以 NNTP Bridge 桥接新闻组方式访问论坛以获取最佳用户体验。
     
    本帖是回复帖,原帖作者是楼上的 "U忧U沉寂5"
     
    大家好。。。
    最近我的电脑经常蓝屏。。。。。
     
     
    2011年1月19日 3:32
    版主
  • 360 的网络监控模块驱动程序文件引起的,请暂时卸载 360 看看能否解决。
     
    --
    Alexis Zhang
     
    http://mvp.support.microsoft.com/profile/jie
    http://blogs.itecn.net/blogs/alexis
     
    推荐以 NNTP Bridge 桥接新闻组方式访问论坛以获取最佳用户体验。
     
    本帖是回复帖,原帖作者是楼上的 "U忧U沉寂5"
     
    大家好。。。
    最近我的电脑经常蓝屏。。。。。
     
     

    你好。。。

    谢谢你的回复。。。

    请问3次蓝屏都是360引起的么。。。。

    那我就试试吧。。。

    我这里还有一次蓝屏代码。。。。。。。


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


    Loading Dump File [C:\WINDOWS\Minidump\Mini011911-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 ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Kernel base = 0x804d8000 PsLoadedModuleList = 0x8055e720
    Debug session time: Wed Jan 19 11:12:11.593 2011 (GMT+8)
    System Uptime: 0 days 1:05:24.314
    *********************************************************************
    * 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 1000008E, {c0000005, 8060e7e8, f77c1a14, 0}

    *** WARNING: Unable to verify timestamp for mssmbios.sys
    *** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.

    *** WARNING: Unable to verify timestamp for Hookport.sys
    *** ERROR: Module load completed but symbols could not be loaded for Hookport.sys
    Probably caused by : Hookport.sys ( Hookport+26cf )

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

    谢谢了。。。。

    2011年1月19日 3:41
  • 最新的这一次也是,HookPort.SYS 是 360 安全卫士对系统进行挂钩操作的核心模块。
     
    --
    Alexis Zhang
     
    http://mvp.support.microsoft.com/profile/jie
    http://blogs.itecn.net/blogs/alexis
     
    推荐以 NNTP Bridge 桥接新闻组方式访问论坛以获取最佳用户体验。
     
    本帖是回复帖,原帖作者是楼上的 "U忧U沉寂5"
     
    谢谢你的回复。。。
    请问3次蓝屏都是360引起的么。。。。
     
     
    2011年1月19日 3:47
    版主
  • 你好,

    从转储文件的分析来看,应该是Hookport.sys文件导致,而该文件是系统核心文件,一般是由于安全软件的调用从而导致工作异常蓝屏崩溃。

    请你按照Alexis Zhang所说,暂时关闭360安全卫士来检查问题是否解决。若问题依旧,请继续提供转储文件分析结果。


    请将已解决的问题标记为“答案”,以便更多的朋友能够方便的找到问题解决方案。 MVP | Windows Desktop Experience | Virtualization Sino
    2011年1月23日 17:11
  •  
    HOOKPORT.SYS 可不算是系统文件。
     
    --
    Alexis Zhang
     
    http://mvp.support.microsoft.com/profile/jie
    http://blogs.itecn.net/blogs/alexis
     
    推荐以 NNTP Bridge 桥接新闻组方式访问论坛以获取最佳用户体验。
     
    本帖是回复帖,原帖作者是楼上的 "Squaredy"
     
    从转储文件的分析来看,应该是Hookport.sys文件导致,而该文件是系统核心文件,一般是由于安全软件的调用从而导致工作异常蓝屏崩溃。
     
     
    2011年1月24日 10:55
    版主