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

We currently have a web server running windows server 2003 with a combination of asp and sites.

This server has stopping responsing 3 times over the last 3 months, despite having the generation of a kernel memory dump and write an entry in the event logs when an bsod occurs nothing is been logged. When viewing the server locally it is nonresponsive with a blank screen we have to power cycle the server to bring it back up.

After the last time we replaced all of the hardware with the expection of the hard disks, does anyone have any idea what could be causing this or what we should look at?




One thing I've find in google is a blog posting saying that a fragmented hard disk could be the cause, as the disk is fragmented we will defrag it to see if that helps. Has anyone experienced this before?

share|improve this question
A few questions: 1) What indicator lights are on the server and what do they do while it's non-responsive? 2) Can you ping the server while it's unresponsive? 3) Can you RDP to it while its unresponsive? – Chris Oct 24 '10 at 16:32

So is a BSOD actually occurring? I'd recommend un-ticking the "automatically restart" option; this gives you a chance to actually see the BSOD. If it is BSOD'ing, you'll be able to see the problem (e.g.: IRQL_NOT_LESS_OR_EQUAL), hopefully the culprit (e.g.: XYZ.SYS) and the STOP code.

share|improve this answer
When the server is accessed locally it is non responsive with a blank screen. The data centre staff have to physically turn it off to bring it back on line. – user58070 Oct 24 '10 at 12:27
Either outdated drivers, or broken hardware. That is it - nothing you can do. Had the same with bad network drivers on 2008 when it came out. An update fixed it. – TomTom Oct 24 '10 at 14:36

If the server has a blank screen and is not responsive then it hasn't crashed, so stop looking for evidence in the event log because there won't be any. There also won't be a memory dump because again, it hasn't crashed, it's become unresponsive. You say that you replaced all of the hardware? I find that a little hard to believe, are you saying that you replaced the motherboard, CPU, memory, hard drives, etc., etc?

share|improve this answer
It was a chasis swap so only the hard disks are the same. – user58070 Oct 24 '10 at 19:49

Your Answer


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