dxvk: Hard crash (whole machine, not just the system) with the latest Nvidia driver
Ok, this one will probably be a bit confusing but my games using DXVK make my machine crash. Not just Linux, the whole machine stops. This has reproduced for a a least a week now (maybe more, I am not sure) with every DXVK app I have on my computer both on Wine and Proton.
After the crash, dmsg seems empty and journalctl -b -1 doesn’t seem to contain any relevant information.
I think, but I am not sure that this issue has appeared after the latest Nvidia driver update (535.54.03). Everything was running smoothly around the beginning of June…
Software information
This reproduces with The witcher 2, both windows version running on Wine (with Lutris) and Steam version running on Proton 8. Also reproduces with Civilization VI on Proton (does not reproduce with Linux version).
This doesn’t reproduce with glmark2 which seem to exclude the problem comes from the nvidia driver.
System information
- GPU: Nvidia GeForce RTX 2070 Mobile
- Driver: 535.54.03
- Wine version: lutris-fshack-7.2
- Proton version
- DXVK version: v2.2 (unknown for Proton)
Apitrace file(s)
I am not sure these will be actually useful. I couldn’t reproduce the issue lauching just wine 'witcher2.exe' > game.log 2>&1.
Log files
Please let me know if you need more informations
About this issue
- Original URL
- State: closed
- Created a year ago
- Comments: 18 (7 by maintainers)
Hi! If you’re interested in the epilogue, the problem came from my laptop’s charger. So absolutely no connection with DXVK.
Still, I wanted to thank you all for helping diagnose the problem.
So it was “the power supply” after all 😃. Happy to hear you figured it out (and thankfully it’s an easy thing to replace).
To be technically correct this excludes the Nvidia OGL driver. There could still be a problem Vulkan-side.
Does
vkcubework?Any particular XID you are seeing in the output of
journalctl -b -1?It’s very unlikely something of this sort is caused by dxvk, anyway. Also, what exactly do you mean by “the whole machine stops”? Is it a hard lock (only reset button works) or can you still ssh into the machine remotely but the display output is frozen?