BSOD Win 11 RADAR_PRE_LEAK_64

Going through some MSInfo32 logs to find the cause of a recurring BSOD and in the exported log file under the [Windows Error Reporting] section I keep seeing lots and lots of RADAR_PRE_LEAK_64.

I’ve seen suggestions online thats its some sort of new Win11 feature/function that can detect memory leaks, and whilst I can reliably trigger it when attempting to run C6.3 9054 on a WinXP SP3 on a VMware Player 17.6 virtual machine, its not 100% consistent.

So running the C6 IDE with the run in Separate Memory Space option ticked will trigger a BSOD 100%, you wont even see the C6 IDE splash window. If I run the C6 IDE with the Separate Memory Space option unticked, the IDE will run some of the time, alot more than less. The 32bit C6 apps like debugger, topscan etc that ship with C6 dont trigger a BSOD. I can less reliably and frequently trigger the BSOD without going anywhere near C6, ie not even running a XP SP3 virtual machine since the latest windows updates.

Versions earlier than VMware Player 17.6 also make the BSOD virtually non existent.
I also have Vmware Player Side Channel mitigation switched off, to keep up the speed by adding
ulm.disableMitigations = “TRUE”
to C:\ProgramData\VMware\VMware Workstation\config.ini because its not an option in VMware Player but is in VMware Workstation so has to be manually added to the config.ini file, but I can still reliably trigger the BSOD with it True or False.

The BSOD’s have only occurred when the latest updates have been applied, it didnt do this in earlier versions of Win11, but I cant be sure if its more to do with the latest VMware Player 17.6 or Windows Updates. The Windows updates triggered the VMware Player to want to install a new version of itself, creating a cascade of update events but also suggesting Broadcom/Vmware are working with MS in advance of window updates.

I also cant rule out this being a 16bit Real Mode issue because I am aware Intel want to remove that part of the chipset in future CPU models, and the C6 IDE uses 16bit Real Mode iirc.

So has anyone else encountered this, and do they know how to disable this RADAR_PRE_LEAK_64 feature for now?

Edit.
I’ve since found an article from 2016 referring to RADAR_PRE_LEAK_64 so this isnt something new or limited to Win11.

Edit2. Google has now shown me these links in its results…
2010 Resource Exhaustion Prevention | Microsoft Learn

Disable Resource Exhaustion — Generic service & computer documentation. documentation (r-pufky.github.io)

TIA