Forum Discussion
@DarthFDG wrote:
- look into the other crashes and memory leaks at the bottom of the DXDIAG report
In case you're wondering, or @Psycho_Stimpy is, the LiveKernelEvent 141 errors are video driver timeouts: the driver failed to respond within what Windows considers an appropriate interval, so Windows killed the driver. The first order of business when seeing this error is to DDU the driver and install a fresh copy, as described here:
A properly-written application should never produce this kind of error on supported hardware and software. Even if the game is the immediate trigger, the error indicates a problem, or an additional problem, with the graphics driver or the GPU itself.
- puzzlezaddict3 years agoHero+
@Psycho_Stimpy There's a separate thread about crashes post-fight:
https://answers.ea.com/t5/Technical-Issues/Game-crashes-after-Vader-Fight/td-p/12536837
I doubt it'll help, but at least it's a known issue. I have no idea why this is happening for a few people, and to be honest I got tired of troubleshooting my own freezes during the fight itself and switched to story mode to get through it. But perhaps some combination of disabling Raytracing and manually capping fps could help you get past these crashes and back to playing.
About STAR WARS Jedi: Survivor™
Recent Discussions
- 9 hours ago
- 9 hours ago