PC Turns On Then Shuts Down Right After Boot? Every Cause and Fix (Windows 11 & 10)

If your PC turns on and then shuts down by itself, first notice when it happens, because that tells you the cause. Off within seconds, before the Windows logo: almost always hardware, such as overheating, the power supply, memory or a loose cable. Off at or after the Windows logo: often Fast Startup, a damaged hibernation file, a crash that restarts silently, or a bad driver or update. Then do three safe things first: unplug everything except power, keyboard and monitor; open Advanced startup's Command Prompt and run powercfg /h off to disable Fast Startup; and disable Automatically restart so a hidden blue screen shows its error. Here is what most guides leave out: a PC that "shuts down" right after the logo is often crashing, not shutting down. Windows restarts or powers off so fast you never see the error. Making the error visible is the single most useful step.

Ethan's gaming desktop started doing it after a heatwave: power on, fans spin, Windows logo, then silence. Sometimes it booted on the third try and ran fine for hours. He reinstalled the graphics driver and ran every repair tool he could find. At Jake's shop the story took five minutes to read: Event Viewer showed Kernel-Power 41 errors, the CPU reached 100 °C within a minute of power-on, and the cooler's fan cable had worked loose from the motherboard. The CPU was protecting itself by switching the PC off. A reconnected fan, fresh thermal paste and a dust clean-out later, it has not shut down since. This page walks through every cause in the order that finds it fastest.

Work through the sections in order and note what you see at each step. A phone video of the startup, showing exactly when the screen goes dark, is surprisingly useful if you later need a repair shop, because the timing is the main clue.

Safety first: when to stop and unplug

Stop trying to start the PC and unplug it if you notice any of these: a burning or hot plastic smell, smoke, crackling or clicking from the power supply, a laptop battery that bulges and lifts the keyboard or case, or a charger that is too hot to hold. Repeated power-on attempts with a failing power supply or a swollen battery can damage other parts or become a fire risk. Those cases need a repair shop or the manufacturer, not software fixes. Everything else on this page is safe to try at home.

Also take care with the inside of a desktop: unplug the power cable and press the power button once to drain stored charge before touching anything, and never open the power supply itself, which holds dangerous voltage even when unplugged. Laptop batteries should only be removed where the design allows it without tools.

When it shuts down tells you why

Is it really off, or just a black screen?

Before chasing shutdowns, confirm the PC is actually turning off. A dead monitor connection, a graphics driver failure or a display that goes to sleep can look identical. Watch the PC itself: are the power light, fans and keyboard lights still on? Does Caps Lock toggle its light? On a desktop, is the monitor plugged into the graphics card rather than the motherboard's video port? If the PC stays powered with a black screen, the problem is display or graphics, not power, and the fixes are different: try another cable or monitor, press Windows + Ctrl + Shift + B to restart the graphics driver, and boot into Safe Mode to roll back the display driver. Only when lights and fans also stop is the PC truly shutting down.

Shuts down before the Windows logo: hardware checks

If the PC turns off before Windows starts loading, Windows is not involved yet, so software fixes cannot help. Check these in order:

1. Strip it down. Unplug everything except power, monitor and keyboard: USB drives, printers, docks, external disks, phone cables, extra monitors. A shorted USB device or cable can trip the power protection. If it now boots, plug things back one at a time.
2. Check the wall and the cable. Try a different wall socket and remove any power strip or extension. On a desktop, check the power supply switch on the back is fully on and the cable is pushed fully in.
3. Feel for heat and listen to fans. If the CPU fan does not spin, or spins and stops, heat protection is likely. See the overheating section.
4. Reset BIOS or UEFI settings. Enter firmware setup (usually Delete, F2, F10 or F12 at power-on) and choose Load optimized defaults or Load setup defaults, then save. This undoes overclocks and memory profiles that can make a PC power-cycle.
5. Reseat the memory (desktops). With the PC unplugged and after touching bare metal to discharge static, remove the RAM sticks and push them back firmly until the clips click. Try one stick at a time to find a faulty one.
6. Check internal power cables (desktops). The 24-pin motherboard cable and the 4 or 8-pin CPU power cable at the top-left of the motherboard must be fully seated. A missing CPU cable gives exactly the "fans spin for a second then off" symptom.

