Direct Download: http://www.ntcore.com/files/4gb_patch.zip
The "4GB Patch" Tool basically allows the allocation of an additional 2GB of virtual memory into the executable through allowing "Large Address Aware" within the executable (See "4-Gigabyte Tuning" on pcgamingwiki for explanation: https://pcgamingwiki.com/wiki/Microsoft_Windows#4-Gigabyte_Tuning)
If you desire the same results on your executable but with more options to play with, use "Large Address Aware Enabler" by FordGT90Concept that basically does the same thing as 4GB Patch but with a more interactable interface https://www.techpowerup.com/forums/threads/large-address-aware.112556/
I tried this on my SCP executable on and I have not had issues with lag spikes and FPS staying at a constant rate rather than dropping to single digits which is what I had before. I have been getting no lag-related MAVs and "failure to load" MAVs are now harder for me to encounter.
I encourage anyone else to try this tool out for themselves and I hope this is implemented in the next possible update of SCP- CB.
EDIT 2: Did some tests on mods, this Patch tool drastically improved the performance for
- SCP: CB Nine Tailed Fox Mod https://undertowgames.com/forum/viewtopic.php?f=11&t=4358
- Project Resurrection https://undertowgames.com/forum/viewtopic.php?f=11&t=5445
- SCP: CB Unity Edition (32 Bit Version) https://undertowgames.com/forum/viewtopic.php?f=3&t=5553
- SCP: CB 087-B Mod http://undertowgames.com/forum/viewtopic.php?f=11&t=4944
EDIT: From the website
I originally wrote this tool for a friend of mine who needed it. This very little tool patches x86 executables in order to let them have 4GB (instead of only 2) of virtual memory on x64 platforms. This tool comes very handy for applications which need a great amount of virtual memory like games, 3D renderization, multimedia etc. To gain these 2GB, you just have to use this tool to patch the executable (*.exe file) of the software you want to have these additional GBs of virtual memory. It can be used by clicking on it and choosing the file or through command line (e.g.: "4gb_patch file.exe"). It automatically creates a backup copy of the original executable.
Why things are this way on x64 is easy to explain. On x86 applications have 2GB of virtual memory out of 4GB (the other 2GB are reserved for the system). On x64 these two other GB can now be accessed by 32bit applications. In order to achieve this, a flag has to be set in the file's internal format. This is, of course, very easy for insiders who do it every day with the CFF Explorer. This tool was written because not everybody is an insider, and most probably a lot of people don't even know that this can be achieved. Even I wouldn't have written this tool if someone didn't explicitly ask me to.