What can be the root cause of crashes with my clean installation of windows 11?

Question

What can be the root cause of crashes with my clean installation of windows 11?

Artur Kulsh 20

Greetings,

I have had issues with Windows 11 culminating in having to do a clean re-installation of it. However, even after clean installation the problems continue to persist and I would like to ask someone to help and find the root cause to them if possible.

Steps undertaken:

Installed all necessary and recommended Windows updates. Installed hardware manufacturer software to update manufacturer's drivers to the current version.
SFC and DISM checks performed with no integrity volations found
MEMCHECK and DSKCHK /r /f performed with no issues found

Reliability Monitor usually doesn't show any errors except "Windows Closed unexpectedly", however most recent point of failure included hardware issues.

Minidump files point to kernel level files so I assume it is something with faulty hardware or drivers.

Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Artur Kulsh 20

Crash 1:

ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY (fc)
An attempt was made to execute non-executable memory.  The guilty driver
is on the stack trace (and is typically the current instruction pointer).
When possible, the guilty driver's name is printed on
the BugCheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: fffff305374bed99, Virtual address for the attempted execute.
Arg2: 8a000007aa45d863, PTE contents.
Arg3: fffff305374beac0, (reserved)
Arg4: 0000000000000000, (reserved)

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1234

    Key  : Analysis.Elapsed.mSec
    Value: 1332

    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: 687

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

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

    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: 0xfc

    Key  : Bugcheck.Code.TargetModel
    Value: 0xfc

    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  : Failure.Bucket
    Value: 0xFC_nt!MiCheckSystemNxFault

    Key  : Failure.Hash
    Value: {a6ae5288-6b71-974a-9b09-23f14d998164}

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 0x7417df84

    Key  : Hypervisor.Flags.AnyHypervisorPresent
    Value: 1

    Key  : Hypervisor.Flags.ApicEnlightened
    Value: 0

    Key  : Hypervisor.Flags.ApicVirtualizationAvailable
    Value: 1

    Key  : Hypervisor.Flags.AsyncMemoryHint
    Value: 0

    Key  : Hypervisor.Flags.CoreSchedulerRequested
    Value: 0

    Key  : Hypervisor.Flags.CpuManager
    Value: 1

    Key  : Hypervisor.Flags.DeprecateAutoEoi
    Value: 1

    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: 55185662

    Key  : Hypervisor.Flags.ValueHex
    Value: 0x34a10fe

    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.19.0.0


BUGCHECK_CODE:  fc

BUGCHECK_P1: fffff305374bed99

BUGCHECK_P2: 8a000007aa45d863

BUGCHECK_P3: fffff305374beac0

BUGCHECK_P4: 0

FILE_IN_CAB:  121425-10296-01.dmp

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


DUMP_FILE_ATTRIBUTES: 0x21808
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffffa405cb6f2080

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1 (!blackboxwinlogon)


CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  Discord.exe

