OBS Won’t Capture Game | Fast Fix Guide

Game on screen, but your scene shows a blank frame. That stalls streams and recordings. This guide gives clear steps that solve the usual capture snags on Windows. You’ll see what to try first, what to change in settings, and when to switch methods. No fluff, just fixes.

Quick Wins That Solve Most Black Screens

Start with the changes that fix the largest share of cases. Do them one by one, then check your preview each time.

Match The GPU Path On Laptops

Dual-GPU laptops route some apps to the iGPU and others to the dGPU. If OBS and the game use different GPUs, the hook fails or shows a blank frame. Set both to the same GPU in Windows Graphics settings. Add the OBS exe and the game exe, then set High performance for each. Restart both apps and try again. You can find the exact menu path in Graphics settings.

Run OBS With Admin Rights When Anti-Cheat Blocks Hooks

Some games with strict drivers need OBS to run with raised rights so the hook can attach. Close OBS, right-click the shortcut, pick Properties → Advanced, then tick the admin box. Launch OBS, open your scene, and test the hook again. If the game uses strong anti-cheat, keep overlays off and stick to a single capture method in the scene.

Pick The Right Game Capture Mode

Open the source’s Properties and use “Capture specific window” for the most stable hook. Point it at the game process. If the game swaps renderers or you tab often, try “Capture any full screen application” and keep only one Game Capture in that scene. Tick “Use anti-cheat compatibility hook” only when the game fails to hook without it. That switch can help, but it can also clash with some drivers. The full breakdown lives in the Game Capture guide.

Fix Conflicts From Overlays And Injectors

Hook conflicts come from apps that draw over the game. Common culprits include GeForce Experience in-game overlay, Radeon overlay, Discord overlay, Steam overlay, RGB apps, and FPS counters. Turn them off, restart the game, then refresh the hook. If you need an FPS readout, try the game’s own counter instead of a third-party layer.

When Your Filters Don’t Appear In The Recording

Driver filters like Freestyle often live on the desktop blend stage, not inside the game buffer that Game Capture reads. That’s why the preview looks plain while the screen on your desk looks graded. If you must record the grade, swap to Display Capture for that scene, or move the grade into OBS with its own filters so the edit is inside the pipeline.

Tune Fullscreen Modes And Scene Layout

Many games move between launchers, lobbies, and matches. Each part can use a different renderer. Make two scenes: one with Window Capture for the launcher or lobby, and one with Game Capture for the match. Use a hotkey to switch. In the game video settings, try Borderless Fullscreen and test the hook again. Keep Display Capture out of the same scene as Game Capture to avoid priority fights.

Match Capture To Game Tech

DirectX 11 and 12, OpenGL, and Vulkan can behave in different ways with hooks. Modern OBS builds support them, but some titles still need a set path. If a Vulkan game won’t hook, try “Capture specific window” and launch the game after the source exists. Keep your OBS build fresh so new hook paths and signed modules are in place.

Update OBS And Your GPU Driver

Hook modules change over time. Update OBS to the newest build, then reboot. Update your GPU driver as well. Use a clean install when the driver offers it. After a big OBS update, one reboot clears stale modules that linger in memory.

Configure Windows Graphics Settings

Windows lets you set per-app GPU routing. Open Settings → System → Display → Graphics settings. Add your apps, pick the GPU, and save. This lines up the render path so the hook can read frames. On desktops with a single GPU, this page still helps if OBS was set to a low power path by mistake. For full steps, see Graphics settings.

Switch Methods When A Game Blocks Hooks

Some anti-cheat drivers block injection in all cases. When that happens, the panel stays blank no matter what you try. Use Window Capture or Display Capture for that title, and keep scenes clean so only one method runs at a time. If the game kills capture only in exclusive full screen, try Borderless and test again.

Clean Source Order And Scene Setup

Source order decides what you see. Put Game Capture above Display Capture. Keep overlays and web sources below the game image. If you need an alert on top, place it above the game. Avoid stacking two Game Capture sources in one scene. Use one per scene, and duplicate scenes for variants rather than piling sources.

Reset A Stubborn Hook

If the source stays blank after changes, delete that Game Capture source and add a fresh one. Pick the exact window again. Close the game, launch OBS first, then launch the game and pause on the menu. Add the source, check the preview, then go live. This order helps with games that build render paths at boot.

When You Stream With A Capture Card

PC-to-PC streams skip the hook, since the card reads HDMI. In that setup, keep overlays off on the game PC, and send a clean feed. On the OBS PC, set the card to the right color range and frame rate. If you still need a PC hook for chat scenes, keep those scenes separate so the card feed never fights with a Game Capture source.

Overlay And Tool Checklist

Log Files That Reveal The Real Cause

Open Help → Log Files → Upload. Copy the link. The log shows hook attempts, GPU paths, and blocks from overlays. When you read it, search for “game capture” lines, GPU names, and “hooked”. One bad overlay stands out fast in the log.

Fast Setup Recipe You Can Reuse

Here’s a repeatable plan that works across most titles: launch OBS first, then the game. Use one Game Capture in the scene set to “Capture specific window”. Pick the game, then set the game to Borderless Fullscreen. Keep overlays off. If the hook fails, run OBS as admin and test again. When the title blocks hooks, swap the scene to Window or Display Capture for that game only.

When To Ask The Game’s Vendor

Studios can change drivers that affect hooks. Check patch notes when capture stops after an update. If a title adds stricter drivers, you may need a plain capture path for a while. Keep OBS current so new hook certificates and modules match game checks.

Advanced Options Inside Game Capture

Open the source, then scroll through its settings. Set Window match priority to “Match title, otherwise find window of same type” for stable hooks. Leave Hook rate on Normal. Tick “Limit capture framerate” only when the game stutters on capture. Leave “Capture third-party overlays” off during tests. Use “Allow transparency” only for stylized crops. If the title still blanks, test the Capture method menu. On recent Windows builds, the “Windows 10 and up” method can help with some render paths.

Special Cases: Riot, League, And Minecraft

Riot’s driver stack can stop injection. Admin mode and a clean scene give the best shot, but some patches still block hooks. When that happens, switch to a plain method. League uses a launcher and a match client, so split scenes as noted earlier. Minecraft has different renderers and mod loaders; pick the exact javaw.exe in Game Capture and launch the game after the source exists. If a mod adds an overlay, turn that layer off while you test.

With these steps you can isolate the snag, match the GPU path, and hook cleanly. Keep scenes tidy and update both OBS and your GPU driver. When hooks are blocked, switch capture methods and keep streaming. Happy streaming with stable hooks today.

Step-By-Step Troubleshooting Order

Work through this list once per title so you don’t chase ghosts across scenes:

1. Update OBS and reboot.
2. Turn off overlays, then launch OBS first.
3. Add one Game Capture set to “Capture specific window”.
4. Run OBS as admin and retest.
5. Align GPUs in Graphics settings and restart both apps.
6. Swap to Window or Display Capture only when hooks are blocked.

Send us your feedbackTell us what you thought about this post

Name * Email *

Your comment *

Quick check — what is …? *

Send feedback