The machine goes off mid-sentence and comes straight back to the login screen. No error, no blue screen, nothing to search for. That is not a PC keeping secrets.
Windows wrote down what happened, and there is a setting on by default that is why you never saw it. I read the crash settings on this laptop and then its own event log, and both are worth doing on yours before you change a thing.
The setting that hides the blue screen from you
Windows restarts itself the instant a Stop error happens, and the blue screen lasts a fraction of a second. The setting is on by default, and it explains the whole mystery.
Ours, read here: AutoReboot is 1 on this machine, which is the default, and yours is almost certainly 1 too. Turn it off first. The next crash then stays put long enough to read the stop code off it.
Microsoft gives the route. Advanced system settings, Advanced, then "In the Startup and Recovery section, select Settings" and "Clear the Automatically restart check box."
Where Windows already wrote it down
You do not have to wait for the next one. Microsoft documents the event: "If your computer shuts down unexpectedly, Windows logs Event ID 41 the next time that the computer starts."
The message text is specific: "The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly."
Ours, from this machine's log: three of those, on 18 September, 11 September and 14 August, each followed by an Event 6008. That does not mean this laptop is failing, and yours may be the same.
Microsoft's Event ID 41 page names a power cut and a held power button among the causes. Neither is a fault.
Four event numbers that tell you which kind of shutdown you had
Worth learning, because the numbers disagree with each other in a way that helps you. Microsoft's own descriptions. Event 41: "This event indicates that Windows restarted without a complete shutdown."
Event 6008: "This event indicates an improper or dirty shutdown." Event 6006 is the opposite: "This event indicates that Windows was adequately turned off."
Event 1074 is a clean one somebody asked for. Microsoft: "logged when an application is responsible for the system shutdown or restart."
The field inside Event 41 that names the cause
The diagnosis really does live in one field. Microsoft explains the mechanism: Windows "records any error codes as it shuts down" and includes them in Event ID 41 on the next startup.
A non-zero BugcheckCode means a Stop error. You had a blue screen and never saw it. The number is decimal, the documentation is hexadecimal, and Microsoft's own example is "159" converts to 0x0000009f.
Now you have a real search term. The stop code is the line worth reading first.
Zeros everywhere, which is the harder answer
Microsoft has a scenario for this, and it points away from software. If your Event 41 shows a BugcheckCode of zero, Microsoft says "something prevents Windows from generating error codes or from writing error codes to disk."
Its first suggestion is blunt, and I would take it seriously. That behavior "might indicate a power supply problem." One of the named causes will be yours.
Those causes are physical: a drained or removed laptop battery, a desktop unplugged or hit by a power cut, or a supply that is "underpowered or faulty."
Microsoft's summary of this case is the sentence to hold on to. These symptoms "typically indicate a hardware problem."
Microsoft's own checklist for the hardware case
Four things, in its order, not mine. Disable overclocking, then check whether the problem still happens at the correct speed. Check the memory with a memory checker. Every chip should run at the same speed and be configured correctly.
Check your power supply has enough wattage for everything installed. Microsoft points out that added memory, a newer processor, more drives or external devices can pull more than the supply gives consistently.
Then check for overheating by reading internal temperatures and looking for any component running hot.
What to do this evening, in order
Five steps, and the first two cost nothing. Turn off Automatically restart, and the next one stays on screen. Open Event Viewer and filter the System log for 41, 6008 and 1074, and you know how many you have had and how often.
Read the BugcheckCode. A number means software or a driver. A zero means power, heat or memory. Then fix what the code names.
A memory stop code has its own path, and a machine that is merely slow rather than crashing is a different question entirely.
**Status: read on 19 September 2026 from Microsoft's Event ID 41 troubleshooting documentation, with the crash control settings and the System event log read on this laptop the same day.
No crash was caused deliberately, no setting was changed and no hardware was tested to write this.**
Why does my PC restart with no blue screen?
Because Windows is set to restart immediately on a Stop error, so your blue screen appears for a fraction of a second. The setting is called Automatically restart, it is on by default, and clearing it makes the next crash stay on screen.
How do I find out why my computer restarted?
Open Event Viewer on your machine and look in the System log for Event ID 41. Microsoft logs it the next time the computer starts after an unexpected shutdown, and the BugcheckCode inside it names the Stop error if there was one.
What does Event ID 41 mean?
Microsoft's wording is that the system has rebooted without cleanly shutting down first, and that this could be caused if the system stopped responding, crashed, or lost power unexpectedly.
For you it is a symptom rather than a single fault.
What if Event 41 shows a bugcheck code of zero?
Microsoft says that might indicate a power supply problem, and lists a drained battery, a power cut or an underpowered supply as causes. It describes this case as typically indicating a hardware problem, so check power, memory and heat.
The Short Version
- Automatically restart is on by default and is why you never see the blue screen.
- Clear it in Startup and Recovery so the next crash stays on screen.
- Windows logs Event ID 41 on the next start after any unexpected shutdown.
- 41 means dirty, 6008 confirms it, 6006 means clean, 1074 means somebody asked for it.
- A non-zero BugcheckCode inside Event 41 means it really was a Stop error.
- That number is decimal and the documentation is hexadecimal. 159 becomes 0x0000009f.
- Zeros point away from software. Microsoft names power supply problems first.
- Its hardware checklist is overclocking, memory, power supply wattage and overheating.
Where to Next
Turn off Automatically restart tonight, because everything else is easier once the screen stays put. Open the event log and count how many Event 41s you have and when, since a pattern is worth more than a single one.
Read the BugcheckCode before you buy anything, because a number and a zero send you in opposite directions. And if it is zeros, start with heat and power rather than reinstalling Windows.
Got an Event 41 with a code that leads nowhere useful? Put the hexadecimal value in the comments and say what the machine was doing at the time.
Isaac Smith is the founder and editor of PC Glance, a website that covers computers, laptops, and technology. He is a tech enthusiast and a computer geek who loves to share his insights and help his readers make smart choices when buying tech gadgets or laptops. He is always curious and updated about the latest tech trends.