How to fix 'Application Not Responding' and 'Program Hang' issues using Windows Resource Monitor
Summary
This guide helps you troubleshoot and resolve: How to fix 'Application Not Responding' and 'Program Hang' issues using Windows Resource Monitor. Follow the steps below to fix the issue.
Common Causes
When an application stops responding, it is often due to a "hang" where the software is waiting for a specific system resource—such as the hard drive, network, or memory—to respond. While Task Manager is useful for killing a frozen app, Windows Resource Monitor allows you to analyse exactly why the program has stopped, helping you determine if the issue is a software bug or a hardware bottleneck. This guide is particularly useful if you have noticed your computer running slow across multiple applications.
Quick Fix Steps
Before diving into deep analysis, try these rapid recovery steps to see if the application resumes normal operation:
- Wait 30 to 60 seconds; some complex tasks may cause a temporary freeze while the system processes data.
- Press
Alt + Tabto see if a hidden dialogue box or confirmation window is blocking the main application. - Press
Ctrl + Shift + Escto open Task Manager, right-click the unresponsive app, and select End Task.
Using Resource Monitor to Analyse the Hang
If an application freezes frequently, use the Resource Monitor to identify the root cause. This tool provides a more granular view than the standard Task Manager.
Step 1: Launching Resource Monitor
- Press the
Windows Keyon your keyboard. - Type
resmonand press Enter. - The Resource Monitor window will open, displaying real-time data across CPU, Memory, Disk, and Network tabs.
Step 2: Identifying the Frozen Process
- Click on the CPU tab.
- In the Processes table, locate the application that is not responding. Processes that have stopped responding are typically marked with a status of "Not Responding" in the Status column.
- Right-click the name of the frozen application.
- Select Analyse Wait Chain.
Step 3: Interpreting the Wait Chain
The Analyse Wait Chain window shows you exactly what is holding up the process. You will typically see one of two scenarios:
- The process is waiting for another process: You will see a tree structure showing that App A is waiting for App B. If App B is frozen, App A cannot proceed.
- The process is waiting for an I/O operation: This indicates the app is waiting for the hard drive or a network share to respond.
Step 4: Interpreting CPU Usage Percentages
On the CPU tab, look at the Average CPU and Maximum CPU columns for the frozen application:
- A process consuming 90% to 100% of a single CPU core for an extended period is likely experiencing a computational loop or a deadlock.
- If CPU usage is near 0% but the app is frozen, the application is likely waiting for an external resource, such as a disk read/write operation or a network response.
Step 5: Checking for Hardware Bottlenecks
If the wait chain does not identify a specific blocking process, check the other tabs in Resource Monitor to see if a system-wide resource is exhausted:
- Disk Tab: Look for high "Highest Active Time" percentages. If the disk is at 100%, the app may be hanging because it cannot read or write data fast enough.
- Memory Tab: Look at the Hard Faults/sec value. Frequent spikes here indicate the system is relying heavily on virtual memory (paging), which significantly slows down application response times.
- Network Tab: Check for high send/receive activity or timeouts. If an application is hanging while trying to access a mapped network drive or cloud service, the network tab will show the bottleneck.
Resolving Common Causes
Safely Ending a Process
If the Analyse Wait Chain identifies a specific non-system process that is causing the hang and you cannot restart the application:
- Check if the application has an auto-save feature or if you can manually save your work in another open window.
- Right-click the blocking process in Resource Monitor and select End Process.
- Confirm the action when prompted. This often "unblocks" the main application, allowing it to resume functioning.
Addressing Disk Bottlenecks
If the Disk tab shows 100% active time:
- Open Command Prompt as an administrator.
- Type
chkdsk C: /fand press Enter to check for and fix disk errors. - Restart your computer to allow the disk check to run if the drive is currently in use.
Addressing Memory Pressure
If the Memory tab shows high hard faults/sec or available memory is critically low:
- Close unnecessary background applications and browser tabs.
- Identify memory-heavy processes in the Memory tab and end those that are not essential.
- Consider upgrading your RAM if the system consistently runs out of available memory during normal operation.
Checking for Software Conflicts and Updates
Recurring hangs are often caused by outdated software or conflicting third-party applications:
- Windows Update: Go to Settings > Windows Update and click Check for updates. Install all available updates and restart your computer.
- Driver Updates: Visit your hardware manufacturer's website to download and install the latest chipset, graphics, and storage drivers.
- Application Updates: Check the application's internal settings or the developer's website for the latest version.
- Antivirus and Firewall: Temporarily disable third-party antivirus or firewall software to determine if it is causing the hang. If the issue stops, add an exception for the affected application.
- Recent Changes: If the hangs started after a recent installation, use Settings > Apps > Installed apps to uninstall the suspect software.
Checking for Malware and Corrupted System Files
Malware can consume system resources and cause application instability:
- Run a full system scan using Windows Security or your installed antivirus solution.
- Open Command Prompt as an administrator and run
sfc /scannowto check for corrupted system files. - If SFC finds errors it cannot fix, run
DISM /Online /Cleanup-Image /RestoreHealthto repair the Windows image.
Deeper Diagnosis Using Event Viewer
For recurring hangs, use Event Viewer to find specific error codes that Resource Monitor may not show:
- Press the
Windows Key, typeEvent Viewer, and press Enter. - In the left pane, expand Windows Logs and click Application.
- Look for events labelled Error or Warning around the time the application hung.
- Double-click an event to view the details, including the source and error code, which can help identify if a specific driver or Windows service is at fault.
Monitoring for Recurrence
After applying a fix, monitor the application over several days to ensure the hang does not return:
- Keep Resource Monitor open during normal use to observe if CPU, Disk, or Memory usage spikes before a freeze.
- Create a baseline of normal system performance by noting typical resource usage when the application is running smoothly.
- If the hang returns immediately upon launch, try running the application in compatibility mode or creating a new user profile to rule out user-specific corruption.
If the application continues to hang despite these steps, please Open a Ticket so our technical team can analyse your system logs.
Still Having Issues?
💻 Open a Ticket