Help with BSOD

[pushingpop]

Having random BSOD since built my setup, sometimes occours 2-3 a day, sometime 1 month without BSOD. Already did memtest86, windows memtest, 0 errors

Minidump files: https://drive.google.com/drive/folders/1OrKqF5SIuzyXjpbSC1SgfuAPF4YIAH3c?usp=sharing

TUF Gaming A520m Plus Wifi
Ryzen 5 3600
2x8gb Crucial Ballistix BLS8G4D32AESEK.M8FE
2x8gb Crucial Ballistix BL8G32C16U4RL.M8FE1
MSI Mech 2x 6600xt
Corsair 550F
Win 11

Spoiler: Last Dump Text

TRAP_FRAME: fffff80373cf4f10 -- (.trap 0xfffff80373cf4f10)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00007fffffff0000 rbx=0000000000000000 rcx=00007fffffff0000
rdx=fffff80373cf5258 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80371e4bf03 rsp=fffff80373cf50a0 rbp=fffff80373cf56c0
r8=0000000000000010 r9=0000000000000000 r10=fffff80373cf51c0
r11=ffffde4f62600000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
nt!RtlpxVirtualUnwind+0x23a4e3:
fffff803`71e4bf03 0fb600 movzx eax,byte ptr [rax] ds:00007fff`ffff0000=??
Resetting default scope

STACK_TEXT:
fffff803`73cf4dc8 fffff803`71e3eaa9 : 00000000`0000000a 00007fff`ffff0000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff803`73cf4dd0 fffff803`71e3a134 : 00000000`00000000 fffff803`71ab45c0 fffff803`73cf51c0 ffffdf88`8e2ae168 : nt!KiBugCheckDispatch+0x69
fffff803`73cf4f10 fffff803`71e4bf03 : fffff803`73ce0400 fffff803`6c816180 00000000`00000001 fffff803`00000006 : nt!KiPageFault+0x474
fffff803`73cf50a0 fffff803`71c0faf5 : fffff803`73ce0400 fffff803`73ce01a8 00000000`00000010 00000000`00000000 : nt!RtlpxVirtualUnwind+0x23a4e3
fffff803`73cf5160 fffff803`71c13a17 : ffffffff`ffffffff fffff803`73ce0250 fffff803`73ce0250 fffff803`73cf5900 : nt!RtlDispatchException+0x215
fffff803`73cf58d0 fffff803`71e2a5c2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x317
fffff803`73cf5fb0 fffff803`71e2a590 : fffff803`71e3ebf5 ffff9488`78e21d90 00000000`00000003 ffff9488`78e21d90 : nt!KxExceptionDispatchOnExceptionStack+0x12
fffff803`73ce0068 fffff803`71e3ebf5 : ffff9488`78e21d90 00000000`00000003 ffff9488`78e21d90 fffff803`836538bf : nt!KiExceptionDispatchOnExceptionStackContinue
fffff803`73ce0070 fffff803`71e39c83 : fffff803`83651e90 fffff803`83659b88 ffff9488`6d654e30 fffff803`73ec1152 : nt!KiExceptionDispatch+0x135
fffff803`73ce0250 fffff803`71e6344c : 00009807`e7e8653c ffff9488`00000000 fffff803`6c816180 00000000`00000010 : nt!KiGeneralProtectionFault+0x343
fffff803`73ce03e8 00009807`e7e8653c : ffff9488`00000000 fffff803`6c816180 00000000`00000010 ffff9488`5cece000 : nt!KiHeteroComputeThreadWorkloadProperties+0xa8
fffff803`73ce03f0 ffff9488`00000000 : fffff803`6c816180 00000000`00000010 ffff9488`5cece000 ffff9488`5cdddd50 : 0x00009807`e7e8653c
fffff803`73ce03f8 fffff803`6c816180 : 00000000`00000010 ffff9488`5cece000 ffff9488`5cdddd50 00000000`00000320 : 0xffff9488`00000000
fffff803`73ce0400 00000000`00000010 : ffff9488`5cece000 ffff9488`5cdddd50 00000000`00000320 00000000`0000fdd4 : 0xfffff803`6c816180
fffff803`73ce0408 ffff9488`5cece000 : ffff9488`5cdddd50 00000000`00000320 00000000`0000fdd4 00000000`00000f44 : 0x10
fffff803`73ce0410 ffff9488`5cdddd50 : 00000000`00000320 00000000`0000fdd4 00000000`00000f44 00000000`0000001b : 0xffff9488`5cece000
fffff803`73ce0418 00000000`00000320 : 00000000`0000fdd4 00000000`00000f44 00000000`0000001b 00000002`00000000 : 0xffff9488`5cdddd50
fffff803`73ce0420 00000000`0000fdd4 : 00000000`00000f44 00000000`0000001b 00000002`00000000 00000000`05000000 : 0x320
fffff803`73ce0428 00000000`00000f44 : 00000000`0000001b 00000002`00000000 00000000`05000000 00000000`00000000 : 0xfdd4
fffff803`73ce0430 00000000`0000001b : 00000002`00000000 00000000`05000000 00000000`00000000 00000000`00000000 : 0xf44
fffff803`73ce0438 00000002`00000000 : 00000000`05000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x1b
fffff803`73ce0440 00000000`05000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00000002`00000000
fffff803`73ce0448 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x5000000

 

