Name
Cause
Description
BSODs and frequent shutdowns
These symptoms can be caused by many issues, including bad hardware, drivers, or applications.
If you believe the issue is software-related, try using System Restore or rolling back a driver. If you're unable to get to the desktop, try using Safe mode.
If you think the BSOD may be hardware-related, try reseating or removing the hardware. You can also try using hardware diagnostics which may be provided by the manufacturer or built into the BIOS.
Sluggish performance
Sluggish performance is caused by a system not having enough resources or its resources being overused.
When facing a sluggish system, try using Task Manager to find any processes with high CPU utilization. Also check Windows Update for any available patches, make sure to check for available disk space and defragment the drive if it's an HDD, and in the case of Laptops, check to see if it's using power-saving mode, which throttles the CPU and results in slower performance. Also ensure that the fans and vents of the system are clear, and consider the possibility of malware being the cause. You may want to run a scan with anti-malware software.
Boot errors: "Operating system not found," "Missing operating system"
These errors can be caused by a boot loader (the code within the boot sector that starts the OS) being replaced or changed, or trying to boot from a non-bootable drive.
This issue can be fixed by ensuring that there's no removable media connected and that the drive you do want to connect to is properly connected. If there's an issue with the bootloader, you can try fixing it with Startup Repair or bootrec /rebuildbcd
.
Missing NTLDR
This issue means that the main windows boot loader is missing. It could be caused by the file being missing or corrupted or by the system trying to boot into the wrong drive.
The issue can be fixed by using Startup Repair, replacing the file manually by copying it from another system, or disconnecting removable media.
Boots to Safe Mode
For this issue, use Startup Repair.
Certain hardware not starting
This issue is often caused by a bad driver.
To fix, check Device Manager to manage drivers and Event Viewer to check logs.
"One or more services failed to start"
This issue is associated with bad drivers or hardware.
To fix, first try starting the service manually, then check account permissions to see if it has permissions to run, then confirm that you have its dependencies. If it's a windows service and it's still not working, you should also check system files. Otherwise, if it's an application service, try reinstalling the application.
Application crashes
To find the cause of and prevent further application crashes, check the Event Log for more information as well as the Reliability Monitor. You can also try reinstalling the application.
Low memory warnings
This is caused by memory being overused.
To resolve this issue, install more RAM, close memory-intensive processes, or increase virtual memory.
USB controller resource warnings
USB controllers support different numbers of endpoints. USB devices require certain numbers of endpoints. When you see this warning, the controller doesn't have enough endpoints for the device.
One solution is to move the device to a different interface and try to match the interface version to the device version.
System instability
This is characterized when a system has a lot of issues in several categories. For example, software errors, system hanging, and crashes. These issues could be caused by basically anything.
Because the cause of these issues is so enigmatic, it's probably best to start with a full diagnostic, testing everything from the ground up. Starting with hardware, using manufacturer-provided diagnostics, storage and memory checks, then onto software diagnostics, such as SFC and running anti-malware scans.
Slow profile load
This issue may be caused by network latency on the path to the domain controller or the client workstation choosing a remote domain controller instead of a local one.
This issue can be fixed by reducing latency or contacting the administrator of the remote domain controller and seeing if there's a way to redirect the workstation to the local domain controller.
Time drift
Naturally, a computer's internal clock will drift over time.
To solve this issue, set the machine to sync automatically or manually.