Fatal Error Message Now when trying to use Boot Camp

Question

I have a new issue that just cropped up. I have been using Boot Camp for some time when I just need to be concentrating on the XP Pro side of the system. However, I typically use Parallels and get in just fine. Yesterday, I attempted to use Boot Camp and go into the PC Side...the WIndows XP Pro emblem comes up duing the boot, and then I get a blue screen with the following message in white text...
STOP: c000021a {Fatal System Error}
The Session Manager Initialization system process terminated unexpectedly with a status of 0xc000003a (0x00000000 0x00000000)
The system has been shut down.
Now, I have not tried to boot up in this since I installed Leopard. So my guess is that could be my problem. Any thoughts? Please let me konw...I need help. Thanks.

Answer 1

I think what Hatter was getting at is OS X gets really cranky when disk space is low, that is, below 10%. Try freeing some space on your drive.
Similarly, windows also gets cranky if it doesn't have enough VM space.
In both cases, you will see at minimum, slowdowns, and at worst, crashes.
How much ram is in your system, and how much have you allocated to windows?
windows does not run efficiently with less than 1gb.
The windows boot CD is an installer.
You should not get a C:\prompt when booting from the CD unless you select the option have entered the System Recovery Console.
The recovery console is good for some things, but you can hose the system even more if you are unsure of what you're doing there.
The repair option will replace some files on your HD - problem there is if you have installed security updates (hotfixes, patches, whatever) the file versions on the HD and the file version on the CD won't match, the repair process will complain, disallow the replacement, or outright fail.
The stop error you received is a big clue. Go to support.microsoft.com and search for that stop error. You'll get lots of hits, and it'll be tedious, but you'll get there.
Also, if you can get back into windows, go to control panels, administrative tools, event viewer. There will be 3-4 logs listed.
Search the system log for the date/time the stop error occurred. 2x click that entry. There will be more info there that will be useful on the ms support site.
If you cant find it, resort by the event type column and look for sysdump. That'll be log entry for the bluescreen error.