Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

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

I am trialing Windows Server 2008 and every 2 weeks to the minute the server is locking up and requires a hard reboot. I check the event logs and there are no errors for the whole day. Is this because it is a trial or is that nothing to do with my lockup issue?

How do I go about finding out what the error is?

Even if I reboot inbetween this 2 week cycle, it still locks up 2 weeks after the last lockup.

When a lockup occurs I cannot access FTP,HTTP or RDP.

share|improve this question

I'm not aware of any limitations in the eval version of W2K8. If W2K8 is true-to-form with other Microsoft Windows Server evals, it should work exactly as the full version until the trial period expires, and then will periodically STOP (panic, blue-screen, etc) but continue to work otherwise. (Lots of fun when a classroom full of computers gets their dates set ahead by another class and you find that all your student VMs are eval-period-expired and blue-screening like crazy for the last 10 weeks of a 16 week class... >smile<).

Does the machine still respond to PINGs? Does the console appear normal? Does the mouse pointer move on the console? (These sound like silly questions, but I'm trying to determine if the machine is still processing the kernel scheduler event loop, or if it has locked into some kind of infinite loop.)

It seems unlikely that a user-land process could cause what you're seeing. Even so, I'd start logging performance counters, I suppose, if nothing was showing up in the event logs. I'd grab the "Processor", "Process", "System", "PhysicalDisk", and "Network" objects to try and correlate the "lock up" to IO events.

I'd suspect dodgy hardware or a bad hardware driver as the culprit. Bad RAM would typically manifest sooner than you're describing, but it's a possibility. I'd be sure I was up-to-date on all my hardware driver versions.

share|improve this answer

In addition to Evan's answer another question: since it happens at the exact same minute every two weeks, is there a scheduled job you're not aware of? Maybe a virus scanner or a backup running?

share|improve this answer

Your Answer


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

Not the answer you're looking for? Browse other questions tagged or ask your own question.