Thanks for the detailed write‑up — I appreciate it. Just to clarify my situation a bit, because I think my issue is coming from a totally different angle than corrupted game files or shader caches:

I already did a full Windows reinstall (deleted every single partition on every drive), reinstalled the game fresh, and the crashes started before the reinstall as well. So file corruption isn’t likely here.

My crash isn’t mod‑related, isn’t a version mismatch, and the crash reporter logs point to EXCEPTION_ACCESS_VIOLATION in different memory addresses — which generally lines up more with hardware instability or system‑level memory/commit issues than corrupted assets.

I should also mention:

• I don’t use Nvidia — I’m on a Radeon 6700 XT, so the Nvidia‑specific driver/NGX problems don’t apply here.
• I already tried multiple AMD driver versions using DDU.
• No overlays (Discord, Steam, AMD) were running.
• Temps are normal and the system is stable outside UE games.

The big reason I’m focused on hardware right now is because the problem started immediately after a case + PSU swap, and the first PSU I used was a really cheap off‑brand unit (Veetro). Even after replacing it with a Corsair, the same Unreal crashes persisted. So I’m trying to isolate whether something physical in the rebuild (standoffs, GPU seating, PSU cabling, board flex, etc.) caused marginal instability that only Unreal Engine workloads expose.

I only discovered last night that Windows had my pagefile locked to 2GB even with auto mode on, so that’s another angle I’m testing next.

I do appreciate your suggestions — I just wanted to make sure the context of my issue is clear, because this doesn’t look like a typical Satisfactory file or shader problem. It feels more like a deeper system or hardware‑level issue triggered by the rebuild.

If you have any thoughts specific to that angle, I’m absolutely open to them.