Hi! A laptop that restarts without warning can feel scary because it looks random — but Windows usually leaves clues about what kind restart it was.

First, tell me what you actually see when it happens (even roughly):
• Instant reboot (screen goes black and it comes back to the login screen)?
• Restarts after a freeze (everything stops responding, then it reboots)?
• Blue screen (BSOD) for a moment, or never? Some people describe “laptop restarts randomly no blue screen.”
• Only on battery, only when plugged in, or both?

Also: Windows 11 or Windows 10, and did this start after anything changed (update, new app, new charger, travel, dust/heat)?

Thanks — “black screen then reboot” with no visible BSOD usually points to one of three buckets:

1) Power interruption (battery/charger/cable/loose connection, or power drop).
2) Overheating protection (the laptop hits a temperature limit and shuts down/restarts). People often notice fan noise/heat before it happens.
3) Crash that auto-restarts (driver or Windows crash, but Windows restarts so fast you never see a stop code).

Let’s approach this safely with evidence, not “random fixes.” Different angle question first:
When it restarts, does it say “Windows didn’t shut down properly” or something like that afterward? Or does it boot normally like nothing happened?

And do you remember if it’s more common during heavier tasks (video calls, streaming, gaming) or even when the laptop is just sitting there?

That mix (sometimes under load + fan noise + “not shut down properly”) makes heat and power stability the first safe suspects — but we’ll confirm with logs, not guesses.

Two built-in Windows tools are perfect here because they only report what happened:
• Reliability Monitor (a simple timeline of failures and “Windows was not properly shut down”).
• Event Viewer (where unexpected restarts often show as Kernel-Power events).

Before we open anything, quick safety/risk check:
• Is the laptop hot to the touch near the vents when it restarts?
• Is it on a soft surface (bed/couch) sometimes?
• Any wiggly charger connection or charging that cuts in/out?

If you’ve ever seen a pattern where problems repeat after a restart, this “how to describe the loop” style can help you collect details: error repeats after restart.

Totally safe — we’re not changing anything, just reading history.

Reliability Monitor (easy view): click Start, type Reliability, open View reliability history.
What you’re looking for is simple:
• Red X events on the days it restarted
• “Windows was not properly shut down”
• Any repeating app/driver name around the time it happens

Event Viewer (more technical, but we only note a few lines): Start → search Event Viewer → Windows Logs → System. Around the restart time, you may see entries like Kernel-Power or “unexpected shutdown.” You don’t need to interpret them perfectly — just capture the event names and the time.

While you’re there, don’t click “fix” buttons or download anything. We’re just gathering evidence so we don’t do risky steps. If you want another example of “diagnose first,” this is similar in spirit: freezes without reason – safe step by step help.

Great job finding those — and no, that doesn’t automatically mean “battery is bad.”

Kernel-Power / unexpected shutdown often means Windows knows it lost power or crashed before it could shut down cleanly. The log is a symptom marker, not a full diagnosis. It can happen from:
• Power drop (loose charger, unstable outlet, battery connection, sudden unplug)
• Overheating shutdown (thermal protection)
• System crash + auto reboot (driver issues can reboot without a visible blue screen)

Let’s narrow it with a few “safe comparisons” (no parts, no advanced changes):
1) Battery vs plugged-in pattern: does it restart more on battery, more on AC, or truly both equally?
2) Heat pattern: does it happen after 20–60 minutes of video/charging/heavy browsing, and is the fan loud right before?
3) Movement sensitivity: if the charger is a bit loose, does a small bump or repositioning ever trigger flicker/charging disconnect?

If the restart tends to happen during “busy laptop” moments, it can overlap with general instability after updates too — this timeline approach can help you describe what changed: freezes after update.

That’s a meaningful clue: charging + warmth + a charger that cuts in/out can absolutely contribute to sudden restarts — either via power interruption or extra heat under load.

Still, we don’t want to assume. Here’s the safe “step-by-step” logic I’d use:

Step 1: Stabilize the environment for a test (no settings changes): hard surface, vents not blocked, avoid couch/blankets, and make sure the charger connection is firm. Then see if the pattern changes over a day or two. If it improves a lot, that points to heat/connection rather than “mystery Windows.”

Step 2: Check the restart type: In Event Viewer, note whether there are any “WindowsUpdateClient” entries right before the restart (update-related) or if it’s just the sudden shutdown markers. (We’re only recording patterns.)

Step 3: Watch for warning signs: do you ever see screen flicker, charging icon toggling, or the laptop suddenly switching performance (fan surge) right before it restarts?

If you’re seeing repeat restarts and it’s turning into a “cycle,” this guide helps frame the pattern clearly: needs frequent restart – how to fix safely.

Yes — a driver change can be part of it, especially graphics, chipset, or power-related drivers. And your instinct is right: uninstalling randomly can create new issues.

The safe way is to use a timeline and only touch what matches the timeline:
• When did the restarts start compared to the driver update?
• Do the restarts happen during graphics-heavy moments (YouTube full screen, video calls, games), or even at idle?
• Does Reliability Monitor show a repeating “hardware error” or a specific driver/app name right before the shutdown event?

If you see a repeating name, that’s when it becomes reasonable to talk about a targeted next step. If you don’t see a repeating name and the restarts correlate with heat/charging/bumps, you focus there first.

If you want, share the general names you see in Reliability Monitor around the time (for example, a driver label or “Windows Hardware Error Architecture”), and we can decide what’s most likely without doing anything destructive.