Computing.Net > Forums > Windows 2000 > c000021a blue stop screen!

Computer Problems? Computing.Net has over 1,000,000 posts about all things technology related! Over 90% answered within 24 hours! Click here to start participating now! Also, be sure to check out the New User Guide.

c000021a blue stop screen!

Reply to Message Icon

Name: Grendell
Date: February 5, 2002 at 13:17:16 Pacific
Comment:

First off, I have my system back. But I have just spent the last 20 hours trying to figure out NTFS security, and I've gotten nowhere. It just doesn't make any sense to me, perhaps someone here can help me make light of this.

My system is a Dell laptop, Windows 2000 build 2195 (SP2). Windows 2000 was installed on a FAT32 partition. I decided to convert it to NTFS since it's supposed to be a better file system (of course that's a whole new debate). So I used the convert command, and everything worked fine.

I then did a right click on drive C: (under "My Computer"), properties, and looked at the "Sharing" tab. I found that Windows 2000 had created a hidden administrative share of the entire C: drive (C$)! Then, after checking the security tab, I found that it had given "Everyone" on my C: drive full control! Wow, that didn't seem very secure. :) I further checked folders and files under my C: drive, and found that they too had security set to "Everyone" for full control.

Here's exactly what I did. First, I changed the owner of C: drive to computername\my_user_logon, let's call it computer\jsmith. Computer\jsmith is my main logon and is a member of the Administrators group. I checked the checkbox and set it propagate down to all child objects. It seemed to work fine (of course except for pagefile.sys, but I guessed that's normal). I then went into the "Security" tab, "Advanced" properties, and added "Administrators" and allowed full control. (Again, this is C: drive.) I then removed "Everyone." Finally, I checked the check box to allow the changes to propagate down and reset for all child objects. It then set the permissions on everything seemingly with no problem, except again of course for pagefile.sys.

Everything seemed to be fine at first, but I then started getting errors that files couldn't be found. Hmmmm. It didn't seem that it was a security issue, I was logged in as computer\jsmith and computer\jsmith is a member of Administrators, who have full control of C: drive and all child objects! So, I rebooted.

Here's where the nightmare began. My computer gave me a blue stop screen on booting. Specifically, a stop c000021a. What would happen exactly is that my computer would boot, I would get a "Starting Windows 2000" black and white screen, then I would get the Windows 2000 loading graphic screen and the progress meter would progress all the way to the right. I then would get a black console screen with the following message displayed on it:

"Autochk program not found. Skipping autocheck."

Immediately following this error message, the next message appeared:

"STOP: c000021a {Fatal System Error}
The Session Manager Initialization system process terminated unexpectedly with a status of 0xc0000013 (0x00000000
0x00000000)."

There was an article on Technet describing this condition, but it only mentions this for NT4 specifically and points to the problem as a disk mirror set problem. This didn't seem to fit my problem, what I had done was reset security. Why would I be getting this stop message?

I tried a number of things. Windows 2000 setup, recovery, recovery console. That thing was pretty much useless, but I guess it was upholding the security I just set. Windows 2000 setup, emergency recovery. I didn't have an emergency recovery disk, so I hit L. It found Windows 2000, but when it tried to run the recovery, it would fail on various files (I forget which ones at this point). When rebooting, I would no longer get the above c000021a stop message, but I would still get a blue screen stop message of c0000135, missing winsrv.dll file.

I tore my hair out for the next TWENTY hours trying to figure out how to get my system back! Finally, I discovered a program called "ERD Commander" by Winternals. What this is is a recovery console that circumvents the NTFS security and gives the user full access to the NTFS partition and allows all NTFS security to be removed and reset to "Everyone" for all files and folders. (The downside, the program cost $350!!!) I booted to the ERD Commander console, it mounted my NTFS partition as D:, I then did an "access d:", switched to d:, then did an "access *.* /s" which reset NTFS access to full control for everyone on all files and folders. I then ran a chkdsk, it found errors and corrected them.

Surprise, Windows 2000 works and boots normally again! Now that I knew how and had the tools to reset NTFS security, I tried some other settings for "Security" for the C: drive. No matter what I tried, if I removed "Everyone" for full access on C: and checked the box for child propagation, I would boot back to a c000021a stop screen, and I'd have to use the ERD Commander method described above to recover. I tried adding (in addition to Administrators), "SYSTEM," "INTERACTIVE," and "SERVICE" (all at once and several combinations thereof), none of which succeeded, again, I booted to a c000021a stop screen every time.

If you've stuck with me and read all of this, can you perhaps give me some insight as to why this is happening? It would *seem* logical to me that setting security on c: drive to "Administrators" and allowing propagation to all child objects would allow the system to boot and would not let anyone log on unless they were a member of "Administrators." Why would I get the c000021a stop screen?

I've left the sharing tab alone throughout all of this. The "owner" of c: plus all child objects has also been left at "Administrators," as I had set it above.

Again, I'd really like to learn what went wrong in the above scenario. You don't need to tell me not to be messing with permissions, I know I shouldn't. But, I want to learn what is happening here. Surely the C: drive can't *only* work unless "everyone" has full control?

Again, ANY insight at all is greatly appreciated!



Sponsored Link
Ads by Google

Response Number 1
Name: Brent
Date: February 5, 2002 at 13:37:57 Pacific
Reply:

Hey man its ok dont have a heart attack there's not much you can do to someone's computer even if someone managed to add there self to you workgroup or domain you have to have the administrator name and password just make sure that you diable the guest account...or put a password on it..but just get a good firewall and anti-virus.. and youl be fine. As for the C:\ Share that comes with windows its an administrator property..so just do this

1.)Disable Guest account, and anyother built in account...

2.)Get a good Firewall

3.)Get a Good Anti-Virus

4.)Dont Worrie about it

As for your file system the blue screen error is just a corrupted file in your registry..i would use Norton utilitys and use win doctor or you can go in there and fix it your self...but if you need Norton i have it just email me at DBZxSnakeyes@hotmail.com and uninstall any nonlagit software..like stuff you have got off the internet..and i suggest you use Black Ice Defender i have that also :) Hope this helped


0
Reply to Message Icon

Related Posts

See More







Post Locked

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.


Go to Windows 2000 Forum Home


Sponsored links

Ads by Google


Results for: c000021a blue stop screen!

Blue Stop Screen at start up. www.computing.net/answers/windows-2000/blue-stop-screen-at-start-up/63558.html

blue stop screen when booting with new H www.computing.net/answers/windows-2000/blue-stop-screen-when-booting-with-new-h/16676.html

Installing W2KPro Blue Stop Screen www.computing.net/answers/windows-2000/installing-w2kpro-blue-stop-screen/62278.html