iSumsoft»Internet » Diagnose Windows Freezes

3 Ways to Diagnose Windows Freezes When CPU, Memory, and Disk Usage Look Normal

Cynthia Huff
Cynthia Huff

Updated:

Windows can freeze even when Task Manager shows plenty of free CPU, memory, and disk. This guide walks you through three reliable diagnostics: reading Reliability Monitor, exporting Windows Error Reporting logs, and trimming heavy context menu entries.

Windows desktop showing troubleshooting tools for freezes

Does your PC pause for seconds or minutes while CPU, memory, and disk usage stay low? These silent hangs are usually caused by hidden application errors, damaged drivers, or shell extensions that misbehave during everyday actions.

The three workflows below help you pinpoint the culprit quickly without reinstalling Windows.

Why Windows Freezes When Usage Looks Normal

Windows can appear idle while the shell waits for a stalled process to respond. Background updaters, audio utilities, VPN clients, and even printer drivers may hang without consuming visible resources. Reliability Monitor and Windows Error Reporting collect detailed fault data every time this happens, so the fastest path to a fix is to read those logs instead of guessing.

Method 1. Inspect Reliability Monitor for recurring errors

Step 1 Press the Windows key, type View reliability history, then open the Reliability Monitor panel.

Search for View reliability history in Windows

Step 2 Focus on the days when the freezes occurred. Red X icons indicate application failures while yellow exclamation marks indicate warnings.

Reliability Monitor timeline highlighting application failures

Step 3 Double click any failure to read the technical details. Note the faulting application or driver. Uninstall, update, or repair that software, then monitor for improvement.

Double-clicking a failure in Reliability Monitor to review more detail information

Reliability Monitor keeps up to a year of history, so you can verify whether the issue started after a recent installation. If multiple apps fail together, update shared dependencies such as graphics drivers or security suites.

Method 2. Review Windows Error Reporting crash logs

Each time a program crashes, Windows creates a .wer report under Windows Error Reporting (WER). These reports live in two folders:

%ProgramData%\Microsoft\Windows\WER\ReportArchive\

%UserProfile%\AppData\Local\Microsoft\Windows\WER\ReportQueue\

Step 1 Open File Explorer and browse to the folders above. Sort by date to find the latest AppCrash entries.

Step 2 If you see an access denied prompt, launch Windows Terminal or PowerShell as administrator and copy the report with:

Get-ChildItem "C:\ProgramData\Microsoft\Windows\WER\ReportArchive\\Report.wer" -Force |

Copy-Item -Destination "$env:USERPROFILE\Desktop\Report.wer" -Force

Step 3 Open the copied Report.wer in Notepad. The Faulting Module and Exception Code entries usually point directly to the unstable driver or app. Share the text with an AI assistant or support team to speed up analysis.

Method 3. Disable heavy items in the right click menu

If freezes trigger when you right click files or folders, a shell extension is likely at fault. Tools such as ContextMenuManager let you toggle context menu entries without deleting them.

Step 1 Launch ContextMenuManager as administrator.

Step 2 Expand ContextMenu categories and disable third party items you rarely use.

Step 3 Restart File Explorer or sign out and back in. If the lag disappears, re-enable items one at a time to isolate the offender.

ContextMenuManager disabling shell extensions

Extra tips to keep Windows responsive

Install critical Windows Updates and reboot after driver changes.

Scan for malware with Microsoft Defender or your preferred suite.

Back up data before removing drivers so you can roll back if needed.

Create a restore point when the system is stable.

Conclusion

Unexplained freezes rarely happen at random. Reliability Monitor tells you when they started, WER reports reveal the exact module, and ContextMenuManager removes shell extensions that get in the way. Work through the steps in order and you will usually uncover the process that stalls Windows, even when Task Manager shows idle hardware.