OBS Game Capture Shows Black Screen but the Game Looks Fine? Admin Rights, GPU Selection, Anti-Cheat & Capture Method Diagnosis

2026-11-09 | GPU Repair | 20 minutes | HK GPU Fix Editorial Team

OBS Game Capture Shows Black Screen but the Game Looks Fine? Admin Rights, GPU Selection, Anti-Cheat & Capture Method Diagnosis

Key Takeaways

OBS Game Capture shows a black screen when its hook cannot reach the game, even though the game looks fine on your monitor. The causes are a privilege gap, the two programs running on different graphics processors, an anti-cheat system blocking the injection, or a capture mode the game does not suit. This guide works through each layer in order.

The Symptom This Guide Is About

This guide covers one specific failure: the game runs normally on your own monitor — the picture is complete, the game responds, nothing looks wrong — but the Game Capture source in OBS shows a solid black frame. The recording that comes out is black, and the stream that goes out is black. Sound may still be present. The picture is not frozen, not stuttering, not tearing; it is simply absent.

Three features define this symptom, and they should be established before anything is changed:

  1. The game looks fine; only the capture is black. The display output layer is working. What has failed is the capture layer, which cannot obtain the game's picture.
  2. It is not stutter or dropped frames. A recording that stutters still has input that the encoder cannot keep up with. Here there is no input at all. That is the fundamental dividing line from encoder overload, where the picture exists but the encoding cannot keep pace — a smooth game with a stuttering recording points at the encoder, while a black recording points at the capture itself.
  3. No capture card is involved. There is no second piece of hardware and no second output path in this setup. A workflow that sends the picture through a separate capture card — with its clone mode, EDID negotiation, HDCP protection and pass-through — is a different problem with different causes.

Several neighbouring symptoms are easy to confuse with this one, and each belongs elsewhere:

The first step in the diagnosis below is a comparison that confirms the fault really sits in the capture layer. Until that comparison is done, changing OBS settings is guesswork.

How Game Capture Actually Gets the Picture

OBS Game Capture does not photograph the monitor. Instead, it injects a small piece of hook code into the running game process and intercepts each frame directly, just before the game hands the picture to the display. That mechanism decides the whole diagnostic logic of this guide, because the hook can only work when two conditions are both true:

  1. The same graphics processor. The hook runs inside the memory space of the graphics processor the game is using. It cannot read the frame buffer of a different graphics processor.
  2. The same privilege level. Windows does not allow a lower-privilege process to inject code into a higher-privilege process. That is a security boundary, not a setting that can be talked around.

When the hook fails, OBS does not show an error message. It simply shows a black frame. That silence is the reason the symptom feels so confusing: the game was selected correctly, OBS reports no problem, and yet nothing appears. The black screen is not an error message. It is the quiet result of a hook that never took hold.

The causes that follow are the five ways that hook can fail, plus one weaker report that should not be treated as a cause. Each one has its own evidence and its own comparison test, and the tests are designed so that only one variable changes at a time.

The Five Causes, in Detail

1. A Privilege Gap: OBS Runs as a Standard User, the Game Runs as Administrator

Games launched through a launcher such as Steam, Epic Games, or Battle.net, or games that request elevated privileges themselves, can run with administrator rights. OBS, launched normally, runs with standard user rights. A standard-privilege process cannot inject its hook into an administrator-privilege process, and Windows blocks the attempt without telling OBS why. The result is a black capture of a game that is running perfectly well.

The evidence for this layer is straightforward: the game is running with elevated privileges — visible in Task Manager or in the launcher's own settings — while OBS is not. The comparison test is equally simple and should be the first step, because it costs nothing: close OBS, restart it by choosing "Run as administrator", and try the same game again without reinstalling anything or changing the game. If the picture appears, the privilege layer is confirmed.

One caution matters here. This must not be written up as a rule that OBS should always be run as administrator. The correct statement is narrower: when the game itself runs with elevated privileges, OBS needs the same level before its hook can reach the game. Running software with elevated privileges carries a security trade-off of its own, and readers should weigh that for themselves rather than adopting administrator mode as a permanent habit.

2. Two Graphics Processors: OBS on the Integrated GPU, the Game on the Discrete GPU

Laptops, and some desktops with two graphics processors, have an integrated graphics processor and a discrete graphics card. Windows assigns each program to a graphics processor, and the two assignments do not have to agree. If OBS is assigned to the integrated processor while the game is assigned to the discrete card, the hook sits in the discrete card's memory space and OBS, running on the integrated side, cannot read it at all. The capture is black.

