dxvk
dxvk copied to clipboard
VK_ERROR_DEVICE_LOST with Wow and Thief 2014
In some games randomly getting vk_error_evice_lost error game freezes i can only kill it.
Thief 2014 - Max Settings other than SSAA
System information
- GPU: 1050Ti Mobile
- Driver:450.66
- Wine version: Staging 5.7
- DXVK version: 1.7.1
d3d11.log https://paste.ee/p/j22pY dxgi.log https://paste.ee/p/wKJOe
Thief works fine on my end, please try a different driver version (and newer wine for new extensions, but that shouldn't be causing GPU crashes). Also try latest master
since that contains a workaround for some Nvidia issues.
I had a similar issue when tabbing out of a game where I the resolution is different from the one on my default resolution. Maybe thats how he triggered that?
The Xid message is this one I get whenever this error ocurs: Sep 13 23:52:49 odin kernel: NVRM: Xid (PCI:0000:01:00): 32, pid=315883, Channel ID 000000ab intr 00040000
There's no vulkan app running, just opengl apps like kwin.
Hello again sorry im late. That VK_ERROR_DEVICE_LOST somehow gone by itself. Im not having that anymore, i guess i did built my kernel with -O3 before it started happening. But now i have another problem while playing games with wine sometimes game just hangs, im having to kill it, i havent faced an erro yet but ill keep an eye on it. Im not sure if this is related to DXVK.
I'm trying to spot the reason. I moved to 5.9rc6 kernel and updated to nvidia-drivers-455.23.04 from 450.66
Try the latest master version of DXVK. It contains a workaround for a problem in the latest Nvidia graphics driver.
Try the latest master version of DXVK. It contains a workaround for a problem in the latest Nvidia graphics driver.
You mean the latest state of the git version? I cant because somehow i cant get mingw64 installed. But i already installed the latest nvidia driver.
Today i faced another vk_error_device_lost error with nvidia-drivers-455.23.04 and 5.8 Kernel. I wonder if that's caused by my kernel config. Ill try disabling nvapi hack.
I remember one of the later drivers added an update to Vulkan to 1.2 after a long time at 1.1 I think 1.2 is still not stable enough. Im downgrading nvidia-drivers to 440.100 ill do test run ith it.
You don't need to post the whole Vulkan spec on device loss, we know what it means.
That, and it's completely useless without knowing what exactly is causing the crash anyway. Especially since it's working on other setups.
That, and it's completely useless without knowing what exactly is causing the crash anyway. Especially since it's working on other setups.
Sorry my friend i thought you'd missed it.
Ok ive added option "NoFlip" "True" in nvidia device section of my xorg.conf file. In my Xorg.0.log file it says NVIDIA(G0): OpenGL flipping disabled. After a few hours of gaming the problem hasnt reoccured yet.
I did, at one point in the past, run across a similar problem and it was while using PRIME render offload on an external GPU (on a laptop with Intel HD graphics), but I haven't seen any such behaviour on my current desktop rig. Perhaps these type of multi-GPU setups have something to do with it?
I did, at one point in the past, run across a similar problem and it was while using PRIME render offload on an external GPU (on a laptop with Intel HD graphics), but I haven't seen any such behaviour on my current desktop rig. Perhaps these type of multi-GPU setups have something to do with it?
Yea, maybe because im on prime offloading too. And setting OpenGL Flipping of solved my problem. For the last 2 days there no freezes anymore. Maybe you should mark it as a workaround.
Setting Option "noflip" "true" in xorg.conf, works around the problem.
After 1 week today got 2 hangs in thief after playing a while. first one got recovered after like a 10 second freeze. Second one couldnt recover and needed a kill. So im not sure about noflip it maybe eased a bit but still happens randomly. My next stop will be destroying my wine prefix and creating a new one.
Ok ive reinstalled my OS, Destroyed my prefix, Tried different kernel versions none of them change anything. Now i downgraded my Nvidia-Drivers package to 440.100-r2. Which uses an older Vulkan version. Performance drop is noticable, starting to test it tomorrow.
Installed latest nvdia-drivers package yesterday which is 455.45.01. 1 day past still havent got any vk_error_device_lost errors yet, i hope it goes like that.
Sad news that thing still happening with 455.45.01 may people with the same problem leave some hardware info here? So we can guess what may be causing the hang.
Everything i tried failed, im still having that bug with 460.32.03 driver. Could it be related to dxvk?
Sad news that thing still happening with 455.45.01 may people with the same problem leave some hardware info here? So we can guess what may be causing the hang.
Hey i'm having the same issue with graphically "intensive" games (newer than 2015-ish). Pretty much tried everything you mentioned myself and didn't find anything helpful on the internet so i'm just living with it. Sometimes i can play a whole day without any issues while other times it's hanging constantly. My setup is Ryzen 1600x with a GTX680.
I'm getting the device lost with 1.9.1, but 1.8.1 and 1.9 seem to work fine for me.
It is also a very specific crash and happens usually only at Karazhan on Wednesday. We are there with like a 100 people at the stone and the warlocks are farming shards on horde players trying to run in while we summon even more people. Strangely enough going into AV or any other graphically intensive areas does not seem to crash 1.9.1.
Usually I can stand around and heal my friends for a while, but then a random amount of time later the screen freezes and WoW closes. Upon logging in it only takes a few seconds to crash again.
I'm using the latest Vulkan beta: 470.56.05
edit: Ill try to fetch a log the next time we raid.
@arabcian @sfjuocekr Friendly ping. Please try with latest dxvk and driver if possible. 515 drivers specifically
Oh, I didn't have this issue anymore since 1.10 or 495. I'm currently on 515.49.10 and have been using VKD3D for WoW.
If any of you still have still have this issue just comment here again.