有么有那為大佬幫看看是什么原因
CRITICAL_STRUCTURE_CORRUPTION (109)This bugcheck is generated when the kernel detects that critical kernel code ordata 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.mspx2) 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, ReservedArg2: b3b6cedf29e8fa9c, ReservedArg3: fffff80116d58e60, Failure type dependent informationArg4: 000000000000001e, Type of corrupted region, can be0 : A generic data region1 : Modification of a function or .pdata2 : A processor IDT3 : A processor GDT4 : Type 1 process list corruption5 : Type 2 process list corruption6 : Debug routine modification7 : Critical MSR modification8 : Object type9 : A processor IVTa : Modification of a system service functionb : A generic session data regionc : Modification of a session function or .pdatad : Modification of an import tablee : Modification of a session import tablef : Ps Win32 callout modification10: Debug switch routine modification11: IRP allocator modification12: Driver call dispatcher modification13: IRP completion dispatcher modification14: IRP deallocator modification15: A processor control register16: Critical floating point control register modification17: Local APIC modification18: Kernel notification callout modification19: Loaded module list modification1a: Type 3 process list corruption1b: Type 4 process list corruption1c: Driver object corruption1d: Executive callback object modification1e: Modification of module padding1f: Modification of a protected process20: A generic data region21: A page hash mismatch22: A session page hash mismatch23: Load config directory modification24: Inverted function table modification25: Session configuration modification26: An extended processor control register27: Type 1 pool corruption28: Type 2 pool corruption29: Type 3 pool corruption2a: Type 4 pool corruption2b: Modification of a function or .pdata2c: Image integrity corruption2d: Processor misconfiguration2e: Type 5 process list corruption2f: Process shadow corruption30: Retpoline code page corruption101 : General pool corruption102 : Modification of win32k.sysDebugging Details:------------------KEY_VALUES_STRING: 1Key: Analysis.CPU.mSecValue: 4499Key: Analysis.DebugAnalysisProvider.CPPValue: Create: 8007007e on MS-UHOHSPJXXAZOKey: Analysis.DebugDataValue: CreateObjectKey: Analysis.DebugModelValue: CreateObjectKey: Analysis.Elapsed.mSecValue: 6588Key: Analysis.Memory.CommitPeak.MbValue: 76Key: Analysis.SystemValue: CreateObjectADDITIONAL_XML: 1OS_BUILD_LAYERS: 1DUMP_FILE_ATTRIBUTES: 0x8Kernel Generated Triage DumpBUGCHECK_CODE:109BUGCHECK_P1: a39fc258d768b509BUGCHECK_P2: b3b6cedf29e8fa9cBUGCHECK_P3: fffff80116d58e60BUGCHECK_P4: 1eCUSTOMER_CRASH_COUNT:1PROCESS_NAME:systemBAD_STACK_POINTER:fffff8011acb0a98STACK_TEXT:fffff801`1acb0a98 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeBugCheckExSYMBOL_NAME:nt!WriteRegisterWithIndex8+0MODULE_NAME: ntIMAGE_NAME:ntkrnlmp.exeIMAGE_VERSION:10.0.19041.208STACK_COMMAND:.thread ; .cxr ; kbBUCKET_ID_FUNC_OFFSET:0FAILURE_BUCKET_ID:0x109_1e_nt!WriteRegisterWithIndex8OSPLATFORM_TYPE:x64OSNAME:Windows 10FAILURE_ID_HASH:{3e8fc38d-21c8-e8b6-d6ca-09982167b347}Followup: machineOwner---------
百度翻譯值得你擁有