GPU Screen Suddenly Goes Black Mid-Game but the Sound Keeps Playing? Persistent Black Screen, Audio & Display-Chain Diagnosis Guide

Key Takeaways
A black screen with sound still playing means the system is still running, so the fault sits in the display chain, not a full crash. This guide works through the audio path, power light, and on-screen display, then a ten-step decision tree of reset shortcuts, cable and port swaps, and Event Viewer records.
The Symptom, Stated Precisely
You are in the middle of a game. The picture cuts to black and stays black. The game audio keeps playing. Nothing you press brings the picture back, and only a manual restart restores the screen. The desktop was fine before you launched the game, and the problem appeared part-way through play, not at launch.
That exact combination matters, because each part of it rules something out. The sound continuing means the game, the processor, the operating system and the audio path are still running. A machine that has fully crashed does not keep playing game audio. So the fault has narrowed to the display side: the graphics output, the driver state, the cable and connection, the display mode, or the monitor itself. The work of this guide is to narrow it further, one controlled test at a time, without guessing and without replacing parts on a hunch.
This symptom is not the same as several look-alikes on this site, and confusing them wastes time. A screen that goes black for one or two seconds and then recovers on its own is a different problem, covered in the article on intermittent black screens. A screen that goes black, then recovers with a notification that the display driver stopped responding and has recovered, is the driver timeout-and-recovery (TDR) outcome, covered in the TDR article. A machine that goes black and restarts itself the moment a game launches points in a different direction again, towards power delivery, and is covered in the article on black screens at game launch. This guide is only for a persistent black screen mid-game, with audio continuing, that does not recover by itself.
Two Observations That Are Not the Same Thing
Before touching anything, work out which of two things you are actually seeing, because they point in different directions.
A monitor that displays a "No Signal" message is telling you that it has power and that it detects no video input at all. A monitor that shows a plain black picture while its power light stays on may be receiving a signal whose content is entirely black, may have entered standby, or may have a backlight problem. These are two different observations, and the rest of the diagnosis depends on recording the right one. Note which one you see, and note it before you start pressing keys, because the answer may change once you do.
How the Audio Path Changes What "Sound Keeps Playing" Proves
"The sound keeps playing" is the most important evidence in this article, but it does not always prove the same thing. Which audio path the sound takes changes the conclusion, and this distinction has to be made explicitly.
If the sound comes through separate speakers or headphones — a 3.5 mm jack, USB headphones, or Bluetooth — it proves only that the host machine and the game are still running. It proves nothing about the display chain, because that audio never travels through the display cable.
If the sound comes through the monitor's built-in speakers over the same HDMI or DisplayPort cable, the situation is different. On those connections, audio packets travel in the blanking intervals of the video signal, so audio and video share the same transport chain. Sound continuing while the picture is black then means the chain has not completely broken: the suspicion moves towards the video path, the output encoding, or the display mode, rather than a cable that has fully failed. Record which path your audio takes before drawing any conclusion from it.
The Three Pieces of Evidence to Record First
A third independent piece of evidence comes from the monitor itself. The monitor's on-screen display (OSD) menu is drawn by the monitor, without passing through the graphics card or the cable. Pressing the monitor's menu button during the black screen therefore tests the monitor on its own. If the menu appears normally over the black picture, the panel and backlight are alive, and the suspicion goes back upstream, before the video input: graphics output encoding, the cable, the connector, or the mode. If the menu cannot be seen at all, the suspicion moves towards the monitor's power or backlight.
The monitor's power light is a related but separate record. A light that is off points towards the monitor's own power, a subject covered in the article on monitors switching themselves off. A light that has changed to its standby colour suggests the monitor is receiving no signal and has entered standby. A light that stays its normal colour while the picture is black suggests a signal is arriving but its content is black, or a backlight problem. Record the light's state, the OSD result, and the audio state together, before running any test.
What TDR Is, and What It Is Not in This Symptom
Windows has a built-in mechanism called Timeout Detection and Recovery (TDR). If the graphics processor does not complete its work within a default limit of 2 seconds, Windows judges the driver to have stalled and resets the display driver. When the reset succeeds, the screen usually goes black or flickers briefly and then recovers, and Windows records Event 4101 in Event Viewer, from the source "Display", with the message that the display driver stopped responding and has successfully recovered.
That successful reset is the ending of the TDR article, not of this one. This article starts from the premise that the picture does not recover and no notification is visible. A failed reset, or too many resets repeated within one minute, can instead end in a blue screen with the code VIDEO_TDR_FAILURE (0x116). A related record, LiveKernelEvent 141 (VIDEO_ENGINE_TIMEOUT_DETECTED), records a single graphics engine timing out and being reset while the machine keeps running; it is an engine-level reset, not a whole-card timeout. These numbers and codes may only be stated in this way. The presence of Event 4101 cannot be read as proof that a particular part has failed, and the frequency of the records matters more than any single occurrence.
The Ten-Step Decision Tree
Work through these steps in this order. Each step is a controlled test with a readable result. Do not skip ahead to reinstalling drivers, and do not change two things at once.
Step 1: Wait 30 seconds and do not press the power button
A TDR reset needs a few seconds to complete. Forcing the machine off immediately loses unsaved progress and adds a Kernel-Power Event 41 (unexpected shutdown) to the event log, which interferes with later judgement. Wait 30 seconds. If the picture returns by itself, follow the TDR article's path: the driver reset and recovered, and this is not the symptom this guide covers.
Step 2: Record the sound, the power light, and the OSD
Note three things: whether the game audio is still playing and through which path (monitor speakers or separate speakers); what state the monitor power light is in (normal colour, standby colour, or off); and whether pressing the monitor's menu button shows the OSD. A power light that is off points towards the monitor power direction. An OSD that cannot be seen points towards monitor power or backlight. A normal OSD means the panel and backlight are alive, so continue down the display chain.
Step 3: The Caps Lock light test
Press Caps Lock and watch whether the keyboard light responds. A light that responds means the system is still running, so continue with the display-chain checks. A light that does not respond suggests the problem may go beyond the display, in which case stop: do not force this guide's decision tree onto a machine that may be frozen as a whole, and a full-system check is needed instead.
Step 4: Win + Ctrl + Shift + B
This is the display-driver reset shortcut documented in Microsoft's own support material on troubleshooting blank screens in Windows. Press the four keys together once and wait a few seconds, listening for a beep and watching for a flicker. A successful reset produces a brief flicker and a beep. It does not restart the machine, does not close programs, and does not change the driver version.
If the picture returns, the fault points towards the driver or compositor state — but a reset is not a repair. It clears the immediate symptom without changing the driver version, clearing leftovers, or addressing the underlying cause, so the driver layer still needs follow-up (see Step 8). If there is no beep and no flicker, the system may not be receiving the input at all, so continue.
Step 5: Win + P to cycle display modes
Windows may have sent the picture to a different display — one that does not exist, or one that is asleep. Press Win + P, then press P to cycle through the modes and Enter to confirm each one, trying "PC screen only" in particular. If one mode brings the picture back immediately, Windows was sending the picture to the wrong display, and the follow-up is a settings check. If every mode stays black, continue.
Step 6: Switch the monitor off and on again
Use the monitor's own power button to switch it off, wait a few seconds, and switch it on again. This is not a restart of the computer. It forces the monitor to re-detect its input and renegotiate the handshake with the graphics card. If the picture returns, the fault points towards the handshake or signal-negotiation state. Do not describe this as "the monitor was broken and fixed itself"; it only shows that the state layer had a problem, and the monitor hardware itself is neither cleared nor convicted by this result. If the picture does not return, continue.
Step 7: Swap the cable, then the port — one at a time
First swap the cable for another one known to be good and of sufficient specification, and test. Then swap to a different port of the same type on the graphics card, and test. Never swap the cable and the port at the same time, because then you cannot tell which change mattered. If the picture returns immediately after a swap, the original cable or port was not keeping up under load. If every combination stays black, continue.
Step 8: The driver layer — only after Steps 4 to 7, or when the fault repeats
Check the driver version date and whether a driver or Windows update happened recently. A clean driver reinstall using Display Driver Uninstaller (DDU) is a last resort, and the DDU process itself is covered in the dedicated articles on this site, not repeated here. Do not call for a driver reinstall before Steps 4 to 7 have been done.
Step 9: Collect the evidence after a manual restart
Once you have restarted the machine manually, open Event Viewer (Windows Logs, then System) and look at the records around the time of the incident: Event 4101 from the source "Display" means the driver timed out and was reset; LiveKernelEvent 141 means a single engine timed out and was reset; a 0x116 blue screen means a reset failed; Kernel-Power Event 41 means only that Windows detected an unexpected shutdown — quite possibly the forced shutdown you performed yourself — and cannot be read as proof that the power supply has failed. Records are clues, not convictions. A single incident, with a long gap before the next, may not need major action. Several incidents in one day, or a rising frequency, is worth following up seriously.
Step 10: Four possible endings
Each ending has its own next step, and none of them is simply "send it for repair" as the only conclusion.
| Ending | What the test showed | Next step |
|---|---|---|
| Handshake or signal state | Switching the monitor off and on brought the picture back | Check the cable, port, and display settings; note whether it recurs |
| Driver state | The reset shortcut brought the picture back | Follow up the driver layer: version history, recent updates, clean reinstall as a last resort |
| Cable or port | Swapping the cable or port brought the picture back | Replace the faulty cable or stop using the faulty port; re-test under load |
| Not narrowed down | No test changed anything | Stop and seek a professional inspection with cross-testing; do not open the card, change voltages, or flash firmware |
Boundary Cases
The decision tree above assumes the core symptom. Several nearby situations belong on different paths, and recognising them early saves wasted work.
- The black screen appears in only one game, while other games are normal: the suspicion moves towards the program layer, and the articles on game crashes and game-file checks are the right direction.
- The black screen appears exactly when switching to fullscreen, pressing Alt+Tab, or during a scene transition: this is a mode-switch problem, covered in the article on black screens during mode changes.
- Only the secondary monitor goes black while the main monitor stays normal: this is the exclusive-fullscreen desktop-recomposition problem, covered in the article on secondary monitors going black.
- The picture flickers or shows artefacts for a while before going black: this may be the lead-up to the same fault. Record the order — artefacts first, then black, versus black with no warning — because that order is itself a clue when the machine is inspected.
- The sound also stops and the keyboard light stops responding: this is not this article's symptom. The machine may be frozen as a whole, and the power-supply and full-freeze directions are the right ones.
- The whole machine restarts itself after the black screen: this points towards power or protection, covered in the articles on black screens at launch and power delivery.
- The black screen already happens at startup or login: that is the startup and login black-screen direction, not mid-game.
- The black screen only happens after waking from sleep: that is the sleep and wake direction.
- The black screen only happens while watching video or in a browser: that is the hardware-decoding and application-acceleration direction.
- The monitor power light is off: that is the monitor-power direction.
- On a laptop with an external monitor: the built-in screen and the external screen must be discussed separately, including lid and output-path behaviour.
Common Mistakes
- "A black screen means the machine has died." Wrong. Audio continuing and the keyboard light responding mean the system is still running; only the display output layer has failed.
- "A black screen means the graphics card has burned out." Wrong. Driver state, handshake, cable, mode, and monitor power can all make the picture black while the card itself is fine. No such conclusion can be drawn before the Step 4 to 7 tests.
- "Holding the power button to force it off is the fastest fix." Wrong. Forcing the machine off is a last resort, not a first step. It loses unsaved progress, interferes with the event record, and proves nothing. The reset shortcut and switching the monitor off and on should be tried first.
- "Win + Ctrl + Shift + B is a repair." Wrong. It only resets the display driver state and clears the immediate symptom. It does not change the driver version or clear leftovers. If it has to be used repeatedly, the underlying cause has not been addressed.
- "Event 4101 appearing means the graphics hardware is faulty." Wrong. Event 4101 only records that the driver timed out and was reset. The cause could be the driver, power delivery, heat, overclocking, or a program instruction; frequency, other records, and controlled tests are needed before any direction can be stated.
- "Kernel-Power 41 means the power supply is faulty." Wrong. Event 41 only means Windows detected an unexpected shutdown, and a manual forced shutdown produces one too. It cannot convict the power supply on its own.
- "Swapping the cable rules out all cable problems." Wrong. Swapping the cable only rules out that one cable. The port, the adapter, and whether the cable's specification is enough for the mode in use have to be tested separately, one change at a time.
- "No Signal means the graphics card has no output." Wrong. "No Signal" only means the monitor receives no input; the cause could be in the cable, the port, the input selection, the handshake, or the graphics output encoding.
- "Raising the TDR delay in the registry fixes black screens." Wrong. Microsoft describes the TDR registry settings as for testing and debugging, not as a routine fix. Lengthening the limit only delays the trigger; it does not address the underlying cause. This guide does not teach or recommend registry changes.
Power Spikes and Heat: Still on the List, Not the Main Suspect
Power and heat remain on the suspect list, but they are not the main subject of this article. Published troubleshooting sources list driver crashes, a power supply struggling with transient power spikes, graphics-card heat triggering display-output protection, and loose or damaged cables among the causes. The distinction to keep is this: if the whole machine restarts or loses power by itself, the direction is power delivery. If only the picture goes black while the system keeps running, the power suspicion is downgraded — but not excluded — because display-output protection switching off is a different thing from the whole machine losing power.
On heat, one rule applies throughout: temperature can only be discussed by comparison with the machine's own usual readings. No universal temperature threshold is given in this guide, and none should be applied. Hardware-accelerated GPU scheduling (HAGS) and overlay or recording software are also mentioned only as a one-line diversion: HAGS on-off testing is covered in the dedicated article, and overlay and recording conflicts are covered in the articles on those subjects.
What This Article Cannot Conclude
Without opening the machine and running cross-tests, no single black screen can be attributed to a particular part. This guide can only say which direction the evidence points, never which part has failed. It cannot be stated that heat triggering display-output protection is a confirmed mechanism: sources list it as one possible cause, without public documentation of which models or conditions behave that way. No driver version or game can be singled out as especially likely to cause this symptom unless the manufacturer has published a known-issue document; the only legitimate check is whether an update happened recently. And switching the monitor off and on bringing the picture back cannot be written as "the monitor is faulty" or "the monitor is fine" — it only proves a problem at the handshake or state layer, with the monitor hardware itself still neither excluded nor convicted.
Frequently Asked Questions
The screen went black mid-game but the sound kept playing. Is my computer dead?
No. If the game audio is still playing and the keyboard light still responds, the system is still running. The fault is in the display chain, not a full crash. Work through the decision tree in this guide, starting with waiting 30 seconds and then recording the audio path, the monitor power light, and the OSD result.
What should I try first when the screen goes black?
Wait 30 seconds, then press Win + Ctrl + Shift + B once and wait a few seconds for a beep or flicker. That resets the display driver without restarting the machine. If nothing happens, try Win + P to cycle display modes, then switch the monitor off and on again to force a fresh handshake.
What does "No Signal" mean compared with a plain black screen?
"No Signal" means the monitor has power and detects no video input at all. A plain black picture with the power light still on may mean the monitor is receiving a signal whose content is entirely black, has entered standby, or has a backlight problem. Record which one you see before running any test, because the two observations point in different directions.
Does Event 4101 in Event Viewer mean my graphics card is broken?
No. Event 4101 only records that the display driver timed out and was reset. It is a clue, not a conviction. Its cause could be the driver, power delivery, heat, overclocking, or a program instruction. Frequency matters: a single isolated record is different from several in one day.
My computer restarted itself after the black screen. Is that the same problem?
No. A machine that restarts itself points towards power delivery or protection, which is a different direction from this article's symptom, where the system keeps running and only the picture is lost. The articles on black screens at game launch and on power delivery cover that path.
When should I seek a professional inspection?
When every test in the decision tree changes nothing, when the black screen happens several times a day and the frequency is rising, or when the Caps Lock test shows the system itself has stopped responding. Bring the notes you recorded: which audio path was playing, the power-light state, the OSD result, which test (if any) brought the picture back, and the Event Viewer records around the time of the incident. Our shop is at Room 1209, Dali Plaza, Shek Mun; telephone 2186 8010; WhatsApp 6558 6806. There is no home-visit service. Diagnosis is charged within the published three-tier pricing of HK$400 to HK$2,800.