DRIVER_OVERRAN_STACK_BUFFER on an ASUS Laptop: How to Fix It

DRIVER_OVERRAN_STACK_BUFFER — stop code 0xF7 — is Windows catching a driver in the act of writing past its assigned memory. Every driver buffer has a hidden “canary” value at its edge, and Windows checks it the way a canary in a coal mine was checked: if it’s dead, something went wrong. When the check fails, Windows blue-screens immediately, because a buffer overrun left running is both a stability disaster and a potential security hole.

On ASUS laptops, the usual suspects are Armoury Crate’s kernel drivers, wireless drivers, and the occasional bad Windows Update. The order below hunts them efficiently.

Why this happens

• Buggy Armoury Crate drivers. ASUS’s utility installs kernel drivers for lighting, fans, and power; flawed versions overrun buffers and trigger 0xF7.
• Outdated wireless drivers. MediaTek, Realtek, and Intel Wi-Fi drivers on ASUS models have all had 0xF7-causing releases.
• Corrupted driver installations. Interrupted updates leave mismatched driver files that misbehave in memory.
• Antivirus network filter drivers. Kernel-level packet filters sit in the network stack where overruns are most damaging.
• Mismatched driver/OS combinations. Old drivers on new Windows 11 builds (or new drivers on old builds) make wrong assumptions about buffer sizes.
• Failing RAM (uncommon). Bad memory can corrupt the canary itself — consider only after driver fixes fail.

How to fix it

Work through these in order — start with Fix 1 and stop when the crashes stop.

Fix 1: Update or reinstall Armoury Crate

The prime ASUS-specific suspect.

1. Open Settings > Apps > Installed apps and uninstall Armoury Crate plus Armoury Crate Service.
2. Restart and test for a day — if crashes stop, Armoury Crate was the cause.
3. Reinstall the latest version from the Microsoft Store to get the fixed drivers.
4. If you don’t use its features, leave it uninstalled — fewer kernel drivers means fewer crash sources.
5. Also remove other ASUS kernel utilities you don’t actively use.

Fix 2: Identify the driver with WinDbg

Stop guessing; read the dump.

1. Install WinDbg from the Microsoft Store.
2. Set the symbol path to SRV*C:\Symbols*https://msdl.microsoft.com/download/symbols under File > Settings > Debugging settings.
3. Open the newest dump in C:\Windows\Minidump via File > Open dump file.
4. Run !analyze -v and read the IMAGE_NAME line — that’s your culprit.
5. Run lmvm <drivername> to see the driver’s version and timestamp; an old timestamp confirms it’s outdated rather than merely buggy.
6. Update, roll back, or remove that specific driver instead of updating everything blindly.

Even if you’ve never used a debugger, this takes ten minutes the first time and two minutes thereafter — and it turns 0xF7 from a mystery into a named suspect.

Fix 3: Refresh wireless and audio drivers

The two most common non-ASUS-utility offenders.

1. In Device Manager, expand Network adapters and note your Wi-Fi chip (Intel, MediaTek, Realtek).
2. Uninstall the Wi-Fi driver (tick Attempt to remove the driver), then install the package from ASUS support for your exact model.
3. Do the same for the audio driver under Sound, video and game controllers (usually Realtek).
4. For Intel wireless chips, Intel Driver & Support Assistant may offer a newer stable build.
5. Restart and test under network-heavy use.

The Dell variant of this crash has its own networking quirks — see our DRIVER_OVERRAN_STACK_BUFFER on Dell guide for comparison.

Fix 4: Remove antivirus and VPN filter drivers

Network filters are classic 0xF7 sources.

1. Uninstall third-party antivirus via Settings > Apps > Installed apps and use the vendor’s cleanup tool for leftovers.
2. Uninstall or fully update any VPN client.
3. Restart and run on Microsoft Defender for several days.
4. If crashes stop, reinstall security software one product at a time to identify the guilty one.
5. Prefer vendors whose drivers are WHQL-signed and recently updated.

Fix 5: Roll back recent driver updates

If crashes started after an update, reverse it.

1. Open Device Manager and check recently updated devices.
2. Use Properties > Driver > Roll Back Driver where available.
3. Otherwise uninstall the device (removing the driver) and install the previous version from ASUS support.
4. Pause Windows driver updates temporarily: Settings > Windows Update > Pause updates, or use the group policy Do not include drivers with Windows Updates.
5. For related driver-crash patterns, our DRIVER_IRQL_NOT_LESS_OR_EQUAL guide uses the same rollback logic.

Fix 6: Update the BIOS and run hardware checks

The deep fixes for stubborn cases.

1. Check your BIOS version with msinfo32 and compare to the latest on ASUS support — update if the changelog mentions stability.
2. Flash only with the charger connected; never interrupt it.
3. Run mdsched.exe to test RAM, since bad memory mimics driver overruns.
4. Run sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth in an admin terminal to rule out corrupted system files.
5. If the laptop also hangs on restart screens, see our ASUS restarting screen troubleshooting .

Closing

DRIVER_OVERRAN_STACK_BUFFER is Windows’ buffer-overrun alarm working exactly as designed — the fix is finding which driver tripped it. On ASUS laptops, start with Armoury Crate (the brand-specific wildcard), identify the driver from the dump if you can, and work through wireless, audio, and security filters. The canary died to protect your system; repaying it with a proper driver fix keeps that protection meaningful.

One more habit that pays off: after any driver update, create a restore point (Control Panel > System > System Protection > Create) before installing. Driver updates are the most common trigger for 0xF7 regressions, and a restore point turns a bad update from an afternoon of troubleshooting into a five-minute rollback. Test each fix for at least a full day of normal use before moving on — buffer overruns are often intermittent, and declaring victory too early is the most common mistake.

Frequently asked questions