[Ralston18]

Look in Reliability History and Event Viewer.

Either one or both tools may be capturing some related error codes, warnings, or even informational events that occur just before or at the time of the BSODs.

Reliability History is much more user friendly and the timeline format may reveal some pattern.

Event Viewer requires more time and effort to navigate and understand.

To help:

How To - How to use Windows 10 Event Viewer | Tom's Hardware Forum (tomshardware.com)

= = = =

Also:

Power down, unplug, open the case.

Clean out dust and debris.

Verify by sight and feel that all connectors, cards, RAM, jumpers, and case connections are fully and firmly in place.

Use a bright flashlight to look for signs of damage: bare conductor showing, melting, cracks, loose or missing screws, pinched/kinked wires, corrosion, browned or blackened areas, swollen components, anything looking wet. etc..

 

[ubuysa]

The dumps are pretty clearly pointing at a hardware issue here. A couple of the bugchecks are rare and typically hardware; WINLOGON_FATAL_ERROR and HYPERVISOR_ERROR. The other two are common bugchecks that are usually a third-party driver; IRQL_NOT_LESS_OR_EQUAL and DPC_WATCHDOG_VIOLATION, but not only are there no third-party drivers on the call stacks, but both fail almost immediately the kernel is entered. All these factors very strongly point at hardware.

I don't know what the differences between the BLS8G4D32AESEK.M8FE and the BL8G32C16U4RL.M8FE1 are, but I'm not a fan of mixing RAM types. All RAM cards need to be in matched sets if you want stability. In addition, neither of those RAM models is on the QVL for that motherboard. That may or may not be significant, but it's not wise IMO.

I would remove one of the two pairs of RAM and see whether it's stable on one set, then swap over and test the other set. Just because Memtest says they're fine doesn't mean they will work on that board or together. And RAM is the single biggest cause of hardware BSODs.

 

[pushingpop]

Thank you for your reply, this BLS8G4D32AESEK.M8FE model are just a new model from BLS8G4D32AESEK.M8FE.

I already tried to put then separated and i still have freeze and/or BSOD

 

[ubuysa]

Have you tried it with just on graphics card? (I assume that 2 x 6600XT means two cards?).

I think it important to check the hardware, because that looks far more likely to be the source of the problem. I would suggest running Prime95 to stress both your CPU and RAM. This will cause your CPU to run hot, so you need a temperature monitor (like CoreTemp) to keep and eye on temperatures.

Run all three Prime95 tests (small FFTs, large FFTs, and Blend) for as long as you can. If Prime95 repoprts errors, if you get a BSOD or crash, or if the CPU temp rises to dangerous levels, stop the test and let us know what happened.

 

[pushingpop]

Have you tried it with just on graphics card? (I assume that 2 x 6600XT means two cards?).

I think it important to check the hardware, because that looks far more likely to be the source of the problem. I would suggest running Prime95 to stress both your CPU and RAM. This will cause your CPU to run hot, so you need a temperature monitor (like CoreTemp) to keep and eye on temperatures.

Run all three Prime95 tests (small FFTs, large FFTs, and Blend) for as long as you can. If Prime95 repoprts errors, if you get a BSOD or crash, or if the CPU temp rises to dangerous levels, stop the test and let us know what happened.

Msi Mech 2x is the model, i doubt its CPU temp because i have BSOD/Freeze on idle too.
I will run Prime95 tests and update this topic.

Thanks!

 

[ubuysa]

SOme CPUs become unstable at the lower power settings at idle. Please run Prime95 to be sure, you can't make assumptions.