locked
64位win7偶尔会蓝屏错误 RRS feed

  • 问题

  • 以前是xp,后来用了64位win7,在上网过程中有时会突然蓝屏,下面是dmp文件,请大神帮忙看看是什么原因,谢谢。
    Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Windows\MEMORY.DMP]
    Kernel Complete Dump File: Full address space is 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+                                    *
    *********************************************************************
    Missing image name, possible paged-out or corrupt data.
    *** WARNING: Unable to verify timestamp for Unknown_Module_6122f378`dc143eb3
    *** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_6122f378`dc143eb3
    Debugger can not determine kernel base address
    Windows Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431
    Kernel base = 0xfffff800`04405000 PsLoadedModuleList = 0xfffff800`04649670
    Debug session time: Mon Apr  8 11:05:49.095 2013 (GMT+8)
    System Uptime: 0 days 2:25:47.001
    *********************************************************************
    * 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+                                    *
    *********************************************************************
    Missing image name, possible paged-out or corrupt data.
    *** WARNING: Unable to verify timestamp for Unknown_Module_6122f378`dc143eb3
    *** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_6122f378`dc143eb3
    Debugger can not determine kernel base address
    Loading Kernel Symbols
    Missing image name, possible paged-out or corrupt data.
    .Unable to read KLDR_DATA_TABLE_ENTRY at 461a0a6a`1071f665 - NTSTATUS 0xC0000141

    Image path too long, possible corrupt data.
    Loading unloaded module list
    .Image path too long, possible corrupt data.
    .Image path too long, possible corrupt data.
    .Image path too long, possible corrupt data.
    .Image path too long, possible corrupt data.
    .Image path too long, possible corrupt data.
    .Image path too long, possible corrupt data.
    .Image path too long, possible corrupt data.
    .Image path too long, possible corrupt data.
    .Image path too long, possible corrupt data.
    .Image path too long, possible corrupt data.
    .Image path too long, possible corrupt data.
    .Image path too long, possible corrupt data.
    .Image path too long, possible corrupt data.
    .Image path too long, possible corrupt data.
    .Image path too long, possible corrupt data.
    .Image path too long, possible corrupt data.
    ..Image path too long, possible corrupt data.
    .Image path too long, possible corrupt data.
    .Image path too long, possible corrupt data.
    .Image path too long, possible corrupt data.
    .Image path too long, possible corrupt data.
    .Image path too long, possible corrupt data.
    .Image path too long, possible corrupt data.
    .Image path too long, possible corrupt data.
    .Image path too long, possible corrupt data.
    .Image path too long, possible corrupt data.
    .Image path too long, possible corrupt data.
    .Image path too long, possible corrupt data.
    .Image path too long, possible corrupt data.
    .Image path too long, possible corrupt data.
    .Image path too long, possible corrupt data.
    .Image path too long, possible corrupt data.
    .Image path too long, possible corrupt data.
    .Image path too long, possible corrupt data.
    .Image path too long, possible corrupt data.
    .Image path too long, possible corrupt data.
    .Image path too long, possible corrupt data.
    .Image path too long, possible corrupt data.
    ..Image path too long, possible corrupt data.
    .Image path too long, possible corrupt data.
    ....Image path too long, possible corrupt data.
    .Image path too long, possible corrupt data.
    .Image path too long, possible corrupt data.
    .Image path too long, possible corrupt data.
    .
    WARNING: .reload failed, module list may be incomplete
    The context is partially valid. Only x86 user-mode context is available.
    The wow64exts extension must be loaded to access 32-bit state.
    .load wow64exts will do this if you haven't loaded it already.
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck D1, {1000028, 2, 0, fffff880079e81a2}

    ***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.

    *********************************************************************
    * 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+                                    *
    *********************************************************************
    *********************************************************************
    * 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+                                    *
    *********************************************************************
    *********************************************************************
    * 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 : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

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

     

    2013年4月8日 6:13

答案

  • 未知类型的驱动程序故障。
     
    如果自从安装好 64 位 Windows 7 后就一直有这种问题,可能当前使用的网络或显示驱动程序有兼容问题。64 位驱动与 32 位驱动是不一样的;如果以前曾经正常,是在更新过某种驱动后出现的问题,那么请先恢复到以前的驱动版本。
     
    --
    Alexis Zhang
     
    http://mvp.support.microsoft.com/profile/jie
    http://blogs.itecn.net/blogs/alexis
     
    推荐以 NNTP Bridge 桥接新闻组方式访问论坛以获取最佳用户体验。
     
    本帖是回复帖,原帖作者是楼上的 "微云"
     
    以前是xp,后来用了64位win7,在上网过程中有时会突然蓝屏,下面是dmp文件,请大神帮忙看看是什么原因,谢谢。
     
     
    • 已建议为答案 Niki Han 2013年4月17日 8:01
    • 已标记为答案 Cloud_TS 2013年4月17日 8:44
    2013年4月8日 12:48