The evidence is visible in Task Manager: OBS and the game are listed under different GPUs, typically shown as GPU 0 and GPU 1. Checking which graphics processor each program is running on is a simple inspection step, and it is the only point this guide shares with the guide on confirming which graphics processor a game is using. That other guide is about game performance — using the wrong processor makes a game slow — while this one is about capture failure: OBS and the game on different processors makes the capture black. The symptom and the consequence are entirely different, and the switching technology behind laptop graphics does not need to be explained again here.

The comparison test is to bring both programs onto the same graphics processor. In Windows Settings, under System, Display, Graphics, find OBS (obs64.exe) and set it to High performance, which selects the discrete graphics card, then restart OBS and the game. The graphics card control panel offers the same choice. If the picture appears once both programs run on the same card, the mismatch layer is confirmed.

3. Anti-Cheat Blocking the Hook

A hook is, in technical terms, code written into another running process. That is the same shape of behaviour that malicious software uses to inject code, so anti-cheat systems — particularly the kernel-level anti-cheat used by some competitive games — can treat the hook as suspicious activity and block it. OBS can detect the game and still be unable to obtain any frames, and the result is a black capture. This is a block by design. It is not OBS being broken, and it is not the game being broken.

The evidence is a pattern, not a single game: only certain competitive games go black, while other games capture normally. OBS also provides a built-in option in the Game Capture properties called "anti-cheat compatibility hook", which exists specifically to work alongside anti-cheat systems. Turning that option on and trying again is the first comparison test for this layer.

If the capture is still black, the next step is to change the capture method rather than fight the block. Window Capture takes its picture through the desktop compositing layer and does not need to inject anything into the game process, so it bypasses the anti-cheat block. The trade-off is real: Window Capture performs worse and adds latency, and it may not suit a game running in exclusive full screen. Display Capture, which takes the whole desktop, is the same kind of alternative.

Two rules apply to this layer without exception. Readers must never be told to disable, bypass, or deceive an anti-cheat system, and no list of games that always block or never block may be given. Anti-cheat behaviour changes with game updates, so this guide describes only the mechanism, the phrase "individual games", and the lawful alternative of a capture method that does not inject anything.

4. The Capture Method and the Display Mode Do Not Match

Game Capture is sensitive to the display mode the game uses. In exclusive full-screen mode, the game bypasses desktop compositing and outputs directly, so the hook must intercept the picture on that direct path. In borderless windowed mode, the game passes through the desktop compositor, and the capture path is different. Some games hook reliably in one mode and not in the other, and the direction varies: a game that is black in exclusive full screen may work in borderless windowed mode, and the reverse can also happen.

The evidence is a change that follows the mode: the same game goes black or works depending only on the display mode selected. The comparison test is to switch the game between exclusive full screen and borderless windowed mode, and in the OBS Game Capture properties to compare "Capture any fullscreen application" with "Capture specific window". One detail matters when choosing a specific window: some games use one window for the lobby and a different window for the match itself, so the source should be selected after the game has already entered a match, not while it is still in the lobby.

Display Capture is the final comparison tool for this layer, and it produces the most important dividing statement in this guide: Display Capture takes the whole desktop and needs no injection at all, so if Display Capture shows the picture while Game Capture is black, the fault is locked to the hook layer. It is not the graphics card, not the driver, and not the game's rendering.

5. Third-Party Software Interfering With the Hook

Overlay layers from Discord, Steam, GeForce Experience, or the Xbox Game Bar, frame-rate counters, and real-time antivirus scanning can all compete with OBS for the same hook position, or treat the injection as suspicious activity and block it. The result is the same black capture, caused by software that has nothing to do with the game itself.

The evidence comes from turning these programs off one at a time. Each overlay or counter should be disabled individually, then the game tested again, before moving to the next one. Switching several off at once proves nothing, because it leaves the reader unable to tell which one was responsible.

Antivirus software deserves the same careful wording. The guide can only say to check whether the antivirus software is intercepting OBS. Readers must not be told to switch antivirus protection off permanently, and adding the game or OBS to an exclusion list must not be presented as a universal repair. The trade-off should be stated plainly and the decision left to the reader.

The Diagnostic Flow, in Order

Work through these steps in order, and change only one thing at a time. Each step narrows the range of possible causes, and the later steps only mean something because the earlier steps established the pattern first. Use the same game and the same scene for every comparison.

