Skip to main content

WELCOME TO YOUR WORLD

Let it come to life.

Explore the full desk collection in motion, with smooth animations and original website sound.

Change your choice anytime in Playback preferences. Your device’s Reduce Motion setting stays on.

YFORGE / SETUP GUIDES

Computer Keeps Restarting? Find the Cause and Fix It

A computer that keeps restarting usually points to heat, power, drivers or memory. Follow this step-by-step guide to find the cause, including during games.

YForge Gaming · November 13, 2026 · AI-assisted guide
Computer Keeps Restarting? Find the Cause and Fix It

A computer that keeps restarting is almost always reacting to one of four things: heat, power, drivers or memory. You can usually find which one in under an hour with Windows’ own logs and a short checklist. Start by making Windows show you the error instead of rebooting, then work through cooling, power, drivers and RAM in that order. This guide covers all of it, with a focus on gaming PCs that restart or crash under load.

Yforgegaming
Choose a Gaming PC Built for You
Explore complete desktop builds by budget or customize components for a tailored gaming PC assembled and tested by YForge.

TL;DR

  • Turn off “Automatically restart” in Windows so a crash leaves a stop code on screen, then write the code down.
  • Open Event Viewer and look for Event ID 41, 6008 or 1074. They tell you whether the restart was a crash, a power loss or a normal reboot.
  • If it restarts only while gaming, suspect GPU or CPU heat, an underpowered power supply (PSU) or a graphics driver first.
  • Reset overclocks and BIOS tweaks to defaults, update Windows and drivers, then reseat the RAM and graphics card.
  • A PC that was built and tested as one balanced system, with a PSU sized for the graphics card, avoids most of these problems from day one.

Table of Contents

First, work out what kind of restart it is

Not every restart is the same, and the type narrows the cause fast.

  • A normal restart. Windows or you started it, for example after an update. Microsoft’s event-log guide says this is commonly logged as Event ID 1074.
  • A crash with a blue screen. Windows hit a fatal error (a “bug check”) and rebooted. Microsoft notes that a stop code such as PAGE_FAULT_IN_NONPAGED_AREA or MEMORY_MANAGEMENT may appear, sometimes with a module name.
  • A sudden black screen and reboot. No warning, no blue screen. The same Microsoft guide associates unexpected restarts with Event IDs 41 and 6008. This pattern often points to power or heat.
  • A boot loop. The PC restarts before it reaches the desktop. System76’s documentation says early boot instability often points toward RAM, and a failing PSU or a corrupted startup are other common reasons.

If your screen goes dark and the machine reboots with no message, you are in the second or third group. That is the case Windows hides by default, so the next step matters.

Step 1: Make Windows show you the error

By default Windows reboots immediately after a crash, so the blue screen flashes by too fast to read. Turn that off:

  1. Press the Windows key, type “advanced system settings” and open View advanced system settings.
  2. Under Startup and Recovery, click Settings.
  3. Under System failure, uncheck Automatically restart and click OK.

The next crash will stay on screen with its stop code. Photograph it or write it down, including any file name. This does not fix anything. It gives you evidence, and Microsoft recommends recording the stop code as the first move in troubleshooting.

If the screen simply goes black and the PC powers off or reboots, there is no stop code to read. That itself is a clue: Windows never got the chance to write one, which points toward a sudden loss of power or a protective heat shutdown.

Step 2: Read the Event Viewer log

Event Viewer records every restart. Open it from the Start menu, then go to Windows Logs > System and choose Filter Current Log. Microsoft’s guide suggests filtering for Event IDs 12, 13, 19, 41, 1001, 1074, 6008, 6009 and 7045 to see the reboot history and whether an update or driver change came just before the problem.

The ones you will meet most:

Event ID What it means What to suspect
1074 A normal, requested restart or shutdown Updates, you or a program asked for it
41 (Kernel-Power) Windows restarted without a clean shutdown Power loss, a crash, heat
6008 The previous shutdown was unexpected Same as 41, confirms the crash
1001 A bug check was recorded Look up the stop code

Event 41 alone does not name the guilty part. Microsoft states it only says the system rebooted without a clean shutdown. If the bug-check code inside it is zero, that can indicate interrupted power or an underpowered or faulty desktop PSU, or that Windows could not finish writing the crash information.

Note the timestamps. If every restart happens ten minutes into a game, you are looking at load. If it happens while idle or watching video, drivers, memory or the PSU move up the list.

Step 3: Check heat

Overheating is the most common reason a healthy-looking PC restarts. When the CPU or GPU gets too hot, the hardware cuts power to protect itself, which looks exactly like a random restart. How-To Geek explains that this protective power loss is a typical reason PCs shut off during games.

