This took longer than anticipated, as the exception code gave me two to three potential issues. Just to narrow it down, check if there are corrupt files in the OS. You can do this by following this guide: Use the System File Checker tool to repair missing or corrupted system files - Microsoft Support
I can also send you an experimental version of the tool, to rule out any build issues on my side.
Thank you so much for the reply.
My windows 10 is an LTSC version and a custom one at that, so some features are disabled, such as updates and because of that when I run sfc /scannow it will say that there are corrupted files, but it will not specify or repair those "corrupted" files because the updates are disabled (permanently on this custom OS).
Can you please send me the experimental version so we can check? (though I highly doubt that it is an issue on your end)
If this doesn't work, I guess I'll just have to re-install windows some time in the future.
And once again, sorry for taking up your time!
Thank you for sending me the experimental version, I've downloaded and tried to open it but same thing happened again (crashed without error), however this time the error in event viewer is different and there are two this time.
Exception code: 0xc0000005
Fault offset: 0x00000000000e013c
Faulting process id: 0x13b8
Exception code: 0xc0000005
Fault offset: 0x00000000000e013c
Faulting process id: 0x3cd0
------------------------------------------------
Exception code: 0xc0000602
Fault offset: 0x000000000010b302
Faulting process id: 0x3b40
