WSL: Critical Structure Corruption (109) by LXCORE.SYS

Version

Microsoft Windows [Version 10.0.22471.1000]

WSL Version

  • WSL 2
  • WSL 1

Kernel Version

5.10.60.1

Distro Version

Ubuntu 20.04

Other Software

No response

Repro Steps

  1. Install WSL2
  2. Have it running in the background

Expected Behavior

  1. Install WSL2
  2. Have it running in the background
  3. No GSOD

Actual Behavior

I get a GSOD about 10 minutes after rebooting the system.

Diagnostic Logs

nt!KeBugCheckEx: fffff80633629170 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffae0ec0ad1d50=0000000000000109


  •                                                                         *
    
  •                    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: a3a0035cefd9563a, Reserved Arg2: b3b70fe342590c6b, Reserved Arg3: fffff80635cf7000, 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: 3562

Key  : Analysis.DebugAnalysisManager
Value: Create

Key  : Analysis.Elapsed.mSec
Value: 3668

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

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

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

Key  : WER.OS.Branch
Value: rs_prerelease

Key  : WER.OS.Timestamp
Value: 2021-09-29T14:15:00Z

Key  : WER.OS.Version
Value: 10.0.22471.1000

DUMP_FILE_ATTRIBUTES: 0x1800

BUGCHECK_CODE: 109

BUGCHECK_P1: a3a0035cefd9563a

BUGCHECK_P2: b3b70fe342590c6b

BUGCHECK_P3: fffff80635cf7000

BUGCHECK_P4: d

PROCESS_NAME: System

STACK_TEXT:
ffffae0ec0ad1d48 0000000000000000 : 0000000000000109 a3a0035cefd9563a b3b70fe342590c6b fffff80635cf7000 : nt!KeBugCheckEx

SYMBOL_NAME: LXCORE!_imp_KeQueryPerformanceCounter+0

MODULE_NAME: LXCORE

IMAGE_NAME: LXCORE.SYS

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 0

FAILURE_BUCKET_ID: 0x109_d_LXCORE!_imp_KeQueryPerformanceCounter

OS_VERSION: 10.0.22471.1000

BUILDLAB_STR: rs_prerelease

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

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

Followup: MachineOwner

About this issue

  • Original URL
  • State: closed
  • Created 5 years ago
  • Reactions: 2
  • Comments: 17 (7 by maintainers)

Most upvoted comments

Blue screen started after WIN 11 22H2 update uninstalling old version FACEIT helped me also. Thanks a lot.

Can confirm that this is still an issue today October 26th, 2022. Using Windows 11 22H2 22621.755 Uninstalling FACEIT did the trick.

Do you have FACEIT anti cheat installed? We’ve seen many instances of this crash due to them using IAT patching in lxcore.

Also can confirm that this is still a problem. Had an old version of FACEIT AC installed (probably from at least a year back because I don’t even use FACEIT anymore) and was suffering from the same error after upgrading to Windows 11 22H2 update. Before that the problem didn’t happen. Uninstalling FACEIT AC seems to have solved it. I unfortunately missed to record the specific version installed before I removed it so I can’t tell exactly which versions are affected. Also don’t know if this is solved by now in newer versions. This really was driving me insane and I already feared that my memory may have been faulty. Who would have thought that a leftover install of FACEIT anti cheat was crashing my computer countless times a day. What a hell to troubleshoot. Luckily I found a link to this report in a random post in the Microsoft Community forum or else I would never have solved this.

@benhillis Sorry to bother you again. Do you know if there is a way to disable the Faceit AC Driver and enable it like I do with Hyper-V? So that I just enable it when I want to play and have it disabled when I want to use WSL?

Touche 😉