StepWhat to doHow to read the result
0Confirm the symptom: the game looks fine on the monitor, and only the OBS Game Capture source is blackIf the game itself is black, this is not the right guide; a black screenshot or shared screen points elsewhere; a stuttering recording points at the encoder
1Switch to Display Capture and check whether it shows a pictureA picture here locks the fault to the hook layer, so continue; no picture means the fault is not a hook problem, so leave this guide
2Restart OBS as administrator and try the same game againA picture now confirms the privilege layer; no picture means moving on
3In Task Manager, check which GPU OBS and the game are running on; if they differ, set OBS to High performance and try againA picture now confirms the dual-GPU mismatch layer; no picture means moving on
4In the Game Capture properties, turn on the anti-cheat compatibility hook and try again; if still black, switch to Window CaptureA picture in Window Capture points at the anti-cheat layer; black in Window Capture too means moving on
5Compare exclusive full screen with borderless windowed mode, and compare "Capture any fullscreen application" with "Capture specific window"A result that follows the mode confirms the display-mode layer
6Turn off overlay layers, frame-rate counters, and real-time antivirus scanning one at a time, testing after eachWhichever one restores the picture is the interfering software
7If still black, record the hook-related lines in the OBS log file, the driver version, the game, and which steps were tried, and take that record to an inspectionDo not keep changing settings at random

Step 1: The Display Capture Comparison

Before touching any setting, switch the OBS source to Display Capture. This single comparison divides the whole investigation. If Display Capture shows the game, the graphics card, the driver, and the game's rendering are all working, and the fault is confined to the hook. If Display Capture is black as well, the fault is not a hook problem at all, and the investigation belongs in a different guide.

Step 2: Administrator Rights as a Comparison

Close OBS and restart it with administrator rights, then try the same game again without changing anything else. A picture that appears now proves the privilege gap. A picture that does not appear excludes this layer and costs nothing to have checked, which is why it comes before the more involved steps.

Step 3: Which Graphics Processor Is Each Program Using?

Open Task Manager and look at the GPU column for OBS and for the game. If they are on different processors, change the Windows graphics setting for OBS to High performance, restart both programs, and test again. If the picture appears, the mismatch is confirmed. If both programs were already on the same processor, this layer is excluded.

Step 4: The Anti-Cheat Compatibility Hook, Then Window Capture

In the Game Capture properties, enable the anti-cheat compatibility hook and test again. If the capture is still black, switch the source to Window Capture and test once more. A picture in Window Capture, where Game Capture was black, is strong evidence that an anti-cheat system is blocking the injection. Neither step involves disabling or deceiving the anti-cheat system; both use capture methods that the software itself provides.

Step 5: Display Mode as a Variable

Change the game between exclusive full screen and borderless windowed mode, testing each in turn, and compare the two Game Capture modes in OBS. A result that follows the mode is the answer. Remember to select the specific window only after the game has entered a match, since the lobby and the match can be different windows.

Step 6: One Interfering Program at a Time

Disable each overlay layer, frame-rate counter, and real-time scanning feature individually, testing after each one. The discipline of changing one thing at a time is what turns a lucky fix into a diagnosis: the reader ends up knowing which program caused the problem, and can decide what to do about it.

Step 7: Stop Changing Settings and Record the Evidence

If every step has been tried and the capture is still black, further random changes will not help. Write down the hook-related lines from the OBS log file, the driver version, the game name, and which steps were tried and what each one showed. That record is what an inspection needs to start from the narrowed-down layer instead of from the beginning.

Boundaries: What This Is Not

Several neighbouring problems look similar at first glance. Each one is a different mechanism.

Common Misconceptions

MisconceptionCorrection
"A black OBS capture means the graphics card is broken."Wrong. The display output layer is working, since the game is visible on the monitor. The fault is in the capture layer, which cannot obtain the picture.
"Changing the cable or the monitor will fix it."Wrong. Software capture does not pass through the signal cable. Cables only affect physical output and capture-card workflows.
"Lowering the encoding settings will fix it."Wrong. Encoding settings affect stutter and dropped frames. A black screen is an input problem, and no encoding change can turn a black picture into a picture.
"Every black capture has the same cause."Wrong. Privilege, dual-GPU assignment, anti-cheat, display mode, and third-party interference all produce the same black frame, which is why each layer needs its own comparison test.
"Running OBS as administrator or switching the antivirus off is a permanent fix."Wrong. These are diagnostic isolation steps and trade-offs, not cost-free repairs. The trade-off should be stated and the decision left to the reader.
"Anti-cheat blocking means the game is targeting OBS."Wrong. Anti-cheat blocks the injection behaviour itself, not OBS specifically. The correct response is to use a capture method that does not inject anything, such as Window Capture or Display Capture.

