windows server 2016 0x109蓝屏

Question

Loading Dump File [C:\Windows\minidump\112420-8312-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRVC:\Symbolshttp://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 14393 MP (8 procs) Free x64
Product: Server, suite: TerminalServer SingleUserTS
Built by: 14393.2248.amd64fre.rs1_release.180427-1804
Machine Name:
Kernel base = 0xfffff802e9e7b000 PsLoadedModuleList = 0xfffff802ea182160
Debug session time: Tue Nov 24 08:51:18.186 2020 (GMT+8)
System Uptime: 0 days 0:58:00.538
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
........

---

• *
• Bugcheck Analysis *
• *

  ---

Use !analyze -v to get detailed debugging information.

BugCheck 109, {a39fcc5b1ec059a6, b3b6d8e171422891, ffff8d02874170d0, 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 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: a39fcc5b1ec059a6, Reserved
   Arg2: b3b6d8e171422891, Reserved
   Arg3: ffff8d02874170d0, 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

Debugging Details:

---

BUGCHECK_STR: 0x109

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff802e9fd6940

STACK_TEXT:
ffffa200e2348978 0000000000000000 : 0000000000000109 a39fcc5b1ec059a6 b3b6d8e171422891 ffff8d02874170d0 : nt!KeBugCheckEx

STACK_COMMAND: kb

SYMBOL_NAME: ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

BUCKET_ID: BAD_STACK

Followup: MachineOwner

dmp链接: https://pan.baidu.com/s/1Vol0ixfNDxdc1DjPMI3GuA 提取码: a855

Answer 1

Hi,

Read this link , it can help :

bug-check-0x109---critical-structure-corruption

please don't forget to mark this reply as answer if it help you to fix your issue