Frequent EXCEPTION_ACCESS_VIOLATION crashes.

[I Play Nude]

Whenever an area is loading, there is a good chance the game will crash with this error:

Unhandled Exception: EXCEPTION_ACCESS_VIOLATION 0x000001c01ca04100

Remnant2_Win64_Shipping
Remnant2_Win64_Shipping
Remnant2_Win64_Shipping
Remnant2_Win64_Shipping
Remnant2_Win64_Shipping
Remnant2_Win64_Shipping
Remnant2_Win64_Shipping
Remnant2_Win64_Shipping
Remnant2_Win64_Shipping
Remnant2_Win64_Shipping
Remnant2_Win64_Shipping
Remnant2_Win64_Shipping
Remnant2_Win64_Shipping
Remnant2_Win64_Shipping
kernel32
ntdll

I can't find any definitive answers, but have tried a number of things with no success. Any ideas would be appreciated.

[SkyNet]

Windows 10 Pro (22h2 - 19045.3271) Intel I9-9900, EVGA RTX 3060, Corsair 32GB DDR4, Samsung 990 Pro 1TB NVME.

I am getting the exact same crash/unreal report extremely frequently. However it's not just on loading, it's literally random. Including just listening to the old guy tell stories. The Frequency of crashes seems to increase in multiplayer.

They always launch Unreal crash reporter with EXCEPTION_ACCESS_VIOLATION error save one singular occassion where it was LowLevelFatalError.
There is no information entered into the event viewer for them.

I've scanned the forums, reddit, twitter, and discord for suggested fixes which have all failed to resolve the crashes:

Verified Integrity of game files.
Disabled steam FPS overlay.
Cleared Shader cache.
Disabled desktop optimizations on normal .exe and shipping .exe
Compatibility mode for windows 7/8 on normal and shipping .exe
Updated Video Card Drivers. (DDU Removal, Clean install update)
Utilized sfc /scannow + DISM.exe
Lowered graphics to minimum settings.
DLSS on/off. (Performance, Balance, Quality all yield the same results)
In Power Management, changed PCI Express Link State Power Management to Off.
Running steam as Administrator.
Clearing and redownloaded/reinstalling the game.
Running Borderless or Fullscreen.
Repaired/Verified newest version of all VCRedists.
Debug Mode with Nvidia Control Panel.

Downclocking video card
(This results in a computer freeze, that requires a hard reset)

Tried using Administrator mode on .exe, not shipping .exe
(This results in the game not detecting the DLC and not being able to play multiplayer)
[EDIT] After reinstalling the game, I could launch the game with the shipping .exe set as Administrator which I could not before I redownloaded. However the problem was not resolved.

Tried updating Windows 10
(Was already on 22h2 and moved up a couple versions, this resulted in crashing MORE frequently)

Game was always installed on C: drive (OS Drive, where Steam is installed)

[Edit.4] Removing Geforce Game Ready drivers and installing Nvidia Studio Drivers seems* to have extended the time between crashes.

[Edit.6?7? Who knows] Downclocked my ram from 3k to 2666, and used the Nvidia Studio Drivers with an ingame frame cap of 60. This has yieled the best results.

[Edit.8ish] No longer using studio drivers, using Nvidia Game Ready 536.99. Functionality remains the same.

[Edit.9?] Frame cap moved up to 120, though I cannot hit 120 frames. Patch 384,830 seems to have further reduced crashing, but not eliminated it entirely.

[Bodine Wilson]

have you tried running memtest to make sure your RAM's not hosed?

[Somnioid Static]

I have a similar/the same issue, only with mine it's on game boot up.

Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address 0x0000000000000000

Remnant2_Win64_Shipping
Remnant2_Win64_Shipping
Remnant2_Win64_Shipping
Remnant2_Win64_Shipping
Remnant2_Win64_Shipping
Remnant2_Win64_Shipping
Remnant2_Win64_Shipping
Remnant2_Win64_Shipping
Remnant2_Win64_Shipping
Remnant2_Win64_Shipping
Remnant2_Win64_Shipping
Remnant2_Win64_Shipping
Remnant2_Win64_Shipping
kernel32
ntdll

[b1k3rdude]

