PC keeps doing hard restart kernal-power event id 41.

Question

************* Preparing the environment for Debugger Extensions Gallery repositories **************
   ExtensionRepository : Implicit
   UseExperimentalFeatureForNugetShare : true
   AllowNugetExeUpdate : true
   NonInteractiveNuget : true
   AllowNugetMSCredentialProviderInstall : true
   AllowParallelInitializationOfLocalRepositories : true
   EnableRedirectToChakraJsProvider : false

   -- Configuring repositories
      ----> Repository : LocalInstalled, Enabled: true
      ----> Repository : UserExtensions, Enabled: true

>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds

************* Waiting for Debugger Extensions Gallery to Initialize **************

>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.016 seconds
   ----> Repository : UserExtensions, Enabled: true, Packages count: 0
   ----> Repository : LocalInstalled, Enabled: true, Packages count: 46

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


Loading Dump File [C:\Users\momma\OneDrive\Desktop\122425-16843-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*
Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 26100 MP (24 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0xfffff805`b7c00000 PsLoadedModuleList = 0xfffff805`b8af5010
Debug session time: Wed Dec 24 21:39:26.357 2025 (UTC - 6:00)
System Uptime: 3 days 3:19:02.171
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.............................
Loading User Symbols

Loading unloaded module list
............................................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff805`b80fb310 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:fffffd82`5fe219a0=0000000000000139
4: kd> !analyze -v
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.............................
Loading User Symbols

Loading unloaded module list
............................................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KERNEL_SECURITY_CHECK_FAILURE (139)
A kernel component has corrupted a critical data structure.  The corruption
could potentially allow a malicious user to gain control of this machine.
Arguments:
Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
Arg2: fffffd825fe21cc0, Address of the trap frame for the exception that caused the BugCheck
Arg3: fffffd825fe21c18, Address of the exception record for the exception that caused the BugCheck
Arg4: 0000000000000000, Reserved

Debugging Details:
------------------


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 906

    Key  : Analysis.Elapsed.mSec
    Value: 903

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

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

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

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.29482.1003

    Key  : Analysis.Version.Description
    Value: 10.2509.29.03 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2509.29.3

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x139

    Key  : Bugcheck.Code.TargetModel
    Value: 0x139

    Key  : Dump.Attributes.AsUlong
    Value: 0x21808

    Key  : Dump.Attributes.DiagDataWrittenToHeader
    Value: 1

    Key  : Dump.Attributes.ErrorCode
    Value: 0x0

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

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

    Key  : Dump.Attributes.ProgressPercentage
    Value: 0

    Key  : FailFast.Name
    Value: CORRUPT_LIST_ENTRY

    Key  : FailFast.Type
    Value: 3

    Key  : Failure.Bucket
    Value: 0x139_3_CORRUPT_LIST_ENTRY_nt!KiFastFailDispatch

    Key  : Failure.Exception.Code
    Value: 0xc0000409

    Key  : Failure.Exception.Record
    Value: 0xfffffd825fe21c18

    Key  : Failure.Hash
    Value: {3aede96a-54dd-40d6-d4cb-2a161a843851}

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 0x7497cf94

    Key  : Hypervisor.Flags.AnyHypervisorPresent
    Value: 1

    Key  : Hypervisor.Flags.ApicEnlightened
    Value: 1

    Key  : Hypervisor.Flags.ApicVirtualizationAvailable
    Value: 0

    Key  : Hypervisor.Flags.AsyncMemoryHint
    Value: 0

    Key  : Hypervisor.Flags.CoreSchedulerRequested
    Value: 0

    Key  : Hypervisor.Flags.CpuManager
    Value: 1

    Key  : Hypervisor.Flags.DeprecateAutoEoi
    Value: 0

    Key  : Hypervisor.Flags.DynamicCpuDisabled
    Value: 1

    Key  : Hypervisor.Flags.Epf
    Value: 0

    Key  : Hypervisor.Flags.ExtendedProcessorMasks
    Value: 1

    Key  : Hypervisor.Flags.HardwareMbecAvailable
    Value: 1

    Key  : Hypervisor.Flags.MaxBankNumber
    Value: 0

    Key  : Hypervisor.Flags.MemoryZeroingControl
    Value: 0

    Key  : Hypervisor.Flags.NoExtendedRangeFlush
    Value: 0

    Key  : Hypervisor.Flags.NoNonArchCoreSharing
    Value: 1

    Key  : Hypervisor.Flags.Phase0InitDone
    Value: 1

    Key  : Hypervisor.Flags.PowerSchedulerQos
    Value: 0

    Key  : Hypervisor.Flags.RootScheduler
    Value: 0

    Key  : Hypervisor.Flags.SynicAvailable
    Value: 1

    Key  : Hypervisor.Flags.UseQpcBias
    Value: 0

    Key  : Hypervisor.Flags.Value
    Value: 38408431

    Key  : Hypervisor.Flags.ValueHex
    Value: 0x24a10ef

    Key  : Hypervisor.Flags.VpAssistPage
    Value: 1

    Key  : Hypervisor.Flags.VsmAvailable
    Value: 1

    Key  : Hypervisor.RootFlags.AccessStats
    Value: 1

    Key  : Hypervisor.RootFlags.CrashdumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.CreateVirtualProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.DisableHyperthreading
    Value: 0

    Key  : Hypervisor.RootFlags.HostTimelineSync
    Value: 1

    Key  : Hypervisor.RootFlags.HypervisorDebuggingEnabled
    Value: 0

    Key  : Hypervisor.RootFlags.IsHyperV
    Value: 1

    Key  : Hypervisor.RootFlags.LivedumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.MapDeviceInterrupt
    Value: 1

    Key  : Hypervisor.RootFlags.MceEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.Nested
    Value: 0

    Key  : Hypervisor.RootFlags.StartLogicalProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.Value
    Value: 1015

    Key  : Hypervisor.RootFlags.ValueHex
    Value: 0x3f7

    Key  : WER.System.BIOSRevision
    Value: 5.35.0.0


BUGCHECK_CODE:  139

BUGCHECK_P1: 3

BUGCHECK_P2: fffffd825fe21cc0

BUGCHECK_P3: fffffd825fe21c18

BUGCHECK_P4: 0

FILE_IN_CAB:  122425-16843-01.dmp

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


DUMP_FILE_ATTRIBUTES: 0x21808
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffffe3858db1c480

TRAP_FRAME:  fffffd825fe21cc0 -- (.trap 0xfffffd825fe21cc0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffb680d8ff8428 rbx=0000000000000000 rcx=0000000000000003
rdx=ffffb680d8bf8360 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8054b17189b rsp=fffffd825fe21e50 rbp=0000000000000708
 r8=0000000000000000  r9=0000000000000001 r10=fffff805b7f13560
r11=ffffe3858db1cd00 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz ac pe cy
Ntfs!NtfsDeleteCcb+0x2eb:
fffff805`4b17189b cd29            int     29h
Resetting default scope

EXCEPTION_RECORD:  fffffd825fe21c18 -- (.exr 0xfffffd825fe21c18)
ExceptionAddress: fffff8054b17189b (Ntfs!NtfsDeleteCcb+0x00000000000002eb)
   ExceptionCode: c0000409 (Security check failure or stack buffer overrun)
  ExceptionFlags: 00000001
NumberParameters: 1
   Parameter[0]: 0000000000000003
Subcode: 0x3 FAST_FAIL_CORRUPT_LIST_ENTRY 

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1 (!blackboxwinlogon)


CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

ERROR_CODE: (NTSTATUS) 0xc0000409 - The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.

EXCEPTION_CODE_STR:  c0000409

EXCEPTION_PARAMETER1:  0000000000000003

EXCEPTION_STR:  0xc0000409

STACK_TEXT:  
fffffd82`5fe21998 fffff805`b82b5fe9     : 00000000`00000139 00000000`00000003 fffffd82`5fe21cc0 fffffd82`5fe21c18 : nt!KeBugCheckEx
fffffd82`5fe219a0 fffff805`b82b65f2     : ffffe385`65a08440 ffffb680`d7f1f010 ffffb680`d7f1f050 00000000`00000702 : nt!KiBugCheckDispatch+0x69
fffffd82`5fe21ae0 fffff805`b82b4228     : 00000000`00000001 00000000`00000000 00000000`00000000 ffffcd6c`23dfa4be : nt!KiFastFailDispatch+0xb2
fffffd82`5fe21cc0 fffff805`4b17189b     : 00000000`00000708 00000000`00000000 00000000`00000000 fffffd82`00000000 : nt!KiRaiseSecurityCheckFailure+0x368
fffffd82`5fe21e50 fffff805`4b2aa187     : fffffd82`5fe224c0 fffffd82`5fe22000 fffffd82`5fe22110 fffffd82`c00000d8 : Ntfs!NtfsDeleteCcb+0x2eb
fffffd82`5fe21eb0 fffff805`4b24d431     : fffffd82`5fe22110 ffffb680`d8ff8180 ffffb680`d8ff8010 ffffe385`65a081b0 : Ntfs!NtfsCommonClose+0x627
fffffd82`5fe21f70 fffff805`4b24d0c6     : 00000000`00000000 fffff805`b82a9e01 ffffe385`65a081b0 fffff805`b8a15840 : Ntfs!NtfsFspCloseInternal+0x341
fffffd82`5fe220d0 fffff805`b7f4453b     : ffffe385`8db1c480 ffffe385`8db1c480 ffffe385`60686a00 ffffe385`60686ae0 : Ntfs!NtfsFspClose+0x76
fffffd82`5fe223c0 fffff805`b808b77a     : ffffe385`8db1c480 ffffe385`8db1c480 fffff805`b7f44080 ffffe385`60686ae0 : nt!ExpWorkerThread+0x4bb
fffffd82`5fe22570 fffff805`b82a31b4     : ffffa400`be68a180 ffffe385`8db1c480 fffff805`b808b720 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffffd82`5fe225c0 00000000`00000000     : fffffd82`5fe23000 fffffd82`5fe1c000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34


SYMBOL_NAME:  nt!KiFastFailDispatch+b2

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.26100.7462

STACK_COMMAND: .process /r /p 0xffffe3856056b040; .thread 0xffffe3858db1c480 ; kb

BUCKET_ID_FUNC_OFFSET:  b2

FAILURE_BUCKET_ID:  0x139_3_CORRUPT_LIST_ENTRY_nt!KiFastFailDispatch

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {3aede96a-54dd-40d6-d4cb-2a161a843851}

Followup:     MachineOwner
---------

Answer 1

The error code Kernel-Power 41 usually indicates a power-related issue, often caused by a sudden or unexpected system shutdown or restart. This can be due to hardware issues, particularly with the power supply or power management settings.

1). Check your Power Supply Unit (PSU), if possible try replacing it temporarily to rule out any issues with unstable power delivery.

2). Enter your BIOS/UEFI settings > Disable CPU power-saving features such as C-States > Save and reboot to check for stability.

More info: https://learn.microsoft.com/troubleshoot/windows-client/performance/event-id-41-restart

3). The dump file you shared does not point to a specific driver only generic errors. If there are any other minidump files available, please share them

Open File Explorer and navigate to: C:\Windows\Minidump

If you find any .dmp files, please zip them.

Upload the zipped file to Google Drive, OneDrive, Dropbox, or any file-sharing site.

Share the link here so I can analyze the files.

Once I have the minidumps, I'll review them to identify what might be causing the crashes.