Community

Forums

Focused discussion for GPU identification, drivers, Linux, CUDA, workstation setups, and hardware troubleshooting.

How to ask a good question

Use the forums for identification help, driver and Linux problems, workstation or CUDA setups, comparison questions, and corrections that benefit from discussion. Include the exact GPU model, operating system, driver version, and what you have already tested.

Troubleshooting Che...
 
Notifications
Clear all
[Sticky] Troubleshooting Checklist: No Display, Crashes, Black Screens, Driver Resets, and Boot Failures
1 Posts
1 Users
0 Reactions
73 Views
Avatar photo
 Saya
(@site-editor)
Member Admin
Joined: 3 months ago
Posts: 12
Topic starter   [#3]

Before you call a GPU dead, unstable, or “a driver problem,” work through this checklist and post the results. It saves time and makes the diagnosis sharper.

1. Confirm the failure state

  • No signal before the OS loads.
  • Black screen only after the driver initializes.
  • System hard-freeze under load.
  • Driver reset, TDR, or recoverable crash.
  • Reboot loop, artifacting, or only one display failing.

2. Record the exact hardware path

  • GPU model and board partner.
  • CPU, motherboard, BIOS version, RAM, PSU model, case, and cooling.
  • Monitor model, cable type, adapter or dock if any, and which GPU port is in use.

3. Check the obvious before chasing ghosts

  • Reseat the GPU and both ends of the display cable.
  • Use a different known-good cable and a different port.
  • Verify every PCIe power lead is fully seated and not split in a way the PSU vendor warns against.
  • Remove risers, adapters, and unnecessary USB devices for first-pass testing.

4. Separate firmware, driver, and hardware layers

  • If there is no image in firmware setup or during POST, that points away from a pure driver issue.
  • If the fault starts only when the OS loads the display driver, note the exact driver branch and version.
  • If the system fails only under load, log hotspot temperature, fan speed, power draw, and PSU behavior.

5. Reduce variables

  • Revert overclocks, undervolts, custom fan curves, and unusual PCIe settings.
  • Test one monitor at stock refresh rate.
  • If possible, test the card in another known-good system or test a known-good card in the same system.

6. Include evidence

  • Event Viewer or Linux journal entries.
  • Photos of artifacts or board damage.
  • HWiNFO, GPU-Z, or sensor logs.
  • Exact crash messages.

A good troubleshooting thread says what failed, under what conditions, and what changed after each test.



   
Quote
Share: