Driver Problems on Windows: How to Diagnose and Roll Back Safely

Diagnose Windows driver problems properly: read the error code, roll back cleanly, stop Windows Update reinstalling a bad driver, and use Driver Verifier safely.

Driver Problems on Windows: How to Diagnose and Roll Back Safely

Drivers cause a disproportionate share of Windows instability, because they run in kernel space. A badly-written one takes the whole machine down rather than just itself. The good news is that Windows keeps the previous version, so rolling back is usually a two-minute job.

The harder problem is stopping Windows Update from putting the bad one straight back.

Quick Facts

  • Device Manager error codes are specific. Code 43 and Code 10 mean different things and need different fixes.
  • Roll Back Driver only works if a previous version exists. It’s greyed out after a clean install.
  • Windows Update reinstalls drivers it thinks are newer. You have to block it explicitly.
  • Get drivers from the hardware vendor, not Windows Update, for graphics and storage.
  • Driver Verifier finds bad drivers, and will bluescreen your machine on purpose. Know how to turn it off first.

Read the error code first

CodeMeaningUsual fix
Code 1Not configured correctlyReinstall the driver
Code 10Device cannot startDriver mismatch, or hardware fault
Code 28Drivers not installedInstall from vendor
Code 31Not working properlyRoll back or reinstall
Code 39Corrupt or missing driverReinstall; check for malware
Code 43Device reported a problemOften genuine hardware failure, especially on GPUs
Code 45Not currently connectedGhost device. Harmless

Code 43 on a graphics card is worth taking seriously. Unlike most codes it frequently indicates the hardware itself has reported a fault, and no amount of driver reinstalling will fix it.

Rolling back cleanly

Quick Steps

  1. Device Manager, find the device, Properties, Driver tab.
  2. Click Roll Back Driver. If it’s greyed out, no previous version is stored. Skip to uninstalling.
  3. Give a reason when prompted, and restart.
  4. If rollback isn’t available: Uninstall device, and tick Delete the driver software for this device.
  5. Restart. Windows reinstalls a generic driver.
  6. Install the vendor’s version manually. Don’t let Windows Update pick.

That tick box matters. Without it, uninstalling removes the device entry but leaves the driver package in the store, so Windows reinstalls the same broken version on reboot.

# List third-party driver packages
pnputil /enum-drivers

# Remove a specific one by its oemXX.inf name
pnputil /delete-driver oem42.inf /uninstall /force

Stopping Windows Update reinstalling it

This is the step people miss, and it’s why a driver problem appears to come back on its own.

  • Microsoft’s “Show or hide updates” troubleshooter lets you hide a specific driver update so it stops being offered.
  • Group Policy: Computer Configuration, Administrative Templates, System, Device Installation, Device Installation Restrictions. Block by hardware ID.
  • Registry: setting ExcludeWUDriversInQualityUpdate stops driver updates arriving with monthly quality updates.
  • Device installation settings: in System Properties, Hardware, turn off automatic manufacturer app and icon downloads.

For graphics drivers specifically, install the vendor’s own control panel and let it manage updates. It will generally supply a newer and better-tested driver than Windows Update anyway.

When you can’t tell which driver it is

If the machine bluescreens and the stop code doesn’t name a driver, Driver Verifier will find it, by deliberately stressing drivers until the bad one fails.

# Start it
verifier /standard /all

# Turn it off - know this BEFORE you start
verifier /reset

Read this before running it. Verifier will bluescreen the machine repeatedly and by design. If it bluescreens during boot you may not reach a desktop to turn it off. You’d boot into Safe Mode and run verifier /reset there. Have a recovery USB ready, and don’t do this on a machine someone needs today.

Once it catches something, the crash dump names the offending driver, and you can go back to rolling that one back.

Glossary

TermWhat it means
Driver storeWhere Windows keeps driver packages for reinstallation. Cleared with pnputil.
Roll Back DriverReverts to the previously installed version. Only available if one is retained.
Hardware IDA unique identifier for a device, used to target policy at specific hardware.
Driver VerifierA stress-testing tool that forces faulty drivers to crash so they can be identified.
Code 43Device Manager code meaning the device reported a fault. Often genuine hardware failure.
pnputilBuilt-in tool for listing and removing driver packages from the store.

Frequently asked questions

Why is Roll Back Driver greyed out?

Because no previous version is stored. Either it’s the first driver installed for that device, or the previous one was cleaned up. Uninstall with the delete-software box ticked instead, then install the vendor’s version.

Should I use driver updater software?

No. They’re a well-known vector for bundled junk, and they frequently install generic drivers over vendor-specific ones. Get drivers from the hardware manufacturer.

Why does Windows keep reinstalling a driver I removed?

Windows Update offers drivers it considers newer, and reinstalls on reboot if the package is still in the driver store. Delete the package with pnputil and block the update explicitly.

Is Driver Verifier safe to run?

It’s safe in that it doesn’t damage anything, but it will bluescreen your machine on purpose and can make it unbootable until you disable it. Only run it when you can afford the downtime, and know the Safe Mode reset command first.

Code 43 on my graphics card. Driver or hardware?

Often hardware, particularly if it persists after a clean driver reinstall. Test the card in another machine if you can before spending money on it.

🛠️

Gear We Recommend

Keeping a recovery USB and a spare drive to hand makes driver troubleshooting far less risky.

Browse our General Tech Accessories picks on Amazon

As an Amazon Associate, TechyGeeksHome earns from qualifying purchases

Disclosure: this post may contain affiliate links. If you buy through one of them, we may earn a small commission at no extra cost to you. We only recommend products we’ve tested or genuinely rate.


Discover more from TechyGeeksHome

Subscribe to get the latest posts sent to your email.

Andrew Armstrong

Andrew Armstrong is a UK-based IT professional with 26+ years of hands-on experience in Windows, Windows Server, SCCM/ConfigMgr, Intune, Active Directory, PowerShell and enterprise infrastructure.

He founded TechyGeeksHome in 2010 and has published 770+ practical guides to real-world IT problems. He also builds free Windows utilities, including Ultimate Settings Panel, which has been downloaded over 850,000 times.

Leave a Reply

Your email address will not be published. Required fields are marked *