Accessing Resource Monitor
To begin monitoring network activity at a deeper level than the standard interface allows, you must launch the Resource Monitor tool directly. This utility is built into Windows 10 and offers real-time data visualization for CPU, Memory, Disk, and Network resources. You can access it through several methods depending on your preference for navigation. The most direct method is using the Run dialog. PressWin + R on your keyboard to open the command box. Type resmon and press Enter. This immediately launches the Resource Monitor window. Alternatively, you can find it via the Start menu by searching for "Resource Monitor" or navigating through the Performance tab in Task Manager. If you are already viewing the Task Manager, click the "Open Resource Monitor" link located at the bottom left of the Performance tab. This contextual link ensures you are looking at the same session's metrics without needing to manually search for the application.
Once the window opens, you will see five tabs across the top: Summary, CPU, Memory, Disk, and Network. Click the Network tab to reveal the specific sections relevant to your query. Here, the interface is divided into three main areas: Processes with Network Activity, Services with Network Activity, and TCP Connections. Each section provides different layers of detail regarding how your computer communicates over the local or wide area network.
Viewing Kernel and Driver Network Usage
A common point of confusion is that many background network activities are handled by system services and kernel-mode drivers rather than user-space applications like browsers or download managers. These components do not always appear prominently in the standard Task Manager list. In the Resource Monitor, under the "Processes with Network Activity" section, you may notice entries labeled as System or specific driver names. These represent kernel-level operations. To see these effectively, ensure that the columns displayed include "Send (B/sec)" and "Receive (B/sec)". Right-click the header row of any table within the Network tab and select "Select Columns". Check the boxes for network throughput metrics if they are not visible by default. This allows you to sort the processes by actual bandwidth consumption rather than just listing them alphabetically. Look for entries such assvchost.exe, which hosts various Windows services, or specific NIC (Network Interface Card) driver entries. While individual kernel threads might not be listed separately, their aggregate impact is shown in the total network utilization graph at the top of the tab.
It is important to understand that some network activity is attributed to the operating system itself for updates, telemetry, or DNS resolution. These are managed by the kernel and appear here. If you suspect a specific driver is causing high latency or excessive traffic, note its name from this list and cross-reference it with installed hardware drivers. For more context on how to interpret other resource spikes, you might find our guide on the Windows Task Manager Memory page explanation helpful, as memory pressure can sometimes correlate with network buffer issues.
Analyzing TCP Connections and Ports
Beyond seeing which process is sending data, you often need to know where that data is going. The "TCP Connections" section in Resource Monitor lists every active network connection established by running processes. This view includes the Local Address, Local Port, Foreign Address (the remote server IP), Foreign Port, State, and Process Name. This is particularly useful for identifying unauthorized connections or understanding why a seemingly idle application is still communicating. If you see a process using significant bandwidth but cannot identify its destination, look at the corresponding entry in the TCP Connections table. The Foreign Address column reveals the IP address of the remote host. You can use online tools or command-line utilities to resolve this IP to a domain name if needed. Additionally, the "Services with Network Activity" section shows background services bound to specific ports. This helps distinguish between a user application connecting to a port and a service listening on one. For users who need to export this data for further analysis or reporting, the Resource Monitor does not have a direct "Export" button for live graphs. However, you can take screenshots of the relevant tables. If you require structured data, consider using PowerShell cmdlets likeGet-NetTCPConnection in an elevated command prompt. For those interested in exporting other Task Manager data formats, our article on Export Command Line Column Task Manager Data to CSV outlines similar data extraction techniques.
Troubleshooting High Network Usage
If you identify a suspicious process or service consuming excessive bandwidth, the next step is isolation. Right-click the process in the Resource Monitor and select "End Process" if it is safe to do so. Be cautious when ending system services, as this may disrupt functionality. For persistent issues, check the startup items to prevent unnecessary network calls at boot. Duplicate or conflicting startup entries can cause redundant network polling. Our guide on Troubleshooting Duplicate Startup Items in Task Manager (Windows 10) provides steps to clean up these entries. Regularly monitoring these metrics helps maintain optimal performance. Sudden spikes in kernel network usage can indicate malware, misconfigured drivers, or failing hardware. By combining the visual data from Resource Monitor with targeted troubleshooting steps, you can pinpoint the source of network congestion without guessing.Frequently Asked Questions
Why doesn't Task Manager show all network-using processes?
The standard Task Manager aggregates some low-level system activity and focuses on user-visible applications. It omits many kernel-mode drivers and hidden system services to keep the interface simple. Resource Monitor exposes these hidden elements by providing a deeper layer of system inspection.
How do I stop a kernel driver from using network bandwidth?
You generally cannot "stop" a kernel driver directly from Resource Monitor. Instead, identify the associated service or device in Device Manager. Disable the specific network adapter feature or update the driver software provided by the manufacturer to resolve known bugs causing excessive traffic.
Can Resource Monitor show historical network usage trends?
No, Resource Monitor only displays real-time current activity. It does not log data over time. To view historical trends, you must use third-party monitoring tools or enable Windows Performance Recorder to capture long-term logs of network stack behavior.
What does the 'System' process represent in network usage?
The 'System' process typically represents kernel-mode components and non-paged pool memory usage related to network I/O. It includes activities like DNS caching, DHCP lease renewals, and TCP/IP stack processing that are not tied to a single user application executable.
Is it safe to end svchost.exe connections in Resource Monitor?
Ending svchost.exe can crash multiple dependent Windows services simultaneously. It is safer to identify the specific service hosted within that process via the Services tab and restart that individual service. Use caution to avoid disrupting critical system functions like Windows Update or networking.