nhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address 0x0000000000000018

[Lex]

hi all.

Seemingly random (for me) crashes during online game. Sometimes in-game, sometimes in ready room, or right after spawn. After crash and restart, unable to join the same server; join server leads to main menu.

Did a clean install of the game/verified game-files. No mods.

[KrisRedbeard]

DX11 or DX12?

[AxXome]

same here, random crash with the same message

[KrisRedbeard]

Same question, DX11 or DX12?

Though I should also ask, AMD of NVIDIA based GPU?

[={FH}=Lt.Dan]

Tagging onto this please, I just bought the game in the sale and am running it on DX12 with Intel processor i7 14th gen NVidia RTX4070 Ti super and have had this error twice, once in training and once in a solo mission game seems to be after around 10 minutes of gameplay each time

[Xm0x]

I have the exactly same problem as you. I got RTX 4060 and Intel i7 12th gen playing with DX12

[KrisRedbeard]

Either run the game in DX11 or disable the DLSS plugin with the command line:

-ngxdisable

[={FH}=Lt.Dan]

Hi yes update I ran on DX11 option and it worked ok, not tried the other suggestion of disabling DLSS plugin though.

[SquirrelzQL]

Interesting, I have DLSS and DLSS Frame Gen on here and no problems... but I don't have an fps cap and I haven't updated Nvidia at all for months I think. Same GPU and everything, 4070 TI 16gb. My friend though on a 4060 is having the same 0x0000000000000018 error code. His problem is crashing only after in the mission at some point, it's usually fairly quick or somewhere in the first few minutes of it the match. It always happens though.

[KrisRedbeard]

No clue either.
Some 40-series users are fine, others crash.
Its seems fairly random.

[Hund]

Something new just popped up, but regarding the usual DX12 crashes, will that ever be fixed? Its been 6 months now...

Assertion failed: State.status == sl::DLSSGStatus::eOk [File:D:/TC1034/Engine/Plugins/Runtime/Nvidia/Streamline/Source/StreamlineCore/Private/StreamlineDLSSG.cpp] [Line: 598] DLSS-FG failed at runtime with DLSSGStatus::eFailReflexNotDetectedAtRuntime (2). This runtime check can be disabled with the r.Streamline.DLSSG.CheckStatusPerFrame console variable

GroundBranch_Win64_Shipping
GroundBranch_Win64_Shipping
GroundBranch_Win64_Shipping
GroundBranch_Win64_Shipping
GroundBranch_Win64_Shipping
GroundBranch_Win64_Shipping
GroundBranch_Win64_Shipping
GroundBranch_Win64_Shipping
GroundBranch_Win64_Shipping
GroundBranch_Win64_Shipping
GroundBranch_Win64_Shipping
kernel32
ntdll

[KrisRedbeard]

Originally posted by Rob:

Something new just popped up, but regarding the usual DX12 crashes, will that ever be fixed? Its been 6 months now...

No clue.
Popping up a quite a number of titles.

Tried deleting all the nvidia DLL's?

 Steam/steamapps/common/Ground Branch/Engine/Plugins/Runtime/Nvidia/Streamline/ 

[Hund]

Originally posted by KrisRedbeard:

Originally posted by Rob:

Something new just popped up, but regarding the usual DX12 crashes, will that ever be fixed? Its been 6 months now...

No clue.
Popping up a quite a number of titles.

Tried deleting all the nvidia DLL's?

 Steam/steamapps/common/Ground Branch/Engine/Plugins/Runtime/Nvidia/Streamline/ 

I did not, probably happened since you can now override which DLSS is to be used in the driver (DLSS 4 in this case) which i tried out.

Im more concerned about not being able to use DX12 because thats a lot of performance you are missing out on compared to DX11.

[Hund]

Disabling one thread frame lag in the advanced options seems to prevent these crashes (which also happen on the 5000 series GPU's).

And the error message also says "This runtime check can be disabled with the r.Streamline.DLSSG.CheckStatusPerFrame console variable" so i dont know if you can just disable it so we dont have to fiddle with the console each time.

[KrisRedbeard]

In dev builds, you can add such things to ConsoleVariables.ini.

May work in shipping builds.