{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreiflaqu6oqjps5t5yil27bcgdz6oribdxun2dxgpj5zzfszsnhoinq",
    "uri": "at://did:plc:ws6dhxzqnqxu5aqxt4kd27oc/app.bsky.feed.post/3mmuyyotxcu52"
  },
  "coverImage": {
    "$type": "blob",
    "ref": {
      "$link": "bafkreig72dida24clfb66zgzdxrtshopuuqrpgtsukq2izfq6kw4uvsfoy"
    },
    "mimeType": "image/jpeg",
    "size": 154396
  },
  "description": "The launch-week crashes mostly trace back to one GPU setting, and switching it takes about a minute.",
  "path": "/007-first-light-crashing-on-pc-fixes-for-launch-day-errors/",
  "publishedAt": "2026-05-28T02:46:43.000Z",
  "site": "https://allthings.how",
  "tags": [
    "NVIDIA GeForce drivers",
    "AMD Radeon drivers",
    "Intel Arc drivers",
    "latest Visual C++ Redistributable",
    "DirectX End-User Runtime Web Installer",
    "@Qieri"
  ],
  "textContent": "007 First Light landed on PC, PS5, and Xbox Series X|S on May 27, 2026, and a chunk of early players are hitting the same wall: the game won't launch, crashes at the title screen, or hangs when starting a new mission. The dominant cause on PC is straightforward — Windows is handing the game to an integrated GPU instead of the dedicated one, and IO Interactive's engine doesn't tolerate that gracefully.\n\n⚡\n\nQuick answer: Force 007 First Light to run on your dedicated GPU. Open Windows Settings → System → Display → Graphics, add the game's executable from Steam\\steamapps\\common\\007 First Light\\Retail, and set GPU preference to High Performance.\n\n* * *\n\n### Why 007 First Light crashes at launch on PC\n\nMost reports trace back to four causes, and they stack. The game silently picks the integrated GPU on laptops and some desktops, ignoring the discrete card entirely. Beyond that, outdated drivers, corrupted Steam files, and missing Visual C++ or DirectX runtimes account for the remaining failure modes.\n\nA smaller cluster of crashes ties to Resizable BAR (ReBar) being enabled in BIOS, and a separate batch of in-gameplay stutters comes from NVIDIA's frame generation override behaving oddly with the game's own DLSS settings.\n\n* * *\n\n### Force the dedicated GPU through Windows Graphics Settings\n\nThis is the fix that's resolved the most launch-day crashes. Windows defaults the executable to \"Let Windows decide,\" and on systems with both integrated and discrete graphics, that decision is often wrong.\n\n**Step 1:** Find the install folder. In Steam, right-click 007 First Light, choose Manage, then Browse Local Files. The path typically ends in `\\007 First Light\\Retail`. Keep this window open so you can copy the path.\n\nLocating the 007 First Light executable in the Steam install folder.\n\n**Step 2:** Open Graphics Settings. Type `Graphics Settings` into the Windows search bar and open the result. You can also reach it through Settings → System → Display → Graphics.\n\n**Step 3:** Add the game. Under \"Add an app,\" select Desktop app, browse to the Retail folder, and pick the 007 First Light executable. It will appear in the list below.\n\nAdding a desktop application in the Windows Graphics Settings menu.\n\n**Step 4:** Set GPU preference. Click the entry, choose Options, select High Performance, and confirm the dropdown lists your dedicated NVIDIA, AMD, or Intel Arc card — not an integrated one. Save and relaunch.\n\nSetting GPU preference to High Performance for the game executable.\n\nYou'll know it worked when the game reaches the IO Interactive splash without closing, and the in-game settings menu shows your discrete GPU under graphics options.\n\n* * *\n\n### Disable the integrated GPU if Windows still ignores the preference\n\nIf Windows keeps falling back to integrated graphics even after the preference is set, disable the iGPU outright. The game will then have only one option.\n\n**Step 1:** Open Device Manager. Search `Device Manager` in the Windows taskbar and launch it.\n\n**Step 2:** Expand Display Adapters. You'll see both your integrated GPU (Intel UHD, Iris Xe, or AMD Radeon Graphics built into the CPU) and your dedicated card.\n\n**Step 3:** Right-click the integrated GPU and choose Disable Device. Accept the warning prompt, then reboot. Re-enable it the same way after you're done playing if you need it for other workflows.\n\n* * *\n\n### Update to the game-ready GPU driver\n\nBoth NVIDIA and AMD shipped drivers specifically tuned for 007 First Light around launch. Running anything older is asking for trouble with a Denuvo-protected, ray-tracing-enabled title.\n\nPull the latest directly from your vendor:\n\nNVIDIA GeForce drivers\n\nAMD Radeon drivers\n\nIntel Arc drivers\n\nAfter installing, reboot. A clean reboot, not just signing out, clears the old driver state.\n\nImage credit: __Nvidia__\n\n* * *\n\n### Verify game files through Steam\n\nInterrupted downloads or partially applied day-one patches leave behind corrupted shaders or executable chunks. Steam's verification rebuilds the bad files.\n\n**Step 1:** In your Steam library, right-click 007 First Light and choose Properties.\n\n**Step 2:** Open the Installed Files tab and click Verify integrity of game files. Wait for Steam to finish; on an SSD with the full 80 GB install, it usually takes five to ten minutes.\n\n**Step 3:** Once verification completes, relaunch. If Steam reports replacing several files, that was likely the culprit.\n\n* * *\n\n### Install Visual C++ and DirectX runtimes\n\nSteam normally installs these dependencies during setup, but permission issues or a stalled install can skip them. Pull them manually from Microsoft.\n\nGrab the latest Visual C++ Redistributable for x64, then the DirectX End-User Runtime Web Installer. Run both, reboot, and try the game again.\n\nImage credit: __Microsoft__\n\n* * *\n\n### Kill leftover game processes before relaunching\n\nAfter a crash, the 007 First Light executable can stick around in memory. Steam thinks the game is still running and refuses to launch it again — or worse, the new instance fights the old one and crashes immediately.\n\nOpen Task Manager with Ctrl + Shift + Esc, scroll the Processes tab for anything containing \"007\" or \"First Light,\" right-click, and choose End task. Then launch normally.\n\nLook for anything named \"007\" or \"First Light\" in the Processes tab of the Task Manager\n\n* * *\n\n### Disable Resizable BAR if crashes persist\n\nReBar improves performance in most modern titles, but a handful of games crash with it enabled. If you've worked through every other fix and the game still won't stay open, toggle ReBar off in BIOS as a diagnostic step.\n\nThe exact menu varies by motherboard — look under PCIe configuration or Advanced settings for \"Re-Size BAR Support\" or \"Above 4G Decoding.\" Disable it, save, boot, and test. If ReBar wasn't the issue, turn it back on; you don't want to lose its benefits in other titles.\n\n* * *\n\n### Other PC fixes worth trying in order\n\n🔧\n\nWork through these one at a time and test the game between each. Trying everything at once makes it impossible to know what fixed it.\n\nFix| When to try it\n---|---\nClose Discord, MSI Afterburner, RivaTuner, capture software| Crashes happen at launch or during cutscenes\nLower ray tracing, shadows, reflections; cap FPS| You reach the menu but crash during gameplay\nRemove CPU, GPU, or RAM overclocks| Frequent freezes under load\nSwitch NVIDIA App \"DLSS Override - Frame Generation Mode\" to \"Use 3D App Setting\"| Stuttering with frame generation enabled\nAdd the game folder to antivirus exclusions| Crashes happen mid-load with no error message\nRun the executable as administrator| Game launches then closes silently\nClean reinstall on SSD with plenty of free space| Verification keeps finding corrupted files\n\n* * *\n\n### PS5 crashes and freezes\n\nConsole troubleshooting is shorter because there are fewer variables. Work through this order.\n\n**Step 1:** Confirm the day-one patch is installed. Highlight 007 First Light, press Options, and choose Check for Update. Disc copies especially need this — the launch patch is mandatory for stability.\n\nHighlight 007 First Light, press Options, choose Check for Update | Image credit: __Sony (via YouTube/@Qieri)__\n\n**Step 2:** Full power cycle. Don't just suspend. Shut the console down completely from the power menu, unplug it for 60 seconds, plug it back in, and boot.\n\n**Step 3:** Check free storage. Even with the install complete, the PS5 needs headroom for patch unpacking and shader caching. Clear space if you're under 50 GB free.\n\nClear space if you're under 50 GB free | Image credit: __Sony (via YouTube/@Qieri)__\n\n**Step 4:** Disable 120 FPS / Performance mode temporarily. Inside the game, open Settings → Video and switch to the 60 FPS or Resolution mode. If crashes stop, the issue is thermal or VRR-related; a cleaner power cycle and good console ventilation usually resolve it.\n\n**Step 5:** Rebuild the database in Safe Mode if nothing else works. Hold the power button until you hear two beeps, plug a controller in via USB, and choose option 5 (Clear Cache and Rebuild Database). It doesn't delete saves.\n\n* * *\n\n### Xbox Series X|S crashes\n\nThe Xbox path mirrors PS5. Confirm the latest update has finished installing, then do a full power cycle by holding the Xbox button on the console for 10 seconds until it shuts off completely. Unplug for a minute, then boot.\n\nIf freezes continue at the same point, uninstall and reinstall the game to internal storage. External drives can introduce read-speed issues with a title this large.\n\n* * *\n\n### When it's not your setup\n\nIf the game still freezes at the same scene after a clean reinstall and a fully updated system on any platform, it's a game-side bug. Ray Reconstruction and Path Tracing are intentionally absent at launch and will arrive in a later patch, so their omission isn't a malfunction. IO Interactive's support channel is the right escalation path for reproducible crashes that survive every fix above.\n\n📌\n\nNote: Crashes that started after a Windows update affecting multiple games point to a system-level issue, not 007 First Light. Run sfc /scannow and chkdsk before reinstalling the game.",
  "title": "007 First Light Crashing on PC: Fixes for Launch-Day Errors",
  "updatedAt": "2026-05-28T02:46:45.322Z"
}