Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to the Power Users community on Codidact!

Power Users is a Q&A site for questions about the usage of computer software and hardware. We are still a small site and would like to grow, so please consider joining our community. We are looking forward to your questions and answers; they are the building blocks of a repository of knowledge we are building together.

Post History

75%
+4 −0
Q&A How do I start diagnosing why a Windows Server turns itself off?

I don't know much about the server versions, but for Windows in general, you'll want to peek in the Event Viewer. It contains all the logs, floods of information, most of it irrelevant and uninter...

posted 3y ago by Lundin‭

Answer
#1: Initial revision by user avatar Lundin‭ · 2021-08-09T16:46:03Z (about 3 years ago)
I don't know much about the server versions, but for Windows in general, you'll want to peek in the _Event Viewer_. 

It contains all the logs, floods of information, most of it irrelevant and uninteresting stuff. The "Administrative Events" and "System" logs are the relevant ones for tracking down unexpected power downs. In particular, you'll want to look for red cross icons (critical errors) in those logs. But red exclamation mark icons (errors) could also be relevant in case you are looking for something specific.

It helps a lot if you know the exact or at least rough time when something bad happened. Once you find an error you can read a bit of textual explanation there, or grab the event id and go search online for it. Since these error codes tend to be _very_ technical.

For example on Windows 10 client, you'll have some event 41 Kernel-Power, which gets logged when the computer has an unexpected shut-down. Which in turn could be caused by a power outage, someone deliberately plugging out the power, PSU failing and so on.