Welp I just got a similar crash near the start of the game after killing the first beast -

bezare that this is a steam game, but the epic account remants (see what I did there...) is still present. But looking at the error files its looks to be related to nvidia DLSS

LoginId:60a3abcf4b9eb73bb9ba79af6b502182
EpicAccountId:

Unhandled Exception: EXCEPTION_ACCESS_VIOLATION 0x00007fff3cd01bc7

nvwgf2umx
nvwgf2umx
nvwgf2umx
nvwgf2umx
D3D12Core
D3D12Core
D3D12Core
nvngx_dlssg
nvngx_dlssg
nvngx_dlssg
nvngx_dlssg
nvngx_dlssg
nvngx_dlssg
nvngx_dlssg
nvngx_dlssg
nvngx_dlssg
nvngx_dlssg
_nvngx
_nvngx
sl_common
sl_common
sl_dlss_g
sl_dlss_g
sl_dlss_g
sl_dlss_g
sl_dlss_g

Doing a manual update of the nvngx_dlss.dll to v3.5 to see if that helps...

[R.V.]

same here
Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address 0x00000003000263a9

Remnant2_Win64_Shipping
Remnant2_Win64_Shipping
Remnant2_Win64_Shipping
Remnant2_Win64_Shipping
Remnant2_Win64_Shipping
Remnant2_Win64_Shipping
Remnant2_Win64_Shipping
Remnant2_Win64_Shipping
Remnant2_Win64_Shipping
Remnant2_Win64_Shipping
Remnant2_Win64_Shipping
Remnant2_Win64_Shipping
Remnant2_Win64_Shipping
Remnant2_Win64_Shipping
Remnant2_Win64_Shipping
kernel32
ntdll

i did un link epic account but still the same

[b1k3rdude]

Originally posted by b1k3rdude:

Welp I just got a similar crash near the start of the game after killing the first beast -

bezare that this is a steam game, but the epic account remants (see what I did there...) is still present. But looking at the error files its looks to be related to nvidia DLSS

LoginId:60a3abcf4b9eb73bb9ba79af6b502182
EpicAccountId:

Unhandled Exception: EXCEPTION_ACCESS_VIOLATION 0x00007fff3cd01bc7

nvwgf2umx
nvwgf2umx
nvwgf2umx
nvwgf2umx
D3D12Core
D3D12Core
D3D12Core
nvngx_dlssg
nvngx_dlssg
nvngx_dlssg
nvngx_dlssg
nvngx_dlssg
nvngx_dlssg
nvngx_dlssg
nvngx_dlssg
nvngx_dlssg
nvngx_dlssg
_nvngx
_nvngx
sl_common
sl_common
sl_dlss_g
sl_dlss_g
sl_dlss_g
sl_dlss_g
sl_dlss_g

Doing a manual update of the nvngx_dlss.dll to v3.5 to see if that helps...

[update] manually install the DLSS 3.5 fixed the crashing with the above error for me.

[b1k3rdude]

But this evening after 2 days of no crashing, I got the dredded main exe file crash -

Remnant2_Win64_Shipping
kernel32
ntdll

[Hex: Thicc Booty]

i have this issue now as well, game ran well for a few days but suddenly crashed


Fatal error!

Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address 0x000003030002c829

Remnant2_Win64_Shipping
Remnant2_Win64_Shipping
Remnant2_Win64_Shipping
Remnant2_Win64_Shipping
Remnant2_Win64_Shipping
Remnant2_Win64_Shipping
kernel32
ntdll

[avocado]

Originally posted by Somnioid Static:

I have a similar/the same issue, only with mine it's on game boot up.

Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address 0x0000000000000000

Remnant2_Win64_Shipping
Remnant2_Win64_Shipping
Remnant2_Win64_Shipping
Remnant2_Win64_Shipping
Remnant2_Win64_Shipping
Remnant2_Win64_Shipping
Remnant2_Win64_Shipping
Remnant2_Win64_Shipping
Remnant2_Win64_Shipping
Remnant2_Win64_Shipping
Remnant2_Win64_Shipping
Remnant2_Win64_Shipping
Remnant2_Win64_Shipping
kernel32
ntdll

Hey man, I've been getting the exact same error. Did you ever get it fixed after?