UE4 Crash: Engine or Windows issue ?

During the last month, Unreal builds I created with 4.21.2 have suddenly gone haywire. I just couldn’t run stuff for a full length of a game anymore. And my new builds share the same fate: Debug, Development or Shipping.

The following is a Debug game and, surprisingly, there is little debug information for me to work with:

2022.11.14-19.48.26:092][498]LogWindows: Warning: CreateProc failed: Le fichier spécifié est introuvable. (0x00000002)
[2022.11.14-19.48.26:092][498]LogWindows: Warning: URL: …/…/…/Engine/Binaries/Win64/CrashReportClient.exe “D:/Documents/Tests_Jeu/20221114_V1/WindowsNoEditor/Amos/Saved/Crashes/UE4CC-Windows-8820AA3646AE38F46958F186E87CBF94_0000” -AppName=UE4-Amos -CrashGUID=UE4CC-Windows-8820AA3646AE38F46958F186E87CBF94_0000 -DebugSymbols=…....\Engine\Intermediate\Symbols
[2022.11.14-19.48.26:092][498]LogWindows: Could not start CrashReportClient.exe
[2022.11.14-19.48.26:092][498]LogMemory: Platform Memory Stats for WindowsNoEditor
[2022.11.14-19.48.26:092][498]LogMemory: Process Physical Memory: 657.99 MB used, 716.04 MB peak
[2022.11.14-19.48.26:092][498]LogMemory: Process Virtual Memory: 1568.95 MB used, 1582.62 MB peak
[2022.11.14-19.48.26:092][498]LogMemory: Physical Memory: 6456.07 MB used, 9870.59 MB free, 16326.66 MB total
[2022.11.14-19.48.26:092][498]LogMemory: Virtual Memory: 6134.12 MB used, 134211592.00 MB free, 134217728.00 MB total
[2022.11.14-19.48.26:092][498]LogWindows: Error: === Critical error: ===
[2022.11.14-19.48.26:092][498]LogWindows: Error:
[2022.11.14-19.48.26:092][498]LogWindows: Error: Fatal error!
[2022.11.14-19.48.26:092][498]LogWindows: Error:
[2022.11.14-19.48.26:092][498]LogWindows: Error: Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address 0xffffffff
[2022.11.14-19.48.26:092][498]LogWindows: Error:
[2022.11.14-19.48.26:092][498]LogWindows: Error: [Callstack] 0x00007ff7997310f1 EnQueteDeJesus-Win64-DebugGame.exe!UnknownFunction
[2022.11.14-19.48.26:092][498]LogWindows: Error: [Callstack] 0x00007ff7997327e3 EnQueteDeJesus-Win64-DebugGame.exe!UnknownFunction
[2022.11.14-19.48.26:092][498]LogWindows: Error: [Callstack] 0x00007ff799715c92 EnQueteDeJesus-Win64-DebugGame.exe!UnknownFunction
[2022.11.14-19.48.26:092][498]LogWindows: Error: [Callstack] 0x00007ff7996ec3a9 EnQueteDeJesus-Win64-DebugGame.exe!UnknownFunction
[2022.11.14-19.48.26:092][498]LogWindows: Error: [Callstack] 0x00007ff799715c92 EnQueteDeJesus-Win64-DebugGame.exe!UnknownFunction
[2022.11.14-19.48.26:092][498]LogWindows: Error: [Callstack] 0x00007ff7996ec3a9 EnQueteDeJesus-Win64-DebugGame.exe!UnknownFunction
[2022.11.14-19.48.26:092][498]LogWindows: Error: [Callstack] 0x00007ff799715c92 EnQueteDeJesus-Win64-DebugGame.exe!UnknownFunction
[2022.11.14-19.48.26:092][498]LogWindows: Error: [Callstack] 0x00007ff7996ec3a9 EnQueteDeJesus-Win64-DebugGame.exe!UnknownFunction
[2022.11.14-19.48.26:092][498]LogWindows: Error: [Callstack] 0x00007ff799715c92 EnQueteDeJesus-Win64-DebugGame.exe!UnknownFunction
[2022.11.14-19.48.26:092][498]LogWindows: Error: [Callstack] 0x00007ff7994e1112 EnQueteDeJesus-Win64-DebugGame.exe!UnknownFunction
[2022.11.14-19.48.26:092][498]LogWindows: Error: [Callstack] 0x00007ff7997152ad EnQueteDeJesus-Win64-DebugGame.exe!UnknownFunction
[2022.11.14-19.48.26:092][498]LogWindows: Error: [Callstack] 0x00007ff79b27a91b EnQueteDeJesus-Win64-DebugGame.exe!UnknownFunction
[2022.11.14-19.48.26:092][498]LogWindows: Error: [Callstack] 0x00007ff79b250543 EnQueteDeJesus-Win64-DebugGame.exe!UnknownFunction
[2022.11.14-19.48.26:092][498]LogWindows: Error: [Callstack] 0x00007ff79b258c5a EnQueteDeJesus-Win64-DebugGame.exe!UnknownFunction
[2022.11.14-19.48.26:092][498]LogWindows: Error: [Callstack] 0x00007ff79b8dcb40 EnQueteDeJesus-Win64-DebugGame.exe!UnknownFunction
[2022.11.14-19.48.26:092][498]LogWindows: Error: [Callstack] 0x00007ff79c13a964 EnQueteDeJesus-Win64-DebugGame.exe!UnknownFunction
[2022.11.14-19.48.26:092][498]LogWindows: Error: [Callstack] 0x00007ff79b9344de EnQueteDeJesus-Win64-DebugGame.exe!UnknownFunction
[2022.11.14-19.48.26:092][498]LogWindows: Error: [Callstack] 0x00007ff79c173bed EnQueteDeJesus-Win64-DebugGame.exe!UnknownFunction
[2022.11.14-19.48.26:092][498]LogWindows: Error: [Callstack] 0x00007ff79b7c4e85 EnQueteDeJesus-Win64-DebugGame.exe!UnknownFunction
[2022.11.14-19.48.26:093][498]LogWindows: Error: [Callstack] 0x00007ff79bff5932 EnQueteDeJesus-Win64-DebugGame.exe!UnknownFunction
[2022.11.14-19.48.26:093][498]LogWindows: Error: [Callstack] 0x00007ff79b78058f EnQueteDeJesus-Win64-DebugGame.exe!UnknownFunction
[2022.11.14-19.48.26:093][498]LogWindows: Error: [Callstack] 0x00007ff79b78e700 EnQueteDeJesus-Win64-DebugGame.exe!UnknownFunction
[2022.11.14-19.48.26:093][498]LogWindows: Error: [Callstack] 0x00007ff798987285 EnQueteDeJesus-Win64-DebugGame.exe!UnknownFunction
[2022.11.14-19.48.26:093][498]LogWindows: Error: [Callstack] 0x00007ff7989952bd EnQueteDeJesus-Win64-DebugGame.exe!UnknownFunction
[2022.11.14-19.48.26:093][498]LogWindows: Error: [Callstack] 0x00007ff79899533a EnQueteDeJesus-Win64-DebugGame.exe!UnknownFunction
[2022.11.14-19.48.26:093][498]LogWindows: Error: [Callstack] 0x00007ff7989a4481 EnQueteDeJesus-Win64-DebugGame.exe!UnknownFunction
[2022.11.14-19.48.26:093][498]LogWindows: Error: [Callstack] 0x00007ff79ce73e2e EnQueteDeJesus-Win64-DebugGame.exe!UnknownFunction
[2022.11.14-19.48.26:093][498]LogWindows: Error: [Callstack] 0x00007ffe5d6574b4 KERNEL32.DLL!UnknownFunction
[2022.11.14-19.48.26:093][498]LogWindows: Error: [Callstack] 0x00007ffe5f2226a1 ntdll.dll!UnknownFunction
[2022.11.14-19.48.26:093][498]LogWindows: Error:
[2022.11.14-19.48.26:104][498]LogExit: Executing StaticShutdownAfterError
[2022.11.14-19.48.26:117][498]LogWindows: FPlatformMisc::RequestExit(1)
[2022.11.14-19.48.26:120][498]Log file closed, 11/14/22 14:48:26

I wondering if this is an OS thing. I upgraded my graphics card drivers. I haven’t got new hardware. But these unknown functions just don’t make any sense to me.

I saw similar reports on this forum, but they are peppered with potential driver warnings that may point more easily to a culprit (D3D, RHI, etc). Mine are pretty clean.

Crash dumps don’t work. It seems that VS 2017 doesn’t recognize the .pdb files in Game\Binaries\Win64, and I would certainly need some pointers for that …

Any, ANY help appreciated.

No clear answer about this. But I decided to compile the same project with 4.22 and VS 2019 and the random crashes seem to have dissipated. Crossing my fingers.