Do you want to know why your PC freezes?

The world of computing is full of mysteries, and one of the greatest is why a computer freezes. The factors to evaluate are so broad and numerous that the diagnostic process can become a real nightmare. Fortunately, the general rules haven't changed, and with the help of specific tools, you can have a much better idea of why your PC freezes.

A little more load on the processor, and suddenly... the computer shut down. Imagine my face at that moment: the day's work was halfway done, and the last thing I needed was to be trapped in a long diagnostic and maintenance session. Once again, the cause was temperature. The system is configured to shut down automatically once the CPU exceeds the safety threshold, so the solution was cleaning the heatsink and replacing the thermal paste.

This is just a simple story with a happy ending, but I know there are thousands of users out there cursing a blue screen with strange errors that seem to come from a Lovecraftian tale. The question is classic, withstands the test of time, and has never lost its demonic profile...

Why does a computer freeze?

In very relaxed terms, 'hangs' are divided into two categories: 'soft' and 'hard'. The so-called 'soft hang' has a software problem as its main cause, ranging from a malware infection to a driver error that causes instability. 'Hard hangs' indicate hardware issues. Excessive temperature, swollen capacitors, hard drives with SMART errors, and failures in memory modules top the list. The trick is knowing how to recognize each one.

Regardless of the code shown, the famous Windows blue screen can do no more than offer a series of suggestions. If the instability occurs after updating a driver, it's logical to assume that driver is the culprit, but if errors appear unexpectedly and follow a pattern (time, or load on the CPU), you'll have to play detective a little.

Could it be the temperature?

Heat is one of the most relentless enemies any computer must face, and this constant struggle means keeping an eye on the temperature of the CPU, the graphics card, and the system as a whole. In the case of the processor, one of the most popular tools is SpeedFan, although it's not recommended for novice users.

Under certain configurations, SpeedFan can make mistakes and report incorrect values, forcing you to visit the computer's BIOS if you want to know the temperature in real time. If the problem is really related to excessive heat, a brush to remove dust, some compressed air, and changing the thermal paste should bring order to the chaos.

Could it be the RAM?

When suspicions point to memory, the two main resources are MemTest86 and its variant MemTest86+. If there's an issue in one of the modules, these programs will let you know. Which is best? Actually, it depends on the computer itself. MemTest86 receives updates more frequently, while MemTest86+ is well known for its work on computers a few years old.

My suggestion is to first try MemTest86+, and if something bad happens, switch to MemTest86. Is there an error in a module? The first step is to remove it and clean the socket. The second is to clean the memory contacts with a simple white eraser (neither red, blue, nor gray). If that doesn't help, maybe it's time to consider a replacement.

It could also be the hard drives!

Finally, we must mention hard drives, though at this point there's not much to do. A drive that throws SMART alerts is a drive about to request permanent retirement, and that extends to all the data stored on it. In the past, we've seen several options with the ability to read SMART status, but my favorite remains HD Tune, which also allows several benchmarks. Remember: the question is not how a hard drive is going to break, but when.

Interpreting a BSOD

"UNMOUNTABLE_BOOT_VOLUME". Very well Windows, now in Spanish. Reading correctly the data presented in a BSOD (Blue Screen of Death), known to most as the blue screen, can be more useful than it seems. As expected, Microsoft doesn't seem interested in making the process easier, or else the errors would be much clearer.

A good program to use as a translator is WhoCrashed, developed by the folks at Resplendence. Each entry is identified by the error name, the module involved, and the date of the event. If the reports mention system files, it's never a bad idea to run 'sfc /SCANNOW' in the command console with elevated privileges, assuming there are no hardware problems.

Otherwise, if the file causing the blue screen belongs to a driver, updating it or reverting to a previous version should suffice. Another recommended software is LastActivityView, from Nirsoft. The program shows exactly what you were doing before the hang, which is very useful when the goal is to reproduce the problem.

Well... let's say you have homework ahead. If the computer hangs, the first thing is to not panic (you even have a lifesaving shortcut!). In most cases, the user can indeed solve the problem with a reasonable investment of time. One way or another, knowing for sure the cause of the failure gives you a considerable advantage when sending the system for repair, or getting a compatible part. Good luck!