Windows Forum

Ask something
Discussion Locked

Windows 2003 Enterprise Edition problem

0 helpful
2 replies

by taniag 1 view

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

We have been experiencing multiple lock ups and restarts on its own accord on our FTP server running Windows 2003 Enterprise Edition Server running on an NT Domain.

Server is running on a RAID-5 (Adaptec ATA 2100S Ultra3 Single Channel

Unfortunately the event viewer only states just before lockup or restart:

1. ESENT: svchost (1292) The database engine 5.02.3790.0000 started.

2. System Error: Error code 00000050, parameter1 ba00ebb4, parameter2 00000000, parameter3 ba32889f, parameter4 00000000.

3. Eventlog: The previous system shutdown at 7:27:53 PM on 12/20/2003 was unexpected.

We have also changed the current drives over to an identical system and we still get the same problem.
We have looked in the on-line technet with no help.

Can anyone help or suggest what the problem may be.

Best regards,
Tania Gurr

2 replies

by victor

Sound like a virus to me. I had the same problem a few weeks back. The only thing that fixed it was to do scan with the latest virus definition. And to remove some settings from the registry.

If you're running web and ftp make sure you lock down the server from unwanted access. If your running SQL, make sure it has the latest security patch installed.

by joseph moore

Wow, so your server is hitting the bugcheck and rebooting itself! A BSOD in Win2K3! I actually haven't seen that yet!
Ok, the bugcheck should be making a memory dump file, called MEMORY.DMP that you can try and diagnose.
You can take this file, and run it against WINDBG to get a better look at what is causing the bugcheck. You would need Windows Symbols, and WINDBG to do this.
More information on these tools, and where to get them, is here:
http://tinyurl.com/yvaz4

I did this once, and I was able to pinpoint the bugcheck to a software driver that was not compatible with the new Intel hyperthreading processors. But let me tell you, this was not the easiest thing in the world to do!

You could also send the .DMP file to Microsoft, and they will debug it for you. If you have a support contract, then you could think about that as an option.

Good luck

This discussion is closed to new replies.