Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsWindows Server 2003Windows 2000Windows NTSmall Business ServerVirtual ServerExchange ServerIISHost Integration ServerISA ServerSMSWSUSMOMWindows Media ServerSecurityCertification
Related Topics
SQL ServerMS WindowsMS OfficePC HardwareMore Topics ...

Windows Server Forum / Windows NT / Setup / February 2004

Tip: Looking for answers? Try searching our database.

Server Not Starting

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
David - 23 Feb 2004 17:21 GMT
Hi:
I have an NT domain, servers at SP6a.
A student did some unauthorized access in some folders,
and deleted some work.
Now, when the server tries to boot, it shows only 256Mb of
the 512Mb RAM, and hangs on the boot with the following
message:
Stop c000021a {Fatal System Error}
The Session Manager initialization system process
terminated unexpectedly with a status of 0xc00000005
(0x00000000, 0x00000000) The system has been shut down.

It then does a dump, and tries to restart.  Then the same
appears.

Any advice?  

Thanks!

Dave
Danny Sanders - 23 Feb 2004 21:02 GMT
See if this helps:
http://support.microsoft.com/default.aspx?scid=kb;en-us;317189&Product=nts40

hth
DDS W 2k MVP MCSE

> Hi:
> I have an NT domain, servers at SP6a.
[quoted text clipped - 16 lines]
>
> Dave
Dave - 24 Feb 2004 14:37 GMT
Danny:

Thanks.  I already followed that article's directions, and
it is still doing the same thing, with the same message.  
When I did it, there were no PendingFileOperations in
either location.
If there is anything else, please let me know.  Otherwise,
the server gets reloaded today.

Dave

>-----Original Message-----
>See if this helps:
[quoted text clipped - 25 lines]
>
>.
anonymous@discussions.microsoft.com - 24 Feb 2004 14:46 GMT
Possible causes:
1) A memory module has failed and the error is incorrect
but caused by the hardware fault.
Solution: remove the modules systematically and determine
if a module is faulty.

2) A system file was removed or modified with a different
version of the file (for example a non SP6 file version)
Solution: Recopy the service pack 6 files into the SYSTEM32
folder from a patched parallel installation. !BACKUP THE
FOLDER FIRST!

3) The permissions of a system file has been reset and the
SYSTEM account can't access it.

>-----Original Message-----
>Hi:
[quoted text clipped - 18 lines]
>Dave
>.
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.