• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 801
  • Last Modified:

Windows Server 2003 R2 SP2 Random Shutdowns

I have a server that is currently running Windows Server 2003 R2 SP2.  The last 2 weeks or so we are experiencing random shut downs with the server.  It is going through a full shut down process.  In event viewer you can see these shut downs and this is what they say;

"The process winlogon.exe has initiated the power off of computer SERVER1 on behalf of user SERVER1\Administrator for the following reason: No title for this reason could be found
 Reason Code: 0x0
 Shutdown Type: power off
 Comment:
"

I've checked all the normal causes that I can think of such as Virus software, Automatic updates, Scheduled tasks, etc.  There is no virus software on this computer.  Automatic updates are turned off.  And there isn't a single scheduled task.  I ran a malware scan which found nothing.

One thing I will mention is that this server is a bit behind on updates.  I am hesitant to do them as the client uses some specific industry software that he claims stops functioning after he updates with the current updates that are waiting to go through.

Any ideas of where to go from here?

Thank you
0
qbarat2
Asked:
qbarat2
  • 4
1 Solution
 
Darius GhassemCommented:
I would update all Drivers and firmware for the hardware
0
 
qbarat2Author Commented:
All drivers appear to be up to date.  Any other suggestions?
0
 
sifueditionCommented:
Check the UPS for the server and if there is any UPS management software. If an APC unit detects power issues and has the agents installed, it can initiate it's own shutdowns.

If the logs indicate a graceful shutdown, I would think this is software. You may want to boot to safe mode and see if the issue is still present. It just becomes a matter of elimination after that.

Unfortunately, on a critical system, all of these kinds of tests can be hard to do or even unacceptable. You may very well need to find a way to get a "good enough" solution for data availability until you can sort this out.

If all else fails, go into full hardware testing, to at least attempt to eliminate it. Get the bootable diagnostics from the manufacturer. Try memtest86. Remove hardware until you are at the minimum to complete POST and see if it's stable. Etc. Most servers now have firmware that can shut the system down under certain conditions.
0
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
qbarat2Author Commented:
I forgot to mention, it IS connected to a UPS but no UPS or any power management software is installed.  The problem is very sporadic and has now not happened in about 7 days so it is very hard to even troubleshoot this.  I currently have new RAM in the server now, but it has happened once even with the new RAM.
0
 
qbarat2Author Commented:
It was a bad power cable
0
 
qbarat2Author Commented:
Found out through trial and error that it was a bad power cable.
0

Featured Post

Nothing ever in the clear!

This technical paper will help you implement VMware’s VM encryption as well as implement Veeam encryption which together will achieve the nothing ever in the clear goal. If a bad guy steals VMs, backups or traffic they get nothing.

  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now