A Windows tool called Driver Verifier was created specifically to identify device driver problems. It is especially useful for identifying the drivers that are responsible for Blue Screen of Death (BSOD) errors. The most effective method for identifying the root causes of the BSOD crash is to use the Driver Verifier.
Fix Blue Screen of Death (BSOD) issues with Driver Verifier
Before proceeding, make sure that Minidumps are enabled. Minidump is a file that stores critical information about Windows crashes. To put it another way, whenever your system crashes, the events leading up to that crash are stored in the minidump (DMP) file. This file is critical in preventing crashes. Driver verifier is only useful if you can log into your Windows normally rather than in safe mode because in safe mode most of the default drivers are not loaded. After that, remember to set up a System Restore point.
IMPORTANT: After running the driver verifier, be sure to switch it off from safe mode. To stop the driver verifier, exit safe mode, launch CMD with administrative permissions, type “verifier /reset” (without the quotes), and press Enter.
Make sure that Minidumps are enabled before continuing. Minidump, as it turns out, is a file that contains important information about Windows failures. Put another way, the minidump (DMP) file contains the events that led up to any system crash. This document is vital for diagnosing
- within your system and can be turned on as
- Type system. cpl and press Enter after pressing Windows Key + R.
- Click on Settings under Startup and Recovery after selecting the Advanced tab.
- Verify that “Automatically restart” is selected.
- Next, under the Write debugging information header, choose Small memory dump (256 KB).
- For Windows 10 users, opt for the Automatic RAM dump feature.
- Lastly, confirm that %systemroot%\Minidump is the Small dump directory indicated
- Turn your computer back on.
Fixing Blue Screen of Death (BSOD) issues with Driver Verifier
- Open the search bar on your Windows computer and type cmd.
- Next, give it a right-click and choose “Run as Administrator.”
- Enter the next command into the CMD and press Enter: Click Next after checking the box marked “Create custom settings (for code developers)”.
- Make all the selections except for the DDI compliance check and the randomized low-resource simulation.
- Once the “Select driver names from a list” box has been checked, click Next.
- Choose every driver save the ones that come from Microsoft. Click Finish to launch the driver verifying program.
- Type the following command into admin cmd to confirm that the driver verifier is running:
- A list of drivers would be returned if the verifier was operating. Restart the driver verifier by following the instructions above if it isn’t working.
- Reboot your computer and carry on with regular operations until the system crashes. If there is a specific action that causes the crash, make sure you take it again.
Note: The primary goal of the above stage is to cause our system to crash since the driver verification is causing stress in the drivers and produces a full crash report. Driver Verifier should be allowed to run for 36 hours before being stopped if your system crashes.
- Lastly, switch to safe mode after utilizing driver verifying for the last time. From here, enable the advanced legacy boot menu.
- With the admin benefits, open CMD, type verifier /reset, and press Enter.
- The goal of the methods mentioned above is to identify the driver that is causing the Blue Screen of Death (BSOD).
- Simply download and install BlueScreenView after you have successfully recorded the issue in the memory dump file (this happens automatically when your computer dies).
- Open BlueScreenView and load your Minidump or Memory dump files from C:\Windows\Minidump or C:\Windows (the files have a.dmp extension).
- After that, you will learn which driver is the source of the problem; simply install that driver, and the issue will be resolved.
- If you’re not familiar with the particular driver, look it up on Google to learn more.
- To save all of your changes, restart your computer.
Errors that Driver Verifier can correct:
- VIOLATION DETECTED BY DRIVER VERIFIER (Violation Detected by Driver Verifier)
- Failure of the Kernel Security Check (Failed Kernel Security Check)
- The term “Driver Verifier Iomanager Violation” refers to this.
- Expool with a driver corrupted: DRIVER_CORRUPTED_EXPOOL
- FAILURE OF DRIVER_POWER_STATE (State of Driver Power Failure)
- The error code for the KMODE exception not handled is KMODE_EXCEPTION_NOT_HANDLED.
- Blue Screen of Death (BSOD) Error in NTOSKRNL.exe
This concludes the tutorial on “Using Driver Verifier to fix Blue Screen of Death (BSOD) errors,” but please feel free to ask any further questions in the comments section if you still have any.
