32 bit subsystem just indicated a bad cpu instruction pointer. it just started running code that was outside any loaded modules.
instruction pointer was inside of a heap address.
which would make me guess it is related to this file:
C:\Windows\System32\msacm32.drv being not loaded at the default address.
Maybe a tool just assumed the old load address and made a call, that might be something this tool would do:
(overwolf)
So I would disable the overwolf drivers
(bad form to put these in a hidden directory anyway)
C:\Users\Davy\AppData\Local\Overwolf\Extensions\ncfplpkmiejjaklknfnkgcpapnhkggmlcppckhcb\196.0.2\obs\data\obs-plugins\win-capture\ow-graphics-hook64.dll Tue Mar 8 11:51:36 2022
C:\Program Files (x86)\Overwolf\0.195.0.18\ow-graphics-vulkan.dll Tue Nov 23 05:46:13 2021
reboot and re-test for failure.
=============================
there might be some issue with the
InternalName: Microsoft ACM Audio Filter
with the driver version not matching the .dll version
Image path: C:\Windows\System32\msacm32.dll
ProductVersion: 10.0.19041.1001
Image path: C:\Windows\System32\msacm32.drv
File version: 10.0.19041.488
i only mention it because the loader loaded the driver at an offset.
msacm32_7fff1d040000
which could mean some mess up with the versions.
you would have to unregister the files and reregister the files to attempt a fix without having to reinstall windows to get the fixed 32 bit subsystem.
reinstall of windows with a current build might fix the subsystem if it is not caused by one of the 32 bit tools you have installed. (overwolf, or tracking software)
also, assuming it is not a bug that was introduced via the update process.
==========
note: tried to validate the heap but hit a bug in the debugger crashed the debugger.