STACK_TEXT:  
fffff305`374be8c8 fffff807`87a9df23     : 00000000`000000fc fffff305`374bed99 8a000007`aa45d863 fffff305`374beac0 : nt!KeBugCheckEx
fffff305`374be8d0 fffff807`87982527     : 00000000`00000003 00000000`00000001 fffff305`374bed99 fffff305`374be990 : nt!MiCheckSystemNxFault+0x3f
fffff305`374be910 fffff807`87952e70     : 00000000`00000011 fffff305`374bea50 fffff305`374bed99 00000000`00000000 : nt!MiRaisedIrqlFault+0x24f
fffff305`374be950 fffff807`87cb11cb     : ffffc881`2c80a640 ffffc881`2c800000 00000000`00000000 00000000`00000000 : nt!MmAccessFault+0x370
fffff305`374beac0 fffff305`374bed99     : ffffa405`cb820080 ffffa405`b11002c0 ffffa405`b11002c0 00000000`00000002 : nt!KiPageFault+0x38b
fffff305`374bec58 ffffa405`cb820080     : ffffa405`b11002c0 ffffa405`b11002c0 00000000`00000002 00000000`00000001 : 0xfffff305`374bed99
fffff305`374bec60 ffffa405`b11002c0     : ffffa405`b11002c0 00000000`00000002 00000000`00000001 fffff305`374bec80 : 0xffffa405`cb820080
fffff305`374bec68 ffffa405`b11002c0     : 00000000`00000002 00000000`00000001 fffff305`374bec80 fffff305`374bec80 : 0xffffa405`b11002c0
fffff305`374bec70 00000000`00000002     : 00000000`00000001 fffff305`374bec80 fffff305`374bec80 00000000`00000000 : 0xffffa405`b11002c0
fffff305`374bec78 00000000`00000001     : fffff305`374bec80 fffff305`374bec80 00000000`00000000 ffffa405`b1107388 : 0x2
fffff305`374bec80 fffff305`374bec80     : fffff305`374bec80 00000000`00000000 ffffa405`b1107388 00000000`00000000 : 0x1
fffff305`374bec88 fffff305`374bec80     : 00000000`00000000 ffffa405`b1107388 00000000`00000000 00000000`00000000 : 0xfffff305`374bec80
fffff305`374bec90 00000000`00000000     : ffffa405`b1107388 00000000`00000000 00000000`00000000 ffffa405`b1107380 : 0xfffff305`374bec80


SYMBOL_NAME:  nt!MiCheckSystemNxFault+3f

MODULE_NAME: nt

IMAGE_VERSION:  10.0.26100.7462

STACK_COMMAND: .process /r /p 0xffffa405cb378080; .thread 0xffffa405cb6f2080 ; kb

IMAGE_NAME:  ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET:  3f

FAILURE_BUCKET_ID:  0xFC_nt!MiCheckSystemNxFault

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {a6ae5288-6b71-974a-9b09-23f14d998164}

Followup:     MachineOwner

Artur Kulsh 20

Crash 2:

VIDEO_MEMORY_MANAGEMENT_INTERNAL (10e)
The video memory manager encountered a condition that it can't recover from. By crashing,
the video memory manager is attempting to get enough information into the minidump such that
somebody can pinpoint what lead to this condition.
Arguments:
Arg1: 0000000000000034, The subtype of the BugCheck:
Arg2: 0000000000000003
Arg3: 0000000000000001
Arg4: 0000000000000000

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1125

    Key  : Analysis.Elapsed.mSec
    Value: 1126

    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: 750

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

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

    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: 0x10e

    Key  : Bugcheck.Code.TargetModel
    Value: 0x10e

    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  : Failure.Bucket
    Value: 0x10e_34_dxgmms2!VIDMM_RECYCLE_RANGE::Unlock

    Key  : Failure.Hash
    Value: {c64bc782-c794-c0e3-7808-887e357b0df3}

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 0x7417df84

    Key  : Hypervisor.Flags.AnyHypervisorPresent
    Value: 1

    Key  : Hypervisor.Flags.ApicEnlightened
    Value: 0

    Key  : Hypervisor.Flags.ApicVirtualizationAvailable
    Value: 1

    Key  : Hypervisor.Flags.AsyncMemoryHint
    Value: 0

    Key  : Hypervisor.Flags.CoreSchedulerRequested
    Value: 0

    Key  : Hypervisor.Flags.CpuManager
    Value: 1

    Key  : Hypervisor.Flags.DeprecateAutoEoi
    Value: 1

    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: 55185662

    Key  : Hypervisor.Flags.ValueHex
    Value: 0x34a10fe

    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.19.0.0


BUGCHECK_CODE:  10e

BUGCHECK_P1: 34

BUGCHECK_P2: 3

BUGCHECK_P3: 1

BUGCHECK_P4: 0

FILE_IN_CAB:  121425-41062-01.dmp

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


DUMP_FILE_ATTRIBUTES: 0x21808
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffffe503ba74b180

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1 (!blackboxwinlogon)


CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:  
ffffbd0a`9b786dc8 fffff807`7cb11316     : 00000000`0000010e 00000000`00000034 00000000`00000003 00000000`00000001 : nt!KeBugCheckEx
ffffbd0a`9b786dd0 fffff807`9def3ae6     : ffffe503`ba603800 ffffd506`42aaf240 00000000`00020000 00000000`00000000 : watchdog!WdLogSingleEntry5+0x156
ffffbd0a`9b786e60 fffff807`9dec67c3     : 00000000`00020000 ffffd506`275176b0 00000000`00020000 ffffe503`ba7cb720 : dxgmms2!VIDMM_RECYCLE_RANGE::Unlock+0x22e
ffffbd0a`9b786ea0 fffff807`9dee54b1     : 00000002`cb440938 ffffd506`1a826101 ffffd506`42cc6120 ffffd506`165d6000 : dxgmms2!VIDMM_RECYCLE_HEAP_MGR::UnlockHeapAllocation+0x83
ffffbd0a`9b786f10 fffff807`9dea9850     : ffffd506`42cc6120 ffffd506`1a826140 ffffe503`ba7ca000 00000000`00000000 : dxgmms2!VIDMM_GLOBAL::UnlockAllocation+0xb5
ffffbd0a`9b786f90 fffff807`9dea9b02     : ffffd506`42cc6120 ffffe503`ba0bcb00 ffffe503`ba0bcb00 ffffe503`ba0bcb00 : dxgmms2!VIDMM_SEGMENT::UnlockAllocationBackingStore+0xcc
ffffbd0a`9b786fd0 fffff807`9debb90d     : ffffd506`42cc6120 ffffbd0a`9b787090 ffffe503`ba0bcb00 fffff807`eaed4e59 : dxgmms2!VIDMM_SYSMEM_SEGMENT::EvictResource+0xb2
ffffbd0a`9b787020 fffff807`9dedcaaf     : 00000000`00000004 ffffd506`42cc6120 ffffd506`42cc6100 ffffe503`d1081700 : dxgmms2!VIDMM_PHYSICAL_ADAPTER::EvictResources+0x275
ffffbd0a`9b7870d0 fffff807`9dedc18b     : 00000000`00000000 fffff807`eaed3702 00000000`00000000 00000000`00000000 : dxgmms2!VIDMM_GLOBAL::ProcessDeferredCommand+0x8fb
ffffbd0a`9b7872d0 fffff807`9def26af     : 00000000`00000000 00000000`00000000 ffffbd0a`9b787449 00000000`00000000 : dxgmms2!VidMmProcessPendingTerminations+0x97
ffffbd0a`9b787390 fffff807`eb08b77a     : ffffe503`ba74b100 fffff807`9def1700 ffff9880`475e1100 025fa46f`b19bbf02 : dxgmms2!VidMmWorkerThreadProc+0xf5f
ffffbd0a`9b7874b0 fffff807`eb2a31b4     : ffff9880`475e1180 ffffe503`ba74b180 fffff807`eb08b720 15ff4800`000001b9 : nt!PspSystemThreadStartup+0x5a
ffffbd0a`9b787500 00000000`00000000     : ffffbd0a`9b788000 ffffbd0a`9b781000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34


SYMBOL_NAME:  dxgmms2!VIDMM_RECYCLE_RANGE::Unlock+22e

MODULE_NAME: dxgmms2

IMAGE_NAME:  dxgmms2.sys

IMAGE_VERSION:  10.0.26100.7462

STACK_COMMAND: .process /r /p 0xffffe503a94d7040; .thread 0xffffe503ba74b180 ; kb

BUCKET_ID_FUNC_OFFSET:  22e

FAILURE_BUCKET_ID:  0x10e_34_dxgmms2!VIDMM_RECYCLE_RANGE::Unlock

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {c64bc782-c794-c0e3-7808-887e357b0df3}

Followup:     MachineOwner

Answer accepted by question author

DaveM121 946.1K Independent Advisor

System crashes should no survive re-installing Windows using a bootable USB, that usually indicates an underlying hardware fault.

Your second minidump file indicates the dedicated graphics card drivers caused that crash, the first one only indicates generic errors.

Open Device Manager, then expand the Display Adapters section, please provide a screenshot of that full window.

Artur Kulsh 20 Reputation points

