Game Crash - Unhandled Exception: EXCEPTION_ACCESS_VIOLATION

[Kiwink]

Hi everyone,

I'm experiencing a consistent crash in FINAL FANTASY VII REBIRTH. The game crashes with an "Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address 0x00000000000004b8" error.

Here's a summary of my system and the crash context:

System:

• CPU: AMD Ryzen 7 5700X 8-Core Processor
  
• GPU: NVIDIA GeForce RTX 4070 Ti
  
• OS: Windows 10 (Release 2009)
  
• RAM: 32 GB

Crash Context:

• Game: FINAL FANTASY VII REBIRTH
  
• Engine Version: 4.26.1-0+++UE4+Release-4.26
  
• Crash Type: Unhandled Exception: EXCEPTION_ACCESS_VIOLATION

I've tried the following troubleshooting steps:

• Verified game files through Steam.
  
• Updated graphics drivers to the latest version.
  
• Reinstalled the game.

Unfortunately, none of these steps have resolved the issue.

Has anyone else encountered a similar crash or have any suggestions on how to fix it?

Thanks in advance for any help!

[This PC]

You can probably trace the culprit through your event viewer in windows, would help ^^
Access violations can be a lot of things, one simple thing you can try is running the game as admin, if it's a permissions issue, this might help.

[Ðine]

are you using a custom engine.ini file, if so may need to revert to stable version, if NOT, try https://www.nexusmods.com/finalfantasy7rebirth/mods/3?tab=files

you will also want to disable "hardware acceleration" in discord and chrome

[Kiwink]

Hey everyone,

Thanks for the suggestions on my previous post. Just wanted to give an update.

Regarding the admin/Steam launch issue, I did try running as admin initially, but it kept prompting me to launch through Steam, even when I was launching from Steam. I suspect there might be something going on with UAC, but I haven't made any permanent changes there yet.
Also, I'm running a completely vanilla install, no mods at all.

After reading up on the error I was getting, I came across some info about potential RAM corruption. I ran MemTest86, and unfortunately, it hit over 10,000 errors and stopped. So, it looks like my RAM is likely the culprit.

Thankfully, my system is still under warranty, and I'm getting the RAM tested and potentially replaced in the next few days.

Once I have the new RAM installed and my system is back up and running, I'll re-test the game and update this thread with the results. Fingers crossed this solves the problem!

Thanks again for your help.