none
1A蓝屏,DUP分析结果是ntoskrnl.exe ( nt+75bc0 ) ,求助冲突的具体是什么内容 RRS feed

  • 问题

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


    Loading Dump File [C:\Users\NICK\Desktop\102414-18361-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 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Machine Name:
    Kernel base = 0xfffff800`0424b000 PsLoadedModuleList = 0xfffff800`0448e890
    Debug session time: Fri Oct 24 00:17:00.966 2014 (GMT+8)
    System Uptime: 0 days 12:26:16.762
    *********************************************************************
    * 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, {41790, fffffa800162a590, ffff, 0}

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

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

    2014年10月24日 1:25

全部回复

  • 最近经常性蓝屏,一直是ntoskrnl.exe ( nt+75bc0 ),,DMP不知道怎么上传,全部复制


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


    Loading Dump File [C:\Users\NICK\Desktop\102414-18361-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 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Machine Name:
    Kernel base = 0xfffff800`0424b000 PsLoadedModuleList = 0xfffff800`0448e890
    Debug session time: Fri Oct 24 00:17:00.966 2014 (GMT+8)
    System Uptime: 0 days 12:26:16.762
    *********************************************************************
    * 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, {41790, fffffa800162a590, ffff, 0}

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

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

    2014年10月24日 1:19
  • 把 .DMP 文件上传至任意网盘,OneDrive 或百度网盘等,然后提供公开下载链接。


    Alexis Zhang

    http://mvp.support.microsoft.com/profile/jie
    http://blogs.itecn.net/blogs/alexis

    推荐以 NNTP Bridge 桥接新闻组方式访问论坛。

    本帖是回复帖,原帖作者是楼上的 "班德尔的小墨"

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

    2014年10月25日 0:39
  • 发不出来,说是没有验证账户
    2014年10月25日 15:47
  • 发不上链接来,求帮助
    2014年10月25日 15:56
  • 因为我不能发送链接

    ht删除tp://pan.baidu.com/s/1o65HkxW

    删除第二行中的汉字就可以了,多谢

    2014年10月25日 16:45
  • 一个未知的驱动错误引起 Windows 内核进程 NTOSKrnl.EXE 无法维持运行,但分析结果没有确定具体是什么驱动,比较有可能是硬件问题。

    这个蓝屏出现过几次?如果只有一次可能只是暂时性的,建议再观察一阵;如果频繁出现,再提供一些其它的 .DMP 文件看看。

    另外最近有没有过任何驱动的添加、更新、卸载?


    Alexis Zhang

    http://mvp.support.microsoft.com/profile/jie
    http://blogs.itecn.net/blogs/alexis

    推荐以 NNTP Bridge 桥接新闻组方式访问论坛。

    本帖是回复帖,原帖作者是楼上的 "班德尔的小墨"

    | 因为我不能发送链接
    | http://pan.baidu.com/s/1o65HkxW  删除第二行中的汉字就可以了,多谢

    2014年10月26日 0:29
  • 还有,你是不是安装有卡巴斯基?检查一下它的日志,最近有没有报毒的记录?


    Alexis Zhang

    http://mvp.support.microsoft.com/profile/jie
    http://blogs.itecn.net/blogs/alexis

    推荐以 NNTP Bridge 桥接新闻组方式访问论坛。

    本帖是回复帖,原帖作者是楼上的 "班德尔的小墨"

    | 因为我不能发送链接
    | http://pan.baidu.com/s/1o65HkxW 删除第二行中的汉字就可以了,多谢

    2014年10月26日 0:33
  • 我用WIN7自带的内存检查工具,检测出我有一根内存条有故障,用memTestPro检测两根内存的稳定性时也有报错,初步怀疑是内存问题。现在拔掉那根检测有故障的,再看

    蓝屏偶尔出现,基本上一周一次,出现的情况不定,有时候游戏,有时候浏览网页。前端时间就是因为蓝屏重装了系统,最近一周蓝了4次,一次是自动蓝,一次是关机途中蓝,还有两次是我运行memTestPro进行负载测试时蓝屏

    2014年10月26日 3:52
  • ht删除tp://pan.baidu.com/s/1jG43tC6
    ht删除tp://pan.baidu.com/s/1pJju18B
    ht删除tp://pan.baidu.com/s/1sjBGCg9

    以上是记录的三个DMP

    2014年10月26日 3:57
  • 那就先排查内存吧,看看是不是没插紧,或者内存外观看起来有异样,有条件换条内存再试试。


    Alexis Zhang

    http://mvp.support.microsoft.com/profile/jie
    http://blogs.itecn.net/blogs/alexis

    推荐以 NNTP Bridge 桥接新闻组方式访问论坛。

    本帖是回复帖,原帖作者是楼上的 "班德尔的小墨"

    | 我用WIN7自带的内存检查工具,检测出我有一根内存条有故障,用memTestPro检测两根内存的稳定性时也有报错,初步怀疑是内存问题。现在拔掉那根检测有故障的,再看

    2014年10月26日 22:48
  • 也就是说内存故障有可能导致这种情况是吗?我那条检测有故障的内存,以及返修了,现在单独一根,看看会不会蓝
    2014年10月27日 6:28
  • 对,Windows 内存检测工具及 MemTest 一般不会轻易报错,既然报了就肯定有问题。先反复替换测试,看看是不是内存条问题,是的话具体是哪条。


    Alexis Zhang

    http://mvp.support.microsoft.com/profile/jie
    http://blogs.itecn.net/blogs/alexis

    推荐以 NNTP Bridge 桥接新闻组方式访问论坛。

    本帖是回复帖,原帖作者是楼上的 "班德尔的小墨"

    | 也就是说内存故障有可能导致这种情况是吗?我那条检测有故障的内存,以及返修了,现在单独一根,看看会不会蓝
    |

    2014年10月27日 22:54
  • JD答应给我换一根了,但是我的是套装4G X2,只换一根不知道会不会没那么好用了
    2014年10月28日 11:10
  • 您好,

    像您这个问题,有可能是其中一个内存条出现故障,您可以尝试逐个测试,看看那个内存有问题。然后把有问题的内存条换下即可。


    Roger Lu
    TechNet Community Support

    2014年10月30日 14:44
    版主
  • 规格一样就可以,不一定非要原装配套的才行。


    Alexis Zhang

    http://mvp.support.microsoft.com/profile/jie
    http://blogs.itecn.net/blogs/alexis

    推荐以 NNTP Bridge 桥接新闻组方式访问论坛。

    本帖是回复帖,原帖作者是楼上的 "班德尔的小墨"

    | JD答应给我换一根了,但是我的是套装4G X2,只换一根不知道会不会没那么好用了
    |

    2014年10月30日 22:41
  • 换的内存还没回来,

    今天早上关机又出现,但是不是1A蓝,是9F蓝,头痛啊···

    ht删除tp://pan.baidu.com/s/1qW9aYJE

    2014年11月3日 0:24
  • 换的内存还没回来,

    今天早上关机又出现,但是不是1A蓝,是9F蓝,头痛啊···

    ht删除tp://pan.baidu.com/s/1qW9aYJE

    2014年11月3日 0:24
  • 0x0000009F 是电源相关配置问题。


    Alexis Zhang

    http://mvp.support.microsoft.com/profile/jie
    http://blogs.itecn.net/blogs/alexis

    推荐以 NNTP Bridge 桥接新闻组方式访问论坛。

    本帖是回复帖,原帖作者是楼上的 "班德尔的小墨"

    | 换的内存还没回来,
    | 今天早上关机又出现,但是不是1A蓝,是9F蓝,头痛啊···

    2014年11月3日 22:44
  • 刚刚用着用着又9F了 晕死,就看网页的时候突然就屏幕黑了,重

    HT删除TP://pan.baidu.com/s/1kTMc3iR

    电源配置问题,该如何检测呢???我这个电源应该没什么问题啊,安钛克550W的,刚刚我只是浏览网页,别的什么都没干


    2014年11月4日 3:16
  • 您好,

    从最近的蓝屏日志分析来看,此次蓝屏可能是 btfilter.sys文件导致的,从0x9f及其参数来看,是由于当前系统的某个设备占用了IRP(I/O request packet)太久导致的蓝屏。

    建议您尝试进入带网络的安全模式检查该问题是否出现,如果没有,那这个问题很有可能是您计算机上安装的软件或驱动导致的蓝屏。建议您检查在该问题出现之前对系统做了哪些改动,安装了哪些驱动或软件并暂时将其卸载。


    Roger Lu
    TechNet Community Support


    2014年11月5日 5:49
    版主
  • 你的系统安装的一个蓝牙驱动 BtFilter.SYS 可能与负责 ACPI 电源管理的主板芯片组驱动存在冲突。先尝试禁用蓝牙设备并重装一下主板驱动,看看能否解决。


    Alexis Zhang

    http://mvp.support.microsoft.com/profile/jie
    http://blogs.itecn.net/blogs/alexis

    推荐以 NNTP Bridge 桥接新闻组方式访问论坛。

    本帖是回复帖,原帖作者是楼上的 "班德尔的小墨"

    | 刚刚用着用着又9F了 晕死,就看网页的时候突然就屏幕黑了,
    | 电源配置问题,该如何检测呢???我这个电源应该没什么问题啊,

    2014年11月5日 22:58
  • 又蓝屏了,冏,刚刚装了SSD,重装系统,是显卡驱动冲突?求大神帮我详细看看

    HT删除TP://pan.baidu.com/s/1kT5NGrl

    2014年11月16日 15:16
  • 您好,

    从蓝屏日志分析来看,是ATI显卡驱动导致的此次蓝屏,建议您卸载并重新安装该驱动。 此外,如果蓝屏继续发生,建议您尝试其他版本的显卡驱动看能否解决该问题。


    Roger Lu
    TechNet Community Support

    2014年11月17日 2:51
    版主
  • 以前用过这个版本的显卡驱动吗?是否正常过?


    Alexis Zhang

    http://mvp.support.microsoft.com/profile/jie
    http://blogs.itecn.net/blogs/alexis

    推荐以 NNTP Bridge 桥接新闻组方式访问论坛。

    本帖是回复帖,原帖作者是楼上的 "班德尔的小墨"

    | 又蓝屏了,冏,刚刚装了SSD,重装系统,是显卡驱动冲突?求大神帮我详细看看
    | HTTP://pan.baidu.com/s/1kT5NGrl

    2014年11月17日 21:57
  • 以前正常,也是这个驱动,

    第一次出现这个代码,不过我这次是刚装系统,买了SSD,现在换了个驱动看看,从这个文件能分析出什么吗?

    2014年11月18日 11:00
  • 不好说,可能是驱动冲突。


    Alexis Zhang

    http://mvp.support.microsoft.com/profile/jie
    http://blogs.itecn.net/blogs/alexis

    推荐以 NNTP Bridge 桥接新闻组方式访问论坛。

    本帖是回复帖,原帖作者是楼上的 "班德尔的小墨"

    | 以前正常,也是这个驱动,
    | 第一次出现这个代码,不过我这次是刚装系统,买了SSD,现在换了个驱动看看,从这个文件能分析出什么吗?

    2014年11月19日 22:52
  • ···C2蓝屏,开始显示有个未识别的USB硬件,启动软件时出现的蓝屏。分析还是

    跟我之前说的那种差不多, ntoskrnl.exe ( nt+75bc0 )

    但是内存也换过来了啊,~这个可能是啥原因啊,强迫症患者都要疯了

    HT删除TP://pan.baidu.com/s/1hqkVlXE

    2014年11月19日 23:59
  • 您好,

    从您最新提供的蓝屏日志分析结果来看,此次蓝屏是ssudbus.sys文件导致的。通过查询发现该文件是SAMSUNG USB Composite Device Driver的一个文件。 如果当年您的计算机上有安装三星相关的组件,建议您卸载该驱动,然后重启电脑,看蓝屏问题是否得到改善。


    Roger Lu
    TechNet Community Support

    2014年11月20日 3:13
    版主
  • 可能是的,因为蓝屏的时候我正好在安装这个三星手机驱动
    2014年11月20日 4:23
  • 那你试一下能不能重新安装一遍这个三星手机驱动,然后试着把它卸载干净。


    Alexis Zhang

    http://mvp.microsoft.com/zh-cn/mvp/Jie%20Zhang-4000545
    http://blogs.itecn.net/blogs/alexis

    推荐以 NNTP Bridge 桥接新闻组方式访问论坛。

    本帖是回复帖,原帖作者是楼上的 "班德尔的小墨"

    | 可能是的,因为蓝屏的时候我正好在安装这个三星手机驱动
    |

    2014年11月22日 2:56