Step 1 — Identify Driver Issues in Device Manager
Device Manager is the authoritative source for hardware and driver status on a Windows system.Open Device Manager
Look for flagged devices
- Yellow exclamation mark (!) — The device has a driver error or configuration problem.
- Red X — The device is disabled.
- Down arrow — The device has been manually disabled.
- Question mark (?) — The device is unrecognized and has no driver installed.
Read the device error code
Check the driver details
Step 2 — Update Drivers via Device Manager
For devices flagged in Device Manager, the quickest first step is to let Windows search for an updated driver automatically. This works well for common peripherals and many chipset components.Right-click the device and choose Update driver
Search automatically for drivers
Check Windows Update for additional driver options
Restart if prompted
Step 3 — Update Drivers from the Manufacturer’s Website
Windows Update does not always carry the latest driver versions, particularly for graphics cards, network adapters, and specialized peripherals. The manufacturer’s site is the authoritative source for the most current, feature-complete driver.Identify the exact hardware model
Navigate to the manufacturer's driver download page
- NVIDIA GPU: nvidia.com/Download/index.aspx
- AMD GPU: amd.com/en/support
- Intel (all components): intel.com/content/www/us/en/download-center
- Realtek audio/NIC: Check your motherboard manufacturer’s support page.
- Laptop/OEM: Use the device manufacturer’s support site (Dell, HP, Lenovo, etc.) and search by service tag or model number.
Download and run the installer
Alternatively, install via Device Manager using a downloaded INF
.inf file rather than a standalone installer:Step 4 — Roll Back a Driver to a Previous Version
If problems started immediately after a driver update, rolling back to the previously installed version is the fastest fix.Open the device properties in Device Manager
Click Roll Back Driver
Prevent Windows from automatically reinstalling the newer driver
Restart and verify stability
Step 5 — Uninstall and Reinstall a Driver
A full uninstall and reinstall clears all cached driver files and registry entries — more thorough than a rollback or update when the driver installation itself is corrupt.Uninstall the device from Device Manager
Scan for hardware changes to trigger automatic reinstall
Remove stubborn driver packages from the driver store
pnputil to manage it:Reinstall the driver from the manufacturer's site
Step 6 — Use Driver Verifier for Instability Diagnosis
Driver Verifier is a built-in Windows tool that stress-tests loaded drivers by imposing additional memory checks and monitoring for rule violations. A driver that passes normal use but occasionally causes crashes will reliably trigger a BSOD almost immediately under Driver Verifier — making it much easier to identify the specific culprit.Launch Driver Verifier Manager
Create a custom configuration
Select drivers to verify
Restart and reproduce the problem
Analyze the minidump to identify the offending driver
MODULE_NAME and IMAGE_NAME fields.Disable Driver Verifier after testing
verifier /reset, boot into Safe Mode — Driver Verifier does not run in Safe Mode — and then execute verifier /reset.Quick Diagnostic Reference
The entries below address common driver failure codes and device-specific scenarios that you can resolve without going through the full troubleshooting workflow.Device shows Code 43 (Device has reported a problem)
Device shows Code 43 (Device has reported a problem)
Device shows Code 10 (Device cannot start)
Device shows Code 10 (Device cannot start)
Audio suddenly stopped working after a Windows Update
Audio suddenly stopped working after a Windows Update
Network adapter disappears from Device Manager after wake from sleep
Network adapter disappears from Device Manager after wake from sleep
Escalation Criteria
Escalate to Tier 2 or a hardware specialist if any of the following apply:- Device Manager shows no driver issues, Driver Verifier triggers BSODs but names only Microsoft kernel components, and the problem persists after a clean OS reinstall — points to a hardware fault (bad RAM, failing PCIe slot, or a damaged device).
- The device is not recognized at all across multiple machines or ports — the hardware itself is likely defective and should be replaced under warranty.
- A critical business application requires a specific older driver version that is incompatible with a required security update — escalate to application owners and the security team for a risk assessment.
- Driver Verifier consistently names the same third-party vendor driver and the vendor has no updated version available — escalate to the vendor’s enterprise support channel with the WinDbg minidump analysis output.
- The machine is a domain-joined device where driver deployment is controlled by SCCM or Intune — driver updates must be packaged and deployed through the standard change management process by the systems team.