Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
we tested:
1) delete savefiles and game like the developer posted
2) run as admin
3) turn off the steam overlay
4) gpu driver update
5) verify files
still not working
DXGI_ERROR_DEVICE_REMOVED --- Simply means that the driver has hung and the OS shut it down.
GPU has a thing called 'timing out' when either the hardware's firmware, or the driver (software side) is unresponsive.
And GPU times out, when they go unstable from whatever operations they are doing, which is too high or too low voltage to clock speeds or temps are too hot, or too much power for the workload for it to handle.
And guess what? Firmwares are likely coded to automatically timed out if the response time is longer than 200 or 300ms in latency.
You know when your FPS plummets to 0 for like half a second or such, your GPU can stall because you undervolted it too far and it's tripping over itself.
It's a software issue then. It's possible that the Graphics Drivers are corrupt or the specs on your GPU is a little too unstable due to overclocking. Stalling can happen if not enough power can be provided to the GPU module too.
I'm not sure what else can be said about this error. DirectX is straight up telling you you're getting a removed device error.
It does not matter that this is the 'only' game that does it, you'll have to ensure that your GPU is not unstable.
https://learn.microsoft.com/en-us/windows/uwp/gaming/handling-device-lost-scenarios
There is also mention of 'system changes from a power-saving graphics adapter to a performance graphics adapter'. Especially for laptop users, try force use of dedicated GPU or maximum performance mode so it doesn't go into power saving or otherwise.
But chances are when you reinstall your drivers, DO use DDU (Display Driver Uninstaller) application you can download to cleanly remove all GPU drivers from the computer so you can install a fresh clean driver that is up to date and not likely corrupted.
The reason is, when you use your computer and it crashes or BSOD (Windows 10 doesn't show blue screen anymore, it just simply resets your PC the hard way, or resets your GPU driver which closes your game immediately) your OS file integrity can be corrupted little by little because of read and write operations that is suddenly stopped, cutting it off midway.
So if yesterday it worked with early access and the only thing that changed is the new bg3 version. why should it be a problem with the driver or windows?
As mentioned above it's irrelevant. DirectX is crashing with that error, not the game.
You can try raising the TDR limit, but this is just a bandaid especially if the issue persists and the timeout ends up longer than your new limit.
Again, try force max performance mode or with nvidia you can enable DEBUG mode in the control panel. Laptop users try to disable the IGPU and force use of your dedicated GPU instead.