Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address 0x0000000000000020
put d3d12.dll in this location for some reason after the update even when you verify them it says its missing a file and will download it but when you boot the game it deletes it and only keeps the core so when you add it manually it sticks not sure why but thats the fix
https://www.dll-files.com/d3d12.dll.html
putting dx11 swithes the rendering to 11 instead of 12 which can cause stuttering and issues graphicly if you have dx12 installed this is a workaround what i posted is the fix
thank you! this fixed the start crash for me. I tried the dx11 workaround, it was ok, but as you wrote the performance wasn't the best
I dont understand how is this still not fixed after release and why it happens only to some people..
my man
fixed for me
And...snake oil! Again. I just tested with a default engine.ini (no added tweaks) and the D3D12.dll in D3D12 Folder. The crash is undefeated, and the game randomly runs if/when it decides to. No posted "fixes" have worked yet. Tried them all, and then some.
D3D12.dll is part of directx and is/should be already in your System32 + SysWOW64 Folder, registered system wide.
LoginId:xoxoxoxoxoxoxoxxoxoxo
EpicAccountId:nope!
Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address 0x0000000000000020
SHProto_Win64_Shipping
SHProto_Win64_Shipping
SHProto_Win64_Shipping
Some workarounds do help, you're misinforming people by saying all of them aren't working.
But does this not stop you using certain settings ? I know this may seem a stupid concept, but maybe we let the dev's fix what they broke