DRIVER_OVERRAN_STACK_BUFFER (0xF7) is Windows catching a driver in a buffer overrun — the driver wrote past the end of its allocated memory and stomped on something important. Windows’ stack protection spots the damage and blue-screens before it can get worse. Think of it as a security guard catching someone climbing over the fence.

This is purely a driver problem, which is actually good news: no hardware replacement, just detective work to find the bad driver and replace it.

Why this happens

  • A buggy device driver with a buffer overrun: The driver writes more data than its buffer holds — the literal definition of this stop code.
  • Outdated network or USB drivers: These handle variable-length data constantly and are the most common 0xF7 offenders.
  • Third-party antivirus filter drivers: Deep system hooks plus aggressive packet inspection make these frequent culprits.
  • A recent driver update with a regression: Newer is not always better — a fresh driver version can introduce the overrun.
  • Corrupted driver binaries: Partially updated or disk-damaged driver files misbehave unpredictably.
  • Incompatible drivers after a Windows feature update: Drivers written for older Windows builds can overrun buffers under new memory layouts.
  • Faulty RAM amplifying the symptom: Rare for this code, but bad memory can corrupt stack cookies and mimic a driver overrun.

How to fix it

Work through these in order, starting at Fix 1. The dump analysis first — it usually hands you the answer.

Fix 1: Read the crash dump to name the driver

  1. Boot into Windows (Safe Mode if necessary: interrupt startup three times → Troubleshoot > Advanced options > Startup Settings).
  2. Press Win + R, type %SystemRoot%\Minidump, press Enter; open the newest .dmp in BlueScreenView (free, NirSoft).
  3. The highlighted driver — often something like rtwlanu.sys, e1d65x64.sys, or a VPN/antivirus .sys file — is your target.
  4. Write down the exact file name before doing anything else.

The update-triggered variant of this crash has its own walkthrough: fixing DRIVER_OVERRAN_STACK_BUFFER after a Windows 11 update .

Fix 2: Update the offending driver

  1. Open Device Manager (Win + X > Device Manager) and locate the device.
  2. Right-click → Update driver > Search automatically for drivers.
  3. Then open Lenovo Vantage > System Update and install everything offered — Lenovo’s validated drivers are the safest on Lenovo hardware.
  4. For Intel network or chipset hardware, the Intel Driver & Support Assistant finds the newest stable releases.
  5. Restart and test for a few days of normal use.

Fix 3: Roll back if the crashes are new

If blue screens started within days of a driver update, reverse it.

  1. In Device Manager, right-click the device → Properties → Driver tab → Roll Back Driver.
  2. Alternatively: Settings > Windows Update > Update history > Uninstall updates → remove the recent driver update.
  3. Restart, monitor for 48 hours, and skip that driver version in Optional updates until the vendor ships a fix.

Fix 4: Remove third-party antivirus and VPN filter drivers

Security and VPN products cause a disproportionate share of 0xF7 crashes.

  1. Go to Settings > Apps > Installed apps and uninstall your third-party antivirus and VPN client.
  2. Restart — Windows Security activates automatically.
  3. Test for 24-48 hours. If crashes stop, the removed software’s filter driver was the cause.
  4. Reinstall only the latest version from the vendor’s official site if you want it back.

Fix 5: Disable Fast Startup and test in Safe Mode

Fast Startup can preserve a corrupted driver state across reboots, and Safe Mode confirms the diagnosis.

  1. Press Win + R, type powercfg.cpl, press Enter → Choose what the power buttons do → Change settings that are currently unavailable → uncheck Turn on fast startup → Save changes.
  2. Boot into Safe Mode (minimal drivers). If no crashes occur in Safe Mode over several hours, a third-party driver is confirmed as the cause — which aligns with everything above.
  3. For the sibling driver crash code, see our IRQL_NOT_LESS_OR_EQUAL guide .

Fix 6: Repair system files and verify memory

Cover the less-common bases so nothing is left to chance.

  1. Open Terminal (Admin) (Win + X > Terminal (Admin)).
  2. Run sfc /scannow, then DISM /Online /Cleanup-Image /RestoreHealth.
  3. Press Win + R, type mdsched.exe, press Enter → Restart now and check for problems.
  4. If the memory test is clean and SFC/DISM repaired any damage, retest the system under load.

Fix 7: Clean-reinstall the driver with the old version fully removed

When update/rollback cycles do not stick, purge the driver completely and install a known-good version.

  1. In Device Manager, right-click the device → Uninstall device → check Attempt to remove the driver for this device → Uninstall.
  2. Restart. If Windows auto-installs a driver, check its version in Properties > Driver — if it is the bad one, disconnect from the internet temporarily and repeat the uninstall.
  3. Install the known-good version: either the previous version from Lenovo Vantage history or the Lenovo support site for your model.
  4. Restart, reconnect, and verify stability over several days.

Fix 8: Update the Lenovo BIOS and chipset package

Firmware-level fixes close out the remaining causes when drivers check out clean.

  1. Open Lenovo Vantage > System Update and install any BIOS/UEFI update offered — Lenovo documents memory-handling and stability fixes in BIOS changelogs regularly.
  2. Install the full chipset driver package from the Lenovo support site for your exact model, even if Device Manager claims your chipset drivers are current.
  3. Restart twice (the first boot after a BIOS update re-trains memory; the second is the real test).
  4. Use the laptop under the previously crashing workload for several days. If 0xF7 crashes persist past this point with all drivers and firmware current, run an extended MemTest86 pass from USB to be thorough about RAM.

Closing

DRIVER_OVERRAN_STACK_BUFFER is refreshingly honest as blue screens go — it tells you exactly what happened: a driver overran its buffer. Read the dump, replace that one driver, and clear out old antivirus filter drivers, and the crashes end. On Lenovo laptops, running the fix through Lenovo Vantage keeps you on vendor-validated driver versions, which is the best long-term protection against this class of bug recurring with the next update cycle.

Frequently asked questions

What does DRIVER_OVERRAN_STACK_BUFFER mean?
It is stop code 0x000000F7: a driver wrote more data than a memory buffer could hold — a classic buffer overrun — and corrupted adjacent memory, often the function’s return address. Windows detects the corrupted stack cookie and crashes to prevent the corruption from being exploited or spreading. It is always a driver bug, not a Windows bug.
Is this error dangerous for my files?
The crash itself does not damage your files — Windows halts precisely to prevent the corrupted memory from doing harm. Your documents are safe. The underlying buggy driver should still be fixed promptly, though, because the same overrun happening outside the crash path could cause subtler instability.
Which drivers usually cause this?
Network adapter drivers, USB device drivers, and third-party antivirus filter drivers are the most common offenders. Outdated drivers written before modern stack-protection checks are especially prone. The minidump usually names the culprit directly.
Can I just disable the driver that's crashing?
Temporarily, yes — disabling the device in Device Manager stops the crashes and confirms the diagnosis. But that also disables the hardware. The real fix is updating to a corrected driver version, or rolling back to the last version that worked, so you keep full functionality.