BSOD 109 Bluescreen

Good afternoon, I can’t decipher the windbg minidump, please help. Here's windbg's analysis. Thanks to everyone who responded.

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 mi c ros of t .com/ wh dc/d river/kern el/ 64bi tPat ching .m spx
  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: a3a0265a8f0076c9, Reserved
    Arg2: b3b732e0e17ebf81, Reserved
    Arg3: fffff80748d3b23c, 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: 1078

Key : Analysis.Elapsed.mSec
Value: 2634

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

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

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

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

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

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

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 : Failure.Bucket
Value: 0x109_1_nt!EtwpTraceHandle

Key : Failure.Hash
Value: {0cdf63fa-41f9-d9d0-2845-1edb9da9de87}

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Version
Value: 10.0.19041.1

BUGCHECK_CODE: 109

BUGCHECK_P1: a3a0265a8f0076c9

BUGCHECK_P2: b3b732e0e17ebf81

BUGCHECK_P3: fffff80748d3b23c

BUGCHECK_P4: 1

FILE_IN_CAB: 021825-9921-01.dmp

FAULTING_THREAD: ffffe7020f3b1040

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: csrss.exe

STACK_TEXT:
ffffe50675b0ed68 0000000000000000 : 0000000000000109 a3a0265a8f0076c9 b3b732e0e17ebf81 fffff80748d3b23c : nt!KeBugCheckEx

SYMBOL_NAME: nt!EtwpTraceHandle+0

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.19041.5486

STACK_COMMAND: .process /r /p 0xffffe701ed702080; .thread 0xffffe7020f3b1040 ; kb

BUCKET_ID_FUNC_OFFSET: 0

FAILURE_BUCKET_ID: 0x109_1_nt!EtwpTraceHandle

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {0cdf63fa-41f9-d9d0-2845-1edb9da9de87}

Followup: MachineOwner

What were you doing at the time? Do you have a custom driver installed? This is saying that some code overwrote some part of a function's code.

The task is to find which driver is failing or which hardware is failing.

There was a program for overclocking the MSI afterburner graphics card and there were previous versions of the driver.

Now everything is deleted and the latest driver from the manufacturer is installed. Clean installation.

Network card - there were installations to improve the Internet. Now everything is reset and reinstalled from the manufacturer.

The old drivers have been removed from the system.

The task is to find which driver is failing or which hardware is failing.

Overclocking/correction for RAM is installed in the BIOS. The voltage for the problematic and hot 13900k processor is set.

There was a systematic BSOD 1-2 times a day with error 0x0000001e.

If this is a random memory overwrite and you do not have a custom driver in the mix, then you have very little chance of solving this.

MAYBE if you catch this in a live kernel debugger, you could trace back in the stack, but something like this can be caused by a driver that is already gone.