<div>
enable minidump kernel images and analyze the files with bluescreen analyzer.<br />
<br />
<a href="http://www.nirsoft.net/utils/blue_screen_view.html" rel="ugc">http://www.nirsoft.net/utils/blue_screen_view.html</a><br />
<a href="http://blog.nirsoft.net/2010/07/27/how-to-configure-windows-to-create-minidump-files-on-bsod/" rel="ugc">http://blog.nirsoft.net/2010/07/27/how-to-configure-windows-to-create-minidump-files-on-bsod/</a>
</div>


<div>
You should have system eventlog entries for sources Eventlog and Userdmp (IIRC). The Eventlog entry should tell you when the system was rebooted, and the following entries why.
</div>


<div>
Event log shows some clue, and it was a credentials' issue on an windows engine.
</div>


<div>
<div class="content wysiwyg-content">
This is using HP Proliant ML350 G5 server. It was loaded with Windows 2003 R2. Recently, found that the server always rebooted by itself. I don't think any software/drivers were installed recently. How to diagnose for the problem? How to solve it?<br />
<br />
Thanks in advance.
</div>
</div>


This is using HP Proliant ML350 G5 server. It was loaded with Windows 2003 R2. Recently, found that the server always rebooted by itself. I don't think any software/drivers were installed recently. How to diagnose for the problem? How to solve it?

Thanks in advance.

enable minidump kernel images and analyze the files with bluescreen analyzer.

http://www.nirsoft.net/utils/blue_screen_view.html
http://blog.nirsoft.net/2010/07/27/how-to-configure-windows-to-create-minidump-files-on-bsod/

You should have system eventlog entries for sources Eventlog and Userdmp (IIRC). The Eventlog entry should tell you when the system was rebooted, and the following entries why.

Event log shows some clue, and it was a credentials&#39; issue on an windows engine.

Why the server rebooted by itself?

This is using HP Proliant ML350 G5 server. It was loaded with Windows 2003 R2. Recently, found that the server always rebooted by itself. I don&#39;t think any software/drivers were installed recently. How to diagnose for the problem? How to solve it?

Thanks in advance.

Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).