Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We have a Windows Server 2003 virtual machine running on Hyper-V. Some months ago, it started rebooting ramdonly once a month, so so. It restarts out of nothing leaving no critical/warning entry in EventViewer, so we have no clue of what caused the reboot. The other virtual machines on the host continue to run without problems.

The machine only hosts:

  • A .NET Windows service which receive TCP connections and save data
  • One site on IIS.
  • A MySQL 5.1 instance, with one active database which is shared between the site and the service.

The number of clients acessing the site is very low and the same holds for the service connections.

The machine parameters:

  • Windows Server 2003 Enterprise SP2
  • 4Gb RAM
  • 38Gb of free space in C:

I've checked the "Windows" directory. There is no "Minidump" folder and no *.dmp file in the directory. I checked "ControlPanel/System/Advanced/Startup and Recovery" and the machine is configured to write "Complete memory dump" in a "MEMORY.DMP" file, overwriting any existent one.

As there are no critical events, the server is virtual and the other machines aren't bothered by that, I don't know what else to check.

Has any one got a clue of what may be happening / has seem anything alike? I'd really appreciate some directions.

share|improve this question
What do the hyper v logs say? – t1nt1n Nov 30 '12 at 19:53
Is a minidump file created? – PHLiGHT Nov 30 '12 at 20:26
Silly suggestion: has Windows Update somehow managed to configure itself to install updates automatically? – Luke Woodward Nov 30 '12 at 20:30
I will check if there is a minidump – Arthur Nunes Dec 1 '12 at 3:18
What you have described is far from a rare occurrence and has nothing to do with it being a VM. Simply: something has become corrupted. You need to either find and fix the problem, which can be difficult and very time consuming, or nuke the machine, reinstall and recover the data from your backup. – John Gardeniers Dec 2 '12 at 10:55

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.