What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
A Windows error message is a notice or code tied to a particular situation: it may describe a serious system crash, a problem with one device, or a failure during setup or an upgrade. Its wording can point you toward the right troubleshooting path, but a code is a clue—not necessarily proof of one root cause. Start by noting exactly where it appeared and recording its full text or code.
What a Windows error message means
Windows error messages report a problem or condition that the operating system has detected. The message’s context matters as much as the code: a stop code shown after a crash is not interchangeable with a Device Manager code or a setup error. These categories have different meanings and require different troubleshooting guidance.
As an Amazon Associate I earn from qualifying purchases.
When you see an error, record the exact wording, any numeric or hexadecimal code, and what you were doing when it appeared. Also note whether Windows restarted, whether the notice appeared beside a particular device, or whether it occurred during installation or an upgrade. Those details help you find the relevant Microsoft instructions instead of applying an unrelated fix.
Recommended Free Tools
How the main categories differ
| Where it appears | What it indicates | Where to start |
|---|---|---|
| Stop code or blue screen | Windows shut down or restarted unexpectedly after a serious problem. Hardware, a driver, or software might be involved; the displayed code narrows the investigation but does not by itself establish the cause. | Record the stop code and any “What failed” name, then follow Microsoft’s stop-code troubleshooting guidance. |
| Device Manager | A particular device or its driver has a status problem represented by a code. The code’s meaning and resolution depend on the exact code. | Look up the code in Microsoft’s Device Manager error-code guide. |
| Windows setup, upgrade, or installation | A problem occurred during that setup process. Its code belongs to installation troubleshooting, not necessarily to a blue-screen diagnosis. | Use Microsoft’s installation and upgrade guidance and the applicable error-code table. |
What a stop code can—and cannot—tell you
A stop code appears when Windows encounters a serious problem and shuts down or restarts unexpectedly. Microsoft also refers to this as a bug check, kernel error, blue-screen error, or BSOD; the screen’s appearance and wording can vary by Windows version. The code and any “What failed” module name can help narrow the possibilities, but neither necessarily identifies a single faulty component. Microsoft notes that hardware, a device driver, or software might have caused the error. See its blue-screen troubleshooting guidance.
#1 Best Overall
Where to begin if a stop-code error keeps returning
Microsoft’s initial steps are intended to help isolate common causes and restore startup; they do not guarantee a fix. Work through the options that fit what changed on your PC:
- Remove recently added hardware. Disconnect new hardware and retry. If the error stops, reconnecting devices one at a time may help identify whether one is associated with the problem.
- Try Safe Mode if Windows is difficult to start. Safe Mode starts Windows with a limited set of files and drivers, which can help distinguish a startup problem from one that occurs only in normal mode. Follow Microsoft’s stop-code guidance for the applicable recovery steps.
- Check Device Manager. Look for devices marked with a warning and investigate their exact status code using the Device Manager code guide.
- Check available disk space. Microsoft says the amount needed varies with system configuration and suggests keeping 10%–15% of the drive free as a practical guideline, not a universal requirement.
- Install available Windows updates. Use Windows Update to check for and install updates, then see whether the stop-code problem recurs.
- Consider Windows recovery options if the problem persists. Choose an option appropriate to the symptoms and follow Microsoft’s recovery instructions; some recovery actions can affect apps or files.
Use logs and diagnostics for further clues
Event Viewer
Event Viewer can show system-log events around the time of a blue screen. Review the System log for critical errors near the restart and compare their timestamps with the crash. A nearby event can provide context, but timing alone does not prove that it caused the stop code.
Windows Memory Diagnostic
Windows Memory Diagnostic is another built-in check to consider when investigating a recurring blue screen. Microsoft says its results can be reviewed in Event Viewer. A diagnostic result is evidence to consider alongside the stop code and other symptoms, rather than a complete diagnosis on its own.
Memory-dump analysis
Windows can produce memory dumps that contain information about a crash. Analyzing those files is an advanced step intended for IT professionals and developers; most users can begin with the standard troubleshooting steps and Microsoft’s guidance rather than trying to interpret a dump without the appropriate tools or experience. Microsoft describes these investigation options in its blue-screen troubleshooting page.
Rank #3
How to find the right guidance
- If Windows displayed a stop code after an unexpected restart, use the stop-code or blue-screen instructions.
- If a specific device has a warning in Device Manager, use the guide for that exact Device Manager code.
- If the error appeared during setup, an update, or an upgrade, use the installation-specific instructions and code table.
Windows error messages are not one universal list with one universal fix. The exact wording, code, and place where the notice appeared determine which explanation is relevant.
Quick Recap
Best Value
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.




