Product: STAR WARS Jedi: Survivor
Platform:Steam-PC
Summarize your bug Since the patch I have been unable to load my save as the game crashes a few sections after clicking "continue", showing the eroor message: LowLevelFatalError [File:Unknown] [Line: 743] pDevice->GetTextureAllocator().AllocateTexture(TextureDesc, ClearValue, Format, *OutTexture2D, InitialState, Name) failed at D:/depot/r8branches/r8release/Engine/Source/Runtime/D3D12RHI/Private/D3D12Texture.cpp:805 with error DXGI_ERROR_DEVICE_REMOVED, Size=128x128x1 Format=(0x00000061), NumMips=8, Flags= My game was actually running alright prior to the patch and it now unplayable, please fix rapid
How often does the bug occur? Every time (100%)
Steps: How can we find the bug ourselves? UNsure if it is the same on all games but it happens when i choose to continue my save
What happens when the bug occurs? Jedi:Survivor Crash reporter comes up with option to send report and close (which i have)
What do you expect to see? A playable game! for over £50 you would expect to at least be able to play through some of the early teething bugs
Hi Guys,
Just started seeing this error myself on the desert planet. This is not the first game I've ever seen this behavior with. I am running a new build. SOC voltage at least on AMD Ryzen systems needs to be dialed in right. It can affect pcie-express devices such as a graphics card. I am considering giving my soc voltage a small bump even though everything seems stable otherwise. I find the stock SOC voltage on Ryzen to always be crap. Every build I have to mess with it to get the system stable
Before I do that I will try turning off TdrLevel in the registry. This is something I had done on my previous build. It def can eliminate this type of error. Usually people say this is a driver error but I've never found that re-installing my driver helps with this tbh.
See URL which has directions. Hopefully this will help me and others. I will report back findings.
Seems CTD when I try to just launch the game...
LoginId:3c59b9141b0ea56a5825e0f364c43128
LowLevelFatalError [File:Unknown] [Line: 686] hr failed at D:/depot/r8branches/r8release/Engine/Source/Runtime/D3D12RHI/Private/D3D12Resources.cpp:507 with error DXGI_ERROR_DEVICE_REMOVED with Reason: DXGI_ERROR_DEVICE_HUNG
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 .
@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.
Bottom line this is the display driver crashing. You will find corresponding nvddm errors and windows reporting errors. All survivor is doing is reporting the display adapter was removed. This really need to be fixed by Nvidia.
Now survivor could more gracefully handle this error by pausing game and waiting for driver to reappear.
i think most of the fixes on this and other threads for this error are false fixes, it seems that rebooting the computer is effective for me as any other fix. This could indicate a time base / cache issue. But unclear.