Laptop owners should stop at step 4 unless comfortable opening the case. Warranty repair is the better route for most laptops.

Overheating: the most common cause after a few minutes

Processors and graphics cards protect themselves. If the temperature reaches a critical limit, typically around 100 °C for many CPUs, the hardware switches the PC off instantly, with no warning and no Windows shutdown. That is what Ethan's PC was doing.

• Check fans spin, including the CPU cooler, case fans and the power supply fan.
• Clean dust from vents, fan blades and heatsink fins with short bursts of compressed air, holding fans still so they do not over-spin. Laptop vents on the side or back clog quickly.
• Check the CPU cooler is attached and its fan is plugged into the CPU_FAN header. A loose cooler or unplugged fan sends temperatures up within a minute.
• Replace dried thermal paste on PCs several years old, or have a shop do it.
• Use the PC on a hard surface; laptops on beds and sofas block their intake vents.
• Watch temperatures once it runs: the firmware setup screen shows CPU temperature, and in Windows, Task Manager's Performance tab shows GPU temperature on most PCs.

A PC that shuts down sooner in hot weather, under games or video exports, or after the fans have become noticeably loud, is almost always running hot.

Power supply problems

A failing or underpowered power supply (PSU) causes sudden shutdowns, especially at power-on, when parts draw a surge, and under load. Signs include a PC that starts only after several tries, shuts down when a game starts, or works on cold mornings but not after warming up, or the reverse. On desktops, check the PSU's wattage label against your graphics card's recommendation; a new card on an old, small PSU is a classic cause. If you have a spare known-good PSU, swapping it in is the definitive test; otherwise a repair shop can test it in minutes. On laptops, try a different genuine charger with the correct wattage; a damaged charger can cut out as soon as the laptop starts drawing more power.

Desktop short circuits: standoffs, screws and cases

A PC that switches off within a second of pressing the power button, every time, may have a short circuit inside. In self-built or recently opened desktops, check for a loose screw lying on the motherboard or behind it, a motherboard mounted without its brass standoffs or with an extra standoff touching the back of the board, and front-panel USB or audio cables with damaged insulation. The quickest test is a "breadboard" start outside the case with only the essentials connected, best done by someone comfortable building PCs. If the PC starts reliably outside the case, the short is in the case wiring or mounting.

Surge protectors, UPS units and house wiring

Power quality matters more than most people think. Brief dips in mains voltage, common during storms, when heavy appliances start, or in areas with unstable supply, can make a PC switch off while lights only flicker. A good surge protector guards against spikes; a UPS (uninterruptible power supply) bridges dips and short outages and lets the PC shut down cleanly. If shutdowns happen when the air conditioner, fridge compressor or washing machine starts, or at the same time as other devices blinking, power quality is the likely cause, and a UPS is the fix. Old power strips also wear out; replace any strip that is hot, scorched or loose.

Shuts down at or after the Windows logo: Windows checks

If the logo appears, the hardware is working well enough to start Windows, and software causes become likely. Because the PC will not stay on, you need the Windows Recovery Environment (WinRE). Force it by interrupting startup: turn the PC on, and when the Windows logo appears, hold the power button for ten seconds to turn it off. Do this three times; on the next start, Windows shows Preparing Automatic Repair and then the blue Choose an option screen. From there:

1. Troubleshoot > Advanced options > Startup Repair: lets Windows fix common startup problems automatically.
2. Troubleshoot > Advanced options > Command Prompt: run powercfg /h off to disable hibernation and Fast Startup, then close and choose Continue.
3. Troubleshoot > Advanced options > Startup Settings > Restart, then press 9 for Disable automatic restart after failure, so a crash shows its error instead of restarting or powering off.
4. Startup Settings again, then 4 or 5 for Safe Mode, where you can roll back drivers and updates.
5. Uninstall Updates: remove the latest quality or feature update if the problem started right after one.
6. System Restore: return to a restore point from before the problem began.

