007 First Light Black Screen on Launch (PC)

What is the 007 First Light Black Screen on Launch?

007 First Light, IO Interactive's Glacier-engine James Bond origin story released May 27, 2026, hits a black-screen-on-launch wall on a meaningful slice of PCs. Unlike the "process exits silently" launch bug we cover in our [main 007 First Light crash guide](/en/errors/007-first-light-crash-wont-launch-pc), this variant shows a window — it just stays black, either with audio playing in the background, completely silent, or right before a crash to desktop.

The fix depends on which of the three sub-cases you have. Treating them all the same is why most generic guides fail. Below is the diagnostic split IO Interactive's own support team uses on its [Known Issues page](https://007firstlight-support.zendesk.com/hc/en-us/articles/36203682496413-007-First-Light-Known-Issues).

When does it occur?

• Black screen WITH menu/intro audio still playing — display-target or monitor problem
• Black screen with NO audio and no input response — DX12 init hang
• Black screen for a few seconds, then a crash to desktop — RTX 50 Vulkan/video-engine timeout
• Only after Alt+Tab, sleep, or a second monitor was unplugged
• On HDR-enabled displays the first time the game switches modes
• After installing the day-one patch on a triple-monitor setup

Common causes

• Game rendering to the wrong display (HDMI 2 / disabled TV output)
• Fullscreen-exclusive failing to grab the panel at the game's native refresh rate
• Glacier DX12 init deadlocking on a stale pipeline_cache
• HDR auto-switch handshake stalling the swapchain on Windows 11 24H2
• RTX 50-series video engine timeout under Vulkan (same root cause as our [video-engine-timeout](/en/errors/nvidia-rtx-50-series-driver-crash-video-engine-timeout) guide)
• Optimus / MUX laptops still routing the dedicated GPU's output through the iGPU framebuffer
• Steam Input or Discord overlay hooking the swapchain before the first frame

Step-by-step fixes

Sub-case A: Black screen WITH audio (display/monitor)

1. Press Alt+Enter as soon as the audio starts — this forces windowed mode. If a window appears with the game running, the issue is display target, not the engine.
2. Force the correct monitor — Windows Settings → System → Display → make your primary monitor the one you're actually looking at, then disable any unused outputs (TVs over HDMI, second displays).
3. Turn off Windows HDR before launching (Settings → System → Display → HDR → off). Re-enable in the game's video options once you're in.
4. Match desktop refresh rate to the game's expected rate — set desktop to 60 Hz for the first launch, then raise it after the intro plays. Adaptive Sync handshakes are a documented cause of first-launch blackouts on G-Sync Ultimate panels.

Sub-case B: Black screen NO audio (DX12 hang)

1. Delete the pipeline cache — %LOCALAPPDATA%\IO Interactive\007 First Light\pipeline_cache\ — close the game, wipe the folder, relaunch. The shader build restarts cleanly.
2. **Add -dx11 as a launch option** — Steam → right-click 007 First Light → Properties → Launch Options → enter -dx11. Glacier supports a DX11 fallback that bypasses the DX12 init hang.
3. Disable Resizable BAR / Smart Access Memory in motherboard UEFI (Advanced → PCIe → Re-Size BAR Support → Disabled). RBAR on certain Z790/X670 boards stalls the Glacier DX12 swapchain.

Sub-case C: Black screen then crash to desktop (RTX 50 / Vulkan)

1. Roll back NVIDIA driver to 580.88 (or newer with the June 2026 hotfix) — earlier 575.x branch drivers cause the [RTX 50 video engine timeout](/en/errors/nvidia-rtx-50-series-driver-crash-video-engine-timeout) on Glacier's Vulkan path. In NVIDIA App → Drivers → ⋮ → Reinstall. If you're on the older driver, clean install the latest Game Ready via DDU. Force the game off Vulkan with -dx12 in launch options as a temporary workaround.

If it still doesn't work

Open Event Viewer → Windows Logs → Application immediately after a crash and look for an "Application Error" event citing 007FirstLight.exe along with the faulting module — nvwgf2umx.dll confirms an NVIDIA driver crash, dxgi.dll points at swapchain failure, and KERNELBASE.dll usually means the anti-tamper layer was killed by Defender. Add the install folder to Windows Security → Virus & threat protection → Exclusions and try once more.

If the screen stays black after every step, capture a DxDiag report and a copy of Glacier.log from %LOCALAPPDATA%\IO Interactive\007 First Light\ and attach both to a ticket on the IO Interactive support portal. For the broader pattern of black-screen-then-crash across DX12 titles, our [DXGI_ERROR_DEVICE_HUNG fix](/en/errors/dxgi-error-device-hung-fix-all-games) covers the GPU-side recovery options.