hi @KrilldAk1nG ,
Slight problem is you have given an image of the crash not the text of the crash this would allow the remote dump tracer to point to the source.
The only alternative was to use Ms Co-pilot to look at the encryted numbers and analyze them using the MS to Unreal Crash bridge.
With all AI it looks good but might have some good suggestions, but may not have an answer
You’re hitting an Access Violation when Unreal Editor for Fortnite (UEFN) tries to write memory—essentially it’s crashing before it ever opens your project. Let’s go deep and get this fixed:
1. Driver & OS Health Check
- Update GPU drivers (AMD/NVIDIA/Intel). Even “game-ready” drivers can be buggy—try clean-installing the previous version if the latest is unstable.
- Run Windows Update, then reboot. Some system DLLs UEFN relies on get patched in OS updates.
2. Verify Engine & Launcher Files
- In Epic Games Launcher, click the three dots next to “Unreal Editor for Fortnite” and choose Verify. This rescans every file, replacing any that are corrupt or missing.
3. Isolate Third-Party Interference
- Turn off or uninstall overlays (Discord, GeForce Experience, MSI Afterburner).
- Disable antivirus or add UEFN’s install folder to its exception list.
4. Clear and Rebuild Local Data
- Completely remove the UEFN cache:
- Close Epic Games Launcher.
- Delete %localappdata%\FortniteGame\Saved\ and %localappdata%\UnrealEngineLauncher\ folders.
- Restart the launcher and let it redownload necessary files.
5. Test a Blank Project
- Create a brand-new, empty Fortnite UEFN world. If that loads, your existing project might have an asset or plugin triggering the crash.
- Gradually import assets from your broken project into the blank one to pinpoint the culprit.
6. Dive into the Logs
- After a crash, open %localappdata%\FortniteGame\Saved\Logs\FortniteEditor.log.
- Search for “Error” or “Warning” near the end. Look for failed loads (missing DLLs, corrupt assets). That’ll point you to the root cause.
7. Memory & Hardware Tests
- Run Windows Memory Diagnostic (type “mdsched” in Start).
- Check your disk’s health: run chkdsk C: /f /r from an elevated Command Prompt, then reboot.
8. Epic Support & Community Wisdom
- If all else fails, bundle the crash dumps and logs, then hit Send and Close in the Crash Reporter. In your support request, be explicit:
• Steps you’ve tried (verification, cache clears, driver rollbacks)
• Excerpts from your log showing the first “Access Violation” line
- Post your crash summary on the UEFN Discord or Unreal forums—often other creators have the same obscure bug and a workaround.
Next Steps: While you troubleshoot, grab a coffee. Within those logs and by slowly isolating variables, you’ll uncover exactly which file, driver, or plugin is tripping UEFN over its own feet. Once it’s fixed, you’ll have a much healthier project and stronger debugging skills for the next inevitable crash.
Well at least this is something else to try.
The disclaimer is this may not be the answer, but would be nice to see how this works.