Well that's new (sort of)
Probably caused by : memory_corruption
Followup: memory_corruption
MODULE_NAME: memory_corruption
IMAGE_NAME: memory_corruption
FOLLOWUP_NAME: memory_corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MEMORY_CORRUPTOR: LARGE
STACK_COMMAND: .cxr 0xffff90017bdfd090 ; kb
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE
BUCKET_ID: MEMORY_CORRUPTION_LARGE
PRIMARY_PROBLEM_CLASS: MEMORY_CORRUPTION_LARGE
So, I'm still thinking memory although I wouldn't necessarily still dismiss a possible third party driver. You have several
npf.sys
speedfan.sys
vbaudio_vmvaio64_win7.sys
vbaudio_vmauxvaio64_win7.sys
LGJoyXlCore.sys
LGBusEnum.sys
CorsairVBusDriver.sys
CorsairVHidDriver.sys
lgcoretemp.sys
RTKVHD64.sys
rzendpt.sys
rzudd.sys
rzpnk.sys
rzpmgrk.sys
rt640x64.sys
CorsairGamingAudioamd64.sys
ladfGSS.sys
A couple of which are a little old. So....
to the extent possible you may want to consider addressing these in a manner or fashion so as to eliminate them from the diagnostic process. Update / Upgrade, uninstall or break them by renaming.
It is important to note that none of these are actually called out in the dump file or enumerated in any back trace, I've seen, so....
That leaves us with memory and perhaps
1. Confirm that you are not overclocking the installed memory, nor the installed video adapter.
2. Since, associated with the memory corruption issue, there is mention of
fffff802282fa17c-fffff802282fa17d 2 bytes - nt!MiInsertLargePageInNodeListHelper+4c
[ 80 fa:00 a6 ]
fffff802282fa998-fffff802282fa999 2 bytes - nt!RemoveListHeadPte+8c (+0x81c)
Both of which suggesting possible "pagefile" involvement, so.....
You may want to use a hard disk diagnostic utility to assess the system drive's health.
AND
IF it is an SSD, assure that you have the most recent manufacturer's firmware installed.