PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchiTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
A server that is slow, unreachable, not responding, or returning errors can be failing in several different places, and the same visible outage often has more than one possible origin. The reliable path to a fix is to narrow the symptom to one fault area, collect evidence while the problem is happening, and change one thing at a time. The steps below draw on Microsoft Learn guidance for Windows Server and AWS documentation for Linux instances on Amazon EC2, and they note where that guidance does not carry over to other platforms.
Scope the failure before you change anything
Write down answers to these four questions before you touch configuration or restart a service. Record timestamps with a time zone, so that logs and metrics from different machines can be lined up later.
- What is broken? The host itself, one service, one application, name resolution, or a particular client path.
- Who is affected? All users, one site or subnet, a single client, or only automated processes.
- When did it start, and what changed beforehand? Consider updates, configuration edits, new deployments, and shifts in traffic.
- Is it total, intermittent, or load-dependent? A failure that appears only at peak times points toward capacity; a failure that never clears points toward a stopped service or a broken dependency.
Then separate four questions that are often treated as one: is the application responding, is the host reachable, does the name resolve, and are resources within their normal range? A report that “the server is down” usually answers only one of them. The table below shows where to look first for each common symptom.
| What you observe | Check first |
|---|---|
| Everything is slow, but the host still answers | Processor, memory, storage, and network measurements together, compared with a baseline |
| Hostname does not resolve, but the IP address works | Client IP configuration, then the DNS server and its records |
| Host does not respond on the network at all | Platform status checks, console or system output, and boot or kernel messages |
| Host is reachable, one application fails | Service status, event or application logs, and application status checks |
| Errors appear only under load | Resource ceilings during the load window, storage I/O errors, and DNS query volume |
Five fault areas behind the same symptoms
The symptoms above can originate in any of five areas. Each one can make the others look broken, which is why the first job is to rule areas in or out rather than to fix the most visible symptom.
#1 Best Overall
- Save valuable floor space: 6U wall mount server cabinet Dimensions: 13.78" H x21.65" W x17.72" D.Maximum mounting depth is 14.2"
- Keep critical network equipment secure: glass door and side panels are lockable to prevent unauthorized access. Front door can be installed on either side of the front of the cabinet to satisfy your door swing orientation preference
- Easy equipment configuration: Fully adjustable mounting rails and numbered U positions, with square holes for easy equipment mounting with top and bottom punch-out panels for easy cable access
- Durability: Made of high quality cold rolled steel holds up to 110lb (50kg) (Easy Assembly Required)
- PCI & HIPPA and EIA/ECA-310-E compliant
Resource bottlenecks
Processor, memory, disk, and network capacity can each slow a server, and a shortage in one can look like a fault in another. A server with busy processors may be waiting on a slow disk, short of memory, or handling a flood of legitimate requests. Out-of-memory messages in a Linux system log point to memory exhaustion, and a busy processor reading alone does not tell you which of these is happening.
Storage and filesystem problems
Failing volumes and damaged filesystems show up as slow reads and writes, timeouts, and I/O errors. Block-device I/O errors and filesystem errors in system logs are the signals to look for on EC2 Linux. A full or damaged filesystem can also stop services that write to it, so a service failure may have a storage cause.
DNS and network faults
When name resolution fails or a network path is blocked, a healthy application becomes unreachable by name. Clients then report that the server is down while the host and the application are both running. Name resolution and connectivity should be tested separately, as the DNS section below explains.
Recommended Free Tools
Application and service failures
A stopped, hung, or misconfigured service can fail while the host itself still answers. On Windows, check service status and event log entries. On EC2 Linux, application status checks can show whether the application is reachable and available.
Operating-system and boot problems
Kernel errors, operating-system configuration problems, and boot failures can make the whole host unresponsive. These need classifying from platform health information and logs before any recovery step, as covered in the EC2 section below.
Rank #2
- Universal 19” Rack Mount Compatibility – Perfect for pro audio, video, IT, and network gear. Compatible with mixers, routers, patch panels, servers, power amps, and more.
- Heavy-Duty Load Capacity – Built to support up to 550 lbs. Ideal for studio gear, DJ setups, server equipment, and AV components that demand serious stability.
- Robust Steel Frame & Design – Made with 1.5mm thick steel and weighs 36 lbs for maximum durability, reduced vibration, and long-term reliability in any setting.
- Mobile & Secure – Preinstalled with 3” industrial-grade caster wheels (lockable), making it easy to move and position your rack exactly where you need it.
- All-In-One Setup Kit Included – Comes with 34 rack screws (5mm & 6mm), a 1U blank spacer, and an assembly tool—ready for fast installation out of the box.
Collect evidence before restarting anything
A restart or reboot clears the state you need to diagnose. Capture logs, service status, and metrics first. The table shows the main evidence sources on each platform.
| Evidence | Windows Server | Amazon EC2 Linux |
|---|---|---|
| Event and system logs | Event Viewer and Server Manager, which can display event log data for local and remote servers | System logs, plus console output for hosts that are not responding |
| Service and health status | Service alerts in Server Manager (Microsoft documents this for Windows Server 2016, 2019, 2022, and 2025) | System and instance status checks; application status checks |
| Metrics over time | Performance Monitor counters, recorded over a period | CloudWatch metrics |
| Network and disk tools | Performance Monitor network counters; network traces for DNS problems | iftop for network traffic; iostat for disk I/O |
| DNS diagnostics | DNS audit logs (enabled by default), analytic logs, and traces | Not applicable |
Diagnosing slow or overloaded servers
Inspect processor, memory, storage, and network measurements together, and compare them with a baseline taken during normal operation. A single high reading is a clue, not a diagnosis, so check whether the other three areas are also under strain and whether the load matches what the server is expected to handle.
Network interface utilization on Windows
Microsoft’s Performance Monitor counter guide, published in 2026, uses the network interface’s Bytes Total/sec counter and sorts utilization into bands. These bands come from that guide and are not universal server-health thresholds.
| Network interface utilization (Microsoft guide) | Label in that guide |
|---|---|
| Below 50% | Healthy |
| 50% to 80% | Warning |
| Above 80% | Critical |
Microsoft notes that interpretation depends on the network card’s speed and the server’s role, so compare the traffic you see with what that server is expected to send and receive. The same guide relates throughput units with 8 bits = 1 byte, so confirm which unit a counter reports before doing any conversion.
Disk and network tools on EC2 Linux
AWS guidance for unresponsive Linux instances points to system logs and to command-line tools for network traffic and disk I/O. Two of them are:
Rank #3
- ADJUSTABLE DEPTH: 4- Post 22U 19" server rack enclosure with 4 vertical rails and adjustable mounting depth 5.7" to 33.0" (14,4cm to 83,8cm); IT rack is compatible with various servers / switches / data / video / AV and other IT networking equipment
- EASY SHIPPING AND ASSEMBLY: Enclosed 22U data rack cabinet ships compact flat-packed to avoid damage and facilitate installation; Include wheels & levelling feet to offer more stability; Home server rack cabinet is only 46.6in (118,3cm) in height
- DESIGN AND VENTILATION: Half height server rack cabinet has lockable and removable door and side panels with vented top allowing airflow; 4 Post 19" rack with 1764lb (800kg) weight capacity (stationary); Computer cabinet rack is EIA/ECA-310-E Compliant
- HARDWARE INCLUDED: Rolling home network rack includes rack mounting and equipment mounting hardware, such as 20 M6 cage nuts / screws, PVC cup washers; Front/rear doors and side panels Keys, 2x allen keys; Rack assembly hardware; Casters and leveling feet
- THE IT PRO'S CHOICE: Designed and built for IT Professionals, this 22U IT Server Cabinet is backed for life, including free lifetime 24/5 multi-lingual technical assistance
iostat, which reports disk I/O statistics. On many distributions it comes from the sysstat package, which may need installing.iftop, which shows live network traffic by connection. It is usually a separate package and may need installing.
Run these during the slow period, not after it has ended, and read their output against the baseline you recorded.
Diagnosing DNS and connectivity problems
Microsoft’s DNS troubleshooting guidance separates client-side causes from server-side causes. It recommends starting on the client unless the scope of the problem already points to the server.
Check the client first
- Confirm the client’s IP configuration. On Windows, run
ipconfig /alland check the address, subnet mask, default gateway, and DNS server entries. - Confirm basic connectivity from the client to the configured DNS server address.
- Test name resolution separately from connectivity. Use
nslookupto query the configured DNS server, then query a second, known-good DNS server. If only the configured server fails, the fault is more likely on the server side; if both fail, look at the client path.
Check the server when the scope points to it
If the client checks point to the server, Microsoft’s guidance covers the server’s own IP configuration, the DNS server service, authoritative data, recursion, and zone transfer. Each affects different queries. Authoritative data answers for zones the server hosts, recursion resolves names outside those zones, and zone transfer copies zone data between servers. Check the component that matches the failing query.
Collect client and server data at the same time
Where feasible, collect data on the affected client and on the DNS server simultaneously. Start the traces on both, reproduce the failure, then save the traces. Matching timestamps show whether a query left the client, reached the server, and returned an answer.
Use DNS diagnostic logging temporarily
According to Microsoft, DNS audit logs are enabled by default. Analytic logs are not, and debug logging can be resource intensive and consume disk space. Microsoft’s DNS logging page gives one scoped example: at 100,000 DNS queries per second on modern hardware, enabling analytic logging can result in 5% performance degradation, while at 50,000 queries per second and lower it reports no apparent impact. These are examples from that page, not guarantees for your hardware. Monitor performance while verbose logging is on, and turn it off once the trace is complete.
Free tools Windows power users keep installed
One-click scans. No signup required.
Rank #4
- DURABLE BUILD: Constructed from high-quality Cold Rolled Steel, the NavePoint Consumer Series 12U network cabinet boasts a sturdy, welded frame. Fitting EIA standard 19” networking equipment, this server cabinet confidently supports up to 110 lbs, providing a resilient base for your vital IT gear and equipment
- CONVENIENT DESIGN: This 12U cabinet features a reinforced, heat-treated, tempered glass front door with a security lock. Perfect for applications requiring both security and accessibility, its compact design of 17.72"L x 21.65"W x 24.42"H offers a practical solution for space-constrained settings.
- EASY & CUSTOMIZABLE EQUIPMENT SET UP - The 12U IT cabinet, with removable side panels and security locks, offers customization at its finest. Whether it's for an efficient device or cable management, this data cabinet ensures secure, adaptable configurations that suit your networking server requirements
- ENHANCED VENTILATION & SECURITY - Built-in fans and flow-through ventilation work to prevent overheating, ensuring optimal operation of your equipment. The reinforced, lockable tempered glass front door not only boosts security but also facilitates easy monitoring of installed equipment.
- SAFETY & COMPLIANCE - All NavePoint products are built to industry standards.
Diagnosing EC2 instances that are unreachable or unresponsive
For boot problems, reachability failures, or a host that stops responding, classify the problem from the platform’s health information and logs before choosing a recovery step.
Status checks
AWS documents system and instance status checks, and separately describes application status checks, which can monitor network reachability and the availability of applications running on the instance. In AWS’s usual split, system status checks look at the underlying infrastructure, which AWS may need to repair, while instance status checks look at the instance’s own software and network configuration. Read the result of each check separately, because a failed instance check and a stopped application call for different responses.
Error categories in system logs
AWS’s EC2 Linux troubleshooting guidance groups example log problems into the categories below. These are examples, not a universal taxonomy of server faults, so confirm the category before you act on it.
| Category | Example in logs | What to check next |
|---|---|---|
| Memory | Out-of-memory messages | Identify the process using memory and review the workload that started the pressure |
| Device | Block-device I/O errors | Check the attached volume and its state before any other change |
| Kernel | Kernel errors | Read the full kernel messages and note any recent kernel or driver change before rebooting |
| Filesystem | Filesystem errors | Limit writes to the affected filesystem until its state is known |
| Operating-system configuration | Configuration problems | Compare recent configuration edits against the platform’s documentation |
Make one targeted change and verify it
- State the hypothesis: which fault area the evidence supports, and what you expect to see if it is correct.
- Record the current state, including configuration values, service status, and the measurements you are watching.
- Change one likely cause at a time, where your operations allow it.
- Check whether the symptom and the related measurement improve. Then check again once load returns to normal, because some faults appear only under load.
- If nothing changes, revert the change and move to the next fault area.
Vendor guidance does not provide one remediation sequence that fits every server problem. For production systems, follow your organization’s change, backup, and escalation procedures, and use guidance specific to the platform and the fault you have confirmed.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Quick Recap
Where these platform guides stop applying
- The Microsoft procedures cover Windows Server. Event Viewer, Server Manager, and Performance Monitor are Windows tools and are not available on Linux hosts.
- The AWS examples cover Linux instances on Amazon EC2. Physical servers, other cloud providers, and other Linux distributions may store logs in different places, use different tools, and offer different health information.
- The Microsoft counter bands and the DNS logging figures are specific to the pages that publish them. Apply them as reference points, not as thresholds for every server.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