Our guides to Advanced startup options and Safe Mode show each screen in detail.

Fast Startup and the hibernation file

Fast Startup saves part of Windows to the hibernation file at shutdown and reloads it at the next start. If that file is damaged, or a driver does not resume properly from it, Windows can power off right after the logo, every time from a "shutdown", while a Restart works normally. That pattern, fails after Shut down but works after Restart, is the giveaway, and it is what the original 2016 version of this page described.

To fix it, disable hibernation, which deletes the file and turns off Fast Startup: run powercfg /h off in an administrator Terminal, or in WinRE's Command Prompt if Windows will not stay on. After a few normal startups you can turn it back on with powercfg /h on, which creates a fresh file, and see whether the problem returns. Our guide to Fast Startup covers the switch in Control Panel as well.

Shuts down when waking from sleep or hibernate

A related pattern is a PC that powers off instead of waking, or shuts down shortly after waking. Causes include a damaged hibernation file, a driver that fails to resume, and firmware power bugs. Turn off hibernation with powercfg /h off as above, update the chipset and graphics drivers from the PC maker, and check for a BIOS update. On laptops with Modern Standby, run powercfg /sleepstudy to produce a report of standby sessions; a session ending in a crash or power loss names the component that failed. Until it is fixed, using Shut down instead of Sleep avoids the problem.

Make the hidden crash visible

By default, when Windows hits a fatal error (a blue screen), it records the error and immediately restarts. If the crash happens early in startup, or the restart fails, it looks exactly like the PC switching itself off. To see the error:

• From WinRE: Startup Settings > press 9 (Disable automatic restart after failure).
• From Windows (if it stays on long enough, or in Safe Mode): press Windows + R, type sysdm.cpl, open Advanced > Startup and Recovery > Settings, and clear Automatically restart.

Now a crash stays on screen with a stop code such as DRIVER_IRQL_NOT_LESS_OR_EQUAL, WHEA_UNCORRECTABLE_ERROR or CRITICAL_PROCESS_DIED, sometimes with the name of a driver file. Photograph it. A driver file name points at the device to roll back; WHEA errors point at hardware such as CPU, RAM or overheating. Current Windows 11 versions show a simplified crash screen, but the stop code is still listed.

Read the cause in Event Viewer

Once the PC stays on, even in Safe Mode, Event Viewer records every unexpected shutdown. Press Windows + X, open Event Viewer, go to Windows Logs > System, and use Filter Current Log with these event IDs:

Open the newest Kernel-Power 41 and look at BugcheckCode in the Details tab. A value of 0 means the power simply disappeared, pointing at heat, the power supply or a power button. A non-zero value means Windows crashed, and the matching BugCheck event gives the stop code. Event 1074 with a program name means something asked Windows to shut down on purpose, which is a software problem, not a fault.

Reliability Monitor: a timeline of every crash

Event Viewer is detailed but busy. Reliability Monitor shows the same information as a simple timeline. Press Windows + R, type perfmon /rel, and press Enter. Each day shows a stability score, with red crosses for critical events such as Windows was not properly shut down and Hardware error. Click a day to see details, and look at what changed just before the first red cross: an update, a driver install, a new app. That date is often all you need to know which change to undo. Reliability Monitor keeps about a year of history, so it also tells you whether the problem is new or has been building for months.

Something is telling Windows to shut down

If Event 1074 shows a deliberate shutdown, find what started it. Common culprits:

• A scheduled task created by you, a family member or a "shutdown timer" app. Open Task Scheduler and look for tasks running shutdown.exe at logon or on a schedule. Run shutdown /a in Terminal right after sign-in to abort a pending shutdown while you look.
• Parental controls or screen-time limits that end the session.
• A battery or UPS app that shuts down when it misreads the battery level.
• Malware that forces restarts. Run a Microsoft Defender full scan and an offline scan.
• Windows Update finishing an install; the event names TrustedInstaller or the update orchestrator. That is normal once, not every time.

