Question Windows 11 suddenly turns off or blue screens --- minidump file is attached ?

[MzKay]

Hi
I've had some issues with my desktop pc lately.
I've tried to use windows 10 and 11 on the desktop and the blue screens keep coming back.
This makes me think that i might have some faulty hardware.
System:
AMD Ryzen 7 7800X3D
Geforce RTX Strix 3070ti OC
G.Skill Trident Z5 NEO DDR5 6400mhz 32GB
ASUS TUF Gaming B650-PLUS WIFI Motherboard
Corsair RM850x, 850W PSU
For Storage i use 1 NVME Samsung 970 1tb and 2 Samsung 850 500gb SSD
I don't use any CPU overclocking, but i do have my RAM overclocked to run at about 6000-6200mhz, I've tried changing the voltage to make sure that this was not the problem.


Edit: The pc chrashing, mostly happens when i playing games. And trying to force the error to appear doesn't work. I've tried using OCCT to test my powersupply and CPU + Ram, but there are no problems when stress testing with OCCT or any other 3d Benchmark testers that I've tried.


Shown here is the Minidump file, please help me understand what is going on, and what i can do with this information.
(Also looking through the file it says OSNAME: Windows 10, yet i am on Windows 11)
5: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: ffffce9421692be8, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80064b26156, address which referenced memory

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 1483

Key : Analysis.Elapsed.mSec
Value: 12859

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

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

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

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

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

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

Key : Bugcheck.Code.LegacyAPI
Value: 0xa

Key : Bugcheck.Code.TargetModel
Value: 0xa

Key : Failure.Bucket
Value: AV_nt!MiAgePte

Key : Failure.Hash
Value: {d9f7a3dd-46b3-6667-1ab7-7828f3f62d30}

Key : Hypervisor.Enlightenments.ValueHex
Value: 1497cf94

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

Key : Hypervisor.Flags.ValueHex
Value: 4a10ef

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: 3f7

Key : WER.OS.Branch
Value: ni_release

Key : WER.OS.Version
Value: 10.0.22621.1


BUGCHECK_CODE: a

BUGCHECK_P1: ffffce9421692be8

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff80064b26156

FILE_IN_CAB: 082424-15265-01.dmp

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


FAULTING_THREAD: ffffb48a372dc040

READ_ADDRESS: fffff8006551c470: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
ffffce9421692be8

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: RocketLeague.exe

TRAP_FRAME: fffff88543659720 -- (.trap 0xfffff88543659720)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffb48a52541b20 rbx=0000000000000000 rcx=ffff953fff37cb08
rdx=ffff954aa552a7f8 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80064b26156 rsp=fffff885436598b0 rbp=ffffce9421692bc0
r8=ffffb48a52541b20 r9=000000000000000e r10=0000fffff80064b2
r11=ffff897955000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!MiAgePte+0xf6:
fffff800`64b26156 480fba652828 bt qword ptr [rbp+28h],28h ss:0018:ffffce94`21692be8=????????????????
Resetting default scope

