Windows OS Hub
  • Windows Server
    • Windows Server 2016
    • Windows Server 2012 R2
    • Windows Server 2012
    • Windows Server 2008 R2
    • SCCM
  • Active Directory
    • Group Policies
  • Windows Clients
    • Windows 10
    • Windows 8
    • Windows 7
    • MS Office
    • Outlook
  • Virtualization
    • VMWare
    • Hyper-V
  • PowerShell
  • Exchange
  • Home
  • About

Windows OS Hub

  • Windows Server
    • Windows Server 2016
    • Windows Server 2012 R2
    • Windows Server 2012
    • Windows Server 2008 R2
    • SCCM
  • Active Directory
    • Group Policies
  • Windows Clients
    • Windows 10
    • Windows 8
    • Windows 7
    • MS Office
    • Outlook
  • Virtualization
    • VMWare
    • Hyper-V
  • PowerShell
  • Exchange

 Windows OS Hub / Windows 8 / Driver Verifier: How to Troubleshoot & Identify Windows Driver Issues

May 22, 2015 Windows 8

Driver Verifier: How to Troubleshoot & Identify Windows Driver Issues

Driver Verifier utility is included in all Windows versions since Windows XP and allows to scan drivers, detect problem drivers, which cause blue screens of death (BSOD), and record a detailed information about the problem driver to the memory dump for further analysis. The tool performs different stress-tests on the drivers simulating various extreme conditions: lack of memory, I/O control, mutual locks, DMA checks, IRP, etc. So it imitates the conditions that seldom occur in productive systems and monitors the driver behavior in them. The objective of the tool is to detect situations that can lead to an unexpected system crash with BSOD.

The executable file of Driver Verifier is called Verifier.exe and is stored in %windir%\system32. You can use the tool either from the command prompt or from its graphic interface.

Important! Before testing drivers, we strongly recommend to create a system restore point and add the Safe Boot mode into Windows 8 boot menu. This will help to disable the debug mode and restore the system to its previous state if something goes wrong.

To enable the driver scan mode in Windows 8, run Driver Verifier by typing

verifier

Driver Verifier - Windows 8

In the tasks list, select Create custom settings (for code developers) and click Next.

Create custom settings (for code developers)

Make sure that Standard settings, Force pending I/O requests, and IRP Logging are checked. Click Next

Standard settings, Force pending I/O requests, and IRP Logging

Then select Select driver names From a list.

Select driver names From a list

Sort the table contents by clicking the heading of the Provider column and select the drivers to be tested from the list. In our example we’ll verify all drivers that are not supplied by Microsoft Corporation. We have checked two drivers: e1g6032e.sys (Intel) and lsi_sas.sys (LSI).

Debug drivers using Driver Verifier

Note. Microsoft digital signature ensures that the driver is tested to verify its stability and its code hasn’t been modified afterwards. This is why it is not recommended disable the verification of the digital signature of drivers or use self-signed drivers.

Now you only have to click Finish and a notification will appear to restart your system for the changes to take effect.

Enable driver verifier Windows 8

Tip. The driver verification mode can be enabled from the command prompt. For example, to start Driver Verifier with the standard settings for myPCDriver.sys driver, the command looks like this:

verifier /standard /driver myPCDriver.sys

After it is restarted, the system boots in the driver verification mode. Driver Verifier works in the background performing different types of tests of the selected drivers to detect errors. Use your computer as usual and wait for the BSOD to appear. If you know what actions have lead to the unexpected crash earlier, do them again. If the BSOD appears, copy the memory dump file (by default it is located in C:\Windows\Minidump\*.dmp) and analyze it with Windbg or a similar tool.

Important! After you activated the driver debug mode using Driver Verifier, this mode is enabled till you disable it manually.

If the problem doesn’t come up within a day or two, to a certain extent you can be sure that the drivers you have verified are not the reason of the system crash and you can disable the verification mode for them.

Tip. Using Windows Driver Verifier is impacting the performance of Windows, so it is not recommended to work with this mode enabled constantly.

You can disable Driver Verifier scanning from the command prompt:

Verifier /reset

Or from GUI by selecting Delete existing settings.

Disable driver verifier

If you can not boot the system in the normal mode, you can disable the debug mode from the Safe Mode.

If the system doesn’t boot in the Safe Mode, try to delete the registry keys in offline mode e, having booted from the installation disk:

  • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
  • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

You can check the current Driver Verifier status like this:

verifier /query

1 comment
0
Facebook Twitter Google + Pinterest
previous post
Manage Domains and Email Address Whitelist in Exchange Server 2013
next post
How to Repair a Corrupt Outlook PST File with Scanpst

Related Reading

How to Restore Deleted EFI System Partition in...

July 29, 2020

Internal SSD/SATA Drive Shows as a Removable in...

December 16, 2019

0x80092004: .NET Framework Install Error on Windows Server

September 16, 2019

Fix: The Local Print Spooler Service Not Running...

July 9, 2019

Resetting Windows Update Agent Settings

May 31, 2019

1 comment

t July 12, 2019 - 3:02 pm

Default location and name of log file, please.

Reply

Leave a Comment Cancel Reply

Categories

  • Active Directory
  • Group Policies
  • Exchange
  • Windows 10
  • Windows 8
  • Windows 7
  • Windows Server 2016
  • Windows Server 2012 R2
  • Windows Server 2008 R2
  • PowerShell
  • VMWare
  • MS Office

Recent Posts

  • Accessing USB Flash Drive from VMWare ESXi

    February 26, 2021
  • How to Sign a PowerShell Script (PS1) with a Code Signing Certificate?

    February 25, 2021
  • Change the Default Port Number (TCP/1433) for a MS SQL Server Instance

    February 24, 2021
  • How to Shadow (Remote Control) a User’s RDP session on RDS Windows Server 2016/2019?

    February 22, 2021
  • Configuring PowerShell Script Execution Policy

    February 18, 2021
  • Configuring Proxy Settings on Windows Using Group Policy Preferences

    February 17, 2021
  • Updating Group Policy Settings on Windows Domain Computers

    February 16, 2021
  • Managing Administrative Shares (Admin$, IPC$, C$, D$) in Windows 10

    February 11, 2021
  • Packet Monitor (PktMon) – Built-in Packet Sniffer in Windows 10

    February 10, 2021
  • Fixing “Winload.efi is Missing or Contains Errors” in Windows 10

    February 5, 2021

Follow us

woshub.com
  • Facebook
  • Twitter
  • RSS
Popular Posts
  • How to Create a 4GB Windows 8.1 x64 Bootable USB Flash Drive
  • Access to more than 4GB of RAM on 32bit Windows 8 (x86)
  • Fix: Windows Modern Apps Don’t Work Over VPN Connection
  • Activation of Data Deduplication in Windows 8.1
  • How to Hide a Windows Service from Users
  • How to create a UEFI bootable USB flash drive for install Windows 8 / Server 2012
  • Windows 8 / 2012 Fix: “Failure configuring Windows updates. Reverting changes”
Footer Logo

@2014 - 2018 - Windows OS Hub. All about operating systems for sysadmins


Back To Top