- Software and digital services
- Operating system
DRIVER_OVERRAN_STACK_BUFFER
Windows DRIVER_OVERRAN_STACK_BUFFER: driver stack buffer overrun
Risk level
High
Professional inspection is recommended.
Urgency
High
Quick answer
DRIVER_OVERRAN_STACK_BUFFER (0xF7) means a driver wrote past a stack buffer and Windows stopped to protect itself. Start by updating or rolling back the driver you installed or changed just before the first crash.
Safety first
Stop and check this first
- Download drivers only from the maker's website or Windows Update; a driver of doubtful origin is exactly the kind of code this error tries to stop.
- Back up your files before uninstalling drivers or restoring Windows to an earlier point.
Safe checks you can perform
- Which driver changed before the first crash
- Roll back the driver in Device Manager
- Full anti-malware scan
- Safe mode if Windows will not reach the desktop
Leave these tasks to a qualified professional
- Do not attempt this professional task: Find the routine that overran the stack
- Do not attempt this professional task: Case with the driver maker
What a technician must be able to justify
Technician visit
These are the steps they must carry out and show you. Tick them as they work: if steps are skipped, do not accept a part swap.
These are not instructions for opening or handling the equipment yourself. They are the checks that should support a technical conclusion.
Find the routine that overran the stack
What they doThe technician opens the dump in WinDbg, runs !analyze -v and gets the stack with kb to locate the last routine before the overrun handlers.
They must show youthe kb stack and the .sys module containing the routine.
In writingthe responsible driver, its version and the version that fixes it.
Case with the driver maker
What they doWith the module identified, the technician or you open a case with the device or software maker to get a fixed version.
They must show youthe module flagged in the analysis and the installed version.
In writingthe case number and the version that solves the overrun.
Before accepting a part or repair
Nothing has been shown yet. Do not accept a part swap based on the code alone.
Follow these steps
Note: Follow the documented order. An error code identifies the affected system, but it does not prove by itself which part has failed.
Which driver changed before the first crash
- Who:
- you.
- How:
- recall which programs, devices or drivers you installed or updated in the days before and note whether the blue screen shows a .sys file name.
- Result that matters:
- having a specific suspect before touching anything.
- If you have a clear suspect:
- look for a fixed version on the maker's website or roll that driver back.
- If you recall no changes and no file is named:
- review Device Manager.
- Evidence to keep:
- dated list of what was installed and a photo of the blue screen.
Evidence: Stop code error or bug check troubleshooting (IT professionals) · Troubleshooting Windows unexpected restarts and stop code errors
Roll back the driver in Device Manager
- Who:
- you.
- How:
- right-click Start, open Device Manager, open the properties of the suspect or flagged device and, on the Driver tab, use Roll Back Driver if it is available.
- Result that matters:
- returning to the version that worked before 0xF7.
- If the crash stops:
- keep that version until the maker publishes a fixed one.
- If there is no earlier version or the crash continues:
- start in safe mode to uninstall the driver or get technical help.
- Evidence to keep:
- driver name and version before and after.
Evidence: Stop code error or bug check troubleshooting (IT professionals) · Troubleshooting Windows unexpected restarts and stop code errors
Full anti-malware scan
- Who:
- you.
- How:
- download Microsoft Safety Scanner from Microsoft's website or use your up-to-date antivirus and run a full scan of the PC.
- Result that matters:
- ruling out malicious software causing the overrun.
- If it finds something:
- let it remove it, restart and check whether the code returns.
- If it comes back clean:
- a faulty driver is the most likely cause.
- Evidence to keep:
- final scan report with date.
Evidence: Stop code error or bug check troubleshooting (IT professionals) · Bug Check 0xF7 DRIVER_OVERRAN_STACK_BUFFER
Safe mode if Windows will not reach the desktop
- Who:
- you.
- How:
- go to Settings, Recovery, Advanced startup, Restart now; then Troubleshoot, Advanced options, Startup Settings, Restart, and press 4 or F4.
- Result that matters:
- starting with the minimum so you can uninstall the suspect driver without 0xF7 firing.
- If safe mode works:
- uninstall or roll back the driver there and restart normally.
- If it will not start in safe mode either:
- take the PC to a technician with the code written down.
- Evidence to keep:
- whether it started in safe mode and what you uninstalled.
Evidence: Stop code error or bug check troubleshooting (IT professionals) · Troubleshooting Windows unexpected restarts and stop code errors
Still not solved
If the error persists, stop here. See what the technician must do and show you.
Where this code applies
A code is meaningful only inside the right product and version context.
Primary scope
- System
- Software and digital services
- Brand
- Microsoft Windows
- Product type
- Operating system
Known code variants
- 0x000000F7
- 0xF7
- blue screen DRIVER_OVERRAN_STACK_BUFFER
- código de detención DRIVER_OVERRAN_STACK_BUFFER
- DRIVER OVERRAN STACK BUFFER
- pantalla azul DRIVER_OVERRAN_STACK_BUFFER
- STOP 0x000000F7
- stop code DRIVER_OVERRAN_STACK_BUFFER
What it means
Microsoft explains that code 0x000000F7 fires when a driver overruns a stack buffer or local variable in a way that would have overwritten the function's return address. It is the classic buffer overrun attack pattern, and Windows halts the system to stop a malicious user from taking control. The parameters are the stack security cookies, useful only in dump analysis. The code does not by itself prove there is an attack or that any part of the PC is faulty.
Warnings and stop conditions
- Highsource verified
Download drivers only from the maker's website or Windows Update; a driver of doubtful origin is exactly the kind of code this error tries to stop.
Evidence: Stop code error or bug check troubleshooting (IT professionals) · Bug Check 0xF7 DRIVER_OVERRAN_STACK_BUFFER
- Mediumsource verified
Back up your files before uninstalling drivers or restoring Windows to an earlier point.
Evidence: Troubleshooting Windows unexpected restarts and stop code errors
Symptoms and causes
Probable causes · in order
- Programming error in a driverCommon
According to Microsoft, a driver overran a buffer on its stack; the last routine before the overrun handlers is the one that caused it.
Evidence: Bug Check 0xF7 DRIVER_OVERRAN_STACK_BUFFER
- Driver installed or updated recentlyCommon
Microsoft's guide for professionals asks you to review recent software and driver changes and consider going back to the earlier version that worked.
Evidence: Stop code error or bug check troubleshooting (IT professionals)
- Malware forcing the overrunPossible
Since the pattern matches a buffer overrun attack, Microsoft generally recommends running Microsoft Safety Scanner or another antivirus after system stops.
Evidence: Stop code error or bug check troubleshooting (IT professionals) · Bug Check 0xF7 DRIVER_OVERRAN_STACK_BUFFER
Virtual technician
Does DRIVER_OVERRAN_STACK_BUFFER still appear after these checks?
Answer a few questions to narrow down the likely cause and the safest next action. Guidance only - it never replaces a professional.
Sources and technical references
- 1
Stop code error or bug check troubleshooting (IT professionals)
Microsoft · 2026 · official_doc
- 2
Troubleshooting Windows unexpected restarts and stop code errors
Microsoft · 2026 · official_doc
- 3
Solución de problemas de reinicios inesperados y errores de código de detención de Windows
Microsoft · 2026 · official_doc
- 4
Bug Check 0xF7 DRIVER_OVERRAN_STACK_BUFFER
Microsoft · 2026 · official_doc
Was this entry useful?