To list scheduled shutdown tasks quickly, run schtasks /query /fo LIST /v | findstr /i shutdown in Terminal. Any task that names shutdown.exe and you did not create deserves a closer look before you delete it.

Drivers and updates that cause instant shutdowns

If the problem began after installing a driver or update, undo it. In Safe Mode, open Device Manager, right-click the device (graphics cards are the most common), choose Properties > Driver > Roll Back Driver, or uninstall it with Attempt to remove the driver for this device checked. For Windows updates, use WinRE's Uninstall Updates or Settings > Windows Update > Update history > Uninstall updates. Our guides to uninstalling a driver and uninstalling an update cover both. Then install the driver from the PC or component maker's website rather than a generic one.

Graphics drivers deserve special attention: if a new version causes shutdowns in games, the graphics maker's clean-install option, or a display driver removal done in Safe Mode, followed by a slightly older known-good version, is the usual fix. Report the problem to the maker so a later version addresses it.

Startup programs: clean boot

If Windows shuts down a minute or two after sign-in, a startup program or service may be the trigger, especially utilities that control fans, RGB lighting, overclocking or power. Boot cleanly: run msconfig, check Hide all Microsoft services on the Services tab, click Disable all, disable all items in Task Manager's Startup apps, and restart. If the PC now stays on, re-enable items in halves to find the culprit. Our guide to clean booting Windows walks through it step by step.

Typical offenders are motherboard utilities that control fan curves or lighting, older overclocking tools, third-party antivirus with its own firewall, and "PC booster" apps that change power settings. Once found, update the program from its maker or remove it. Remember to return msconfig to Normal startup when you finish, so Windows services start normally again.

Repair Windows system files

Damaged system files can cause crashes during startup. From Safe Mode, or from WinRE's Command Prompt, repair them. In Windows (Safe Mode) open Terminal (Admin) and run DISM /Online /Cleanup-Image /RestoreHealth, then sfc /scannow. From WinRE's Command Prompt, where Windows is offline, use sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows, checking the drive letter first with dir C:\Windows, since WinRE sometimes assigns different letters. Also run chkdsk C: /f to fix file system errors on the drive.

If sfc reports that it found corrupt files and could not fix some of them, run the DISM command again while connected to the internet, then sfc once more. Results are logged in C:\Windows\Logs\CBS\CBS.log. Repeated failures point to a deeper problem that a repair install or reset solves faster than further scans.

Test the memory

Faulty RAM causes random crashes and power cycling at startup. Windows includes a memory test: press Windows + R, type mdsched.exe, and choose Restart now and check for problems. If Windows will not stay on long enough, run it from WinRE's Command Prompt with the same command. The test runs before Windows loads and reports results after the next sign-in, in the notification area or Event Viewer under source MemoryDiagnostics-Results. Any error means a stick should be replaced. On desktops with several sticks, testing one at a time pinpoints the faulty one.

For a more thorough test, the Windows Memory Diagnostic's extended mode, chosen by pressing F1 during the test, runs longer and catches intermittent faults. A single error is enough to justify replacing the stick; memory errors do not fix themselves and tend to get worse.

Check the drive

A failing SSD or hard drive can freeze or crash Windows during startup, sometimes powering off. Clicking or grinding from a hard drive is a red flag; back up your files immediately if the PC stays on long enough. Check drive health in Settings > System > Storage > Advanced storage settings > Disks & volumes, then the drive's Properties, which shows Drive health with estimated remaining life and temperature on NVMe drives. The drive maker's own tool gives more detail. A drive with warnings should be replaced before it fails completely.

On older hard drives, a quick check of SMART status in the maker's tool shows reallocated sectors, the early warning that a drive is failing. If you see them rising, copy your important files somewhere safe today rather than waiting for the drive to stop completely.

BIOS and firmware updates

