Following up. After extensive testing I can confirm nothing to do with software whether its the OS, DirectX, drivers, or repairing the game matters.
On jedha you will get device hung errors at some point most likely.
As suspected in my last post. An increase of SOC voltage directly effects the frequency of my crashes on Jedha running 4k epic with Ray tracing. I am now running 1.30v SOC. The max I can on my 7950x3d. 8 hours on Jedha 1 crash in cutscene. At 1.25 SOC crashes every 5-15 minutes. My RAM is doing nothing special. Standard 6000mhz CL30 everyone runs. Not really overclocking my CPU. You can't do much of that anyway with an x3D. You can only change the voltage curve.
Temps are all fine. Rock solid stability in everything else. Yet there is an improvement when I up SOC and a drastic one at that. So, who is to blame here? AMD and Intel for releasing unstable hardware that can't really run pcie express 4.0 GPUs at safe SOC or the developer? To me quality assurance is bad right now on PC hardware. AMD let their chips be released at 1.4 SOC set as default on motherboards then chips starting combusting and now they just pull 1.3SOC out of their *? Who really knows if that is safe either but I need to run 1.30 SOC to get through Jedha and even then I experienced this error at least once so far. I will try increasing my VDDIO again up to 1.4v Nothing I can do now about the SOC unless I want blow my chip up.
Jedha is the ultimate gaming rig stress test for some reason. Whether its really respawns fault or not it would be nice if somehow their was an update to make this level run more friendly with RT on. There are seemingly hundreds of people on forums with this issue at a minimum. Not to mention unreported cases.
Good to know PC gaming is back to basics in 2023 where we have to customize voltage in the motherboard BIOS just to get a game to not crash every 5 minutes.
RTX off and still LowLevelFatalError [File:Unknown] [Line: 686] pResource->Map(Subresource, pReadRange, reinterpret_cast<void**>(&pData)) failed at D:\depot\r8branches\r8release\Engine\Source\Runtime\D3D12RHI\Private\D3D12RHIPrivate.h:1253 with error DXGI_ERROR_DEVICE_REMOVED with Reason: DXGI_ERROR_DEVICE_HUNG on every planet.
i managed to pass crash points and frame drops in jeda base and sallon when i stopped running like crazy.It seems game is loading stuff all the time especially after patches
try to WALK the crash points,it will probably work .
I also have this issue.
The most common place I've encountered this issue is around the scrap metal house to the left of the entrance to Ramblers Reach on Koboh.
First crash I had was at the very first green laser door you see when you first meet up with your crew on Coruscant.
The lack of any autosaves outside of meditation points can get really frustrating when crashes make you lose a half hour of progress.
