Fixed my "LowLevelFatalError" Crash

[NoDMoD]

Hi guy, I had a constant:
LowLevelFatalError [File:E:\ASAContinuous\Engine\Source\Runtime\D3D12RHI\Private\D3D12Util.cpp] [Line: 873]
Crash.

I think I fixed it, by increasing virtual memoryi nwindows, from about 5000 to min 8000 and max around 38000.

Maybe this will work for you too.


Edit:
These new changes seem to have fixed the problem now:

- Turn off Antialiasing FXAA in Nvidia system panel.
- In REGEDIT:
-- Change the value of "TdrDelay" to 24 instead of 8
-- ADD "TdrDdiDelay " and set value to 24

[Forbhidden]

didn't work for me.
still crashes, mostly when i open my fridge. or when i open a box.

tryed in singleplayer without any mods or on the server i play with a hand full of mods. makes absolutely no difference.

i play on a i9, 128gb ram with an rtx 4090.


i play on max graphic settings with 75...150fps. absolutely nothing to worry there. but since the patch 2...3 days ago i get these problems and crashes.

tried every voodoo i found in several discussions here so as your tip too.

finally i'm sure as long as the devs don't fix this problem, the game was a waste of money for me because it's unplayable.

[NoDMoD]

Originally posted by Forbhidden:

didn't work for me.
still crashes, mostly when i open my fridge. or when i open a box.

tryed in singleplayer without any mods or on the server i play with a hand full of mods. makes absolutely no difference.

i play on a i9, 128gb ram with an rtx 4090.


i play on max graphic settings with 75...150fps. absolutely nothing to worry there. but since the patch 2...3 days ago i get these problems and crashes.

tried every voodoo i found in several discussions here so as your tip too.

finally i'm sure as long as the devs don't fix this problem, the game was a waste of money for me because it's unplayable.

Have you turned off the inventory transition effects in UI options?

[BigAlek]

Originally posted by NoDMoD:

Hi guy, I had a constant:
LowLevelFatalError [File:E:\ASAContinuous\Engine\Source\Runtime\D3D12RHI\Private\D3D12Util.cpp] [Line: 873]
Crash.

I think I fixed it, by increasing virtual memoryi nwindows, from about 5000 to min 8000 and max around 38000.

Maybe this will work for you too.

Didnt work for me ether

[daveola1]

Roll out to 3rd person view prior to opening ANY inventory and storage. See if that fixes it for now.

[VibezZ]

Originally posted by Forbhidden:

didn't work for me.
still crashes, mostly when i open my fridge. or when i open a box.

tryed in singleplayer without any mods or on the server i play with a hand full of mods. makes absolutely no difference.

i play on a i9, 128gb ram with an rtx 4090.


i play on max graphic settings with 75...150fps. absolutely nothing to worry there. but since the patch 2...3 days ago i get these problems and crashes.

tried every voodoo i found in several discussions here so as your tip too.

finally i'm sure as long as the devs don't fix this problem, the game was a waste of money for me because it's unplayable.

Try turning off DLSS and Nvidia Reflex im fairly sure thats the issue. I turned them off and havent had a single crash since.

Ive also heard that max settings can result in crashes so try also turning off foliage/water interactions and volumetric clouds and hopefully that stops it.

I play on medium sttings with a few things turned on high. Volumetric clouds, water reflections and fog off and no foliage/water interactions and make sure menu transitions are turned off too.

[NoDMoD]

Originally posted by Forbhidden:

didn't work for me.
still crashes, mostly when i open my fridge. or when i open a box.

tryed in singleplayer without any mods or on the server i play with a hand full of mods. makes absolutely no difference.

i play on a i9, 128gb ram with an rtx 4090.


i play on max graphic settings with 75...150fps. absolutely nothing to worry there. but since the patch 2...3 days ago i get these problems and crashes.

tried every voodoo i found in several discussions here so as your tip too.

finally i'm sure as long as the devs don't fix this problem, the game was a waste of money for me because it's unplayable.

I also just crahsed again. False alarm, it didn't fix it.

But differetn error this time:

LowLevelFatalError [File:E:\ASAContinuous\Engine\Source\Runtime\D3D12RHI\Private\D3D12Util.cpp] [Line: 873]
PresentInternal(SyncInterval) failed
at E:\ASAContinuous\Engine\Source\Runtime\D3D12RHI\Private\D3D12Viewport.cpp:633
with error DXGI_ERROR_DEVICE_REMOVED

[NoDMoD]

With the latest edits I had no more crashed and actually set my settings higher. The game looks better now and runs better.

[Vikinglord]

Originally posted by NoDMoD:

With the latest edits I had no more crashed and actually set my settings higher. The game looks better now and runs better.

How did you stop the crashing

[viv]

Where did you get the idea with changing the tdr value? Note that I don't say you shouldn't set the tdr delay value higher. But that's not meant to be used by normal users. Simply spoken, it would set the allowed time for the graphic card to react to (graphic) commands (before kernel goes into panic) higher, and although there is a certain space to increase the value, there are limits. '8' is an estimation by the vendors and experience, a bit strict perhaps. Don't put the tdr delay aggressively too high. If something happens to the graphic card, the kernel won't be able to prevent damage if you set it too high. (That's the danger.)

But *if* changing tdr values *helped* for Ark playing, then it (unfortunately) means that the graphic card wasn't responding in time *before* the tdr delay value was changed. And now it doesn't because you changed the rules. To go against the root cause, optimize the game (developer, yeah sure...) or reduce graphic setting (user).
https://learn.microsoft.com/en-us/windows-hardware/drivers/display/tdr-registry-keys
Please use tdr delay changes (only) non-permanently. A slight increase might also be ok for long term usage.

[NoDMoD]

Originally posted by Vikinglord:

Originally posted by NoDMoD:

With the latest edits I had no more crashed and actually set my settings higher. The game looks better now and runs better.

How did you stop the crashing

I reverted my Nvidia Driver to an older Studio version, the only thing that helped.

[Vikinglord]

Originally posted by NoDMoD:

Originally posted by Vikinglord:

How did you stop the crashing

I reverted my Nvidia Driver to an older Studio version, the only thing that helped.

How you do that?

[Kali]

still crashing with studio driver

[Automatic12pro]

How many of those here have intel CPU's? FYI there's a known issue with MB default bios settings pushing them beyond capability and could be your root cause

[prostobizon]

Hello! Try disable"water and foliage interaction"

[NoDMoD]

Originally posted by Vikinglord:

Originally posted by NoDMoD:

I reverted my Nvidia Driver to an older Studio version, the only thing that helped.

How you do that?

In your geforece experience. You can chose which drivers to use