that one usually means that there is something wrong with the operating system installation. Did you bring the server up via an older, maybe scratched, win2003 disk? The cd could be corrupted or did the server come with the op sys pre installed?

Hopefully someone here will come up with a better way but you may have to re-install the operating system.

Nope, used a brand new disc and installed it. No errors were thrown in the installation process.

If possible, try to start windows with "Last known good configuration".

KB156669 from MS might also be to some help.

http://support.microsoft.com/default.aspx?scid=kb;en-us;156669


I hope it helps and good luck!

Try updating the printer driver on both the server and on the Admins workstation and see if it helps.
And as a workaround you could actually connect the printer through the network (if it supports it) or the Admin could share his printer and then map it up on the server in question.

That was a common stop code about a year ago from Trend Micro AV.  Basically it was (falsely) detecting one of the core sys files as a virus and not allowing it to start up.  

Can you get into safe mode?  If so, try disabling your AV software (even if it isn't TM AV)  in safe mode and reboot into normal mode (just as a test, do not run live w/o AV software)
 
This was the first thing that came to mind when I saw this error.

Otherwise, you can try a repair install or replace these files from a know good machine with the same OS & SP Level - explorer.exe, lsass.exe, services.exe, smss.exe & spoolsv.exe.

- Chris

Server has been running fine so far this week after one of our admins stopped logging into it.

There is no AV running on it.

Chris:
How can i repair those system files you mentioned?

Best way is to copy them from a know working system *IMPORTANT* - with the same Service Pack level.  Or you can extract them from the SP update package available from MS.

Then you would need a bootable os such as Bart PE or Knoppix to boot the system off of or you could copy them to the server, boot to recovery console and move them via cmd line into the correct directories.  Some are in C:\windows and others are in C:\windows\system32.

Just reread the fact it is only 2 weeks old though... I would look toward bad hardware or an error during installation.