What to Do With the Result

If the diagnostic flow identifies the layer — a privilege gap closed by running OBS at the same level as the game, a dual-GPU mismatch fixed by assigning OBS to the high-performance processor, an anti-cheat block worked around with Window Capture, a display mode that only fails in one setting, or an interfering overlay — the result should be recorded with the same care as the original symptom: which step changed the outcome, and which settings are now in place. That record makes the fix repeatable.

If every step has been worked through and the capture is still black, and especially if Display Capture is black as well, the problem has gone beyond what settings can isolate. The next step is a professional inspection, carried out with the machine in the shop. Bring the written record — the OBS log lines, the driver version, the game name, which graphics processor each program was using, and which steps changed the outcome — because that record lets an inspection start from the layer the tests have already narrowed down, instead of from the beginning. An inspection will not change the Windows privilege model or an anti-cheat policy, so a problem that clearly follows privilege, dual-GPU assignment, anti-cheat, or display mode is a settings matter, not a hardware matter, and should be treated as one.

HK GPU Fix offers a diagnostic inspection at its Shek Mun shop: Room 1209, Dali Plaza, Shek Mun. The published inspection fee range is HK$400–2,800 in total, and the actual price is subject to a post-inspection quotation. Phone 2186 8010, WhatsApp 6558 6806. There is no on-site service; inspection is carried out at the shop.

Frequently Asked Questions

The game looks fine on my monitor, but OBS Game Capture is black. Is my graphics card broken?

Almost certainly not. The display output layer is working, since you can see the game. The fault is in the capture layer: the hook that OBS injects into the game has not taken hold. Start with the Display Capture comparison — if Display Capture shows the game, the graphics card and the driver are fine, and the fault is confined to the hook.

Why does OBS show no error message when the capture is black?

Because a failed hook is silent. OBS does not receive an error from Windows when the injection is blocked; it simply receives no frames, and an empty frame looks black. The black screen is not an error message. It is the quiet result of a hook that never took hold.

Should I always run OBS as administrator?

No. Run OBS as administrator only as a comparison test when the game itself runs with elevated privileges. If the picture appears, the privilege gap is confirmed. Running software with elevated privileges carries a security trade-off, so it should be a deliberate choice, not a permanent habit.

My laptop has two graphics processors. Could OBS be on the wrong one?

Yes. If OBS is assigned to the integrated processor while the game runs on the discrete card, the hook cannot reach the game's frames. Check Task Manager to see which GPU each program is running on, then set OBS to High performance in the Windows graphics settings so both programs use the same card.

A competitive game is black in OBS, but other games capture fine. What is happening?

An anti-cheat system may be blocking the hook, because injecting code into a running process is the same shape of behaviour that anti-cheat systems are designed to stop. Turn on the anti-cheat compatibility hook in the Game Capture properties. If that does not work, switch to Window Capture, which does not inject anything into the game. Never disable or try to deceive the anti-cheat system.

The game works in borderless windowed mode but not in exclusive full screen. Why?

Game Capture is sensitive to the display mode, because exclusive full screen bypasses the desktop compositor while borderless windowed mode passes through it. The capture path is different in each mode, and some games hook reliably in only one of them. A result that follows the mode confirms the display-mode layer.

I turned off several overlays at once and the picture came back. Which one was it?

That cannot be known from that test, because several things changed at once. Turn the overlays back on one at a time and test after each one, so the interfering program can be identified. Changing one thing at a time is what turns a lucky fix into a diagnosis.

Display Capture is black as well. What does that mean?

It means the fault is not in the hook layer. Display Capture needs no injection, so if it is also black, the problem sits somewhere else — in the driver, the system capture layer, or the game's own rendering — and this guide no longer applies. Record what was tested and take that record to an inspection.

Will switching to a different capture method fix the problem permanently?

It depends on the layer. Window Capture or Display Capture is a genuine workaround for an anti-cheat block, because those methods do not inject anything. For a privilege gap or a dual-GPU mismatch, changing the capture method only hides the cause; the underlying assignment should still be corrected.

The capture was working yesterday and is black today. What changed?

Check the two most common moving parts first: whether the game or its launcher has started running with elevated privileges, for example after an update, and whether Windows has reassigned OBS to a different graphics processor. Record the driver version and the game version as well, since a change in either one is part of the timeline an inspection would need.

Related articles

Related services

If you need Display output repair, see these service pages: