Review drivers and updates

Build the change timeline before touching a driver

Open Settings > Windows Update > Update history and record quality, driver and definition updates installed near the first crash. In Device Manager, open the relevant device's Properties > Driver and record provider, date and version. Also check the application or hardware vendor's release notes when the problem is tied to a specific device.

A driver date is not a quality score. Some stable manufacturer packages use older dates, and Windows may select a compatible package rather than the numerically newest file. The strongest evidence is a symptom that starts after one change and improves when that change is safely reversed.

Use a trusted driver source order

Microsoft states that most driver updates arrive through Windows Update. If Windows Update cannot provide a suitable driver, use the device manufacturer's official site. Microsoft explicitly warns against downloading drivers from other websites.

Avoid generic driver-updater programs that scan the system and replace many packages at once. They weaken rollback evidence and can install mismatched drivers. For laptops and prebuilt PCs, the computer manufacturer's validated package may be preferable to a generic component driver, especially for power, chipset, graphics switching and firmware.

1. 1

   Install pending supported Windows quality updates only after protecting data.

2. 2

   Check Optional updates for a driver specifically related to the symptom.

3. 3

   Record the current driver provider, version and date before changing it.

4. 4

   Download manually only from Microsoft or the device/computer manufacturer.

5. 5

   Verify the exact model and Windows version before installation.

6. 6

   Keep the previous installer or rollback path when practical.

Roll back one recent driver when the evidence supports it

Device Manager includes a Roll Back Driver option when Windows retains the previous package. Microsoft support guidance uses rollback when a device worked before a recent driver update, rather than as a general performance tweak.

Create a restore point, close active work and roll back only the device linked to the symptom. Restart, repeat the original workload and record whether the crash returns. If Roll Back is unavailable, use the manufacturer's supported reinstall instructions; do not delete driver-store files manually.

1. 1

   Open Device Manager and locate the device connected to the symptom.

2. 2

   Open Properties > Driver and capture the current details.

3. 3

   Select Roll Back Driver only if the issue began after that update.

4. 4

   Choose an accurate reason and restart Windows.

5. 5

   Repeat the same workload at least twice.

6. 6

   Restore or update again if the rollback does not improve the symptom.

Treat Windows updates as testable changes, not permanent suspects

Microsoft provides update history and supported uninstall paths, including Windows Recovery Environment when Windows cannot start. Uninstalling an update should be tied to a recent problem and followed by verification; security implications also matter.

Before uninstalling, check Microsoft's release-health information for known issues and mitigations. Do not permanently block all updates. If one update is removed for testing, document it and plan how the device will return to a supported security state.

Escalate firmware and chipset work when model-specific guidance is unclear

BIOS/UEFI and firmware updates can correct stability issues but carry higher risk than ordinary driver changes. Use the exact device model, power requirements and vendor instructions. Never interrupt firmware installation or use a package intended for a similar model.

On managed systems, contact IT. For crashes involving storage, encryption or boot, confirm the BitLocker recovery key before firmware changes.

Common mistakes to avoid

• Using an unofficial driver download site.
• Replacing many drivers before testing one hypothesis.
• Assuming the newest version number is always best for an OEM laptop.
• Uninstalling security updates indefinitely without a supported plan.