Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
Driver Verifier is a built-in Windows 10 diagnostic tool, not a driver updater. It stress-tests kernel-mode and graphics drivers and can intentionally trigger a blue screen when it detects illegal behavior. The safest workflow is to verify one suspected third-party driver, reproduce the failure, collect the evidence, and then reset Verifier. Because it can cause crashes or a boot loop, create recovery options before enabling it.
Driver Verifier is present in most Windows 10 editions as %WinDir%System32Verifier.exe; Microsoft specifically excludes Windows 10 S. Windows 10 free mainstream support ended on October 14, 2025, but the utility remains available on installed Windows 10 systems. See Microsoft’s Driver Verifier documentation.
What Driver Verifier does
Verifier monitors kernel-mode and graphics drivers for problems such as illegal calls, memory misuse, synchronization errors, I/O failures, security violations and other improper behavior. When a violation is detected, it may deliberately stop Windows so the failure can be captured. A common result is bug check 0xC4, DRIVER_VERIFIER_DETECTED_VIOLATION.
It does not repair, update or replace a driver. A named driver is evidence that the driver was involved in a violation, not absolute proof that its vendor code alone is defective. Corruption from another driver, incompatible firmware, faulty memory or storage, or an interaction with a filter, security or virtualization driver can produce the same symptom.
#1 Best Overall
Use it after ordinary troubleshooting: record the stop code, remove recently added hardware, inspect Device Manager, and update or roll back the relevant driver. Microsoft’s stop-code guidance is at this support page.
Before you enable Driver Verifier
- Sign in with an administrator account; membership in the Administrators group is required.
- Save work and back up important files.
- Create a System Restore point if Windows is currently stable.
- Know how to open Windows Recovery Environment (Windows RE) and Safe Mode. If BitLocker is enabled, have the recovery key available.
- On an important or production computer, arrange a recovery plan before deliberately enabling crash testing.
First record any existing configuration from an elevated Command Prompt:
verifier /querysettings
verifier /query/querysettings shows settings scheduled for the next boot; /query shows current activity and statistics. Volatile settings are not listed by /querysettings.
Identify a driver worth testing
Start with a third-party .sys file named by an existing blue screen or dump. Other useful clues are a driver installed or updated just before the crashes and the device involved—graphics, storage, networking, audio, virtualization, security software or a peripheral. Check the file’s vendor and date in its properties or Device Manager, and use WinDbg or another debugger when a dump is available.
Rank #2
- 15.6" diagonal, HD (1366 x 768), micro-edge, BrightView, 220 nits, 45% NTSC.
A filename alone does not establish liability. After Verifier identifies a driver, update, roll back, disable or uninstall it and test whether the original failure disappears.
Use Driver Verifier Manager (GUI)
- Press Windows key + R, type
verifier, and press Enter. Approve the User Account Control prompt. You can also runverifierfrom an elevated Command Prompt. Microsoft describes the utility at The Verifier utility. - Select Create standard settings, then select Next.
- Choose Select driver names from a list, then select Next.
- Check one suspected third-party driver, or a small set belonging to the same device stack. Select Finish.
- Restart Windows. Verification normally becomes active after the restart.
Standard settings include Special Pool, Force IRQL Checking, Pool Tracking, I/O Verification, Deadlock Detection, DMA Verification, Security Checks, miscellaneous checks, DDI compliance checking and (through the /standard syntax on relevant Windows 10 versions) WDF verification. Microsoft notes that selecting one driver leaves more resources for detailed checks; selecting every driver can exhaust Special Pool and other resources and degrade performance. See driver-selection guidance.
Use an elevated Command Prompt
Open Command Prompt with Run as administrator. Replace each example name with the driver’s actual binary name.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Verify one or several drivers
verifier /standard /driver example.sys
verifier /standard /driver driver1.sys driver2.sysDriver names are separated by spaces; wildcards such as n*.sys are not supported by /driver. On Windows 10 versions after 1803, prefer /standard over older guides that use /flags 0x209BB: Microsoft documents that the hexadecimal form no longer automatically enables WDF verification, while /standard includes the standard options and WDF verification.
Rank #3
- 10th Generation Intel Core i5-1035G1 processor
- 12GB system memory for full-power multitasking
- 256GB Solid State Drive
- 15.6" Micro-edge touchscreen display
Verify every driver (advanced)
verifier /standard /allThis gives broader coverage but increases overhead, can consume diagnostic resources and makes frequent crashes or boot failures more likely. It should not be the default choice for a home troubleshooting session.
Check status
verifier /querysettings
verifier /queryAfter the restart: reproduce and investigate
- Use the computer normally enough to reproduce the failure.
- Record the stop code and any named driver; photograph the screen if Windows restarts too quickly.
- Save the resulting minidump or memory dump and inspect it with WinDbg or another debugger. Microsoft notes that a debugger connected to the test computer can display the violation when Verifier detects it.
- Compare the driver with its device or vendor, installation date and available update, rollback or removal options.
- Change or remove the suspected driver and test independently. Keep Verifier enabled only long enough to collect useful evidence.
Turn Driver Verifier off
From an elevated Command Prompt, clear the settings and then restart:
verifier /reset
shutdown /r /t 0The reset is not fully applied until Windows reboots. You can also open verifier, choose Delete existing settings, finish the wizard and restart. Do not leave Verifier enabled indefinitely; its stricter checks can cause unnecessary crashes and performance impact.
If Driver Verifier causes a boot loop
Use Windows RE and Safe Mode
- Enter Windows RE. Hold Shift while selecting Power > Restart, or in Windows 10 go to Settings > Update & Security > Recovery > Advanced startup > Restart now.
- If Windows cannot reach Settings, allow failed starts to launch Automatic Repair, interrupt startup twice so Windows RE normally appears on the third restart, or boot Windows installation media and choose Repair my PC.
- Select Troubleshoot > Advanced options > Startup Settings > Restart.
- Choose Safe Mode with Command Prompt (or Safe Mode), then run:
verifier /reset
shutdown /r /t 0Safe Mode starts Windows with only basic files and drivers. Recovery procedures may request the BitLocker recovery key. Microsoft’s references are Startup Settings and Windows RE.
Rank #4
- Latitude 7480 Laptop 14"
- Intel Core i7 6th Gen i7-6600U -Core Processor 2.6GHz (3.4GHz With Turbo Boost)
- 256 GB SSD Hard Drive & 16GB Memory
- 1920x1080 FHD resolution Non-Touch with Webcam and an integrated graphics chip
- Wireless Wifi & Bluetooth
Reduce boot risk before testing
The command-line utility supports these boot modes:
verifier /bootmode oneboot
verifier /bootmode disableafterfail
verifier /bootmode persistent
verifier /bootmode resetonunusualshutdownonebootapplies verification to the next boot only.disableafterfaildisables it on subsequent boots if Windows fails to start.persistentkeeps verification active across reboots.resetonunusualshutdownkeeps it active until an unusual shutdown occurs.
oneboot or disableafterfail can limit exposure, but neither removes every recovery risk.
Advanced: volatile settings
Volatile settings take effect immediately and last only until the next boot. They are intended for experienced testers, not the normal GUI workflow. For example:
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11verifier /volatile /flags 0x10 /adddriver example.sysHere, 0x10 is I/O Verification. Microsoft documents volatile-setting limitations and deprecation considerations at Using volatile settings and I/O Verification.
Best Value
- ★ Outstanding Performance: 14" BrightView glossy screen maintains the vivid colors in your photos and videos. Typical 1366 x 768 HD resolution and Micro-edge display to see more, do more from anywhere with a less than 7 mm micro-edge bezel display, 4GB system memory for basic multitasking, adequate high-bandwidth RAM to smoothly run multiple applications and browser tabs all at once.
- ★ Rapid Connection: Connect to a Wireless-AC router for nearly 3x the speed, more capacity, and wider coverage than Wireless-N (150 Mbps). Backward-compatible with all other Wi-Fi networks and hotspots. Gigabit Ethernet LAN port. Built-in media reader for simple photo transfer
- ★ AMD Radeon Graphics: Integrated graphics chipset with shared video memory provides solid image quality for Internet use, movies, basic photo editing, and casual gaming.
- ★ Complete Configuration: The HP 14 14" HD SVA Anti-Glare Micro-Edge WLED-backlit Laptop covers 1x SuperSpeed USB Type-C 5Gbps signaling rate, 2x SuperSpeed USB Type-A 5Gbps signaling rate, 1x RJ-45, 1x Headphone/microphone combo, 1x AC Smart pin, 1x HDMI. With the Accessory Bundle (USB Extension Cord, HDMI Cable, and Mouse Pad).
- ★ Windows 10 Home in S mode: Experience the most secure Windows ever built with fast boot times, increased responsiveness and added protection against phishing and malware.
Driver Verifier command reference
| Command | Purpose |
|---|---|
verifier |
Opens Driver Verifier Manager. |
verifier /standard /driver name.sys |
Enables standard checks for a named driver. |
verifier /standard /all |
Enables standard checks for all drivers. |
verifier /querysettings |
Displays settings scheduled for the next boot. |
verifier /query |
Displays current activity and statistics. |
verifier /reset |
Clears Driver Verifier settings; restart afterward. |
verifier /bootmode oneboot |
Applies verification for one boot. |
verifier /bootmode disableafterfail |
Disables verification after a failed Windows start. |
Frequently asked questions
Frequently Asked Questions
Is Driver Verifier safe?
It is safe only as a deliberate diagnostic test on a system with backups and a recovery route. It can intentionally crash Windows and can cause a boot loop.
Should I verify all drivers?
Usually no. Start with one suspected third-party driver or a small related group. Microsoft warns that verifying all drivers can exhaust resources and reduce performance.
Does Driver Verifier fix a blue screen?
No. It exposes improper driver behavior. You must update, roll back, disable or remove the implicated driver and verify the result.
Free tools Windows power users keep installed
One-click scans. No signup required.
What does stop code 0xC4 mean?
It is commonly DRIVER_VERIFIER_DETECTED_VIOLATION, indicating that Verifier detected a driver violation. The named driver still requires independent validation.
Does it identify faulty hardware?
Not directly. A violation may involve hardware or firmware incompatibility, but memory, storage and other hardware faults require separate testing.
Does Driver Verifier require a download?
No. It is built into most Windows 10 editions as Verifier.exe; Windows 10 S does not include it.
The Bottom Line
Use targeted standard verification, prepare Windows RE or Safe Mode first, collect the stop-code and dump evidence, and run verifier /reset followed by a restart as soon as the investigation is complete.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesQuick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
