ASRock B650M Pro RS frequent blue screen (BSOD)

Hi, my new PC is giving a lot of windows BSOD: "WINDOWS FAULTY HARDWARE CORRUPTED PAGE". According to my research it could be related to some faulty drivers having memory leaks.

I did an SFC /scannow, it found and corrected a problem. For a week the PC worked fine, but now it bluescreened again.

Speaking of hardware and drivers, I noticed that the USB-C port at the back of the motherboard doesn't work, could it be related?

If I don't manage to solve the problem I'll have to RMA the motherboard.

I'll past a memory dump analysis after the specs, let me know if you need the whole dump file (1.5GB), I can send the link privately to you.

Thanks.


System specs:

CPU Ryzen 5 7600
100-100001015BOX

MB ASRock B650M Pro RS - UEFI BIOS 2.01
90-MXBLP0-A0UAYZ

RAM G.Skill Trident Z5 Neo DDR5 32GB (2x16) 6000MHz CL30
F5-6000J3038F16GX2-TZ5N

SSD M.2 Western Digital Black SN850X 2 TB
WDS200T2X0E

GPU nvidia RTX 3060
GV-N3060VISION OC-12GD 2.0

PSU Cooler Master MWE Bronze 550
MPX-5501-ACAAB

Windows:
Windows 10 Pro
Version     22H2
Install date:     ??1/??1/??023
OS Build      19045.3693
Windows Feature Experience Pack 1000.19053.1000.0


MEMORY DUMP ANALYSIS:

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


Loading Dump File [E:\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff807`2a000000 PsLoadedModuleList = 0xfffff807`2ac2a6d0
Debug session time: Wed Nov 22 15:12:34.434 2023 (UTC + 1:00)
System Uptime: 0 days 8:00:56.130
Loading Kernel Symbols
...............................................................
.................Page 80d447 not present in the dump file. Type ".hh dbgerr004" for details
...............................................
................................................................
...............
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000000`00202018). Type ".hh dbgerr001" for details
Loading unloaded module list
..........
For analysis of this file, run !analyze -v
3: 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: 00000003671ab8d0, 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: fffff8072a3f6382, address which referenced memory

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


KEY_VALUES_STRING: 1

    Key : Analysis.CPU.mSec
    Value: 2311

    Key : Analysis.DebugAnalysisManager
    Value: Create

    Key : Analysis.Elapsed.mSec
    Value: 2588

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

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

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

    Key : WER.OS.Branch
    Value: vb_release

    Key : WER.OS.Timestamp
    Value: 2019-12-06T14:06:00Z

    Key : WER.OS.Version
    Value: 10.0.19041.1


FILE_IN_CAB: MEMORY.DMP

BUGCHECK_CODE: a

BUGCHECK_P1: 3671ab8d0

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff8072a3f6382

READ_ADDRESS: 00000003671ab8d0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME: JustCause3.exe

TRAP_FRAME: fffffd8ae22debc0 -- (.trap 0xfffffd8ae22debc0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000006196b02 rbx=0000000000000000 rcx=00000003671ab8c0
rdx=00000000e22deebf rsi=0000000000000000 rdi=0000000000000000
rip=fffff8072a3f6382 rsp=fffffd8ae22ded50 rbp=00000000e22deebf
r8=0000000000000001 r9=0000000000222db2 r10=0000000000c00000
r11=fffffd8ae22dedd8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0        nv up ei ng nz na po nc
nt!MiGetFreeZeroLargePages+0x52:
fffff807`2a3f6382 488b4910        mov     rcx,qword ptr [rcx+10h] ds:00000003`671ab8d0=????????????????
Resetting default scope

STACK_TEXT:
fffffd8a`e22dea78 fffff807`2a411729     : 00000000`0000000a 00000003`671ab8d0 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffffd8a`e22dea80 fffff807`2a40d2e3     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffffd8a`e22debc0 fffff807`2a3f6382     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x463
fffffd8a`e22ded50 fffff807`2a2da12e     : 5c4e1000`00000000 000000ff`ff968f03 00000000`00000000 00000000`00000000 : nt!MiGetFreeZeroLargePages+0x52
fffffd8a`e22dede0 fffff807`2ac50c00     : ffff968f`13739490 00000000`005c3f5a ffffd70b`fb01a948 968f035c`4e100420 : nt!MiGetLargePage+0xc2
fffffd8a`e22def30 ffff968f`13739490     : 00000000`005c3f5a ffffd70b`fb01a948 968f035c`4e100420 ffffea80`06196b00 : nt!MiSystemPartition
fffffd8a`e22def38 00000000`005c3f5a     : ffffd70b`fb01a948 968f035c`4e100420 ffffea80`06196b00 ffff968f`035c4e10 : 0xffff968f`13739490
fffffd8a`e22def40 ffffd70b`fb01a948     : 968f035c`4e100420 ffffea80`06196b00 ffff968f`035c4e10 fffffd8a`e22df039 : 0x5c3f5a
fffffd8a`e22def48 968f035c`4e100420     : ffffea80`06196b00 ffff968f`035c4e10 fffffd8a`e22df039 fffff807`2a26d278 : 0xffffd70b`fb01a948
fffffd8a`e22def50 ffffea80`06196b00     : ffff968f`035c4e10 fffffd8a`e22df039 fffff807`2a26d278 ffff968f`13739490 : 0x968f035c`4e100420
fffffd8a`e22def58 ffff968f`035c4e10     : fffffd8a`e22df039 fffff807`2a26d278 ffff968f`13739490 fffffd8a`00000000 : 0xffffea80`06196b00
fffffd8a`e22def60 fffffd8a`e22df039     : fffff807`2a26d278 ffff968f`13739490 fffffd8a`00000000 ffffd70b`fb01a948 : 0xffff968f`035c4e10
fffffd8a`e22def68 fffff807`2a26d278     : ffff968f`13739490 fffffd8a`00000000 ffffd70b`fb01a948 fffffd8a`e22df480 : 0xfffffd8a`e22df039
fffffd8a`e22def70 fffff807`2a22dc65     : fffffd8a`e22df200 ffffd70b`fb01a948 ffffea80`06196b00 fffffd8a`e22df1e0 : nt!MiResolveMappedFileFault+0x378
fffffd8a`e22df0a0 fffff807`2a2264a5     : fffffd8a`e22df200 00000000`00000000 fffffd8a`e22df1e0 ffff968f`0f70c700 : nt!MiResolveProtoPteFault+0x1205
fffffd8a`e22df1a0 fffff807`2a2243e9     : 00000000`3bff5d55 00000000`00000007 00000000`c0000016 ffffd70b`fb01a948 : nt!MiDispatchFault+0x3d5
fffffd8a`e22df2e0 fffff807`2a40d1d8     : ffff968f`13375640 00000002`ed9b7238 00000000`00000000 00000000`00000001 : nt!MmAccessFault+0x189
fffffd8a`e22df480 00007fff`dece2c91     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x358
00000001`126fe460 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fff`dece2c91


SYMBOL_NAME: nt!MiGetFreeZeroLargePages+52

MODULE_NAME: nt

STACK_COMMAND: .cxr; .ecxr ; kb

IMAGE_NAME: ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET: 52

FAILURE_BUCKET_ID: AV_nt!MiGetFreeZeroLargePages

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {186f18c5-5f7c-784d-6f92-519f63a812f6}

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