Attempting to launch any available version leads to crashing upon selecting an IWAD

[TheCiv]

Currently experiencing a crash on every version of the game I've tested (through several older versions going back to December 2023) after selecting an IWAD. The game will load into a black screen, and then promptly close.

On checking Event Viewer to see if I could get some more info, it's giving me this:

Faulting application name: doomretro.exe, version: 5.1.2.0, time stamp: 0x657969db
Faulting module name: ntdll.dll, version: 10.0.22621.3733, time stamp: 0x67ca8829
Exception code: 0xc0000374
Fault offset: 0x000000000010c8f9
Faulting process id: 0x0x3E6C
Faulting application start time: 0x0x1DAEE436ECEA2F4
Faulting application path: C:\Users\xxxxxxxxxxx\Downloads\doomretro-5.1.2-win64\doomretro.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 923a96c8-9d70-46f7-ab88-36ff8879e29d
Faulting package full name: 
Faulting package-relative application ID: 

Running a scannow didn't find this DLL to be corrupted/replacable though, and given that it's a protected system file I'm at a bit of a loss as to what else I could try.

Currently on 2024-08 Cumulative Update for Windows 11 Version 23H2 for x64-based Systems (KB5041585), if that helps at all. Have tried a few forced updates as well just to test, and no luck.

[bradharding]

Thanks for the report. Certainly it's not an issue with ntdll.dll. There'd be some sort of heap corruption caused by DR's code. Could you please provide some further info?

• Does it occur with any IWAD/PWAD?
• You say you're "selecting an IWAD". Does that mean you're using DR's built in launcher?
• Are there any non-Latin characters in the IWAD's path?
• Do you have any files in the autoload folder?
• Does it happen with a clean install (that is, no doomretro.cfg file present)?

[TheCiv]

• It happens with every official IWAD tested
• Yep, going through the official "Where's All The Data?" launcher when starting the .exe
• Nope, and I've tried moving WAD locations a handful of times just to see if directories or the drives they were located on were causing issues for whatever reason
• Autoload is clean
• Each version I've tested, I've tested on a completely fresh install, and manually deleted the .cfg file a few times as well just to be certain, still producing the same result

I had come across a lot of similar answers about heap corruptions in the .dll file when researching that error in the event viewer and it had left me pretty stumped, haha. For most people with those issues, it means problems with several other programs too, but I'm literally only seeing this now with DR which is really odd.