What to do:

  • Watch temperatures under load. Use a free monitoring utility, start a game and note CPU and GPU temperatures just before a crash. If they climb steadily toward their limit and the PC dies, heat is your answer. Your CPU and GPU makers publish the maximum safe temperature for each model.
  • Clean the dust. Power the PC off and unplug it. Use compressed air on the intake filters, heatsink fins and fans, holding fan blades still so they do not overspin.
  • Check every fan spins. CPU cooler, GPU fans and case fans. A fan that stopped is an easy fix.
  • Give it air. A PC jammed into a closed desk cubby, or a case with its front panel blocked, runs hotter. So does a warm room.
  • Consider the thermal paste. On an older PC, dried paste between the CPU and its cooler can raise temperatures. Reapplying it is a job for someone comfortable removing the cooler.

AMD lists overheating, unstable overclocking, unsupported memory and faulty hardware among the possible causes of reboots, crashes and hangs, so cooling belongs at the top of any checklist.

Step 4: Check power

The PSU converts wall power into the steady voltages every part needs. A graphics card pulls far more power during a game than at the desktop, so a weak or aging PSU can run a PC fine for hours and then fail the moment a demanding scene loads. How-To Geek notes that gaming can expose an insufficient PSU for exactly this reason.

Checks that cost nothing:

  • Compare wattage to requirements. Look up your graphics card maker’s recommended PSU wattage and compare it to the label on your PSU.
  • Check the power cables. Make sure the PCIe power connectors on the graphics card are fully clicked in, and that you used separate cables where the card calls for them.
  • Test the outlet. Plug the PC directly into a wall outlet instead of a cheap power strip, and try a different outlet.
  • Note the symptom. An instant black screen and reboot with no blue screen, plus Event 41, is the classic PSU or power signature.

If you swapped in a more powerful graphics card recently and the restarts began after, the PSU is the first suspect. Intel’s support guidance for restarts during games includes confirming PSU requirements and checking the cables.

Step 5: Get back to a standard configuration

Tuning is a frequent hidden cause. A memory profile that is slightly unstable, a CPU overclock or an undervolt can pass for days and then crash. AMD recommends restoring BIOS optimized defaults, updating Windows, chipset and graphics drivers, disabling third-party monitoring or overclocking tools, and removing aftermarket accessories to establish a standard configuration.

In practice:

  1. Enter the BIOS (usually by tapping Delete or F2 at startup) and choose Load Optimized Defaults.
  2. Turn off any overclocking or tuning software.
  3. Run the PC the way it came, and see whether the restarts stop.
  4. If they stop, re-enable one setting at a time to find the unstable one.

This is also the step that separates a settings problem from a hardware problem. If a clean default setup still crashes, you can stop blaming your tweaks.

Step 6: Update drivers and Windows

Drivers are the software that lets Windows talk to your hardware. They are the biggest single cause of blue-screen crashes. Microsoft’s analysis of stop errors found about 70% were caused by third-party driver code, 10% by hardware, 5% by Microsoft code, and 15% could not be determined because memory was too corrupted to analyze.

So drivers deserve real attention:

  • Install the latest graphics driver from your GPU maker. If you suspect a bad driver, do a clean install, which removes the old one first.
  • Install Windows updates, plus the latest chipset driver and BIOS update for your motherboard.
  • If restarts began right after a driver or update, roll it back in Device Manager (right-click the device, Properties, Driver, Roll Back Driver).
  • Open Device Manager and look for yellow warning icons. Microsoft advises updating or disabling problem devices and keeping roughly 10% to 15% of your drive free.
  • Run a malware scan with Windows Security.

If you can reach the desktop but crashes are frequent, try Safe Mode. If the PC is stable there, a driver or startup program is the likely culprit, not the hardware.

Step 7: Test the memory and reseat the parts

Bad RAM causes some of the most confusing crashes: random restarts, corrupted files, stop codes like MEMORY_MANAGEMENT. Dell’s stop-code guidance says faulty RAM is a common hardware cause of these errors, and that a module that reports errors should generally be reseated or replaced.

  1. Run Windows Memory Diagnostic (search for it in the Start menu) and let it restart the PC and test.
  2. For a deeper test, AMD suggests a memory test such as MemTest86, and checking that your RAM is in the correct DIMM slots and compatible with the motherboard.
  3. Power off, unplug, and reseat each RAM stick firmly until both clips click.
  4. Test with one stick at a time. If one stick crashes the PC and another does not, you have found the bad module.
  5. Reseat the graphics card and check the PCIe power connectors. Intel’s guidance also covers reseating the GPU and RAM, removing dust and booting with only essential components.

