VK_ERROR_DEVICE_LOST

[shubh]

I've been getting this error for awhile now whenever the game ends a chapter or i repeatedly esc the game a couple of times.
Tried reaching out to the devs but they only told me to update the drivers and verify the integrity of the game files. :((
QUICK FIX.

So try putting the resolution scale to 1.0
This worked for me
hope it solves the problem <3

[byecam]

was referring to the actual game on steam but i have now installed an older amd driver to see if it will work

[Scoops Robin for DBD]

rogb1970 の投稿を引用：

What worked in 2020 for Nvidia should work now. Basically, you uninstall the GPU driver using DDU (Display Driver Uninstaller) in Safe Mode. Then, when you install the new driver, don't select Express, use the other option, then tick clean install. This will install new Vulkan libraries. Hopefully, you shouldn't encounter the issue again after this.

AMD drivers may have the same clean install option, I only know what worked for Nvidia.

It's best to do a clean install of every new driver as constant overwrites can lead to corruption.

They do, and I've tried that. Still doesn't work.

[rogb1970]

Don't know what else to suggest then, it fixed it before. I know with D3D errors where the device lost error comes up you lower the boost clock on your GPU. Depending on the GPU brand there are utilities where you can do this. If you don't have one then MSI Afterburner works for all brands. Lowering it to 1600 is best.

As I said though that was for D3D games that used Unreal, but, it could still be worth a try in this case. Some games can be finicky when it comes to overclocked GPU's whether you did it or the factory did.

[Scoops Robin for DBD]

rogb1970 の投稿を引用：

Don't know what else to suggest then, it fixed it before. I know with D3D errors where the device lost error comes up you lower the boost clock on your GPU. Depending on the GPU brand there are utilities where you can do this. If you don't have one then MSI Afterburner works for all brands. Lowering it to 1600 is best.

As I said though that was for D3D games that used Unreal, but, it could still be worth a try in this case. Some games can be finicky when it comes to overclocked GPU's whether you did it or the factory did.

I mean that could be it. I do know my GPU is factory overclocked, but that's not really something I want to mess with just for one game. I'll just wait until I someday get a PS4 or a different video card. Both are equally likely.

[rogb1970]

Up to you I guess. At the time I found that fix I was playing a whole slew of Unreal engine titles. That said though, DBH was pretty broken the last time I played it and I don't know what or even if the devs did anything with it.

I'm not even sure what Quantic Dream are up to these days. There was a trailer for a Star Wars game, but, I don't think it's still in development now. DBH is old now and if they haven't moved with the times it could remain that way.

[byecam]

Made a video in short what to do for AMD users with this issue: https://youtu.be/6fO0N0_uVMg

[Scoops Robin for DBD]

Funny thing is, my drivers are older than that and my card it says 22.6 is the latest update, so I'll try those. If it doesn't work then I don't know. At least I should be able to test it easily since for me the crash happens at the very beginning of the game even with the demo.

Nope still crashes as I am walking down the hallway.

[Turpentine]

Setting the exe to Windows 8 compatibility mode worked for me

[Scoops Robin for DBD]

Turpentine の投稿を引用：

Setting the exe to Windows 8 compatibility mode worked for me

Hmm worth a try I guess though I have to reinstall it later haha.

[rogb1970]

Ohh, yeah, I did read about that. I can't remember if it worked or not. Have a search through the forums and see what fixes there were, I know some worked as I completed the game.

[Góngora]

cam94z28 の投稿を引用：

UPDATE: I uninstalled the newest AMD drivers using "Uninstall" in the "AMD Software" app (add/remove programs), rebooted in safe mode, totally removed the drivers with DDU, and reinstalled an older driver. Specifically 22.11.1, because it was the only other driver i had on my hard drive.
After doing all that, it is now working. I got past the area it kept freezing, and have played another 20 minutes without issue.

After 5 hours fighting the error this worked for me, now I've only passed the freezing section, I hope that it keeps working.

I tried everything on youtube and google:
-Deleting shaders
-Unistalling and reinstalling AMD Adrenaline
-Unistalling AMD Adrenaline with DDU in Safe Mode and reinstalling an older version (23.1)
-Using MSI Afterburner to lower the CPU Clock Speed
-Etc.

This was the only fix that worked for me until now, if someone has trouble finding the installer for Adrenaline 22 just follow this link: https://www.amd.com/es/support/kb/release-notes/rn-rad-win-22-11-1

The downloadable is under the "The AMD Software: Adrenalin Edition 22.11.1 installation package can be downloaded from the following link:" section. If for any reason you are unable to download the installer feel free to contact me and I will share it with you, I'm keeping it for the rest of my life xD

If you don't want to open this hyperlinks, which I understand, just google "Adrenalin 22.11.1", and you'll have the page as the first result.

UPDATE: I was able to finish the game and to replay parts to get different paths.

[Puddleglum]

Hi, rolling back to 22.11.1 fixed the problem for me but now I can't get any sound on my computer at all. I reinstalled audio drivers twice already and that didn't do anything to fix it. Any advice?

[neku]

Quantic Dream ought to look at this issue just want to get past freeing androids then progress in the game

[76561199063597985]

Scoops Robin for DBD の投稿を引用：

Sad to see everyone is STILL having this issue 2 freakin' years later.

Just like me 😞

[dodesskiy]

IGHOST6 の投稿を引用：

Scoops Robin for DBD の投稿を引用：

Sad to see everyone is STILL having this issue 2 freakin' years later.

Just like me 😞

22.11.1 did work for me just now. I kept expecting that sound, but it went OK going outside the shop, and to the end of it. The fix is for AMD Radeon, but likely the similar date driver for Nvidia will work too. If we bombard AMD, and or Nvidia they might release the newest fix. But it really was the card driver like the system stated.