有么有那为大佬帮看看是什么原因

更新时间2020-12-30 23:30:50

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: a39fc258d768b509, Reserved
Arg2: b3b6cedf29e8fa9c, Reserved
Arg3: fffff80116d58e60, Failure type dependent information
Arg4: 000000000000001e, 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
2b  : Modification of a function or .pdata
2c  : Image integrity corruption
2d  : Processor misconfiguration
2e  : Type 5 process list corruption
2f  : Process shadow corruption
30  : Retpoline code page corruption
101 : General pool corruption
102 : Modification of win32k.sys
Debugging Details:
------------------
KEY_VALUES_STRING: 1
   Key  : Analysis.CPU.mSec
   Value: 4499
   Key  : Analysis.DebugAnalysisProvider.CPP
   Value: Create: 8007007e on MS-UHOHSPJXXAZO
   Key  : Analysis.DebugData
   Value: CreateObject
   Key  : Analysis.DebugModel
   Value: CreateObject
   Key  : Analysis.Elapsed.mSec
   Value: 6588
   Key  : Analysis.Memory.CommitPeak.Mb
   Value: 76
   Key  : Analysis.System
   Value: CreateObject
ADDITIONAL_XML: 1
OS_BUILD_LAYERS: 1
DUMP_FILE_ATTRIBUTES: 0x8
 Kernel Generated Triage Dump
BUGCHECK_CODE:  109
BUGCHECK_P1: a39fc258d768b509
BUGCHECK_P2: b3b6cedf29e8fa9c
BUGCHECK_P3: fffff80116d58e60
BUGCHECK_P4: 1e
CUSTOMER_CRASH_COUNT:  1
PROCESS_NAME:  system
BAD_STACK_POINTER:  fffff8011acb0a98
STACK_TEXT:  
fffff801`1acb0a98 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
SYMBOL_NAME:  nt!WriteRegisterWithIndex8+0
MODULE_NAME: ntIMAGE_NAME:  ntkrnlmp.exe
IMAGE_VERSION:  10.0.19041.208
STACK_COMMAND:  .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET:  0
FAILURE_BUCKET_ID:  0x109_1e_nt!WriteRegisterWithIndex8
OSPLATFORM_TYPE:  x64
OSNAME:  Windows 10
FAILURE_ID_HASH:  {3e8fc38d-21c8-e8b6-d6ca-09982167b347}
Followup:     machineOwner
---------

百度翻译值得你拥有