Motherboard and laptop makers fix power, memory and compatibility bugs through BIOS (UEFI) updates. If your PC shuts down after a Windows update or with new hardware, check the maker's support page for your exact model and compare the latest version with yours; our guide to finding your BIOS version shows how. Update only from the maker's site, only with a laptop plugged into its charger, and never interrupt a BIOS update. If the PC cannot stay on long enough to run the updater from Windows, many motherboards can update from a USB stick in the firmware setup screen.

If shutdowns started right after a BIOS update, the update may have reset settings such as fan curves, memory profiles or the boot mode. Re-check them against what you used before, or load defaults and set only what you need.

CMOS battery and BIOS settings resets

A coin-shaped CMOS battery on the motherboard keeps the BIOS settings and clock. When it dies, typically after five to ten years, the PC may lose its settings every time it is unplugged, sometimes causing power-cycling at start, a wrong date, or a warning such as "CMOS checksum error". Replacing the battery (usually a CR2032) is cheap and quick on desktops. Clearing the CMOS, using the motherboard's jumper or button, or removing the battery for a few minutes with the PC unplugged, resets all BIOS settings, which can also fix a PC stuck in a power-on loop after a bad settings change.

Signs that point to the CMOS battery: the clock is wrong every time the PC has been unplugged overnight, the firmware asks you to press F1 to continue at startup, or BIOS settings such as boot order keep returning to defaults. If you see any of these alongside shutdowns at power-on, replace the battery first; it costs very little and takes minutes.

Laptop-specific causes

• Battery reporting zero: a worn battery may suddenly report empty and trigger a shutdown at startup. Run a battery report and compare full charge capacity with design capacity.
• Battery reset: many laptops have a pinhole reset on the underside, or a key combination in the manual, that resets the embedded controller; this fixes some power-on loops.
• Charger and port: try another genuine charger and, on USB-C laptops, a different USB-C port.
• Lid sensor: if the laptop powers off when opened, a faulty lid sensor or magnet may be signaling "closed". Test with an external monitor and the lid open.
• Swollen battery: stop using the laptop and get the battery replaced.

Laptops also log their own thermal and power events in the maker's support app, such as Lenovo Vantage, Dell SupportAssist, HP Support Assistant or MyASUS. Their hardware scans test the battery, fans, memory and drive in one run and often detect a failing fan before it causes shutdowns. Run the full scan once when shutdowns start; if a part fails, the report is exactly what warranty support asks for.

A stuck or faulty power button

A power button that sticks, or a desktop's front-panel cable that shorts, can send a "hold to power off" signal right after start. On desktops, unplug the front-panel power switch cable from the motherboard and start the PC by briefly touching the two power-switch pins with a screwdriver, following the motherboard manual; if it now stays on, the case button or its cable is at fault. On laptops, a sticky button often comes with a visibly uneven key or button edge. Also check Choose what the power buttons do in Control Panel, which may be set to Shut down, in case something presses it.

After installing new hardware

If the shutdowns began right after adding a graphics card, RAM, an SSD or an expansion card, remove the new part and test. If the PC is stable without it, the part is faulty, incompatible, not fully seated, or drawing more power than the supply can deliver. For graphics cards, check every power connector on the card is plugged in with the PSU's own cables, not adapters. For RAM, check the motherboard's supported memory list, and turn off XMP or EXPO profiles to test at default speed.

Also check the new part is in the right slot: graphics cards belong in the top full-length PCIe slot on most boards, and two RAM sticks usually go in specific slots shown in the motherboard manual. A card or stick that is not fully pressed in can let the PC start for a second before power protection cuts in.

Shuts down only when gaming or under heavy load

If the PC runs fine for browsing but switches off within minutes of starting a game, a render or a video export, the cause is almost always heat or power. Watch temperatures with the graphics maker's overlay while gaming; GPU temperatures in the high 80s °C and above, or CPU temperatures near their limit, need better cooling. If temperatures look fine but the PC still cuts out, the power supply is struggling with the graphics card's sudden power spikes, especially with older or lower-quality units. Capping the frame rate in the game or the graphics control panel reduces load as a quick test; if shutdowns stop, plan a stronger, quality power supply.

