CRITICAL_STRUCTURE_CORRUPTION

Hello, I have been having the critical structure corruption error for about 3 months now I've tried a lot of different fixes such as sfc scan, updating windows and drivers, reinstalling windows, running a ram check, checking my hdd. But nothing seemed to fix the issue forever as it would happen some days and other days the error would not occur at all even though I've scanned the ram and its come up with having no issues I still believe it might be causing my bsod if anyone could look through my minidump and tell me what the problem might be it would be very appreciated.

Loading Dump File [C:\Windows\Minidump\123024-17500-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 26100 MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Kernel base = 0xfffff805bfe00000 PsLoadedModuleList = 0xfffff805c0cf4850 Debug session time: Mon Dec 30 19:40:21.136 2024 (UTC + 0:00) System Uptime: 0 days 1:56:36.794 Loading Kernel Symbols ............................................................... ................................................................ ................................................................ ................... Loading User Symbols PEB is paged out (Peb.Ldr = 0000004f4fcaf018). Type ".hh dbgerr001" for details Loading unloaded module list .............. For analysis of this file, run !analyze -v nt!KeBugCheckEx: fffff805c02b85d0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffbc0d`aa326d30=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: a3a01d6560c9b5a0, Reserved Arg2: b3b729ebb3485bc2, Reserved Arg3: fffff805c025e0f4, Failure type dependent information Arg4: 0000000000000001, 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: 2328

Key  : Analysis.Elapsed.mSec
Value: 9368

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

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

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

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

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

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

Key  : Analysis.Version.DbgEng
Value: 10.0.27725.1000

Key  : Analysis.Version.Description
Value: 10.2408.27.01 amd64fre

Key  : Analysis.Version.Ext
Value: 1.2408.27.1

Key  : Bugcheck.Code.LegacyAPI
Value: 0x109

Key  : Bugcheck.Code.TargetModel
Value: 0x109

Key  : Dump.Attributes.AsUlong
Value: 21008

Key  : Dump.Attributes.DiagDataWrittenToHeader
Value: 1

Key  : Dump.Attributes.ErrorCode
Value: 0

Key  : Dump.Attributes.KernelGeneratedTriageDump
Value: 1

Key  : Dump.Attributes.LastLine
Value: Dump completed successfully.

Key  : Dump.Attributes.ProgressPercentage
Value: 0

Key  : Failure.Bucket
Value: MEMORY\_CORRUPTION\_ONE\_BIT

Key  : Failure.Hash
Value: {e3faf315-c3d0-81db-819a-6c43d23c63a7}

BUGCHECK_CODE: 109

BUGCHECK_P1: a3a01d6560c9b5a0

BUGCHECK_P2: b3b729ebb3485bc2

BUGCHECK_P3: fffff805c025e0f4

BUGCHECK_P4: 1

FILE_IN_CAB: 123024-17500-01.dmp

DUMP_FILE_ATTRIBUTES: 0x21008 Kernel Generated Triage Dump

FAULTING_THREAD: ffffde0cdcead540

MEMORY_CORRUPTOR: ONE_BIT

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: csrss.exe

STACK_TEXT:
ffffbc0daa326d28 0000000000000000 : 0000000000000109 a3a01d6560c9b5a0 b3b729ebb3485bc2 fffff805c025e0f4 : nt!KeBugCheckEx

SYMBOL_NAME: nt!MiPageMightBeZero+0

MODULE_NAME: nt

IMAGE_VERSION: 10.0.26100.2605

STACK_COMMAND: .process /r /p 0xffffde0cc86b1040; .thread 0xffffde0cdcead540 ; kb

IMAGE_NAME: ntkrnlmp.exe

FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {e3faf315-c3d0-81db-819a-6c43d23c63a7}

Followup: MachineOwner