LXCORE.SYS BlueScreen Error.

Question

I am receiving the LXCORE.SYS error. This is the third time this has happened today.
I used a registry cleaner yesterday (This has more than likely caused the issue.)
The windows version is windows 11 not 10.
I have used WinDbg to try and debug the error and find a fix but I am unsure what this information reads.
Any help would be appreciated thank you.

Below is the code from WinDBG

Microsoft (R) Windows Debugger Version 10.0.25200.1003 AMD64 Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\Minidump\032823-16218-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv* Executable search path is: Windows 10 Kernel Version 22621 MP (16 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Edition build lab: 22621.1.amd64fre.ni_release.220506-1250 Machine Name: Kernel base = 0xfffff80342000000 PsLoadedModuleList = 0xfffff80342c13430 Debug session time: Tue Mar 28 15:16:26.938 2023 (UTC + 11:00) System Uptime: 0 days 0:34:10.717 Loading Kernel Symbols ............................................................... ................................................................ ................................................................ .............................................. Loading User Symbols Loading unloaded module list ...................... For analysis of this file, run !analyze -v nt!KeBugCheckEx: fffff80342429400 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff8304171aee10=0000000000000109 6: 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: a3a025645a3b0508, Reserved Arg2: b3b731ea9a52915e, Reserved Arg3: fffff80347858000, 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: 796

Key  : Analysis.DebugAnalysisManager
Value: Create

Key  : Analysis.Elapsed.mSec
Value: 12950

Key  : Analysis.IO.Other.Mb
Value: 26

Key  : Analysis.IO.Read.Mb
Value: 0

Key  : Analysis.IO.Write.Mb
Value: 33

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

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

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

Key  : Bugcheck.Code.DumpHeader
Value: 0x109

Key  : Bugcheck.Code.Register
Value: 0x109

Key  : WER.OS.Branch
Value: ni\_release

Key  : WER.OS.Timestamp
Value: 2022-05-06T12:50:00Z

Key  : WER.OS.Version
Value: 10.0.22621.1

FILE_IN_CAB: 032823-16218-01.dmp

TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b

BUGCHECK_CODE: 109

BUGCHECK_P1: a3a025645a3b0508

BUGCHECK_P2: b3b731ea9a52915e

BUGCHECK_P3: fffff80347858000

BUGCHECK_P4: d

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
ffff8304171aee08 0000000000000000 : 0000000000000109 a3a025645a3b0508 b3b731ea9a52915e fffff80347858000 : nt!KeBugCheckEx

SYMBOL_NAME: LXCORE!_imp_KeQueryPerformanceCounter+0

MODULE_NAME: LXCORE

IMAGE_NAME: LXCORE.SYS

IMAGE_VERSION: 10.0.22621.1105

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 0

FAILURE_BUCKET_ID: 0x109_d_LXCORE!_imp_KeQueryPerformanceCounter

OS_VERSION: 10.0.22621.1

BUILDLAB_STR: ni_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

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

Followup: MachineOwner

Answer 1

Hi Ash,

I'm Dyari. Thanks for reaching out. I will be happy to assist you in this regard.

Kindly check C:\Windows\Minidump and copy available minidump files to the desktop then share them via One Drive or Google Drive in order to be analyzed and indicate which file is causing the crash.
https://answers.microsoft.com/en-us/windows/for...

Also, check C:\Windows and share the MEMORY.DMP file.