关于win10蓝屏 错误代码0x00000109，有windebug分析

纯牛奶x

问题描述：
        1.蓝屏大约一两个小时一次，
        2.蓝屏前装过卡巴斯基，进行了一次全盘扫描
        3.下过360，和在不知道的情况下被安装了腾讯管家。


以下是windebug的分析，求助- -


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


Loading Dump File [C:\Users\侯明明\Desktop\蓝屏\062616-5625-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 10586 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff803`68a04000 PsLoadedModuleList = 0xfffff803`68ce2cf0
Debug session time: Sun Jun 26 18:44:08.257 2016 (GMT+8)
System Uptime: 0 days 0:30:12.149
*********************************************************************
* 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
.............
Cannot read PEB32 from WOW64 TEB32 0000949e - Win32 error 0n30
The call to LoadLibrary(ext) failed, Win32 error 0n2
    "系统找不到指定的文件。"
Please check your debugger configuration and/or network access.
The call to LoadLibrary(exts) failed, Win32 error 0n2
    "系统找不到指定的文件。"
Please check your debugger configuration and/or network access.
The call to LoadLibrary(kext) failed, Win32 error 0n2
    "系统找不到指定的文件。"
Please check your debugger configuration and/or network access.
The call to LoadLibrary(kdexts) failed, Win32 error 0n2
    "系统找不到指定的文件。"
Please check your debugger configuration and/or network access.
The call to LoadLibrary(ext) failed, Win32 error 0n2
    "系统找不到指定的文件。"
Please check your debugger configuration and/or network access.
The call to LoadLibrary(exts) failed, Win32 error 0n2
    "系统找不到指定的文件。"
Please check your debugger configuration and/or network access.
The call to LoadLibrary(kext) failed, Win32 error 0n2
    "系统找不到指定的文件。"
Please check your debugger configuration and/or network access.
The call to LoadLibrary(kdexts) failed, Win32 error 0n2
    "系统找不到指定的文件。"
Please check your debugger configuration and/or network access.
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Bugcheck code 00000109
Arguments a3a01f59`4957d556 b3b72bdf`9bd888ab ffffe000`b7be05e0 00000000`0000001c

RetAddr           : Args to Child                                                           : Call Site
00000000`00000000 : 00000000`00000109 a3a01f59`4957d556 b3b72bdf`9bd888ab ffffe000`b7be05e0 : nt+0x1427a0
00000000`00000109 : a3a01f59`4957d556 b3b72bdf`9bd888ab ffffe000`b7be05e0 00000000`0000001c : 0x0
a3a01f59`4957d556 : b3b72bdf`9bd888ab ffffe000`b7be05e0 00000000`0000001c 00000000`00000000 : 0x109
b3b72bdf`9bd888ab : ffffe000`b7be05e0 00000000`0000001c 00000000`00000000 00000000`00000000 : 0xa3a01f59`4957d556
ffffe000`b7be05e0 : 00000000`0000001c 00000000`00000000 00000000`00000000 00000000`00000000 : 0xb3b72bdf`9bd888ab
00000000`0000001c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xffffe000`b7be05e0
00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x1c
00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0

ELOHIM

WARNING: Unable to verify timestamp for ntoskrnl.exe
ntoskrnl.exe 时间戳验证失败。是不是这个文件被修改了？
签名时间：‎2016‎年‎5‎月‎28‎日 13:25:51

纯牛奶x

ELOHIM 发表于 2016-6-27 13:48
WARNING: Unable to verify timestamp for ntoskrnl.exe
ntoskrnl.exe 时间戳验证失败。是不是这个文件被 ...

昨天蓝屏又频繁了，30分钟一次差不多，然后重装系统了。。。。

ELOHIM

纯牛奶x 发表于 2016-6-28 11:14
昨天蓝屏又频繁了，30分钟一次差不多，然后重装系统了。。。。

好吧，现在蓝的怎么样？

纯牛奶x

ELOHIM 发表于 2016-6-28 11:16
好吧，现在蓝的怎么样？

重装系统就好了~~~

ELOHIM

纯牛奶x 发表于 2016-6-30 13:20
重装系统就好了~~~

恭喜你通过基础操作解决问题。
那你看一下 ntoskrnl.exe 时间戳，贴上来看看。

纯牛奶x

ELOHIM 发表于 2016-6-30 13:47
恭喜你通过基础操作解决问题。
那你看一下 ntoskrnl.exe 时间戳，贴上来看看。

额  这个怎么看呢- -   好几天没上卡饭  没看到消息  不好意思

xianghui

ntoskrnl.exe有问题系统根本运行不了，所以这种提示意义不大，一般蓝屏有此提示就是重装系统，还不行就硬件替换。