The Driver Overran Stack Buffer blue screen (stop code 0x000000F7) is Windows telling you that a driver wrote past the end of its allocated memory and stomped on something important. Windows treats this as a potential security breach and shuts everything down immediately. It can happen during gaming, file transfers, or when a device wakes from sleep.

The upside: this error almost always traces to one specific driver, so once you identify it, the fix is straightforward. The steps below walk you from the most common suspects to the advanced identification tools. If you’ve upgraded to Windows 11, the same logic applies — see Driver Overran Stack Buffer on Windows 11 — and for post-update cases check the after-update variant .

Why this happens

  • An outdated or buggy device driver. Graphics, network adapter, and audio drivers are the usual offenders — they handle large data buffers constantly.
  • Old peripheral drivers. USB Wi-Fi dongles, printers, and scanners with years-old drivers can overflow their buffers during transfers.
  • A recent driver update gone wrong. A new driver version with a buffer-handling bug starts the crashes overnight.
  • Conflicting drivers. Two drivers trying to manage the same hardware (like a manufacturer utility plus Windows’ own driver) can corrupt each other’s memory.
  • Corrupted driver files. A bad Windows update or disk error can damage a driver that was previously fine.
  • Overclocking instability. An unstable GPU or CPU overclock can cause driver code to misbehave in ways that look like buffer overruns.

How to fix it

Work through these in order. Identifying the driver is half the battle.

Fix 1: Update your most likely drivers first

Start with the usual suspects before doing detective work.

  1. Open Device Manager (press Win + X and choose it).
  2. Expand Display adapters, right-click your GPU, and choose Update driver > Search automatically for drivers.
  3. Do the same for Network adapters (especially Wi-Fi and Ethernet) and Sound, video and game controllers.
  4. For manufacturer-fresh drivers, visit NVIDIA , AMD , or Intel and install the latest for your hardware.
  5. Restart and watch for further crashes.

Fix 2: Read the minidump to name the faulty driver

Windows saves a crash record that usually names the culprit.

  1. Check that minidumps are enabled: press Win + R, type sysdm.cpl, press Enter, go to the Advanced tab, click Settings under Startup and Recovery, and confirm Small memory dump is selected.
  2. After the next crash, navigate to C:\Windows\Minidump and find the newest .dmp file.
  3. Download Microsoft’s free WinDbg Preview from the Microsoft Store, open the dump file, and run !analyze -v in the command box.
  4. Look for the MODULE_NAME or IMAGE_NAME line — it names the driver file (e.g., nvlddmkm.sys for NVIDIA or Netwtw10.sys for Intel Wi-Fi).
  5. Update, roll back, or reinstall that exact driver.

Fix 3: Roll back or reinstall the identified driver

Once you know the driver, fix that one specifically.

  1. In Device Manager, find the device, right-click it, and choose Properties.
  2. On the Driver tab, click Roll Back Driver if it’s available.
  3. If not, choose Uninstall device, tick Attempt to remove the driver for this device, and restart — Windows will install a clean copy.
  4. Then install the latest stable version from the manufacturer’s site rather than the version Windows Update picked.

Fix 4: Disconnect suspect USB devices and update their drivers

Peripherals are an underappreciated cause of this stop code.

  1. Think about what was connected when the crashes happened — a USB Wi-Fi adapter, external drive, printer, or capture device.
  2. Unplug the suspect device and use the laptop for a while. If crashes stop, you’ve found it.
  3. Download the newest driver for that device from its manufacturer’s support page and reinstall it.
  4. If no new driver exists, consider replacing the device — a $20 Wi-Fi adapter isn’t worth repeated blue screens.

Fix 5: Run SFC and DISM to repair corrupted driver files

Disk errors or bad updates can damage driver files that were previously fine.

  1. Right-click the Start button and choose Windows PowerShell (Admin) or Command Prompt (Admin).
  2. Run: sfc /scannow
  3. After it completes, run: DISM /Online /Cleanup-Image /RestoreHealth
  4. Restart and test.

Fix 6: Disable overclocking and fast startup

Both can make drivers behave erratically.

  1. If you use any overclocking utility, reset all values to stock.
  2. Open the Control Panel, go to Power Options, and click Choose what the power buttons do.
  3. Click Change settings that are currently unavailable and uncheck Turn on fast startup.
  4. Click Save changes and restart. Fast startup can load stale driver states that trigger this exact error.

Fix 7: Use Driver Verifier as a last-resort identifier

Only if you still can’t find the culprit — and only after creating a restore point.

  1. Press Win + R, type verifier.exe, and press Enter.
  2. Choose Create custom settings, then select Special pool, Force IRQL checking, and Pool tracking.
  3. Choose Select driver names from a list and tick only the non-Microsoft drivers you suspect.
  4. Restart. If the chosen driver misbehaves, Verifier will crash the system immediately and name it in the dump.
  5. When done, run verifier /reset from an admin prompt and restart — never leave Verifier on permanently.
  6. Microsoft documents the official process in its Windows support hub.

Closing

Driver Overran Stack Buffer sounds dramatic, but it’s really just Windows catching one driver misbehaving and telling you about it. Update the graphics and network drivers, read the minidump to confirm the culprit, and replace the offending driver with a clean version. Do that, and the blue screens stop — no reinstall needed.

Frequently asked questions

What does Driver Overran Stack Buffer mean in plain English?
A driver wrote more data than its memory ‘stack’ was allocated to hold, spilling over into neighboring memory. Windows catches this security violation and crashes immediately. It’s almost always a single misbehaving driver — commonly graphics, network, or an older peripheral driver.
Is this error caused by a virus?
Not typically. Genuine malware infections are a rare cause; the usual culprit is an outdated or buggy legitimate driver. That said, if the crashes started after installing software from a shady source, run a full Defender scan — but start with driver updates, which fix most cases.
Can a USB device trigger Driver Overran Stack Buffer?
Yes, surprisingly often. Old USB Wi-Fi adapters, printers, and external drives with outdated drivers can trigger this stop code when they wake from sleep or transfer data. If crashes happen when plugging in a specific device, update or replace that device’s driver first.
Should I use Driver Verifier to find the bad driver?
Driver Verifier is powerful but risky — it intentionally stresses drivers and can cause boot loops if a bad driver is present at startup. Only use it after backing up your data and creating a restore point, and be ready to disable it from Safe Mode. For most people, checking minidumps is the safer route.