Windows 11 Troubleshooting: Fix Common Errors & Problems

A computer that will not cooperate has a way of derailing an entire day. One minute you are answering emails or finishing a report, and the next you are staring at a frozen cursor, a black screen, or a stop code you have never seen before. Windows 11 problems come in many shapes, from a single application hanging occasionally to a full system crash that repeats every time you turn the machine on. The frustrating part is rarely the crash itself; it is not knowing whether the fix is a two-minute setting change or a sign that a hard drive is failing.

This guide exists to remove that guesswork. It walks through the most common forms of windows 11 troubleshooting, starting with why crashes happen in the first place, moving through specific stop codes such as critical process died and system service exception, and ending with the diagnostic tools professionals use to trace a crash back to its exact cause. Everything here reflects how Windows 11 behaves in its current, actively updated state, including the shift toward a black screen for many stop errors and the ongoing stream of driver and firmware fixes Microsoft ships through Windows Update.

Most windows 11 issues trace back to one of four sources: a driver, a corrupted system file, a hardware fault, or a software conflict introduced by a recent update. Drivers are the most common culprit by a wide margin, since they sit between the operating system’s kernel and the physical hardware, meaning a single poorly written graphics or storage driver can bring down the entire system rather than just the application using it. Corrupted system files, often the result of an interrupted update or a sudden power loss, are the second most frequent cause, and they tend to produce inconsistent, hard-to-reproduce symptoms.

Hardware faults deserve particular attention because they masquerade as software problems more often than people expect. Failing RAM, an overheating CPU, or a storage drive with developing bad sectors can all trigger the exact same stop codes as a bad driver, which is why a proper windows 11 troubleshooting guide always includes a hardware verification step rather than assuming every crash is fixable through software alone. Finally, feature updates and quality updates occasionally introduce regressions of their own; Microsoft has acknowledged several update-related BSOD waves over the past year, including a January 2026 optional update that triggered crashes on certain GPU configurations before a corrective patch resolved it in a later cumulative release.

Every windows 11 blue screen of death event, sometimes now appearing as a black screen rather than the traditional blue one following Microsoft’s recent visual modernization, displays a stop code near the bottom of the error message. That code is the single most valuable piece of diagnostic information you have, because it narrows the likely cause from “something is wrong” down to a specific category of failure. Writing it down, or photographing it with your phone before the system restarts, should always be the first action you take.

Stop codes fall into recognizable families. Some point almost exclusively to drivers, others point to memory or storage hardware, and a few indicate that Windows itself detected tampering or corruption in a protected system process. The table below summarizes the codes windows 11 troubleshooting most commonly involves, along with what each one usually means in practice.

Windows 11 Critical Process Died

Windows 11 critical process died is one of the more alarming-sounding errors, though it is usually more fixable than its name implies. It means a process Windows relies on to keep the operating system running, something core to the kernel or session manager, unexpectedly terminated. The most frequent triggers are corrupted system files, a botched update installation, or a driver that interfered with a protected process. Because the error touches the operating system’s foundation rather than a single peripheral, general driver troubleshooting alone often does not resolve it; running the System File Checker and Deployment Image Servicing and Management tool together, described later in this guide, resolves this stop code more often than any other single fix.

Windows 11 System Service Exception

Windows 11 system service exception occurs when a system service call, essentially a request from an application to the operating system kernel, fails in a way Windows cannot recover from safely. In practice, this stop code is most often linked to graphics drivers, particularly after a driver update, and to specific .sys files named directly in the error details, such as win32kfull.sys. Community reports throughout 2026 have tied several waves of this error to browser-heavy workloads, including Chrome sessions with many open tabs running alongside outdated graphics drivers following the May 2026 cumulative update. If the crash names a specific driver file, searching that filename alongside “BSOD” typically confirms whether it is a known issue with an available fix, and updating or rolling back that specific driver resolves the majority of cases.

Windows 11 Kernel Security Check Failure

