PE2650 Windows 2003 SP1 freezes

Hi,

we have a Dell PE2650 with Windows 2003 SP1 installed. Over half a year the Server freezes from time to time. Call was running with DELL but Hardware seems to be OK. So call was closed. Server freezed maybe 1 time a month.
But now the last 2 Weeks the Server freezes 2 times a week. Thats a problem now. Its a file and printserver.

Problem is, theres no error messages in eventlog. Next Problem ist, theres no Blue Screen. It seems, that the explorer.exe crashes. Display of Server is just black. Sometimes iam able to start the task manager and when i look at explorer i see, lots of cpu is used. but cant start any other programs, have to do a hard reboot then.

tonight i will update the latest DELL drivers and windows updates and uninstall symantec antivurs 10 client. my thought are going to antivirus and broadcom network cards. teaming we cut long time ago. one adapter is diabled.

But when server freezes again, how to troublehoot? ive no memory.dmp file, because of no blue screen?

Thanks a lot for your ideas,

Marcus

 

I am suffering from the exact same problem. I have a Dell SC 420 server running Windows SBS 2003. I have been experiencing this problem in increasing frequency just as you mention. Also just a blank screen, unresponsive system, no BSOD and nothing in the event logs to signify why the problem occured.

I will post if I find any solutions or clues to the problem.

 

just for info: i uninstalled temporarly Symantec 10 and updated the
server with the latest hardware updates. Since then, server is running.
But i cant let it go without antivirus....

bye
marcus

 

I found someone that was having a similar problem, and one person had a possible cause:

Something keeps on hanging / freezing every 3-4 days > Small Business Server Forum - English > Smallbizserver.Net
http://www.smallbizserver.net/Default.aspx?tabid=53&forumid=11&tpage=3&view=Topic&postid=34562

I don't know if this could apply to your problem or not, but I thought I would share...It definitely sounds like a possibility for me, because the only events I saw in my server log before the last time this problem occured were a few very large print jobs and I have a similar size system partition/free space issue.