阅读399 返回首页    go windows

蓝屏错误Unknown


Microsoft (R) Windows Debugger Version 10.0.14321.1024 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 15063 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff801`cac11000 PsLoadedModuleList = 0xfffff801`caf5d660
Debug session time: Mon Dec 18 10:19:06.016 2017 (UTC + 8:00)
System Uptime: 0 days 0:25:08.781
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, {a39fe25acf7ca79d, b3b6eee121fe23e8, ffffa30232663740, 1c}

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 https://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: a39fe25acf7ca79d, Reserved
Arg2: b3b6eee121fe23e8, Reserved
Arg3: ffffa30232663740, Failure type dependent information
Arg4: 000000000000001c, 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
26  : An extended processor control register
27  : Type 1 pool corruption
28  : Type 2 pool corruption
29  : Type 3 pool corruption
101 : General pool corruption
102 : Modification of win32k.sys

Debugging Details:
------------------


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

SYSTEM_MANUFACTURER:  LENOVO

SYSTEM_PRODUCT_NAME:  80RU

SYSTEM_SKU:  LENOVO_MT_80RU_BU_idea_FM_Lenovo ideapad 700-15ISK

SYSTEM_VERSION:  Lenovo ideapad 700-15ISK

BIOS_VENDOR:  LENOVO

BIOS_VERSION:  E5CN52WW

BIOS_DATE:  04/28/2016

BASEBOARD_MANUFACTURER:  LENOVO

BASEBOARD_PRODUCT:  Lenovo ideapad 700-15ISK

BASEBOARD_VERSION:  SDK0K09938 WIN

DUMP_TYPE:  2

DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

BUGCHECK_P1: a39fe25acf7ca79d

BUGCHECK_P2: b3b6eee121fe23e8

BUGCHECK_P3: ffffa30232663740

BUGCHECK_P4: 1c

CPU_COUNT: 4

CPU_MHZ: 900

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 5e

CPU_STEPPING: 3

CPU_MICROCODE: 6,5e,3,0 (F,M,S,R)  SIG: 74'00000000 (cache) 74'00000000 (init)

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  BAD_STACK_0x109

BUGCHECK_STR:  0x109

PROCESS_NAME:  System

CURRENT_IRQL:  2

ANALYSIS_SESSION_HOST:  DESKTOP-NN75UK3

ANALYSIS_SESSION_TIME:  12-18-2017 10:36:38.0627

ANALYSIS_VERSION: 10.0.14321.1024 amd64fre

STACK_TEXT:  
ffffe780`0f30ecf8 00000000`00000000 : 00000000`00000109 a39fe25a`cf7ca79d b3b6eee1`21fe23e8 ffffa302`32663740 : nt!KeBugCheckEx


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    fffff801cad7d833-fffff801cad7d840  14 bytes - nt!KiRestoreProcessorControlState+33
[ 0f 01 59 66 0f b7 41 70:68 00 70 0f 92 c7 44 24 ]
14 errors : !nt (fffff801cad7d833-fffff801cad7d840)

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

BUCKET_ID:  BAD_STACK_0x109

PRIMARY_PROBLEM_CLASS:  BAD_STACK

FAILURE_BUCKET_ID:  BAD_STACK_0x109

TARGET_TIME:  2017-12-18T02:19:06.000Z

OSBUILD:  15063

OSSERVICEPACK:  786

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  2017-11-30 10:34:10

ANALYSIS_SESSION_ELAPSED_TIME: 1691

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:bad_stack_0x109

FAILURE_ID_HASH:  {b4d7023a-05c3-49b2-3ea4-6240fe57d90e}

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

您好！

 

感谢您联系微软技术支持。

 

我了解到您遇到系统蓝屏的问题 。

 

请您在电脑重启之后，上传蓝屏minidump文件到百度网盘，然后提供链接，文件默认路径在C:\Windows\Minidump（不需要进行压缩操作）。

 

您可以通过以下方案收集您的dump日志文件：

 

1）打开控制面板>>系统>>高级系统设置>>高级>>启动和故障恢复>>设置；

 

2）写入调试信息>>选择“小内存转储（256KB）”，路径选择默认，确定并重启您的计算机；

 

3）再次蓝屏后，前往C:\Windows\Minidump提取即可。

 

希望以上的信息可以帮助到您。

您好！

 

由于长时间未得到您的回复，该问题我们会暂时作为归档处理，如果您仍有问题，欢迎随时跟帖回复。如果有其他问题需要提交，也欢迎您再次提问。

 

感谢使用微软产品。

 

如果您所咨询的问题，得到解决请对我们的回复进行标记解答（对我们的工作非常重要）

 

如您的问题没有解决，我们会继续为您提供技术支持。

 

我们秉承客户至上的服务理念。如果您对微软工程师在论坛中的服务有意见与建议，欢迎提出，以便我们提供更优质的服务。Microsoft Answers欢迎您！

最后更新：2017-12-28 09:04:27

  上一篇：go 下载office2010提示错误
  下一篇：go WIN10蓝屏，代码109，windbg分析verifier之前和之后的DUMP文件，结果均为un