Windows 11 kernel security check failure appears when Windows detects that a data structure in the kernel has been corrupted or tampered with, which triggers a protective shutdown rather than allowing the system to continue running in a potentially unsafe state. A significant share of recent reports connect this error to kernel-mode anti-cheat systems used by certain games, particularly when hardware-enforced stack protection is enabled alongside an outdated anti-cheat driver. Microsoft addressed a well-documented version of this issue affecting titles with kernel-level anti-cheat in a February 2026 update, so if this error appears specifically while gaming, updating both Windows and the game’s anti-cheat component should be the first troubleshooting step before assuming a deeper system problem.

Once you know the stop code, work through the following sequence in order rather than jumping straight to the most drastic option. Each step resolves a specific category of cause, and going in order avoids wasted effort chasing the wrong fix.

1. Install pending Windows updates.

Open Settings, then Windows Update, and click Check for updates. Install everything available, including optional driver updates, since Microsoft regularly patches BSOD-causing bugs through routine cumulative updates. A large share of windows 11 crash reports tied to a specific feature update get resolved within a few weeks once Microsoft ships a corrective patch, so this single step alone eliminates a surprising number of cases.

2. Identify and roll back recently changed drivers.

Open Device Manager, expand Display adapters and any other hardware category you recently updated, right-click the device, choose Properties, then the Driver tab, and select Roll Back Driver if the option is available. If it is greyed out, download the previous stable version directly from the manufacturer’s support page instead. Graphics, storage, and network drivers are responsible for the majority of driver-related crashes, so start there.

3. Run System File Checker and DISM.

Open Command Prompt as an administrator and run sfc /scannow, letting it complete fully. Follow with DISM /Online /Cleanup-Image /RestoreHealth, which repairs the underlying Windows image that SFC draws from when replacing damaged files. Running DISM before a second pass of SFC often catches corruption that SFC alone cannot repair, since DISM restores the local component store that SFC relies on as its source of clean files.

4. Test your RAM with Windows Memory Diagnostic.

Press Windows key plus R, type mdsched.exe, and choose to restart and check for problems immediately. Faulty memory tends to produce a rotating cast of different stop codes rather than the same one every time, since corrupted data lands in a different memory location with each crash, so inconsistent error codes across multiple crashes are a strong hint to check this first.

5. Check the drive with CHKDSK.

Open an elevated Command Prompt and run chkdsk C: /f /r, then confirm the scan for next restart if prompted. This step scans for and attempts to repair bad sectors and file system errors, which commonly affect older mechanical drives but can also surface on SSDs experiencing firmware issues.

6. Use System Restore or uninstall the latest update.

If the crashes began immediately after a specific update, open Settings, Windows Update, Update history, and use the option to uninstall the latest quality or feature update. Alternatively, use System Restore to roll the entire system back to a restore point captured before the problem started. Both options are available from the Windows Recovery Environment if the system cannot boot normally.

A windows 11 black screen is not always the same problem as a traditional blue screen crash, even though the two sometimes overlap now that Microsoft has shifted several stop error displays to a black background as part of its ongoing visual modernization. More often, a black screen with no error text at all points to a display driver that failed to initialize, a loose or faulty display cable, or a Windows Explorer process that crashed without restarting itself.

Start by pressing Windows key plus Ctrl plus Shift plus B, which forces a graphics driver refresh and often restores the display within a few seconds if the driver simply hung rather than crashed outright. If that does nothing, press Ctrl plus Alt plus Delete to see whether the login screen or Task Manager appears; if it does, the issue is isolated to Windows Explorer, and you can restart that process directly from Task Manager’s File menu using Run new task and typing explorer.exe. If the screen remains completely black with no response to any input, connect the display cable to a different port, or test a different cable and monitor entirely, since black screens with zero response are disproportionately caused by loose physical connections rather than software.

A system that displays the manufacturer logo, restarts, or shows an error before Windows ever loads is dealing with a different category of problem than a mid-session crash. Windows 11 won’t boot situations most often trace back to a corrupted boot configuration, a failing drive, or a Windows update that did not finish installing correctly.

The fastest path to recovery is entering the Windows Recovery Environment, which happens automatically after two or three failed boot attempts in a row, or manually by holding the power button during startup to force an interruption. From there, Troubleshoot, Advanced options presents several tools worth trying in sequence: Startup Repair scans for and attempts to automatically fix common boot problems, Startup Settings lets you boot into Safe Mode to isolate whether a driver or startup program is the culprit, and Command Prompt provides access to manual repair commands such as bootrec /fixmbr, bootrec /fixboot, and bootrec /rebuildbcd, which rebuild the boot configuration data that Windows depends on to start correctly. If none of these succeed and the drive itself is suspected, connecting it to another computer as a secondary drive can confirm whether the hardware is still readable, which is the clearest sign of whether you are looking at a software fix or a drive replacement.

