@WhiskeyTourettes wrote: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.
Well I got to fight a surprising main boss 15 times. Not because the boss was too hard but because the game kept crashing halfway through the fight. I lowered my RAM down to base JEDEC voltage timings and frequency. In other words the standardized spec that should basically always be stable. Still getting this error. I cant increase my SOC voltage to stabilize the PCI express signaling anymore. I dont know what to do at this point. Either game is broken or certain hardware can't run this game stable. I see alot of people on the latest gen hardware both Intel and amd complaining.
I turned Ray tracing off and I was able to complete this boss on Jedha. Im not saying the name of the boss so I dont spoil anything but im sure the tech support could take a guess here and get it right.
I'm interested in this direction of thought - I have my SOC set at 1.3V (7900x CPU on Asus Strix motherboard, DDR5 6000MHz RAM) and since the bios was patched I cannot increase more than that.
I'm wondering about downgrading my bios to an old one or trying to force the PCIE bus to gen 3 or something to see if it plays nicer.
Have you had any further progress?
I don't recall the timing but I had ZERO crashes for days as of purchasing release day and then I began to get crashes at the known hot spots (first was cutscene leaving coruscant - I just skipped it and fine).
I had no "Device Hung" crashes and then suddenly they began to appear after game patch. Now I cannot even get into the game.
It will fail to work 30x in a row and then a few hours later be just fine.
I wish EA/ Respawn would pull their finger out and do something with this or have the balls to acknowledge they can't fix it... because I want to know if I will refund or not.
Australian Consumer Guarantees mean EVERY Australian who has a crashing game is entitled to a refund because it is not materially what was promised - and that has no timeframe. Even STEAM ack that now.
