FxFixLog
Windows  //  error reference

The errors that show up.
The fixes that work.

Plain, step-by-step solutions for real Windows stop codes, boot failures, and update problems — no walls of theory, just what to try and the order to try it in.

Ad · 728×90 unit goes here

Latest fixes

6 entries
0x0000007BBoot / Critical

INACCESSIBLE_BOOT_DEVICE on startup

Windows can't reach the drive it's meant to boot from — usually after a storage-driver change, a BIOS mode switch, or a bad update.

  1. Enter BIOS/UEFI and confirm the SATA/NVMe mode matches what Windows was installed with (AHCI vs RAID). Flipping this is the most common cause.
  2. Boot into recovery, open a command prompt and run chkdsk /f /r C: to repair a corrupt file system.
  3. Uninstall the most recent quality update from Recovery → Troubleshoot → Uninstall Updates.
  4. If it started after adding a drive, disconnect the new drive and boot again to isolate it.
100% DiskPerformance

100% disk usage in Windows 11

The machine freezes for seconds at a time and Task Manager shows the disk pinned at 100% even when idle.

  1. Disable Windows Search temporarily: net stop "Windows Search" and check if usage drops.
  2. Turn off SysMain (formerly Superfetch) in Services if you're on an SSD — it rarely helps and often thrashes.
  3. Run sfc /scannow to rule out corrupted system files causing background repair loops.
  4. Update or roll back your storage controller driver from Device Manager → IDE ATA/ATAPI controllers.
CRITICAL_PROCESS_DIEDBSOD

Blue screen: CRITICAL_PROCESS_DIED

A process Windows treats as essential shut down unexpectedly, forcing a stop. Often driver or system-file corruption.

  1. Boot to Safe Mode (hold Shift while clicking Restart → Troubleshoot → Startup Settings).
  2. Run the deployment image tool: DISM /Online /Cleanup-Image /RestoreHealth, then sfc /scannow.
  3. Update chipset and GPU drivers from the manufacturer, not just Windows Update.
  4. If it began recently, use System Restore to a point before the crashes started.
Ad · in-feed / responsive unit
0x80070002Windows Update

Windows Update error 0x80070002

Update download or install fails, usually from a damaged update cache or missing temporary files.

  1. Stop the update services: net stop wuauserv and net stop bits.
  2. Rename the cache folder: ren C:\Windows\SoftwareDistribution SD.old.
  3. Restart the services and retry the update so Windows rebuilds the cache from scratch.
  4. If it persists, run the built-in Windows Update troubleshooter from Settings → System → Troubleshoot.
DLL missingApps

"MSVCP140.dll was not found" and similar

A program won't launch because a shared runtime library is missing — almost always a Visual C++ Redistributable, not a virus.

  1. Install the latest Microsoft Visual C++ Redistributable (both x86 and x64) from Microsoft's official download page.
  2. Repair the specific app through Settings → Apps → Installed apps → Modify/Repair.
  3. Run sfc /scannow in case a system DLL itself was corrupted.
  4. Avoid downloading loose .dll files from random sites — they're a common malware vector and won't fix the root cause.
WHEA_UNCORRECTABLE_ERRORHardware

Blue screen: WHEA_UNCORRECTABLE_ERROR

The Windows Hardware Error Architecture caught a fault it couldn't recover from — typically CPU, memory, or an unstable overclock.

  1. Reset any CPU/RAM overclock or XMP/EXPO profile back to stock in BIOS and test stability.
  2. Run Windows Memory Diagnostic, or MemTest86, to check for failing RAM.
  3. Update your BIOS/UEFI and chipset drivers to the latest stable versions.
  4. Check temperatures under load — repeated faults can come from overheating or a failing power supply.
Ad · responsive unit

About FixLog

FixLog is an independent reference of tested, plain-language solutions to common Windows errors. Each entry lists the steps in the order worth trying, from the most likely cause to the last resort. It's written for people who just want the machine working again.

FixLog is not affiliated with, endorsed by, or connected to Microsoft Corporation. "Windows" is a trademark of Microsoft, referenced here only to describe the operating system these guides apply to.

Privacy Policy

Last updated: 16 July 2026

This page explains how information is handled when you visit FixLog. This site does not ask for, collect, or store personal details such as names, email addresses, or phone numbers. There is no signup, no newsletter, and no contact form.

Log data

Like most websites, standard server logs may record non-identifying technical information such as browser type, approximate region, and the pages visited. This is used only to understand general traffic and keep the site running.

Cookies

FixLog itself does not set tracking cookies. However, third-party services used on this site — mainly advertising — may place cookies in your browser, as described below.

Google AdSense & advertising

This site displays ads served by Google, using the Google AdSense program. Google's use of advertising cookies enables it and its partners to serve ads to you based on your visits to this and other sites.

  • Third-party vendors, including Google, use cookies to serve ads based on your prior visits to this website and other websites on the internet.
  • Google's use of advertising cookies enables it and its partners to serve ads to you based on that browsing activity.
  • You can opt out of personalized advertising by visiting Google Ads Settings.
  • You can opt out of some third-party vendors' use of cookies for personalized advertising at aboutads.info/choices and youronlinechoices.com.

For more on how Google uses data from sites that use its services, see the Google Partner Sites policy. Third-party ad networks may have their own privacy practices, which FixLog does not control.

Consent

By using FixLog, you consent to this Privacy Policy. If you're in a region that requires a consent notice for advertising cookies (such as the EEA or UK), an appropriate consent prompt is shown before personalized ads are served.

Disclaimer

Last updated: 16 July 2026

The guides on FixLog are provided for general informational purposes only and are offered in good faith. Following them is at your own risk.

Editing system settings, the registry, BIOS/UEFI, or drivers can affect how your computer runs. Back up your important files before making changes. FixLog and its authors accept no liability for any data loss, downtime, or damage that results from using this information.

If a problem involves data you can't afford to lose, or hardware that may be failing, consider a qualified technician.