Crashing due to an Exception Access Violation

[Yogurt]

I've had this error multiple times now, though with it trying to access different memory locations. It crashes to desktop after playing for a while, with varying times in a map. It hasn't crashed in the setup room (or the brief time I played around in the training). I've tried updating my graphics drivers, reinstalling (and verifying game files) multiple times, including by deleting all files in the AppData and Documents folders, as well as the Steam install folder.

This time the Unreal Crash Reporter had this to say:

"Unhandled Exception: EXCEPTION_ACCESS_VIOLATION 0x00000570


GroundBranch_Win64_Shipping
PhysX3_x64
.
.
.
GroundBranch_Win64_Shipping
.
.
.
kernel32
ntdll"

If you would like me to post the actual crash log (or the full game log) let me know and I can put it in a pastebin link.

Specs:
Windows 10 Home Build: 20H2
ASRock B550 PRO4 Motherboard
AMD Ryzen 5800x CPU
NVIDIA RTX2060 (non super) GPU
16GB 3600MHz HyperX Fury RAM
Game is located on an XPG GAMMIX S11 Pro 1TB M.2 SSD

[Yogurt]

Update: Had another occurrence, this time it was:

"Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address 0xffffffff"

with similar "GroundBranch_Win64_Shipping" and "kernel32" and "ntdll" at the end.

[Rick James Bish]

Try this. Not saying it is your issue but simple to do and will have no adverse effects.
Start CMD as admin. Type sfc /scannow This will check for corrupt dll and fix.

[Yogurt]

Originally posted by Rick James Bish:

Try this. Not saying it is your issue but simple to do and will have no adverse effects.
Start CMD as admin. Type sfc /scannow This will check for corrupt dll and fix.

I appreciate that, I forgot to mention in the initial post that I did do that as well. I also tried force reinstalling the ntdll.dll file. sfc /scannow found no corrupted data files.

I suppose I'm getting close to my annual/bi-annual SSD formatting and fresh reinstall of Windows, so it's possible that would help, but I'm not sure it's 100% on my side. Hopefully a dev sees this.

[KrisRedbeard]

Check your log file when it happens.

If it mentions issues with a file being corrupt or not being able to garbage collect some object, it could well be simple as reinstalling the game etc.

If similar errors keep happening after your reinstall, then I'd be concerned it could be SSD/HDD related.

[Yogurt]

Originally posted by KrisRedbeard:

Check your log file when it happens.

If it mentions issues with a file being corrupt or not being able to garbage collect some object, it could well be simple as reinstalling the game etc.

If similar errors keep happening after your reinstall, then I'd be concerned it could be SSD/HDD related.

Here's the pastebin of the log when it crashed.

https://pastebin.com/vqXXJJen

There were a bunch of Lua errors of trying to get length of a nil value before the "===Critical Error===" line, where it mentions the "EXCEPTION_ACCESS_VIOLATION" and the memory address. I have reinstalled the game multiple times, including deleting all the files in AppData, Documents, and the Steam folders. Feel free to look at the end of the log at the pastebin link.

Edit: I also wanted to mention that I have installed the game on both of my SSD's, the 1TB M.2 mentioned in the specs, and also my 1TB SATA SSD. The error persisted on both storage devices.

[KrisRedbeard]

Could have been the Lua timer causing the crash.
I've fixed that internally and it'll be in the next patch.

The physx part... no clue :(

[Yogurt]

Yeah, I was pretty confused about that one too. I recently updated my GPU driver (after the initial crashes, which persisted after I updated as well) so that may be it. I don't remember if the original logs had that PhysX stuff in them.

I'll wait and see if the next patch fixes it for me. For what it's worth, I'm really enjoying the game (when it doesn't crash!).

[KrisRedbeard]

Glad you're enjoying it.

I haven't come across your crash yet.
With any luck I'll get more info when I do.

Talking of crashes, I came across a 10+ reports from a single user, in which the issue is simply a missing file. No amount of coding will fix that :)