Work with the PC unplugged and touch bare metal on the case first to discharge static.

When it only restarts while gaming

The patterns below are a quick guide, not a diagnosis. Combine them with your Event Viewer log.

What you see Most likely cause First thing to try
Restarts after 10 to 30 minutes in a game, fans loud Heat Clean dust, check temperatures
Instant black screen the moment a demanding scene loads PSU or power cables Check wattage and PCIe connectors
Game freezes, driver error, then restart Graphics driver Clean driver install
Blue screen with MEMORY_MANAGEMENT RAM Memory test, reseat sticks
Started after enabling XMP or an overclock Unstable settings Load BIOS defaults
Started after adding a new part Power draw or compatibility Remove the part and retest

The same logic covers a gaming PC that crashes to the desktop without restarting: it is a milder version of the same causes, usually the graphics driver, heat or unstable settings.

Why a balanced build prevents most of this

Look at the list above: cooling that cannot keep up, a PSU too small for the graphics card, mismatched memory, an unstable tuning profile. These are mostly mismatches between parts, not parts that are bad on their own. A PC that is assembled and tested as one system avoids them, because the components are chosen to work together before the first game is ever launched.

That is the idea behind YForge. We assemble and rigorously test each PC, and you can either choose a complete build for your budget or customize individual components. Our YFORGE SYSTEMS gaming PCs start at $1,443, and if you are watching your budget, the gaming PCs under $1,000 page is the place to start. We deliver nationwide in the U.S., and orders are processed after payment.

Yforgegaming

If you are building or upgrading yourself, the checklist above doubles as a buying guide: size the PSU to the graphics card with room to spare, make sure the case moves air, and keep memory on the motherboard’s supported list. If you would rather have all of that decided and tested for you, browse our made-to-order gaming PCs for U.S. delivery.

And if your setup also needs a better home, a desk with proper airflow around the tower is a small thing that helps heat. Our YGAMERDESK line starts at $499, and a custom gaming desk is $799.

Why a balanced build prevents most of this

When to stop and get the PC looked at

If you have restored defaults, cleaned the PC, updated everything, passed a memory test and the restarts continue, the fault is probably a physical part: the PSU, the motherboard, the CPU or the graphics card. AMD advises that when stability problems persist after troubleshooting, you should contact the system or component manufacturer for technical and warranty assistance.

Before you do, gather what makes the conversation short:

  • The stop code, if one appeared.
  • The Event Viewer entries around the restart (ID 41, 6008, 1001).
  • Temperatures you recorded under load.
  • What changed just before it started: a new part, a driver, an update.
  • Which of the steps above you already tried.

Stop using the PC and unplug it if you ever smell burning, see smoke or notice a swollen component. That is a safety issue, not a troubleshooting one.

One more thing to protect: back up your files. Repeated hard shutdowns can corrupt Windows and your data. If the PC still boots, copy your important files to an external drive or cloud storage before you keep testing.

FAQ

Why does my computer keep restarting by itself?

The usual causes are overheating, a failing or underpowered PSU, bad drivers, unstable overclock or memory settings, and faulty RAM. Event Viewer will tell you whether Windows saw a crash or a power loss: Event ID 41 and 6008 mark unexpected restarts, while 1074 marks a normal one. Match that with when the restarts happen to narrow the cause.

Why does my gaming PC restart while playing games?

Games push the CPU and GPU to full load, which raises heat and power draw at the same moment. If cooling is clogged with dust or the PSU is too small for the graphics card, the system shuts down or restarts under that load. Check temperatures, PSU wattage and the graphics driver first.

How do I stop my computer from restarting automatically after a crash?

Open advanced system settings, go to Startup and Recovery, click Settings, and uncheck Automatically restart under System failure. This keeps the blue screen visible so you can read the stop code. It does not cure the underlying fault, so follow up with the cooling, power, driver and memory checks.

Can a restart with no blue screen still be a software problem?

Yes, but a sudden black screen and reboot more often points to power or heat, because Windows had no time to log an error. Check for Event ID 41 with a bug-check code of zero, which can indicate interrupted power or an underpowered PSU. If drivers or updates changed recently, roll them back as well.

Could a new graphics card cause restarts?

It can, if the PSU cannot supply enough power under load or a power cable is loose. Compare the card maker’s recommended PSU wattage to yours, reseat the card and confirm every PCIe power connector is fully clicked in. Then install a fresh graphics driver.

Sources

Made with BabyLoveGrowth to grow site authority

THE COMMUNITY

Join the conversation.

Have a question or an idea? Share it with the community.

Loading discussion…

← All guides & discussions