Windows 11 won’t shut down is a quieter but equally disruptive problem, usually surfacing as the system hanging on the “Shutting down” screen indefinitely, or appearing to shut down and then restarting on its own. The most common cause is a background application or service refusing to close, often because Fast Startup, a feature that hibernates the kernel session instead of performing a full shutdown to speed up the next boot, is interacting poorly with a specific driver.

Disabling Fast Startup resolves this issue more often than any other single fix. Open Control Panel, Power Options, choose what the power buttons do, click Change settings that are currently unavailable, and uncheck Turn on fast startup. If shutdown problems persist afterward, open Event Viewer, navigate to Windows Logs, System, and filter for Critical and Error events around the timestamp of a failed shutdown attempt, which usually names the specific service or driver responsible. Updating that driver, or temporarily disabling the associated background application, typically resolves the remaining cases.

When windows 11 keeps freezing or windows 11 keeps crashing on a recurring basis rather than as an isolated event, the troubleshooting approach shifts from reacting to a single incident toward building a pattern. Pay attention to when the freeze happens: during specific applications, under heavy load such as gaming or video editing, at idle, or seemingly at random. A freeze that only occurs under load points toward thermal throttling or power delivery issues, while a freeze that happens at idle more often points toward a background service, a driver conflict, or a failing storage drive.

Reliability Monitor, accessible by typing “reliability” into the Start menu search box, is one of the most underused built-in tools for this exact scenario. It displays a day-by-day timeline of every application crash, Windows failure, and warning event on the system, making it far easier to spot whether a freeze correlates with a specific piece of software or a specific date, which often lines up with when a particular driver or update was installed. Combine this with Task Manager’s Performance tab during an active freeze, if the system remains responsive enough to open it, to check whether CPU, memory, disk, or GPU usage spikes to its ceiling right before the freeze occurs, since a resource bottleneck behaves very differently from a true system hang and calls for a different fix.

As a general windows 11 freeze fix, close background applications one at a time to isolate whether a specific program is responsible, particularly overlay software from graphics card utilities, chat applications, or recording tools, since overlays are a disproportionately common cause of freezing that has nothing to do with the operating system itself. As a broader windows 11 crash fix for recurring issues, a clean boot, which starts Windows with only essential Microsoft services and no third-party startup programs, isolates whether a startup application is interfering with core system stability; you can configure this through the System Configuration utility, accessible by typing msconfig into the Start menu.

When the built-in troubleshooting steps narrow down the problem but you still need to pinpoint the exact driver or module responsible, dedicated crash-analysis tools read the minidump files Windows automatically generates during a crash and translate the raw data into something readable. The following tools are established, actively maintained, and remain reliable for windows 11 troubleshooting as of 2026.

Fixing a crash after it happens is only half of good windows 11 troubleshooting; the other half is reducing how often you need to troubleshoot at all. Keeping graphics, chipset, and storage drivers current is the single highest-leverage habit, since these three categories are responsible for the overwhelming majority of stop codes covered in this guide. Most manufacturers now offer lightweight utilities that check for driver updates automatically, and checking manually every month or two through Device Manager takes only a few minutes.

Maintaining at least 10 to 15 percent free space on your system drive also matters more than most users realize, since low free space interferes with paging file operations, temporary update files, and Windows’ own repair mechanisms, occasionally contributing to instability that looks unrelated to storage at first glance. Running Disk Cleanup periodically, or using Storage Sense under Settings, System, Storage to automate the process, keeps this from becoming a recurring issue.

Finally, resist installing every Windows update the moment it appears if your system handles mission-critical work. Waiting a week or two after a major feature update’s public release, unless a security patch is involved, gives Microsoft time to identify and patch early regressions like the ones referenced earlier in this guide, and it means you benefit from the collective troubleshooting the broader Windows community has already done on your behalf.