Different BSOD when playing or closing games.

Solution
cpu was released Q3'12
your bios is dated april 2012
you should update the bios to the current version. since it might not have the correct default settings for your cpu. (cpu microcode updates would have overroad the bios but over time the updates might assume you have updated the bios and not provide the old updates)
(i do not see the windows intel microcode patch being loaded as a device driver, you should update the bios to get the CPU patches)
last update 10/31/2018
https://downloadcenter.intel.com/product/66983/Intel-Desktop-Board-DH61HO
-------------
zam64.sys Wed Aug 17 10:06:53 2016
zamguard64.sys Wed Aug 17 10:06:53 2016

if you are not using this you might want to remove.
-------------
windows maintains a list of what is...
cpu was released Q3'12
your bios is dated april 2012
you should update the bios to the current version. since it might not have the correct default settings for your cpu. (cpu microcode updates would have overroad the bios but over time the updates might assume you have updated the bios and not provide the old updates)
(i do not see the windows intel microcode patch being loaded as a device driver, you should update the bios to get the CPU patches)
last update 10/31/2018
https://downloadcenter.intel.com/product/66983/Intel-Desktop-Board-DH61HO
-------------
zam64.sys Wed Aug 17 10:06:53 2016
zamguard64.sys Wed Aug 17 10:06:53 2016

if you are not using this you might want to remove.
-------------
windows maintains a list of what is currently in memory (ram) and what is moved from ram to virtual memory (pagefile.sys) when something has not been used for some time the system will take it out of RAM but when it was working on this the list was not correct and it resulted in this bugcheck.

I would suspect some issue with this driver: (but I don't know)
UsbDk.sys Thu Apr 6 10:43:10 2017
this driver could mess up the list also:
SCSI Pass Through Direct Host - Daemon Tools
sptd2.sys Tue Feb 23 00:25:39 2016
(anything that is non standard for the storage driver would be suspect)

you might disable it or maybe run verifier to see if it is doing something incorrectly.
you should also change the memory dump to kernel so the proper debug info is saved so it can be debugged.
machine info:
Vendor Intel Corp.
BIOS Version HOH6110H.86A.0010.2012.0424.1632
BIOS Starting Address Segment f000
BIOS Release Date 04/24/2012
Product DH61HO
Version AAG62445-102
Processor Version Intel(R) Core(TM) i3-3220 CPU @ 3.30GHz
Processor Voltage 80h - 0.0V
External Clock 100MHz
Max Speed 3800MHz
Current Speed 3300MHz

 
Solution


The 2 drivers you pointed out were not even working. Uninstalling both seems to have fixed the issue, for now at least. My motherboard is fairly old (built when Vista was the latest Windows) and I couldn't find any newer bios updates.

I'll come back to this thread if the problem comes back.

Many thanks for your help!