积极答复者
Help me pleaseT T我的电脑蓝屏了T T

问题
答案
-
0x00000109 蓝屏表示严重的 Windows 内核数据错误,一般是由于驱动程序编写有 BUG 或者硬件本身存在问题引起的。
你贴出的 Dump 文件分析结果并没有准确检测到有问题的驱动或进程名,因此不太好判断原因。这台电脑的硬件有没有运行异常的地方?或者最近有没有更换过驱动?
Alexis Zhang
http://mvp.microsoft.com/zh-cn/mvp/Jie%20Zhang-4000545
http://blogs.itecn.net/blogs/alexis推荐以 NNTP Bridge 桥接新闻组方式访问论坛。
本帖是回复帖,原帖作者是楼上的 "敏爷"
| 下面是我用Windbg解析Dmp的结果但是看不懂T T可以麻烦帮忙看看么?
| Microsoft (R) Windows Debugger Version 10.0.10586.567 AMD64- 已标记为答案 敏爷 2016年3月24日 6:58
全部回复
-
你通过微博分享的 .DMP 文件无法打开,提示当前使用的账号存在异常,需要输入手机号解除异常状态。请检查一下。
Alexis Zhang
http://mvp.microsoft.com/zh-cn/mvp/Jie%20Zhang-4000545
http://blogs.itecn.net/blogs/alexis推荐以 NNTP Bridge 桥接新闻组方式访问论坛。
本帖是回复帖,原帖作者是楼上的 "敏爷"
| 各位救救我啊T T我的电脑突然蓝屏了,,没有下载什么软件插件之类的,也没有什么不正确的操作。。就是突然蓝屏了。。有时候是开机一会儿就要蓝屏。。有时候是开机一两个小时不动他就会自己蓝屏。。
-
下面是我用Windbg解析Dmp的结果但是看不懂T T可以麻烦帮忙看看么?
Microsoft (R) Windows Debugger Version 10.0.10586.567 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Minimin\Desktop\新建文件夹\032216-32984-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*
Executable search path is:
Windows 8.1 Kernel Version 9600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 9600.18202.amd64fre.winblue_ltsb.160119-0600
Machine Name:
Kernel base = 0xfffff800`de406000 PsLoadedModuleList = 0xfffff800`de6d9630
Debug session time: Tue Mar 22 10:57:14.158 2016 (UTC + 8:00)
System Uptime: 0 days 0:02:11.657
Loading Kernel Symbols
.
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
..............................................................
................................................................
.......................................
Loading User Symbols
Loading unloaded module list
.............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 109, {a3a01f590988f6c7, b3b72bdf5c08e256, 3, 18}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
CRITICAL_STRUCTURE_CORRUPTION (109)
This bugcheck is generated when the kernel detects that critical kernel code or
data have been corrupted. There are generally three causes for a corruption:
1) A driver has inadvertently or deliberately modified critical kernel code
or data. See http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx
2) A developer attempted to set a normal kernel breakpoint using a kernel
debugger that was not attached when the system was booted. Normal breakpoints,
"bp", can only be set if the debugger is attached at boot time. Hardware
breakpoints, "ba", can be set at any time.
3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
Arguments:
Arg1: a3a01f590988f6c7, Reserved
Arg2: b3b72bdf5c08e256, Reserved
Arg3: 0000000000000003, Failure type dependent information
Arg4: 0000000000000018, Type of corrupted region, can be
0 : A generic data region
1 : Modification of a function or .pdata
2 : A processor IDT
3 : A processor GDT
4 : Type 1 process list corruption
5 : Type 2 process list corruption
6 : Debug routine modification
7 : Critical MSR modification
8 : Object type
9 : A processor IVT
a : Modification of a system service function
b : A generic session data region
c : Modification of a session function or .pdata
d : Modification of an import table
e : Modification of a session import table
f : Ps Win32 callout modification
10 : Debug switch routine modification
11 : IRP allocator modification
12 : Driver call dispatcher modification
13 : IRP completion dispatcher modification
14 : IRP deallocator modification
15 : A processor control register
16 : Critical floating point control register modification
17 : Local APIC modification
18 : Kernel notification callout modification
19 : Loaded module list modification
1a : Type 3 process list corruption
1b : Type 4 process list corruption
1c : Driver object corruption
1d : Executive callback object modification
1e : Modification of module padding
1f : Modification of a protected process
20 : A generic data region
21 : A page hash mismatch
22 : A session page hash mismatch
23 : Load config directory modification
24 : Inverted function table modification
25 : Session configuration modification
102 : Modification of win32k.sys
Debugging Details:
------------------
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 9600.18202.amd64fre.winblue_ltsb.160119-0600
SYSTEM_MANUFACTURER: Acer
SYSTEM_PRODUCT_NAME: Aspire E1-410G
SYSTEM_SKU: EA40_BM_083E_2.10
SYSTEM_VERSION: V2.10
BIOS_VENDOR: Insyde Corp.
BIOS_VERSION: V2.10
BIOS_DATE: 05/13/2014
BASEBOARD_MANUFACTURER: Acer
BASEBOARD_PRODUCT: Aspire E1-410G
BASEBOARD_VERSION: V2.10
DUMP_TYPE: 2
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
BUGCHECK_P1: a3a01f590988f6c7
BUGCHECK_P2: b3b72bdf5c08e256
BUGCHECK_P3: 3
BUGCHECK_P4: 18
CPU_COUNT: 4
CPU_MHZ: 74b
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 37
CPU_STEPPING: 3
CPU_MICROCODE: 6,37,3,0 (F,M,S,R) SIG: 322'00000000 (cache) 322'00000000 (init)
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: BAD_STACK_0x109
BUGCHECK_STR: 0x109
PROCESS_NAME: System
CURRENT_IRQL: 2
ANALYSIS_SESSION_HOST: ACER
ANALYSIS_SESSION_TIME: 03-23-2016 13:48:43.0197
ANALYSIS_VERSION: 10.0.10586.567 amd64fre
STACK_TEXT:
ffffd001`be07a1c8 00000000`00000000 : 00000000`00000109 a3a01f59`0988f6c7 b3b72bdf`5c08e256 00000000`00000003 : nt!KeBugCheckEx
STACK_COMMAND: kb
THREAD_SHA1_HASH_MOD_FUNC: 81a83ae0317433a47fcc36991983df3b6e638b71
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 6e16edd8c7dd677734fdbcd2397a2e35e9fae964
THREAD_SHA1_HASH_MOD: 76cd06466d098060a9eb26e5fd2a25cb1f3fe0a3
SYMBOL_NAME: ANALYSIS_INCONCLUSIVE
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Unknown_Module
IMAGE_NAME: Unknown_Image
DEBUG_FLR_IMAGE_TIMESTAMP: 0
IMAGE_VERSION:
BUCKET_ID: BAD_STACK_0x109
PRIMARY_PROBLEM_CLASS: BAD_STACK
FAILURE_BUCKET_ID: BAD_STACK_0x109
TARGET_TIME: 2016-03-22T02:57:14.000Z
OSBUILD: 9600
OSSERVICEPACK: 0
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 784
PRODUCT_TYPE: 1
OSPLATFORM_TYPE: x64
OSNAME: Windows 8.1
OSEDITION: Windows 8.1 WinNt TerminalServer SingleUserTS Personal
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: 2016-01-20 00:19:09
BUILDDATESTAMP_STR: 160119-0600
BUILDLAB_STR: winblue_ltsb
BUILDOSVER_STR: 6.3.9600.18202.amd64fre.winblue_ltsb.160119-0600
ANALYSIS_SESSION_ELAPSED_TIME: 12e4
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:bad_stack_0x109
FAILURE_ID_HASH: {b4d7023a-05c3-49b2-3ea4-6240fe57d90e}
Followup: MachineOwner
---------
1: kd> g
^ No runnable debuggees error in 'g'
1: kd> g
^ No runnable debuggees error in 'g' -
您好,
我查阅了一些资料,关于蓝屏0x109错误,可以参考以下链接:(原文为英文网页)
https://msdn.microsoft.com/zh-cn/library/ff557228(v=VS.85).aspx
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.
-
0x00000109 蓝屏表示严重的 Windows 内核数据错误,一般是由于驱动程序编写有 BUG 或者硬件本身存在问题引起的。
你贴出的 Dump 文件分析结果并没有准确检测到有问题的驱动或进程名,因此不太好判断原因。这台电脑的硬件有没有运行异常的地方?或者最近有没有更换过驱动?
Alexis Zhang
http://mvp.microsoft.com/zh-cn/mvp/Jie%20Zhang-4000545
http://blogs.itecn.net/blogs/alexis推荐以 NNTP Bridge 桥接新闻组方式访问论坛。
本帖是回复帖,原帖作者是楼上的 "敏爷"
| 下面是我用Windbg解析Dmp的结果但是看不懂T T可以麻烦帮忙看看么?
| Microsoft (R) Windows Debugger Version 10.0.10586.567 AMD64- 已标记为答案 敏爷 2016年3月24日 6:58
-
那试一试重新安装一遍所有设备驱动吧,可以借助驱动精灵,有更新的驱动顺便升级一遍。如果还是有问题的话,估计就是硬件故障了。
Alexis Zhang
http://mvp.microsoft.com/zh-cn/mvp/Jie%20Zhang-4000545
http://blogs.itecn.net/blogs/alexis推荐以 NNTP Bridge 桥接新闻组方式访问论坛。
本帖是回复帖,原帖作者是楼上的 "敏爷"
| 我感觉的话是没有什么异常的,,我一直没有对电脑有什么改动,,就是突然这样了。。
|