heap corruption problems can be hard to find, and take some time to reproduce.
often you will find that if you just reboot your system at the end of the day you will not hit the problem.
I would also disable your overclock driver and the gpu overclock access tool. gamingosd.exe
until you figure out the problem.
I will take a quick look at the memory dumps to see if I can get a good guess as to the type of corruption and likely cause.
first bugcheck looks like a buffer overflow. that would most likely be a programming mistake. error was detected at cleanup, so you don't know who caused the error, just the name of the process that was the victim.
second one looks like a driver corrupted memory and memory manager access something that should have been in memory was the info was corrupted and it tried to read it in from a pagefile and got a error object not found.
third was a bad stack pointer in a new thread in your game.
i would focus on the first two bugchecks. ie remove the overclock driver, the asus gamingosd.exe and see if you still bugcheck.
your NT kernel also looks like it has 4 changes from what it should be.
After I removed the various software for overclocking. I would start cmd.exe as an admin then run
dism.exe /online /cleanup-image /restorehealth
and see if will repair your windows install.
some old tools for windows 7 hack in to the kernel so they can reroute functions , this is no longer allowed but it is still done sometimes,
google for autoruns and download if from microsoft, you can use it to see if you have something in startup that might be changing the kernel, you can also look in task scheduler to see if asus has scheduled a task to reinstall their tools. for the case where tools come back after you have removed them.