none
win7 64位正版系统蓝屏死机求教 RRS feed

  • 问题

  • 我的是用的宏基的4750G 笔记本 I5处理器  540M独显卡,系统为正版WIN7家庭版,我电脑老是出现蓝屏死机的现象,特别是在使用显卡时,(比如玩3D游戏和看高清视频时)

    我新恢复系统,换内存条,且把显卡驱动升级到重新驱动也不和,把电脑拿到售后两次都发现有这个问题,就是没办法解决,现在我所最近的蓝屏文件贴上来:

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


    Loading Dump File [C:\Windows\Minidump\102211-20467-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 \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Windows 7 Kernel Version 7600 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
    Machine Name:
    Kernel base = 0xfffff800`04261000 PsLoadedModuleList = 0xfffff800`0449ee70
    Debug session time: Sat Oct 22 12:06:13.160 2011 (GMT+8)
    System Uptime: 0 days 2:09:06.424
    *********************************************************************
    * 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\ntoskrnl.exe, Win32 error 0n2
    *** 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 3D, {fffff80000b9bf60, 0, 0, fffff8000422b371}

    *** 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.

    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    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 : ntoskrnl.exe ( nt+705c0 )

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

    还有很多的蓝屏文件我打包放到网盘上了,地址为http://dl.dbank.com/c0gh133t3u

    请帮忙分析一下这个是什么原因造成的啊,如果是硬件问题,我好去找售后换,谢谢!

    2011年10月26日 11:19

答案

  • Windows 内核驱动 System Management BIOS Driver 运行有问题,如果系统文件没有受到过破坏,此问题由硬件故障引起的可能性很大。
     
    --
    Alexis Zhang
     
    http://mvp.support.microsoft.com/profile/jie
    http://blogs.itecn.net/blogs/alexis
     
    推荐以 NNTP Bridge 桥接新闻组方式访问论坛以获取最佳用户体验。
     
    本帖是回复帖,原帖作者是楼上的 "feibaoli822"
     
    我的是用的宏基的4750G 笔记本 I5处理器 540M独显卡,系统为正版WIN7家庭版,我电脑老是出现蓝屏死机的现象,特别是在使用显卡时,(比如玩3D游戏和看高清视频时)
     
    2011年10月27日 1:42
  • 你好。

    这是由于系统管理BIOS驱动程序工作异常导致,一般来说是不会出现这样的硬性错误。建议你优先排除程序错误,如果不运行该程序仍然存在此问题,则可能是硬件问题,建议你对硬件进行检查。


    Please mark as "answer" if the problem have been solved, to help more friends find the solution.
    Best Regards, Microsoft MVP, Rein Xu
    https://mvp.support.microsoft.com/profile/Rein
    2011年10月27日 2:03
    版主

全部回复

  • Windows 内核驱动 System Management BIOS Driver 运行有问题,如果系统文件没有受到过破坏,此问题由硬件故障引起的可能性很大。
     
    --
    Alexis Zhang
     
    http://mvp.support.microsoft.com/profile/jie
    http://blogs.itecn.net/blogs/alexis
     
    推荐以 NNTP Bridge 桥接新闻组方式访问论坛以获取最佳用户体验。
     
    本帖是回复帖,原帖作者是楼上的 "feibaoli822"
     
    我的是用的宏基的4750G 笔记本 I5处理器 540M独显卡,系统为正版WIN7家庭版,我电脑老是出现蓝屏死机的现象,特别是在使用显卡时,(比如玩3D游戏和看高清视频时)
     
    2011年10月27日 1:42
  • 你好。

    这是由于系统管理BIOS驱动程序工作异常导致,一般来说是不会出现这样的硬性错误。建议你优先排除程序错误,如果不运行该程序仍然存在此问题,则可能是硬件问题,建议你对硬件进行检查。


    Please mark as "answer" if the problem have been solved, to help more friends find the solution.
    Best Regards, Microsoft MVP, Rein Xu
    https://mvp.support.microsoft.com/profile/Rein
    2011年10月27日 2:03
    版主