RTX 5080 black screens in Baldur's Gate 3. Driver issue or failing GPU?

November 18, 2026 5 answers
Asked by Norlixa.6v

Baldur's Gate 3 has twice frozen my PC with a black screen, stopped audio and fans ramping up. Both crashes produced NVIDIA TDR dumps and required a forced shutdown. The first happened with a GPU undervolt, and the second after returning the GPU to stock.

Can a game or driver problem cause a lockup this severe? How can I narrow it down without assuming the card is faulty?

Answers

_m38!ferrulekite.2

Yes, a game or driver interaction can lead to a GPU timeout and sometimes a full system hang. Fans going fast don't by themselves prove the GPU is defective. Identical TDR dumps also tell you where Windows noticed trouble, not necessarily what caused it.

Keep the GPU at stock and see whether the problem repeats in the same game conditions. If it does, try another NVIDIA driver version and change one thing at a time. Other demanding games and benchmarks are useful comparisons, though passing them won't completely rule out a hardware fault.

Reply to this answer
4t!wickerlathe_683

Check the physical power connection too. Shut the PC down, switch off the PSU and inspect the GPU connector for discoloration or damage. Reseat it fully and make sure the cable isn't pulling on the plug.

If you have another compatible cable or the manufacturer's adapter, that can be a useful test. Don't mix modular PSU cables unless they're explicitly compatible with that PSU.

Reply to this answer
p.581~gasketbadger

Don't overlook the rest of the system just because the dump points at the graphics driver. EXPO is still an overclock, so try the memory at default settings for a while. Check for motherboard BIOS and chipset driver updates too, but change things separately so you can tell what helped.

_x84~mivquari.7:

Back up anything important before a BIOS update, and follow the motherboard maker's instructions. No need to change firmware and memory settings at the same time.

Reply to this answer
_g81~tavmexo.3

Save the dumps and note the time of each crash, then check Windows event logs for errors around those times. A forced shutdown can generate its own events afterward, so don't automatically treat those as the original cause. A tool can help organize the logs, but its diagnosis still needs checking against the actual entries.

Reply to this answer
TORVANI+6x

If you're using any mods, try the same area without them. A mod or a particular rendering situation could expose a problem that doesn't show up elsewhere. That would narrow the trigger, though it wouldn't prove whether the game, driver or hardware is responsible.

Reply to this answer

Add your answer

Answers are reviewed before publication.

Related Discussions