What Really Happens Inside a CPU When Your Computer Freezes?

Recently a friend asked why computers crash and what the CPU does during a freeze. Most users have experienced a dead computer, especially on older, less powerful machines when running several heavy applications.

The CPU is the core of a computer, constantly fetching and executing instructions until the system is shut down. In theory, a crash could be caused by the CPU refusing to execute further instructions (hardware crash), but this is rare.

More commonly, crashes are software‑level: the CPU gets trapped in a loop or waiting state, preventing other programs from running.

void dead_loop() {
  while (1) {
    ...
  }
}

Running such a dead loop only makes the CPU work harder; the system usually continues to operate because the operating system can preempt the loop.

Interrupts

Interrupts are one of the greatest inventions in computer history. They allow the CPU to pause its current work and handle higher‑priority events, such as timer interrupts that let the OS regain control and schedule other threads.

Even if a thread enters an infinite loop, the OS will reclaim the CPU after its time slice expires, so a simple dead loop cannot freeze the whole machine.

On multi‑core CPUs, even if one core is stuck in a loop, other cores can still be scheduled, preventing a total system freeze.

There are two main scenarios where a freeze can occur:

1. Interrupts cannot preempt the CPU – Interrupts have priorities; a low‑priority interrupt cannot interrupt a high‑priority one. If the OS mishandles an interrupt (e.g., gets stuck in a spin lock), the CPU core becomes unresponsive.

2. The CPU is preempted but no runnable thread is available – Similar to a deadlock in the kernel: if a global lock is held and the interrupt handler cannot acquire needed resources, all other threads wait, leading to a complete system hang.

Understanding interrupts, their priorities, and proper kernel synchronization is essential to prevent such freezes.