I checked the three dump files. They show:
0x1A MEMORY_MANAGEMENT with parameter 0x404, meaning an inconsistency was detected between the PFN and page-table data.
0xA IRQL_NOT_LESS_OR_EQUAL and 0x1E KMODE_EXCEPTION_NOT_HANDLED, both failing inside ntoskrnl.exe with invalid memory access.
ntoskrnl.exe is most likely where the corruption was detected, not the actual cause. No specific third-party driver is consistently identified. Together with PFN_LIST_CORRUPT and the different random stop codes, this strongly suggests memory corruption. Faulty RAM is the leading suspect, but unstable XMP/overclocking, the CPU memory controller or motherboard can cause the same symptoms. Microsoft’s explanation is here: https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x1a--memory-management
Enter BIOS, load the default settings and disable XMP/EXPO, CPU overclocking and undervolting. Update the BIOS from the computer or motherboard manufacturer.
Then test one RAM stick at a time in the same slot using MemTest86, allowing at least four complete passes: https://www.memtest86.com/
Any error is unacceptable. If one stick fails, replace it. If both pass separately but crashes return when installed together, suspect XMP compatibility, the motherboard or the CPU memory controller rather than Windows.