A hardlock is a complete system freeze where your computer becomes totally unresponsive. Your mouse won’t move, your keyboard does nothing, and the screen stays stuck on whatever it was displaying. Unlike a slowdown or a partial freeze, a hardlock means the processor is trapped in a loop so deep that it can’t even process the basic signals (called interrupts) that let it respond to your input. The only way out is usually a forced restart by holding the power button.
How a Hardlock Differs From Other Freezes
Not every freeze is a hardlock. The distinction matters because it points to different causes and different levels of severity.
A “soft lock” (or soft lockup) happens when the operating system’s core gets stuck running one task for more than about 20 seconds without letting other programs take a turn. Your system becomes painfully slow, the mouse might crawl across the screen, but things are still technically responding. The processor can still handle basic housekeeping signals, so the system isn’t completely dead.
A hardlock is a step beyond that. The processor has been stuck for more than 10 seconds without responding to any interrupts at all. That means nothing gets through: no mouse movement, no keyboard input, no signals from other hardware. The system is, for all practical purposes, a brick until you cut power. This is more severe than a soft lock because even the operating system’s internal safety mechanisms can’t break through to regain control.
A hardlock is also different from a blue screen (BSOD) or kernel panic. Those crashes are actually the system detecting a problem and shutting itself down in a controlled way. A hardlock is worse in the sense that the system doesn’t even get the chance to crash gracefully. It just stops.
What Causes a Hardlock
Hardlocks can come from both hardware and software problems, but they almost always involve something going wrong at a very low level, close to the hardware itself.
Driver and Software Issues
Faulty drivers are one of the most common culprits, especially graphics drivers. Windows has a built-in safety timer called Timeout Detection and Recovery (TDR) that monitors whether the graphics card is responding. By default, Windows waits about 2 seconds before deciding the GPU is unresponsive and killing the driver. When TDR works correctly, you’ll see a brief screen flicker and a message that the display driver recovered. When it doesn’t work, or when the freeze happens outside the GPU, the result can be a full hardlock.
Operating system bugs can also cause hardlocks, particularly in kernel-level code that runs with the highest system privileges. If a piece of kernel code enters an infinite loop or gets stuck waiting for a resource that never becomes available, it can lock the processor entirely.
Hardware Failures
Power delivery problems are a surprisingly frequent trigger. Users have reported hardlocks traced to unstable power supplies, where the system’s power draw drops dramatically during the freeze (from a normal 140-160 watts at idle to around 86 watts). This kind of sudden power instability can leave components like the GPU without adequate power, freezing the entire system.
Other hardware causes include failing RAM (even when memory test utilities come back clean), overheating processors that hit thermal limits, and motherboard issues. Faulty RAM is particularly tricky because standard memory tests don’t always catch intermittent errors that only show up under specific workloads.
How Systems Detect Hardlocks
Modern operating systems use watchdog timers to catch lockups. In Linux, the hardlock detector works by sending a special type of interrupt (called a non-maskable interrupt, or NMI) that the processor can’t ignore under normal circumstances. A timer checks in on each processor core at regular intervals. If a core hasn’t responded to any interrupt for 10 seconds, the watchdog flags it as a hardlock and either logs a warning or forces a system restart, depending on the configuration.
The soft lockup detector works similarly but with a longer threshold of 20 seconds and checks whether the system is still scheduling tasks rather than responding to interrupts. Both detectors exist primarily on servers and Linux systems where unattended reliability matters. On a typical Windows desktop, there’s no equivalent hardlock detector built in, which is why a hardlocked Windows PC simply stays frozen until you manually restart it.
Diagnosing a Hardlock After It Happens
The challenge with hardlocks is that because the system is completely unresponsive, it often can’t write any information to its logs before it goes down. After a forced restart, you may find very little evidence of what happened.
On Windows, check the Event Viewer under System and Application logs. Look for entries timestamped just before the freeze occurred. Error events from the Service Control Manager, application crash records, and memory-related errors (Event IDs 2019 and 2020) can sometimes point you in the right direction. If you see entries suggesting a process consumed excessive resources right before the logs go silent, that’s often your culprit.
On Linux, the kernel’s watchdog detectors will write diagnostic information to the system log if they manage to fire before the system becomes completely unresponsive. These messages include details about which CPU core locked up and what code it was running at the time.
If hardlocks are recurring, keeping track of what you were doing when each one happened is often more useful than log analysis. Patterns like “always happens during gaming,” “only when the system wakes from sleep,” or “started after installing new hardware” narrow the problem quickly. Repeatable hardlocks during heavy GPU use often point to graphics drivers or power delivery, while random hardlocks under light load tend to suggest RAM or motherboard issues.
The Other Meaning: Hardware Dongles
If you came across “Hardlock” as a product name rather than a system freeze, it refers to something completely different. Hardlock was a brand of physical USB dongle made by a company called Aladdin Knowledge Systems. These small devices plugged into a computer’s port and served as copy protection keys. Software that required a Hardlock dongle simply wouldn’t run unless the dongle was physically connected. This was an early form of digital rights management used mainly by expensive professional software. Aladdin Knowledge Systems also produced other security products like the HASP key, which served a similar purpose. These hardware dongles are still used in some industries today, though cloud-based licensing has largely replaced them.