Multiple BSOD Crashes over the past year of owning a HP Victus 15-fb1000

[Knightranger]

Hello, I will be as precise as possible here. Over the past year or so, I have experienced numerous crashes and failures with this Victus which I purchased just over a year ago. 

Most common BSODs occurred while browsing, listening to music and working on a word processor. Nothing fancy. It would then cut out to a BSOD and restart. Occasionally this will take place during gaming but very rarely.

I have most of the dump files from this time which I can pass to support staff if needed

List of Bug Checks:
SYSTEM_SERVICE_EXCEPTION (3b)
IRQL_NOT_LESS_OR_EQUAL (a) (Very common)
FAULTY_HARDWARE_CORRUPTED_PAGE (12b) MemCompression (Very common)
MEMORY_MANAGEMENT (1a) (Very common)
IRQL_NOT_LESS_OR_EQUAL (0xA) 
DPC_WATCHDOG_VIOLATION (0x133) 
SYSTEM_SERVICE_EXCEPTION (0x3B)

My most recent crash was FAULTY_HARDWARE_CORRUPTED_PAGE (0x12B)

I have run all of the HP Diagnostics tests and have come up with the all clear every time. 
I have run the UEFI memory test and it was all clear
I have run the windows memory test and it gave me the all clear
I have run disk clean up
I have ran system repair via commands and also chkdsk
I also have ran SSD testing and that also came back fine

My instinct tells me that this is a RAM issue but I cannot detect it being faulty which is very weird. Despite there being so many error messages relating to memory

[betty098ar]

Hello,

You’re dealing with a classic case of "stealthy" hardware failure. Even though your tests are coming back clean, that specific combination of errors—especially the FAULTY_HARDWARE_CORRUPTED_PAGE involving memory compression is a massive red flag for a physical RAM defect that only triggers under specific voltages or heat levels during daily use. Standard Windows and UEFI tests are unfortunately notorious for missing these Verve Card intermittent faults because they don't stress the modules the same way an operating system does. Since you've already cleared the software side with system repairs and disk checks, I'd bet on a failing memory stick or a finicky motherboard slot. Your best bet now is to run a more rigorous, bootable test like MemTest86+ or try the "one-stick-at-a-time" method to see if you can isolate which module is causing the headache.

[Knightranger]

Thank you for the reply, I will attempt this as my next step. I have been trying to get a hold of HP Customer support and been left waiting for a long time on their chat. So, I will try this if they do not get back to me today

[Knightranger]

Memtest86 has come up completely clean. So I am going to try other methods