Rockstar RDR2 crash

[alphaps]

hello

after many hours I finally found out that windhawk was the one causing my game to crash at start.
when stopping windhawk, it fixed RDR2 crash (Rockstar Games).

issue is : when windhawk (1.4.1 or 1.5.1 the same) is running, RDR2 randomly crashes at start with 0xe0000027 (seems to be ERROR ALREADY RUNNING, found in launcher.log):
[2024-08-13 16:02:56.361] [DISPLAY] [14000] [gamelaunch] Launching game...
[2024-08-13 16:02:56.361] [DISPLAY] [14000] [gamelaunch] Path: E:\users\xxx\Games\Red Dead Redemption 2\RDR2.exe
[2024-08-13 16:02:56.361] [DISPLAY] [14000] [gamelaunch] Command Line: "E:\users\xxx\Games\Red Dead Redemption 2\RDR2.exe" @commandline.txt -enableCrashpad -scCommerceProvider=4 -rglLanguage=fr-FR
[2024-08-13 16:02:56.361] [DISPLAY] [14000] [gamelaunch] Working Directory: E:\users\xxx\Games\Red Dead Redemption 2
[2024-08-13 16:03:13.373] [DISPLAY] [14000] [gamelaunch] Game exited with code 0xe0000027 (3758096423)
[2024-08-13 16:03:13.413] [DISPLAY] [14000] [crashdetection] Reading game exit file...
[2024-08-13 16:03:13.414] [WARNING] [14000] [crashdetection] Not found: EXIT_CODE
[2024-08-13 16:03:13.414] [WARNING] [14000] [crashdetection] No exit code found in exit file.
[2024-08-13 16:03:13.414] [WARNING] [14000] [crashdetection] Not found: ERROR_FILE_HASH
[2024-08-13 16:03:13.414] [DISPLAY] [14000] [crashdetection] No additional error information found.
[2024-08-13 16:03:13.414] [WARNING] [14000] [crashdetection] Not found: ERROR_MESSAGE
[2024-08-13 16:03:13.414] [DISPLAY] [14000] [crashdetection] No additional error message found.
[2024-08-13 16:03:13.414] [DISPLAY] [14000] [crashdetection] Deleting game exit file...
[2024-08-13 16:03:13.414] [ ERROR ] [14000] [crashdetection] Exit code 0xe0000027 indicates a fatal game exit (reason: Unknown Error Code)

hope that helps others facing the same issue, couldn't find anything on the net
still, windhawk is awesome !
-Al

[m417z]

Thanks for letting me know. Perhaps you already know that, but you can exclude the game in Windhawk's advanced settings. Let me know if you need help with that.

Also, can you capture a crash dump? You should be able to get it with the following steps:

• Open regedit
• Go to: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting
• Create a key named LocalDumps
• Create a DWORD value named DumpType with value 2
• Trigger the crash
• Go to the %LocalAppData%\CrashDumps folder, you should see a dump file in there

[alphaps]

Hello,

Adding rdr2.exe to windhawk's process exclusion list did the trick, thank you !
Also reproduced the issue without this + the LocalDumps regkey, I do have some dmp files in %LocalAppData%\CrashDumps, but not anything for rdr2.exe
So it's probably not a crash per se, rather the game exiting itself.
The error code made me think of "process already running", isn't windhawk trying to re-spawn the process with some injection? maybe the game detects that & thinks it's running twice.

-Al

[m417z]

isn't windhawk trying to re-spawn the process with some injection?

No, Windhawk doesn't do that.

If you can reproduce it with just the executable, even if it's not running, let me know. Any different behavior will do, for example if the executable (without the game resources) shows an error message, but with Windhawk just exits, I can take a look. If it requires the multi-GB setup of the game, which is also unlikely to be free, then I'll pass for now.

[alphaps]

I tried running just the executable but it fails in both cases (with/without process exclusion) as it's looking for many DLLs.
Otherwise, I have a windbg Run file captured when reproducing the issue, interested? I couldn't make much of it myself, I just saw there are 2 C++ exceptions in Vulkan driver / OpenAdapter.

[m417z]

If you can make a bundle with several dlls, that can work as well, as long as it's self-contained, around 1GB or less, and not tens of GBs of the actual game that also needs to be purchased.

Regarding the Vulkan exceptions, I don't think it can help in this case, unless Windhawk is mentioned somewhere.

[alphaps]

Hi again
I saw issues with many other programs and finally understood it's because windhawk tries to inject into them.
As I will not exclude all of them (and some I don't even start myself) I decided to uninstall windhawk. I was using it only for taskbar clock customization mod and found ElevenClock does the trick for me without any process injection.
For this kind of use case when using a single mod like clock mod, couldn't you have an option to avoid any injection at all (except maybe explorer.exe for the taskbar)?

Processes that were failing silently or misbehaving :
WebEx.exe
Cargo (rust)
Chrome updater.exe (this one auto starts, that's the kind we cannot know in advance to exclude)
Vscode (either from Ms store or from their website)
Eclipse ide installer
And I'm probably missing others.

Thanks anyway and keep it up!

[m417z]

Hi,

For this kind of use case when using a single mod like clock mod, couldn't you have an option to avoid any injection at all (except maybe explorer.exe for the taskbar)?

You can configure it in the advanced settings. You can set * - all processes - in the exclusion list, and explorer.exe in the inclusion list. Note that this will cause mods to be injected into Explorer with a slight delay. For the clock customization mod that isn't that important, but for other mods it might be.

Processes that were failing silently or misbehaving :
WebEx.exe
Cargo (rust)
Chrome updater.exe (this one auto starts, that's the kind we cannot know in advance to exclude)
Vscode (either from Ms store or from their website)
Eclipse ide installer
And I'm probably missing others.

That's a long list! What kind of problems did you experience, and why do you think they're related to Windhawk?

A problem with Cargo was reported in the past, but I was unable to reproduce it, and the author couldn't either after some time: #179.
I'm using VSCode and Chrome with Windhawk full-time and didn't experience any issues.
I'm not using the other software from the list.

[alphaps]

Thanks for the tip to exclude "* but explorer.exe"
I also found it mentioned in other issues here.
I understand the rationale to catch subprocesses, but I'd also vote to have "* but explorer.exe" as the default setting ;-)

WebEx: crashed after sign-in if not run as admin. When run as admin, randomly fails to load audio/video devices.
Cargo: worked once, and after always failed with ERRORLEVEL -536870873
Chrome updater: saw this one failing in event viewer. Exception code: 0xc0000005
Vscode: failing silently at start. worked once as admin.
Eclipse ide installer: fails silently after the initial popup

HTH

All these were never reproduced after uninstalling windhawk.

[m417z]

I'd like to investigate and, if possible, fix these issues. If you can still reproduce these problems and willing to help, can you capture crash dumps? You should be able to get it with the following steps:

• Open regedit
• Go to: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting
• Create a key named LocalDumps
• Create a DWORD value named DumpType with value 2
• Trigger the error
• Go to the %LocalAppData%\CrashDumps folder, you should see a dump file in there