After using Claude to look into this problem it appears that my Simagic force feedback is the culprit. Disconnecting my ffb wheel seems to aliviate the crash.
"The faulting address and the instruction address are the same, so the CPU jumped to an address that isn’t valid code. That address starts with 0x7ffe5a…, while the rest of the call stack is in the game’s own range (0x7ff7…). So the game called into a DLL, and that DLL jumped somewhere bad. The “Couldn’t resolve world path” line is probably just the last thing logged before the crash. The log embedded in the dump has the same line with a 20:25 timestamp, so this is a third crash with the same sequence.
Likely suspect. The crash handler labeled the address DllUnregisterServer, which is just the nearest exported function name. It means the DLL exports COM registration functions. The only DLLs that look like third-party drivers in the dump’s module list are:
BattlEye’s BE.dll
TrackIR’s NPClient64.dll
Simagic’s simpro_1.dll
Steam’s overlay
NVIDIA’s driver
My best guess is the Simagic force-feedback driver. DirectInput FFB drivers are COM DLLs that typically export those functions, and the build path embedded in it says 2023, so it may be an old build. Update 1.9 also added more advanced driving physics and support for racing wheels and pedals, so the game may initialize force feedback when a scenario starts. This is a hypothesis, not proven. indian-tv
What to try, in order
Close the Simagic software and TrackIR software, unplug the wheelbase, pedals and TrackIR, then launch Eden.
If it loads, update the Simagic software and driver, then reconnect devices one at a time to find the culprit.
If it still crashes with everything unplugged, try Conflict to see whether it’s Eden-specific. Then reinstall BattlEye by running Uninstall_BattlEye.bat and then Install_BattlEye.bat as administrator from the game’s BattlEye folder, and verify game files after that."