I press Ctrl+Shift+Esc out of habit. Open the built in Windows task panel, sort by memory, kill whatever is eating the RAM, close the window, move on. For most people that is the whole job. I had been doing it the same way for fifteen years and never thought much about it. Then a friend who games heavier than I do pointed me at a small free program called System Informer. I had been hearing about it for years and never tried it. After one week, I have already replaced my keyboard shortcut.
What surprised me most is that the value is not in any single feature. It is in the fact that the program answers five questions I had been asking the built in panel for years and getting nowhere.
Question one: what is this process really running under?
The built in Windows panel hands you a flat list of running processes, sorted by what they are eating. That is fine for killing things. It is useless for understanding them. System Informer hands you a tree instead, so you can see exactly which service spawned which worker, which background helper pulled in which other helper, and which process is the one your game is actually fighting for resources against.
When I expanded the tree on my own machine for the first time, I saw that my antivirus had launched four helper processes underneath itself, two of which were scheduled to wake up on timers. The built in panel showed me one process called Antivirus.exe using sixty megabytes. The free program showed me the actual cost.
A tree view is not a new idea. The old Sysinternals utility Process Explorer had it for years. The original author of Process Explorer now contributes to System Informer, which is why the two tools feel so similar. The difference is that System Informer is actively developed and Process Explorer is largely in maintenance mode.
Question two: which version of this DLL is the game actually using?
When a game crashes on launch and the error message names a DLL, the next step is usually guessing. System Informer removes the guessing. Double click any process and a separate window opens with a Modules tab that lists every DLL that process has loaded. Each row has the full path, the version number, and the company name. If a game has loaded a modded DLL or is shipping a stale one, you see it instantly. If a program is pulling a DLL from a different folder than the one it should be using, you can see that too.
I used the Modules tab on a process I had been troubleshooting for an hour. The built in Windows panel would have shown me the process name and a memory number. System Informer showed me every DLL with full paths and version numbers. The DLL I was looking for was second from the bottom, with a version string that did not match what the developer site said. That one screen saved me at least an hour of guessing.
Question three: who is hitting my disk right now?
The built in panel shows disk activity as a percentage. That tells you the disk is busy. It does not tell you who. System Informer adds a column that shows disk write bytes per process, broken out by time, with an I/O history graph. You see which process is doing the writing, when the spike started, and how long it lasted.
I had a Windows service that was pegging the disk every fifteen minutes for a few seconds. The built in panel would have shown me a spike and then nothing. System Informer showed me the spike, the process responsible, and the exact time it happened. From there it took about two minutes to find the misconfigured log setting.
Question four: who is using my GPU?
The built in Windows panel has a GPU column, but it does not break down which engine is doing what. System Informer has a GPU tab in the process detail window that breaks down engine usage by frame, plus a column for GPU dedicated bytes for any process that touches the GPU. If a game is misbehaving and you want to know whether the GPU is the bottleneck or whether something on the CPU side is causing the stutter, the breakdown is right there.
I have not had a game stutter mystery this week, but knowing the breakdown exists is what matters. The next time something stutters, I will not need to find a new tool.
Question five: is this process really what it claims to be?
There is a category of malware that runs under a name like svchost.exe but was not actually started by Windows. The built in panel shows you the process name and trusts you to take it at face value. System Informer lets you add a column that shows the command line used to start each process, which shows you exactly which executable launched each process. If a Windows process was started from the wrong path, you have caught something the built in panel would never have surfaced.
The command line column is the simplest way to spot imposters. You do not need special skill to read it. You just look for Windows processes whose command lines point at folders you do not recognize.
What the install actually looks like
System Informer is free and open source. The install is straightforward, and the project ships binaries for download from the official site. The one thing that surprises people is that Windows Defender sometimes flags the installer during a first install. The flag is a false positive. The program inspects running processes because that is what it does, and inspection looks like the same behavior malware uses to find targets. The project site explains it and the source is open, so anyone can verify.
A few practical things about the install.
- Free and open source, install from the project site or a trusted package manager
- Windows only, no macOS or Linux build at the moment
- The installer may get flagged by your antivirus on first install, that is a false positive
- Pick the option to set a global hotkey during install so you can summon it like the built in panel
- The first launch will look dense compared to what you are used to, that is the design
Trade-offs
The program is not free in time. There is a real learning curve coming from the built in panel. The first launch feels busy. The default columns are denser than what most people want. The right click menu has dozens of options, some of which can terminate threads or unload DLLs if you pick the wrong one. None of this is a dealbreaker, but you should know what you are signing up for.
If you only ever open the built in panel to kill a frozen browser tab, none of the five questions above are questions you have ever asked. That is fine. Stick with what you know. If you have asked any of them, this is the free way to get answers without paying for a heavier tool.
For most people, the answer is going to be: install it once, set the hotkey, use it the next time something weird happens on your PC, and otherwise leave it alone. You do not have to make it your daily task panel. You just have to have it ready when you need it.
Bottom line
After a week I am keeping it. The hotkey is bound. The browser-tab kill shortcut I used to use still works because I never deleted it. If you have ever lost an hour to a mystery DLL or a pegged disk you could not identify, give this free program a try. If you have not, the built in panel is probably fine for you.