My pleasure, and not a problem!
Right, so the kernel-dump is of the
DRIVER_OVERRAN_STACK_BUFFER (f7) bug check.
This indicates that a driver has overrun a stack-based buffer.
Code:
5: kd> kv
Child-SP RetAddr : Args to Child : Call Site
ffffd000`207cdac8 fffff800`685bc441 : 00000000`000000f7 4d140000`000089ee 0000a0fc`844448ef ffff5f03`7bbbb710 : nt!KeBugCheckEx
ffffd000`207cdad0 fffff800`6845afbc : ffffd000`207a3180 ffffd000`207cdb4c ffffd000`207cdb50 ffffd000`207cdb58 : nt!_report_gsfailure+0x25
ffffd000`207cdb10 fffff800`685567bc : ffffd000`207a3180 ffffd000`207a3180 ffffd000`207af340 00000000`00000000 : nt!PoIdle+0x2ac
ffffd000`207cdc60 00000000`00000000 : ffffd000`207ce000 ffffd000`207c8000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x2c
-- DEFAULT_BUCKET_ID:
GS_FALSE_POSITIVE_MISSING_GSFRAME
Was Driver Verifier enabled at the time of this crash? Hopefully no, because we'll need to enable it to likely get more information as to what specifically caused this buffer overrun. It doesn't appear to be enabled:
5: kd> !verifier
Verify Level 0 ...
Driver Verifier:
What is Driver Verifier?
Driver Verifier is included in Windows 8, 7, Windows Server 2008 R2, Windows Vista, Windows Server 2008, Windows 2000, Windows XP, and Windows Server 2003 to promote stability and reliability; you can use this tool to troubleshoot driver issues. Windows kernel-mode components can cause system corruption or system failures as a result of an improperly written driver, such as an earlier version of a Windows Driver Model (WDM) driver.
Essentially, if there's a 3rd party driver believed to be at issue, enabling Driver Verifier will help flush out the rogue driver if it detects a violation.
Before enabling Driver Verifier, it is recommended to create a System Restore Point:
Vista - START | type rstrui - create a restore point
Windows 7 - START | type create | select "Create a Restore Point"
Windows 8 -
Restore Point - Create in Windows 8
How to enable Driver Verifier:
Start > type "verifier" without the quotes > Select the following options -
1. Select - "Create custom settings (for code developers)"
2. Select - "Select individual settings from a full list"
3. Check the following boxes -
- Special Pool
- Pool Tracking
- Force IRQL Checking
- Deadlock Detection
- Security Checks (Windows 7 & 8)
- DDI compliance checking (Windows 8)
- Miscellaneous Checks
4. Select - "Select driver names from a list"
5. Click on the "Provider" tab. This will sort all of the drivers by the provider.
6. Check EVERY box that is
NOT provided by Microsoft / Microsoft Corporation.
7. Click on Finish.
8. Restart.
Important information regarding Driver Verifier:
- If Driver Verifier finds a violation, the system will BSOD.
- After enabling Driver Verifier and restarting the system, depending on the culprit, if for example the driver is on start-up, you may not be able to get back into normal Windows because Driver Verifier will flag it, and as stated above, that will cause / force a BSOD.
If this happens, do
not panic, do the following:
- Boot into Safe Mode by repeatedly tapping the F8 key during boot-up.
- Once in Safe Mode - Start > Search > type "cmd" without the quotes.
- To turn off Driver Verifier, type in cmd "verifier /reset" without the quotes.
・ Restart and boot into normal Windows.
If your OS became corrupt or you cannot boot into Windows after disabling verifier via Safe Mode:
- Boot into Safe Mode by repeatedly tapping the F8 key during boot-up.
- Once in Safe Mode - Start > type "system restore" without the quotes.
- Choose the restore point you created earlier.
How long should I keep Driver Verifier enabled for?
It varies, many experts and analysts have different recommendations. Personally, I recommend keeping it enabled for at least 24 hours. If you don't BSOD by then, disable Driver Verifier.
My system BSOD'd, where can I find the crash dumps?
They will be located in %systemroot%\Minidump
Any other questions can most likely be answered by this article:
Using Driver Verifier to identify issues with Windows drivers for advanced users
Regards,
Patrick