You updated your GPU driver, rebooted, and now your capture card has vanished. OBS shows “Video Capture Device” with a black screen or an error like “Failed to start streaming,” Device Manager shows the card under “Other devices” with a yellow warning triangle, or the card simply does not appear anywhere at all. On some systems, the capture software launches fine but the preview freezes on the first frame; on others, Windows plays the USB connect chime on repeat as the card repeatedly re-enumerates.
This is urgent but not catastrophic. If you are a streamer or content creator mid-production, every hour without a working capture card is lost footage, so work through this guide in order — most fixes take under ten minutes. The good news: in the overwhelming majority of cases, a driver update did not break your card. It changed something downstream of it, and one of the fixes below will get you back up and running. Budget 15–60 minutes total before you consider RMA territory.
Likely Causes
| Cause | How to confirm | Fix difficulty |
|---|---|---|
| GPU driver replaced the display output your capture card relies on (signal routing changed) | Card was working on a port that the new driver re-initialized; preview black but card visible in Device Manager | Easy |
| Capture card driver corrupted or version-mismatched by the update process | Yellow warning icon in Device Manager, error Code 43 or Code 52 | Easy |
| Windows installed a generic driver over the vendor driver | Device Manager shows “Generic USB Video” or similar instead of the card’s actual name | Easy |
| USB power management turned the device off (USB capture cards) | Card disappears after idle; Event Viewer shows Kernel-PnP warnings | Moderate |
| PCIe lane/bifurcation changed after chipset driver install (internal cards) | Card missing entirely from Device Manager even with “Show hidden devices” | Moderate |
| DRM/HDCP handshake failure after GPU driver reset | Black screen only on protected content (consoles, Netflix); normal sources fine | Moderate |
Fix 1: Power Cycle Everything in the Right Order
What causes it
A driver update leaves the capture card’s firmware in a stale state. The card holds onto its old handshake with the GPU driver, and a normal Windows restart doesn’t fully clear it because the card never loses power through a warm reboot.
How to check
If the card was working minutes before the driver update and failed immediately after, this is your first suspect. No diagnostics needed — just do this before anything more involved.
What to do
Shut down Windows fully (hold Shift while clicking Shut Down to disable Fast Startup). Flip the PSU switch off. For a USB capture card, unplug it from the PC. For an internal PCIe card, power off the PSU and press the case power button for 10 seconds to drain residual charge. Wait 60 seconds. Reconnect everything, flip the PSU back on, and boot.
How to undo it
Nothing to undo — this is a non-destructive reset. If it didn’t help, move on to Fix 2.
Fix 2: Roll Back or Reinstall the Capture Card Driver (Not the GPU Driver)
What causes it
Windows Update often bundles chipset and capture device drivers alongside your GPU driver update. A bad or generic capture driver got installed at the same time, so the GPU update gets the blame.
How to check
Open Device Manager (right-click Start > Device Manager). Expand “Cameras,” “Sound, video and game controllers,” or “Other devices.” Right-click your capture card > Properties > Driver tab. Note the driver version and date. If the date matches today’s update, this is likely your problem. A Code 43, Code 45, or Code 52 in the “Device status” box confirms it.
What to do
In that same Driver tab, click “Roll Back Driver” if the option is available. If it’s grayed out, click “Uninstall Device,” check “Attempt to remove the driver for this device,” and confirm. Then download the current driver directly from the card manufacturer (Elgato, AVerMedia, Magewell, etc.) — not through Windows Update — and install it. Reboot when prompted.
How to undo it
The vendor installer typically includes a “restore default” or you can repeat the uninstall/reinstall cycle with a different driver version. Rollback via Device Manager restores the previous version automatically.
Fix 3: Disable USB Selective Suspend and Power Management
What causes it
Windows power plans suspend USB devices to save energy. After a driver update, the active power plan sometimes resets to “Balanced” with aggressive selective suspend, killing idle capture cards that the system then fails to wake correctly.
How to check
If the card vanishes after a few minutes of inactivity but returns after unplugging and replugging it, this is it. Also check Event Viewer (Win+R, type eventvwr.msc) under Windows Logs > System for Kernel-PnP events referencing your device failing to start.
What to do
Open Control Panel > Power Options > Change plan settings > Change advanced power settings > USB settings > USB selective suspend setting, and set both Battery and Plugged in to “Disabled.” Then, in Device Manager, expand “Universal Serial Bus controllers,” right-click each “USB Root Hub” and “Generic USB Hub” > Properties > Power Management tab, and uncheck “Allow the computer to turn off this device to save power.” Do the same on your capture card’s own entry under “Universal Serial Bus devices” if present. Reboot.
How to undo it
Return to the same menus and re-enable selective suspend or the power-management checkboxes. There is no stability risk in leaving these disabled on a desktop PC.
Fix 4: Clean Reinstall the GPU Driver with DDU
What causes it
The GPU driver update itself broke the video pipeline your capture card uses — especially for internal cards that negotiate bandwidth with the GPU, or when the driver installer reset multi-monitor and HDCP settings.
How to check
Your capture card appears healthy in Device Manager but preview stays black in OBS or the vendor software, and rolling back the capture driver (Fix 2) did nothing. This points at the GPU side of the chain.
What to do
Download Display Driver Uninstaller (DDU) and the latest GPU driver from NVIDIA, AMD, or Intel directly. Boot into Safe Mode (hold Shift while clicking Restart > Troubleshoot > Advanced options > Startup Settings > Restart > press 4). Run DDU, select your GPU type, and choose “Clean and restart.” After reboot, install the fresh GPU driver, choosing “Custom/Advanced” install and unchecking any bundled extras you don’t need. Reboot again and test the capture card.
How to undo it
Run DDU again and install a previous driver version downloaded from the GPU vendor’s archive page. GPU drivers keep no user settings that can’t be reconfigured in a few minutes.
Fix 5: Force the Correct Driver Manually in Device Manager
What causes it
Windows replaced the vendor’s driver with a generic one (e.g., “Microsoft Basic Display Adapter”-equivalent for capture devices) and refuses to auto-detect the proper one, because the device’s hardware ID matched a generic in-box driver first.
How to check
In Device Manager, right-click the device > Properties > Details tab > Property dropdown > “Hardware Ids.” You’ll see values like USB\VID_0FD9&PID_0066. Then check the Driver tab: if the provider is “Microsoft” instead of the card’s manufacturer, you’ve got the wrong driver.
What to do
Right-click the device > “Update driver” > “Browse my computer for drivers” > “Let me pick from a list of available drivers on my computer.” Uncheck “Show compatible hardware” only if the vendor driver doesn’t appear — otherwise leave it checked. Select the manufacturer-named driver and click Next. If the correct driver isn’t listed, install it from the vendor’s package first (extract the .inf if it ships as a zip), then repeat this selection.
How to undo it
Device Manager > right-click device > Properties > Driver tab > “Roll Back Driver,” or repeat the manual selection with the generic driver.
Fix 6: Change PCIe Slot or USB Port
What causes it
A chipset driver installed alongside the GPU update changed PCIe link training or USB controller behavior. The card can no longer negotiate a stable link in its current slot or port — common with USB 3.x cards on specific controllers, or PCIe cards sharing bandwidth with an M.2 drive.
How to check
For USB cards: try a different port, ideally a USB 3.0/3.2 Type-A port directly on the motherboard rear I/O (not a front-panel header or hub). If the card works in one port and not another, it’s a controller issue. For internal cards: check whether your motherboard manual lists the slot as sharing lanes with M.2 or SATA — some slots disable or downgrade when specific M.2 slots are populated.
What to do
Move the card to a different port or slot. Prefer motherboard rear I/O ports for USB devices; prefer a CPU-attached PCIe x16 or x4 slot over a chipset-attached one for internal cards. Update the chipset driver from your motherboard vendor’s support page while you’re at it — AMD users should grab the latest chipset package, Intel users should check for an updated INF and Management Engine driver.
How to undo it
Move the card back to its original slot or port. Nothing else to reverse.
Fix 7: Disable HDCP on the Source or in the Capture Software
What causes it
The GPU driver update reset HDCP negotiation, breaking the handshake between your console/streaming device and the capture card. Protected content triggers a black or scrambled preview even though the card itself enumerates fine.
How to check
Test with an unprotected source — a laptop desktop, a camera, or an unprotected game console output with HDCP disabled. If unprotected sources capture fine and protected ones don’t, HDCP is your culprit.
What to do
On PlayStation 5: Settings > System > HDMI > Enable HDCP > Off (note: this blocks some streaming apps on the console). On Xbox Series X/S: Settings > General > TV & display options > Video modes > uncheck “Use HDCP.” In the vendor software (Elgato 4K Capture Utility, AVerMedia RECentral), look for an HDCP setting under device properties and disable it if offered. Then power cycle the console and capture card.
How to undo it
Re-enable HDCP in the same menu on your console or software. You’ll need it back on for console streaming apps.
Fix 8: Roll Back via System Restore
What causes it
Multiple intertwined changes from the update (driver packages, power settings, registry entries) combined to break the card, and you can’t isolate the single cause.
How to check
You’ve tried Fixes 1 through 7 without success, and you know roughly when the card last worked (before the update). System Restore is the catch-all.
What to do
Press Win+R, type rstrui.exe, and press Enter. Choose “Choose a different restore point” and pick one dated before the driver update. Click “Scan for affected programs” to see what will change. Confirm and let Windows restore and reboot. This does not affect personal files, only drivers, registry settings, and installed programs from after the restore point.
How to undo it
Run rstrui.exe again — the restore operation itself creates an undo point you can revert to.
If Nothing Works
Test the capture card on a completely different computer. If it works there, your Windows installation or motherboard is the problem — an in-place repair install of Windows (Settings > System > Recovery > “Fix problems using Windows Update,” or the Installation Assistant keeping files and apps) is less drastic than a clean install and resolves deep driver-stack corruption. If the card fails on a second machine too, especially after trying a different cable and confirming the source device outputs signal, the card may have coincidentally failed at the same time as your driver update — an unlucky but real scenario. Contact the manufacturer’s support with your card model, driver versions, and Windows build number (Win+R, type winver) before pursuing an RMA.
FAQ
Can a GPU driver update really break a capture card?
Indirectly, yes. The GPU driver controls the video pipeline, HDCP handshakes, and sometimes PCIe lane behavior that internal capture cards depend on. Windows also tends to install chipset and capture device drivers bundled with GPU updates, so multiple things change at once even though the GPU update gets the blame.
Should I just uninstall the new GPU driver and go back to the old one?
It’s worth trying early if you know the exact driver version that worked — use Device Manager’s “Roll Back Driver” on your GPU, or DDU plus the previous version from the vendor’s archive. But if the capture card driver was also swapped by Windows Update at the same time, rolling back only the GPU driver won’t fix it, so check Device Manager first.
Why does my capture card work in OBS but not in the manufacturer’s software (or vice versa)?
OBS and vendor software often use different driver interfaces. OBS typically uses DirectShow or Media Foundation, while vendor apps use their own driver stack. If one works, the card and driver are fundamentally healthy — reinstall or update the failing application, and check for a settings conflict like both apps trying to claim the device exclusively at the same time.
How do I stop this from happening again after the next driver update?
Set your Wi-Fi or Ethernet connection to “Metered” (Settings > Network & internet > your connection > Metered connection) to pause automatic driver installs via Windows Update, and defer optional driver updates under Settings > Windows Update > Advanced options. Download drivers manually from the vendor when you choose to update, create a restore point first (search “Create a restore point” in the Start menu), and update when you have a free evening — not right before a stream.
