running a game.
debugger shows that the graphics driver did not process something
then when it went to clean up the memory it used a bad memory address (the number 20)
this is most likely going to be a bug in the graphics driver and you should just look for a updated version.
a memory address of 20 is more likely to be part of a memory header to indicate the size of a block.
valid memory address would look something like this
fffff807`00400a02
your driver was:
amdkmdag.sys Wed Nov 4 18:39:22 2020
it looks pretty up to date but look for a update anyway.
Also, this same bug can happen if another driver writes data over the top of memory locations that they no longer own.
this is also very common.
you also have this driver installed:
npf.sys Thu Feb 28 17:31:24 2013
it is a filter driver used with winpcap what does network packet injection
used to cheat at games, steel passwords and accounts and to look at network packets.
you did not seem to have winpcap installed.
it would be a suspect driver for this case.
this driver is known to corrupt memory
ScpVBus.sys Sun May 5 14:31:26 2013
normally you would not get this type of corruption.
this would also be another suspect driver (for corruption)
zamguard64.sys Wed Aug 17 10:06:53 2016
you can download the microsoft tool autoruns to show what drivers you have running
then disable a driver by unchecking it and rebooting. this can allow you test to find out what caused the problem
or you can just remove the drivers if you don't need them.
Autoruns for Windows - Windows Sysinternals | Microsoft Docs
you also have a overclock driver installed but you would never get this type of corruption but it could cause your hardware to miss a hardware event in the electronics. iocbios2.sys Thu May 28 13:42:10 2015
overall, i would remove any of these that you do not actively use. if you must have them then you would run verifier.exe and set the system to crash if a driver modifies data that it does not own. I would expect several of these drivers to crash the system if you used verifier.exe
if you do use verifier you must read up on it and be sure you turn off fastboot and know how to get into safe mode so you can run verifier /reset
to turn off verifier if you don't you can get into a fast bugcheck early in the boot process that some people just do not know how to get out of so they end up having to re install windows.