Laptop keeps rebooting: a complete guide to fixing the problem

The situation when laptop turns on, shows the manufacturer's logo, and then immediately turns off and repeats this cycle endlessly, is one of the most frightening for the user. This kind of failure is often called an “infinite reboot loop” or “boot loop”, and it can be caused by both software conflicts and critical hardware failures. In most cases, the problem lies in damage to operating system system files, driver failures, or overheating of components.

Do not immediately panic and take the device to a service center if you notice such symptoms. Often the reason lies in a banal failure Windows boot loader or processor overheating due to dust. Correct diagnostics allows you to identify the root of the problem and fix it without wasting time and money, using built-in recovery tools or simple manipulations with the hardware.

Primary diagnostics and hardware testing

Before diving into complex operating system settings, it is necessary to rule out physical malfunctions. The most common reason for sudden reboots is CPU overheating or video chip. If the protection system detects a critical temperature, it forcibly de-energizes the device to prevent irreversible damage.

Check ventilation holes and cooler operation. If you hear a loud noise when you turn it on, or, conversely, silence while there is heat inside the case, the problem is obvious. It is also worth paying attention to the RAM: a loosely installed bar RAM may cause constant failures during system initialization.

Sometimes the culprit is the power supply or battery. Unstable voltage can cause the laptop to try to boot, but there is not enough power to complete the initialization process. Try removing the battery (if the design allows) and start the device exclusively from the mains.

• ✅ Check that the ventilation grilles are not blocked by foreign objects
• ✅ Inspect the case for swelling of the battery or signs of overheating
• ✅ Try a cold start: turn off the power and remove the battery for 5 minutes

⚠️ Attention: If you hear a specific burning smell or see smoke, immediately stop trying to turn on and contact a specialist, as this may indicate a short circuit.

Troubleshooting Windows Recovery Environment

If the hardware is OK, the file system or boot sector is most likely damaged. In modern versions of Windows such as Windows 10 or Windows 11, there is a built-in recovery environment that starts automatically after several failed boot attempts. This is where the key to solving the problem lies.

To access the recovery menu, you often need to forcefully abort the boot process three times in a row. This is done by holding the power button for 5-10 seconds immediately after the logo appears. After the third time, the system will display the message “Preparing automatic recovery” and offer options for action.

From this menu, select Advanced Options, then Troubleshooting. Here you will be able to run Startup Repair, which will try to automatically fix startup file errors without losing your data.

• 🛠 Run Startup Repair to fix errors automatically
• 🛠 Use System Restore to roll back to a restore point
• 🛠 Try running “Command Prompt” to manually fix files

Using the command line to repair the bootloader

If automatic recovery does not help, you will have to resort to manual intervention via the command line. This method allows you to repair the BCD bootloader and fix errors on the disk. To do this, select “Command Prompt” from the recovery menu.

The first step is to check the file system for errors. Enter the command chkdsk c: /f /r and press Enter. This utility will scan the disk, find bad sectors and try to repair them. The process can take from 30 minutes to several hours depending on the amount of data.

After checking the disk, you need to restore the boot records. Enter the following commands in sequence, pressing Enter after each: bootrec /fixmbr, bootrec /fixboot, bootrec /scanos And bootrec /rebuildbcd. If the system finds Windows installed, confirm adding it to the download list.

chkdsk c: /f /r
bootrec /fixmbr
bootrec /fixboot
bootrec /scanos
bootrec /rebuildbcd

Sometimes an access error occurs when entering the fixboot command. In this case, you must first assign a letter to the system partition. Use the utility diskpart, then list volto find the EFI partition, and the command assign letter=S before trying the fixboot command again.

⚠️ Attention: Do not force close the command prompt window until the disk check process is completely completed, otherwise you may permanently damage the file system.