STACK_TEXT:
fffff885`436595d8 fffff800`64c2bc29 : 00000000`0000000a ffffce94`21692be8 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff885`436595e0 fffff800`64c27089 : 1a000002`a6a20867 1a000002`a6a20867 ffff953e`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff885`43659720 fffff800`64b26156 : 00000000`00000000 ffffc700`075829e0 00000000`00000000 00000000`00000003 : nt!KiPageFault+0x489
fffff885`436598b0 fffff800`64a233c6 : fffff885`43659e10 fffff885`43659e10 fffff885`43659e10 00000000`00000000 : nt!MiAgePte+0xf6
fffff885`43659950 fffff800`64a2378a : fffff885`00000000 ffffb48a`6dd8d840 ffff954a`00000000 fffff885`43659e60 : nt!MiWalkPageTablesRecursively+0x266
fffff885`436599e0 fffff800`64a2378a : fffff885`00000000 ffffb48a`6dd8d840 ffff954a`00000000 fffff885`43659e70 : nt!MiWalkPageTablesRecursively+0x62a
fffff885`43659a70 fffff800`64a2378a : fffff885`43659e10 ffffb48a`6dd8d840 ffff954a`00000000 fffff885`43659e80 : nt!MiWalkPageTablesRecursively+0x62a
fffff885`43659b00 fffff800`64a23061 : fffff885`00000000 ffffb48a`6dd8d840 00000000`00000000 fffff885`43659e90 : nt!MiWalkPageTablesRecursively+0x62a
fffff885`43659b90 fffff800`64a24abc : fffff885`43659e10 fffff885`00000002 ffffb48a`00000002 00000000`00000000 : nt!MiWalkPageTables+0x371
fffff885`43659c90 fffff800`64a246a5 : 00000000`00000000 00000000`00000000 ffffb48a`6dd8d840 fffff800`64b5ff83 : nt!MiAgeWorkingSet+0x21c
fffff885`4365a190 fffff800`64b5f9c9 : fffff885`4365a310 ffffb48a`6dd8d840 00000000`00000000 ffffb48a`6dd8d8f8 : nt!MiTrimOrAgeWorkingSet+0xd5
fffff885`4365a210 fffff800`64b617ac : 00000000`00000000 fffff800`6546afc0 fffff800`6546afc0 ffffb48a`3705c360 : nt!MiProcessWorkingSets+0x319
fffff885`4365a3c0 fffff800`64b90d40 : 00000000`00000001 00000000`00000001 00000000`ffffffff fffff800`64b90bf0 : nt!MiWorkingSetManager+0x12c
fffff885`4365a480 fffff800`64b54d07 : ffffb48a`372dc040 00000000`00000080 fffff800`6546afc0 00000000`00000000 : nt!KeBalanceSetManager+0x150
fffff885`4365a570 fffff800`64c1ae24 : fffff800`61acd180 ffffb48a`372dc040 fffff800`64b54cb0 00000000`00000000 : nt!PspSystemThreadStartup+0x57
fffff885`4365a5c0 00000000`00000000 : fffff885`4365b000 fffff885`43654000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34


SYMBOL_NAME: nt!MiAgePte+f6

MODULE_NAME: nt

IMAGE_VERSION: 10.0.22621.4036

STACK_COMMAND: .process /r /p 0xffffb48a371bf040; .thread 0xffffb48a372dc040 ; kb

IMAGE_NAME: ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET: f6

FAILURE_BUCKET_ID: AV_nt!MiAgePte

OS_VERSION: 10.0.22621.1

BUILDLAB_STR: ni_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {d9f7a3dd-46b3-6667-1ab7-7828f3f62d30}

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

 

[MzKay]

Ive also got the Reliability Monitor screenshots if they can help in any way

https://imgur.com/GGauKzK

View: https://imgur.com/GGauKzK

https://imgur.com/tsPGE70

View: https://imgur.com/tsPGE70

https://imgur.com/6x0eXOc

View: https://imgur.com/6x0eXOc

https://imgur.com/PIXmqXN

View: https://imgur.com/PIXmqXN

 

[lantis3]

See if bluescreenview helps

 

[ubuysa]

You may be overclocking your RAM too far. If you look at the spec for your Ryzen 7 7800X3D you'll see that the maximum DDR5 RAM speed it supports is 5200 MT/s (MHz in DDR). This is the maximum speed that AMD warranty the CPU will accept, many (most) CPUs will happily accept RAM transfer rates higher than this, but 5200 MT/s is as fast as AMD guarantee.

The location of the BSOD in the analyze -v output you posted shows that the error happened whilst managing a PTE (A Page Table Entry) and this is very much RAM related.

What I suggest you do first is remove the RAM overclock and run it at the SPD speed of 4800 MHz. If the system is stable at that speed then overclock it to 5200 MHz and see whether it's stable there. If it is then it's working as designed.

If it still BSODs with no RAM overclock then can you please download the SysnativeBSODCollectionApp and save it to the Desktop. Then run it and upload the resulting zip file to a cloud service with a link to it here. The SysnativeBSODCollectionApp collects all the troubleshooting data we're likely to need. It DOES NOT collect any personally identifying data. It's used by several highly respected Windows help forums (including this one). I'm a senior BSOD analyst on the Sysnative forum where this tool came from, so I know it to be safe.

You can of course look at what's in the zip file before you upload it, most of the files are txt files. Please don't change or delete anything though. If you want a description of what each file contains you'll find that here.