閱讀117 返回首頁    go iPhone_iPad_Mac_apple

win10 1703 CRITICAL

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


Loading Dump File [C:\Windows\Minidump\101917-33656-01.dmp]
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 = 0xfffff800`e5201000 PsLoadedModuleList = 0xfffff800`e554d5a0
Debug session time: Thu Oct 19 12:11:11.778 2017 (UTC + 8:00)
System Uptime: 0 days 0:12:59.214
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, {a39fc1e3d5c8b567, b3b6ce6a284a32d6, ffff828b3897cc20, 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: a39fc1e3d5c8b567, Reserved
Arg2: b3b6ce6a284a32d6, Reserved
Arg3: ffff828b3897cc20, 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
    2a  : Type 4 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:  20445

SYSTEM_SKU:  LENOVO_MT_20445_BU_idea_FM_Lenovo M40-70

SYSTEM_VERSION:  Lenovo M40-70

BIOS_VENDOR:  LENOVO

BIOS_VERSION:  8BCN46WW(V3.09)

BIOS_DATE:  12/03/2014

BASEBOARD_MANUFACTURER:  LENOVO

BASEBOARD_PRODUCT:  INVALID

BASEBOARD_VERSION:  31900060WIN

DUMP_TYPE:  2

DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

BUGCHECK_P1: a39fc1e3d5c8b567

BUGCHECK_P2: b3b6ce6a284a32d6

BUGCHECK_P3: ffff828b3897cc20

BUGCHECK_P4: 1c

CPU_COUNT: 4

CPU_MHZ: 95a

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 45

CPU_STEPPING: 1

CPU_MICROCODE: 6,45,1,0 (F,M,S,R)  SIG: 1D'00000000 (cache) 1D'00000000 (init)

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  BAD_STACK_0x109

BUGCHECK_STR:  0x109

PROCESS_NAME:  System

CURRENT_IRQL:  2

ANALYSIS_SESSION_HOST:  UPAN-20170309SV

ANALYSIS_SESSION_TIME:  10-19-2017 12:35:30.0408

ANALYSIS_VERSION: 10.0.15063.468 amd64fre

STACK_TEXT:  
ffffc480`33bcad78 00000000`00000000 : 00000000`00000109 a39fc1e3`d5c8b567 b3b6ce6a`284a32d6 ffff828b`3897cc20 : 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

BUCKET_ID:  BAD_STACK_0x109

PRIMARY_PROBLEM_CLASS:  BAD_STACK

FAILURE_BUCKET_ID:  BAD_STACK_0x109

TARGET_TIME:  2017-10-19T04:11:11.000Z

OSBUILD:  15063

OSSERVICEPACK:  0

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-03-18 12:40:44

ANALYSIS_SESSION_ELAPSED_TIME:  7a3

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:bad_stack_0x109

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

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

dmp

文件已上傳網盤。麻煩協助修複問題。
https://pan.baidu.com/s/1dFtmDMT

感謝！

最後更新：2017-10-19 13:03:21

  上一篇：go 關於windows8.1基於x64的係統更新（kb2919355）更新失敗
  下一篇：go edge,在 Web 上記筆記,無法將網頁拉到底