Windows 10: BsoD and multiple restarts / crashes with 32gb DIMM 2x16

I recently purchased an upgrade 32GB Corsair Vengeance RGB Pro SL, 2x16, 3600MHz from a previous corsair vengeance pro 2x8.upon installation, the computer would not get past the DRAM test stage, with a solid orange light on the Mobo.as well as the motherboard sometimes although rarely, passing the POST then restarting itself 2 seconds later.I tested the memory modules individually, one on its own at first seemed to work, then subsequent tries would have the same issue.i then tested the modules in my old computer with an old motherboard and cpu and it worked fine.i have tried updating dr

:)

 

Random BSOD multiple stopcodes

The ram.txt from two days ago showed them in DIMM 0 and DIMM 1 which I believe equates to A1 and A2 in the manual. This is what the manual shows:

 

BSOD - "Whea Uncorrectable Error" and SSD/Windows not found after restart

Hello,

I am having a problem and have researched in several places, but I have not found a solution.

My computer is giving BSOD with the message " Whea Uncorrectable Error ", and it happens after hours or days of using the computer all of a sudden. Just when that happens, the computer automatically restarts and the message that Windows was not found (
suggesting pressing CTRL + ALT + DEL to restart). Upon entering the BIOS I see that the SSD is no longer in the list of devices.
It only reappears after I unplugged the computer for a few seconds.

What can this be, any problem with the SSD, Motherboard or Windows? My computer is less than 2 months old.

If that matters, the specifications are:

MSI Tomahawk B450

Ryzen 9 3900x

32Gb 3200mhz Xpg (2x16)

SSD Nvme SX8800 Pro Adata

Sapphire Nitro+ 5700 XT

Riotoro 650W 80+

 

Multiple BSOD

Bug Check 0x1A: MEMORY_MANAGEMENT

Bug Check 0x1A MEMORY_MANAGEMENT - Windows drivers | Microsoft Docs

MEMORY_MANAGEMENT BSODs, accompanied by occasional app crashes/GPUTDR.

MEMORY_MANAGEMENT BSODs, accompanied by occasional app crashes/GPUTDR.

The relevant Parameter appears to be 0x41284 which means, A PTE or the working set list is corrupted, which in itself means nothing to most of us poor Windows users. I still wonder if this is not just bad RAM?

Is it possible to remove one stick of RAM for testing purposes and then test all sticks one at a time (that's is you have multiple sticks of RAM, otherwise it is a daft suggestion on my part).