******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************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/64bitP... 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: a3a00f58c45ab69b, ReservedArg2: b3b71bdf16d9ee1a, ReservedArg3: ffffe00175d61790, Failure type dependent informationArg4: 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 modificationDebugging Details:------------------BUGCHECK_STR: 0x109DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULTPROCESS_NAME: SystemCURRENT_IRQL:… 2LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff803289d39a0STACK_TEXT: ffffd001`78cd41c8 00000000`00000000 : 00000000`00000109 a3a00f58`c45ab69b b3b71bdf`16d9ee1a ffffe001`75d61790 : nt!KeBugCheckExSTACK_COMMAND: kbSYMBOL_NAME: ANALYSIS_INCONCLUSIVEFOLLOWUP_NAME: MachineOwnerMODULE_NAME: Unknown_ModuleIMAGE_NAME: Unknown_ImageDEBUG_FLR_IMAGE_TIMESTAMP: 0BUCKET_ID: BAD_STACKFollowup: MachineOwner--------- Ukázat celý příspěvek
