Critical Structure Corruption

Question

Hello, I've updated to the latest Win 11 build and then crashes started to appear.
I've looked trough the dump file but couldn't find anything helpfull.
Could anyone help me with what could be causing that?
Link for the dumpfile

Here is it analyzed:
3: 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: a39fd95ddac045ce, Reserved Arg2: b3b6e5e42d41b233, Reserved Arg3: fffff804458d7000, Failure type dependent information Arg4: 000000000000000d, 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: 3859

Key  : Analysis.DebugAnalysisManager
Value: Create

Key  : Analysis.Elapsed.mSec
Value: 5662

Key  : Analysis.Init.CPU.mSec
Value: 390

Key  : Analysis.Init.Elapsed.mSec
Value: 43082

Key  : Analysis.Memory.CommitPeak.Mb
Value: 87

DUMP_FILE_ATTRIBUTES: 0x808 Kernel Generated Triage Dump

BUGCHECK_CODE: 109

BUGCHECK_P1: a39fd95ddac045ce

BUGCHECK_P2: b3b6e5e42d41b233

BUGCHECK_P3: fffff804458d7000

BUGCHECK_P4: d

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
ffffe48c76dcce28 0000000000000000 : 0000000000000109 a39fd95ddac045ce b3b6e5e42d41b233 fffff804458d7000 : nt!KeBugCheckEx

SYMBOL_NAME: LXCORE!_imp_KeQueryPerformanceCounter+0

MODULE_NAME: LXCORE

IMAGE_NAME: LXCORE.SYS

IMAGE_VERSION: 10.0.22471.1000

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 0

FAILURE_BUCKET_ID: 0x109_d_LXCORE!_imp_KeQueryPerformanceCounter

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {c56c53a9-25f2-3e6b-c28a-ea78d08f805f}

Followup: MachineOwner

Answer 1

Thank you for letting us know.

Answer 2

Installed the latest build and looks like the problem is gone. Thank you for your support and your time.

Answer 3

Yes, getting stuck in the reboot loop is common, but you would have easily restored it using a system restore point or other options:

https://www.tenforums.com/tutorials/5470-enable...

Content on the above blog is written by a Windows MVP so it is safe. However, do watch out for the ads.

Answer 4

I've found thanks to you and verifier what was causing the problem, but then I was stucked with the BSOD screen so I had to restore. So I'm gonna install again the newest Win 11 build and see if it would be working without that application.

Answer 5

Hi Petulikan,

I am Sumit here to assist you with this question.

No 3rd party driver was named in the minidump, however, Lxcore.sys was named which is a part of the OS though.

The next step,

Let us try finding any misbehaving driver

Enable Driver Verifier:

http://answers.microsoft.com/en-us/windows/wiki...

(Must create a Restore point before)

Upload the newer dumps when you get Driver_Verifier_detected_voilation.

Please note that the system might crash before you reach the desktop-if it does please let us know so that we can guide you to disable Verifier.