Second Monitor Goes Black When a Game Enters Fullscreen Exclusive, but Returns on the Desktop? Exclusive-Mode Desktop Rebuild, Signal & Monitor Sleep Diagnosis Guide

Key Takeaways
When a second monitor goes black the moment a game enters fullscreen exclusive mode and returns as soon as the game exits to the desktop, the pattern itself is the diagnosis: this guide uses the enter-and-exit test, the monitor's own power and signal signs, and single-variable display checks to separate exclusive-mode behaviour from cable, sleep, and monitor faults.
What Exactly Counts as This Symptom
This guide deals with a narrowly shaped symptom, and the shape has to be matched before anything is changed. Two monitors are connected and both work normally on the desktop. A game is launched on the main monitor in fullscreen exclusive mode, and at that moment the second monitor goes black and stays black for the whole gaming session. Nothing on the second monitor is visible: no desktop, no windows, no video, no chat window. The game itself on the main monitor plays normally. When the game is closed, or when it returns to the desktop, the second monitor comes back, showing the desktop again as if nothing had happened.
The duration is the defining feature. The second monitor is not black for a few seconds at the switch and then fine. It is black for the entire time the game holds exclusive fullscreen, and it returns when exclusive fullscreen ends. That whole-session shape is what separates this guide from the mode-switch guide, where a screen goes black only briefly at a transition and then returns on its own. It also separates this guide from a monitor that powers itself off, where the monitor needs its power button pressed before it will show anything again. Here, no button press is needed: leaving fullscreen is enough.
Several lookalike situations must be ruled out first. A second monitor that goes black at random moments during ordinary desktop use, with no game involved, is not this symptom. A main monitor that blacks out while the second monitor stays fine is a different symptom, belonging to the main display rather than the second. A second monitor that stays black after the game has closed, until the machine is restarted or the monitor is power-cycled, is not this symptom either, because the return-on-desktop feature is missing. And a second monitor that stutters, tears, or plays unevenly while the game runs, but never actually goes black, is a playback-timing problem, not a black-screen problem. If the second monitor is black for the whole fullscreen session and back on the desktop, this guide applies.
The Mechanism: Exclusive Fullscreen Takes the Display
To understand this symptom, it helps to understand what exclusive fullscreen actually does, because it is quite different from an ordinary maximised window. On the desktop, a component of the operating system called the desktop compositor takes the picture from every open window, combines them, and presents the combined desktop to each monitor. Every window is composited, including windows on the second monitor, and the compositor is in charge of all displays at once.
A game in exclusive fullscreen steps outside that arrangement. It asks the graphics driver for direct, exclusive control of the main display, bypassing the compositor for that display so that it can present its own frames with as little delay as possible. The driver hands the main display over to the game, and the compositor steps back from that display for as long as the game holds it. That handover is the point of exclusive mode, and it is also the point where the second monitor can be affected.
What happens to the second monitor during that handover depends on how the driver, the game, and the monitor negotiate the change. In some arrangements, the driver keeps the second output active and the compositor keeps presenting the desktop there, and the second monitor stays lit. In other arrangements, the driver suspends or drops the second output while the game holds the main display, or the mode change on the main display causes the whole display arrangement to be re-detected, and the second monitor stops receiving a signal. A monitor that stops receiving a signal does what monitors are designed to do: it shows a no-signal message, or it drops into a low-power standby state, and its screen goes dark. The monitor is not broken in that sequence. It is reacting correctly to an absent signal.
When the game exits exclusive mode, the driver hands the main display back, the compositor resumes control of all displays, and the signal to the second monitor is restored. The monitor wakes from standby, the desktop reappears, and the session looks as though nothing happened. That clean return is itself evidence: a monitor that was truly faulty, or a cable that was truly broken, would not reliably heal itself at the exact moment the game exits, every single time.
There is a second mechanism that can produce the same visible result, and it must be separated from the first. Some monitors and some power settings treat a sustained absence of signal as a reason to enter a deeper sleep, and some games and drivers change the refresh rate or the colour mode of the main display in a way that forces the second monitor to re-negotiate its own signal and fail to do so. In those cases the second monitor is still reacting to the exclusive-mode handover, but the chain of events runs through a sleep setting or a mode negotiation rather than through a simple suspended output. The tests below are designed to separate those chains, because they lead to different responses.
A third possibility should be stated plainly so it is not confused with the first two: the game itself may be configured, by default or by an earlier setting, to blank or disable other displays while it runs. Some games offer multi-monitor options, and some driver settings govern how secondary displays behave during fullscreen play. In that case the black second monitor is not an accident of the handover at all, but a setting doing what it was set to do. The tests below include a settings check for exactly that reason.
Step One: The Enter-and-Exit Test, Repeated
The decisive first test changes no setting at all. Launch the game in fullscreen exclusive mode, note whether the second monitor goes black, play briefly, then exit the game to the desktop and note whether the second monitor returns, and how quickly. Repeat the cycle a second time with the same game. Record the result in plain words: black on entering, black throughout, back on exiting, both times.
Repeatability is the evidence. A second monitor that blacks out on entering and returns on exiting, twice in a row, with the same timing, is showing a pattern tied to exclusive mode, not a random signal drop. A second monitor that blacks out only once, or returns only after a delay or a button press, is showing something else, and the later steps about sleep and power must be given more weight. A vague memory of the pattern is not enough: the enter-and-exit cycle must be observed deliberately, because every later test is judged against it.
While running this test, also note what happens to the windows that were on the second monitor. If they stay where they were and reappear in place when the desktop returns, the system most likely kept the second display in its arrangement throughout, and only the signal was suspended. If the windows migrate to the main monitor during the game and have to be moved back afterwards, the system most likely dropped the second display from its arrangement and re-detected it on exit. Both outcomes are consistent with an exclusive-mode cause, but they point at different parts of the chain, and the distinction is useful when advice is sought later.
Step Two: Read the Monitor's Own Signs While It Is Black
While the second monitor is black during a game session, look at the monitor itself before touching any setting. Note whether its power light stays on, changes colour or pattern, or goes out entirely. Note whether the screen shows a no-signal message, a message naming an input, or nothing at all. Note whether pressing a monitor menu button brings up the monitor's own on-screen menu. These signs are the monitor reporting its own state, and they separate three situations that look identical from the chair.
A monitor whose power light stays on, whose screen shows a no-signal message, or whose own menu still appears is powered, awake, and waiting for a signal it is not receiving. That points at the signal chain: the driver, the game mode, or the display arrangement. A monitor whose power light goes out, or which needs its power button pressed before it shows anything again even after the game has closed, is behaving as a monitor that powered itself down, and that points at sleep or power behaviour rather than at exclusive mode alone. A monitor whose own menu does not appear at all, even when its buttons are pressed, is not responding as a powered monitor should, and that points at the monitor or its power supply rather than at the game.
This step must be done while the game is still running, because the signs change the moment the game exits. A monitor inspected only after the desktop has returned will always look normal, and the evidence will have been lost.
Step Three: Is the Display Still Detected While It Is Black?
Still during a game session, or immediately after noting the monitor signs, check whether the system still believes the second display exists. This can be checked from the game session only indirectly, so the practical version of the test is done at the boundary: exit the game, open the display settings, and confirm the arrangement is still the expected extended desktop with the correct monitor identified as the second display. Then, in a second run, use a remote or secondary means of checking if available, such as asking whether audio or notifications routed to the second display still behave as though it exists. The key question is whether the second display vanished from the arrangement or merely lost its signal while remaining in the arrangement.
If the arrangement is intact on return and the windows stayed in place, the display was most likely kept in the arrangement with its signal suspended, which is the classic exclusive-mode pattern. If the arrangement has to be re-detected, or windows migrated, the handover most likely dropped the display, and the investigation should give more weight to driver behaviour and display re-detection. Either result still belongs in this guide, but the two results lead to different emphases in the later steps, and recording which one occurred prevents the later steps from being applied blindly.
Step Four: The Borderless Diagnostic Test
Change one variable only: set the same game to borderless windowed mode, if the game offers it, and run the same session again. Borderless windowed mode keeps the game inside an ordinary window that covers the main screen, with the desktop compositor still in charge of all displays, so the exclusive handover does not happen. Note whether the second monitor stays lit throughout the session.
If the second monitor stays lit in borderless mode but goes black in exclusive mode, the exclusive handover is confirmed as the trigger. That result does not settle which mode is better in general, and this guide does not recommend one mode over the other as a permanent choice. The borderless run is used here purely as a diagnostic comparison: same game, same monitors, same cables, only the display mode changed, and the symptom followed the mode. If the second monitor goes black in borderless mode as well, exclusive mode is not the trigger, and the investigation must move to the cable, port, and monitor tests below, because a mode-independent black screen has a different cause.
Step Five: One Game Setting at a Time
If the borderless test confirms exclusive mode as the trigger, work through the game and driver settings one at a time, returning to exclusive mode for each test. Check whether the game offers a multi-monitor or secondary-display option and what it is set to. Check the refresh rate of the main display in the game against the refresh rate of the second monitor, and test with the game's refresh rate set to match the desktop setting. Test with variable refresh and high-dynamic-range options in the game switched off, one at a time, if the game and the monitor offer them. After each single change, repeat the enter-and-exit test and record whether the second monitor stayed lit.
Each result has a specific meaning. If a single game setting keeps the second monitor lit in exclusive mode, that setting was part of the trigger chain, and the setting itself is the response. If no single game setting changes anything, the trigger lies deeper in the driver or the display negotiation, and the next steps apply. Changing several settings at once and getting a lit second monitor teaches nothing about which setting mattered, and the symptom will return the next time the settings change.
Step Six: Cable, Port, and Monitor Swap, One at a Time
Even when exclusive mode is confirmed as the trigger, the physical chain can still decide whether the trigger succeeds. Swap one element at a time, repeating the enter-and-exit test after each swap: the cable to the second monitor, then the port the second monitor uses on the graphics card, then, if a spare monitor is available, the second monitor itself. Note whether the symptom follows the cable, the port, or the monitor, or whether it stays with the arrangement regardless of which physical parts are used.
If the symptom follows one cable, that cable or its connection is part of the chain, even though the desktop looked fine, because a marginal signal can survive the desktop and fail during the mode change that exclusive fullscreen demands. If the symptom follows one port, the port or its configuration is part of the chain. If the symptom stays with the arrangement through every swap, the physical chain is cleared, and the cause sits in the driver, the game mode, or the display negotiation. A swap test that changes the cable and the port at the same time proves nothing, for the same reason as the settings test: two variables changed at once.
Step Seven: Driver, Sleep, and Power Settings
The remaining steps concern the driver and the power behaviour that can turn a suspended signal into a sleeping monitor. First, check the monitor's own power-saving and sleep settings through its on-screen menu, and check the operating system's power and display sleep settings, noting whether either is set to put the display to sleep quickly. A monitor that enters a deep sleep on loss of signal may need longer to return, or may need a button press, and that behaviour can make an exclusive-mode signal suspension look like a monitor fault. Adjusting a sleep setting is a test, not a verdict, and the enter-and-exit cycle must be repeated after each adjustment.
Second, reinstall the graphics driver cleanly, following the driver maker's own clean-install procedure, and repeat the enter-and-exit test. A corrupt or mismatched driver can mishandle the exclusive handover and the display re-detection in ways that no game setting can correct, and a clean install is the only test that clears the driver properly. Updating over the top of an existing driver without the clean step does not test the same thing, because leftover driver state survives an ordinary update. If the clean driver install changes nothing, the driver is cleared, and the remaining explanation is the negotiation between the game, the driver, and the monitor during the handover itself, which is a matter for the game's and driver's own settings rather than for hardware replacement.
| Test | What the result proves | What it does not prove |
|---|---|---|
| Enter-and-exit cycle repeats identically | The symptom is tied to entering and leaving exclusive fullscreen | Which part of the chain creates the black screen, without the later tests |
| Monitor shows no-signal message, own menu works | The monitor is powered and waiting for a signal it is not receiving | That the cable or the driver is at fault, without the swap and driver tests |
| Monitor power light goes out, needs a button press | The monitor powered itself down, pointing at sleep or power behaviour | That exclusive mode is innocent; the signal suspension may still be the trigger |
| Windows stay in place on return | The display was kept in the arrangement with its signal suspended | Anything about which setting created the suspension |
| Windows migrate to the main monitor | The display was dropped from the arrangement and re-detected on exit | That the monitor is faulty; dropping and re-detection are driver behaviours |
| Borderless mode keeps the second monitor lit | The exclusive handover is the trigger | Which mode is better in general; borderless here is a diagnostic comparison only |
| Borderless mode also goes black | Exclusive mode is not the trigger | Anything about the physical chain, which must then be tested by swapping |
| One game setting keeps the second monitor lit | That setting was part of the trigger chain | That the setting is the only factor; other settings may still matter |
| Symptom follows one cable or port | That cable or port is part of the chain | That the cable or port is faulty on the desktop, where it may look fine |
| Symptom survives every swap | The physical chain is cleared | That the driver is at fault, without the clean driver test |
| Clean driver install changes nothing | The driver is cleared as the cause | That hardware replacement is needed; the handover negotiation itself remains |
Boundary Cases: When It Is Not This Whole-Session Black Screen
First, a screen that goes black only briefly at launch, at a mode switch, or on alt-tabbing, and then returns on its own, is a mode-switch re-negotiation, not this whole-session symptom. Second, a monitor that powers itself off and needs its power button pressed even after the game has closed is a monitor power or sleep problem, and the monitor's own signs step is the place to separate it. Third, a main monitor that is dragged down in resolution or refresh by a cloned display is a clone-mode problem, not a second-monitor black screen. Fourth, a main screen that stutters while a video plays on the second screen is a playback-timing problem, not a black screen. Fifth, windows that rearrange themselves after the machine wakes from sleep are a wake-and-detection problem, unrelated to entering fullscreen. Sixth, a second monitor that stays black after the game has closed, until restart or power-cycling, is a persistent detection or signal problem, not the return-on-desktop pattern this guide covers. Seventh, a game that crashes when entering fullscreen, taking both monitors with it, is a crash, not a display-mode behaviour.
Common Misconceptions
Misconception one: the second monitor must be broken because it goes black. A monitor that returns perfectly, every time, at the exact moment the game exits, is reacting to a missing signal, not failing on its own. A broken monitor does not heal itself on a schedule set by a game.
Misconception two: the graphics card is not powerful enough for two monitors. Power affects frame rate and smoothness, not whether a second output receives a signal during exclusive fullscreen. A card that drives both monitors fine on the desktop is not suddenly too weak when a game takes exclusive control of one of them.
Misconception three: a new cable will always fix it. A cable can be part of the chain, and the swap test exists for that reason, but a symptom that follows the display mode rather than any cable, and survives every swap, is not a cable problem.
Misconception four: exclusive fullscreen damages the second monitor. It does not. The monitor is designed to handle loss of signal by showing a message or entering standby, and restoring the signal wakes it. No damage is done by the handover itself.
Misconception five: switching to borderless mode permanently is the repair. Borderless mode avoids the exclusive handover, so it can remove the symptom, but it does not explain or repair the handover behaviour, and whether it is the right permanent choice is a separate question about latency and convenience, not a diagnosis.
Misconception six: turning the second monitor off in display settings before gaming fixes the cause. It hides the symptom by removing the display from the arrangement, but the handover behaviour is unchanged, and the second monitor still has to be re-enabled afterwards.
Misconception seven: changing the game mode, the cable, and the driver all at once, and getting a lit second monitor, is good enough. A recovery with several changes teaches nothing about which change mattered, and the symptom will return the next time any one of those elements changes. One variable at a time is slower, but it is the only way the result can identify a cause.
When to Stop and Seek Advice
Stop experimenting with settings if any of the following appears. Both monitors go black and stay black, which is a different problem from a second monitor alone. The monitor's own menu does not appear when its buttons are pressed, which points at the monitor or its power supply. The machine crashes, restarts, or loses the picture on the main monitor as well when entering fullscreen. Or the second monitor stays black after the game has closed and needs a restart or a power cycle, which is a persistent detection problem rather than this guide's pattern.
Bring four items to any inspection: the repeated enter-and-exit result, the monitor's own signs while black, whether windows stayed in place or migrated, and the borderless diagnostic result, stating which single changes were tried and which one first kept the second monitor lit. Those four let advice start from the handover directly, without repeating tests already done.
Readers nearby are welcome to bring their records to HK GPU Fix for advice, at Room 1209, Dali Plaza, Shek Mun, telephone 2186 8010, WhatsApp 6558 6806. Describing which game triggers it, what the monitor showed while black, and whether borderless mode kept the second monitor lit is enough for a quick judgement on the next step.
Frequently Asked Questions
Why does my second monitor go black only when a game is in fullscreen exclusive mode?
Because exclusive mode hands direct control of the main display to the game and bypasses the desktop compositor, and during that handover the driver may suspend or drop the second output. The monitor then has no signal to show, so its screen goes dark until the game exits and the signal is restored.
Does a black second monitor mean the monitor is broken?
No, not when it returns perfectly every time the game exits. A monitor that heals itself on exactly the schedule of the game is reacting to a missing signal. A broken monitor would not return reliably at the moment of exit.
Why do my windows move to the main monitor during the game?
Because the system dropped the second display from its arrangement during the handover and re-detected it on exit, so windows that lived on the second display were moved to the remaining display. Windows staying in place instead suggests the display was kept in the arrangement with only its signal suspended.
What does a no-signal message on the black monitor tell me?
It tells you the monitor is powered, awake, and waiting for a signal it is not receiving. That points the investigation at the signal chain, the driver, or the display arrangement, rather than at the monitor's power supply.
Does switching to borderless mode fix the problem?
It avoids the exclusive handover, so it can remove the symptom, but it is used in this guide as a diagnostic comparison, not as a verdict on which mode is better. Whether borderless is the right permanent choice depends on latency and convenience, which are separate questions.
Why would a cable matter if the second monitor works fine on the desktop?
Because a marginal signal can survive the desktop and fail during the mode change that exclusive fullscreen demands. The desktop is not a demanding test of the signal chain, so a cable that looks fine there can still be part of the chain that fails at the handover.
Will a clean driver reinstall help if an ordinary update did not?
It can, because an ordinary update leaves existing driver state in place, while a clean install removes it. If the handover is mishandled because of leftover driver state, only the clean procedure tests that possibility properly.
What if the second monitor goes black in borderless mode too?
Then exclusive mode is not the trigger, and the investigation must move to the cable, port, monitor, and driver tests. A mode-independent black screen has a different cause from the whole-session pattern this guide covers.
What should I bring if I seek advice?
Bring the repeated enter-and-exit result, the monitor's own signs while black, whether windows stayed in place or migrated, and the borderless diagnostic result, stating which single changes were tried and which one first kept the second monitor lit. That record lets advice start from the handover rather than repeating the whole diagnosis.