Overclocking, XMP and EXPO

Memory profiles (XMP for Intel, EXPO for AMD) and CPU or GPU overclocks run parts faster than their basic specifications. Some combinations are unstable, especially as parts age or in hot weather, and the result can be sudden power-offs at startup or under load. Load BIOS defaults, which turns them off, and test for a few days. If the PC is stable, re-enable the memory profile alone, and if needed lower the memory speed one step. Undervolting tools and overclocking utilities in Windows can also be the cause; uninstall them while testing.

Laptops and prebuilt desktops sometimes ship with performance modes in the maker's app that raise power limits. If shutdowns happen under load, try the balanced or quiet mode for a few days to see whether stability returns.

When to reset or reinstall Windows

If Event Viewer shows crashes with different stop codes, and hardware tests pass, a fresh Windows can rule out software entirely. From WinRE, choose Troubleshoot > Reset this PC, pick Keep my files, and Cloud download for a clean copy. Apps are removed but your files stay. Back up anything important first if you can reach it. If the PC still shuts down on a freshly reset Windows, the cause is hardware, and you can stop spending time on software fixes.

A reset takes an hour or two. Afterward, reinstall apps one at a time from their official sites, testing for a day between major ones such as games, security software and hardware utilities, so that if shutdowns return you know which install brought them back.

When to take it to a repair shop

Go to a shop or the manufacturer when the PC turns off before the logo after the stripped-down checks, when temperatures are high despite cleaning, when Kernel-Power 41 shows BugcheckCode 0 repeatedly, after any burning smell or swelling battery, or when the PC is under warranty. Bring your notes: when it shuts down, what the Event Viewer shows, what you have tried. Shops can test the power supply, memory and motherboard with known-good parts, which is the fastest way to a definite answer.

If the PC is under warranty, contact the maker before opening it, since some warranties exclude damage from home repairs. Many makers offer remote diagnostics that read the same logs described here and can authorize a part replacement quickly.

Keep it from happening again

• Clean dust from vents and fans every six to twelve months, more often with pets or in dusty rooms.
• Keep laptops on hard surfaces and away from direct sun.
• Use a surge protector, or a UPS where power is unreliable.
• Install drivers from the PC or component maker, and BIOS updates for known power issues.
• Do not run overclocks or memory profiles you have not tested for stability.
• Replace laptop batteries when health drops well below their original capacity.
• Create a System Restore point before big driver or software changes.

A quick monthly glance at Event Viewer for new Kernel-Power 41 or WHEA events catches problems early, often before they become daily shutdowns.

For IT admins: diagnosing unexpected shutdowns

Collect evidence. Kernel-Power 41, 6008 and BugCheck 1001 events across devices show patterns: one model with BugcheckCode 0 events points at hardware or firmware; many models after one update point at a driver or patch. Configure kernel or automatic memory dumps and keep them for analysis with WinDbg.

Firmware and drivers. Track BIOS and driver versions centrally; vendor tools and Intune driver and firmware update policies keep fleets consistent. Pause a problematic driver or update ring as soon as shutdowns cluster.

Thermals. Docking stations and closed laptop lids in hot rooms produce thermal shutdowns that look like software faults; check vendor thermal logs where available.

PC shuts down right after starting: frequently asked questions

Ethan's desktop has not switched itself off since the afternoon he and Jake read its event log. The lesson he took away was to stop guessing. A PC that turns itself off leaves clues: the moment it happens, the events it records, the temperature it reaches. Read those first, and the fix is usually one cable, one setting or one driver away. Software repairs fix software causes, and no amount of reinstalling cools a CPU whose fan has stopped.

Revision note. Written October 2, 2026, rewriting our 2016 Fast Startup fix into a full guide for PCs that turn off after starting. May your PC stay on until you say so.