2025-12-14T13:19:33.9866667+00:00

Hi Dave,

Thank you for the fast response. Screenshot is attached. Both Nvidia card and Intel integrated card have the most recent drivers, installed after the DDU wipe:
DaveM121 946.1K Reputation points Independent Advisor

2025-12-14T13:25:37.9133333+00:00

Thank you for that information, the best option is to use DDU again in Safe Mode to remove the Nvidia drivers, then go to the Nvidia website to download a couple of slightly older versions of the drivers Nvidia provide around version 572, to try to find a version of the driver that stabilizes your system.
Artur Kulsh 20 Reputation points

2025-12-14T13:27:24.71+00:00

Thank you, I will monitor the system closely for a couple of days after I do that. If that stabilizes things I will consider your answer successfully solving the problem.

Cheers and have a fantastic day!
DaveM121 946.1K Reputation points Independent Advisor

2025-12-14T13:29:22.15+00:00

Glad to help!
Artur Kulsh 20 Reputation points

2025-12-14T15:47:31.2433333+00:00

A few hours later the machine suffered a catastrophic failure and is unable to boot. As such, this points to the hardware issues. I will close this question as solved by Dave and will work on replacing the faulty parts.

1 additional answer

Your answer

Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Artur Kulsh 20 Reputation points

2025-12-14T13:19:33.9866667+00:00

Hi Dave,

Thank you for the fast response. Screenshot is attached. Both Nvidia card and Intel integrated card have the most recent drivers, installed after the DDU wipe:
DaveM121 946.1K Reputation points Independent Advisor

2025-12-14T13:25:37.9133333+00:00

Thank you for that information, the best option is to use DDU again in Safe Mode to remove the Nvidia drivers, then go to the Nvidia website to download a couple of slightly older versions of the drivers Nvidia provide around version 572, to try to find a version of the driver that stabilizes your system.
Artur Kulsh 20 Reputation points

2025-12-14T13:27:24.71+00:00

Thank you, I will monitor the system closely for a couple of days after I do that. If that stabilizes things I will consider your answer successfully solving the problem.

Cheers and have a fantastic day!
DaveM121 946.1K Reputation points Independent Advisor

2025-12-14T13:29:22.15+00:00

Glad to help!
Artur Kulsh 20 Reputation points

2025-12-14T15:47:31.2433333+00:00

A few hours later the machine suffered a catastrophic failure and is unable to boot. As such, this points to the hardware issues. I will close this question as solved by Dave and will work on replacing the faulty parts.

Answer 1

The root cause of crashes in a clean installation of Windows 11 can be attributed to several factors, even after performing updates and checks. Here are some potential causes:

Faulty Hardware: Despite running diagnostics like MEMCHECK and DSKCHK, some hardware components may still be faulty. This includes RAM, hard drives, or other peripherals that might not have been detected during standard checks.
Driver Issues: Even with updated drivers, there could be compatibility issues with specific hardware or software. Third-party drivers are often a significant cause of system crashes, as they may not be fully compatible with Windows 11.
Kernel-Level Problems: Since your minidump files point to kernel-level files, this indicates that the issue may lie within the core components of the operating system or drivers interacting with the kernel. This could be due to outdated or corrupted kernel drivers.
Software Conflicts: Sometimes, installed software can conflict with system processes, leading to unexpected crashes. This is especially true for software that operates at a low level, such as antivirus programs or system utilities.
BIOS/Firmware Issues: Outdated BIOS or firmware can lead to compatibility issues with the operating system. Ensuring that your system's BIOS is up to date can sometimes resolve these types of problems.
Corrupted System Files: Although SFC and DISM checks did not find integrity violations, there could still be underlying issues that were not detected. Running these tools multiple times or in different configurations may yield different results.
Insufficient Resources: Ensure that your system has adequate resources (CPU, RAM, disk space) to run Windows 11 smoothly. Insufficient resources can lead to performance issues and crashes.

Given these possibilities, it may be beneficial to systematically test hardware components, review driver compatibility, and monitor system performance to identify the root cause of the crashes.

References: