Main Site Nav
Topics Topics Edit Profile Profile Help/Instructions Help    
Search Last 1|3|7 Days Search Search Tree View Tree View  

Stop Errors, Reinstall, and Raid

Trish's Escape from Hardware Hell Help Board » Hardware » Dead, Dying or Booting Problems » Stop Errors, Reinstall, and Raid « Previous Next »

Author Message
Dave W
Posted on Friday, March 21, 2003 - 5:14 am:   

A few days ago when I went to bed everything was OK and I left my XP computer running as usual. In the morning when I wiggled my mouse to wake up the monitor nothing happened. I used the reset button to restart and everything looked normal up to and including the Windows XP logo screen. I then got the following blue screen error message:

" Stop: c000021a (Fatal System Error)

The windows subsystem system process terminated unexpectedly with a status of ox c00001d (ox77e7e93e ox0053e1do) The system has been shut down. "

I turned off the computer completely, waited ten minutes and tried again with the same results ( except that the status numbers were ox c00005 ( ox77f5214f ox00c8dde0).

There was no hint of a problem before this.

I then tried safe mode. It took forever (15 minutes or more) until the desktop and icons began to load. At that point Explorer.exe crashed and was shut down, causing the desktop icons and taskbar to disappear.

Next I tried booting into Last Known Good Configuration. The process stopped to check for an error on my FAT32 hard disk which is my C Drive. It found a too long File Folder name entry which was news to me, and supposedly repaired it. As soon as this finished A blue screen came up with the following scary message:

" Stop c0000218 (Registry File Failure)

The registry cannot load the Hive(File) \systemroot/system32\config\software or its log or alternate.

It is corrupt, absent, or not writable. "

This morning I tried a reinstall. I thought that after the Eula the
install routine would look for a previous installation and offer to repair it. But instead of the "If one of the following Windows XP installations is damaged ...." screen, I was greeted with the following:

"You chose to install Windows XP on a partition that contains another operating system.Installing windows on this partition might cause the other operating system to function improperly.

Caution: Installing multiple operating systems on a single partition is not recommended.

To continue using this partition, press C
To select a different partition , Press Esc."

I have no other operating system on the computer except the apparently damaged WinXP Sp1 with all of the subsequent updates. I escaped out of the reinstallation attempt.

WinXP is on it's separate hard disk, C:, with a few programs and minimal data. The rest of my stuff is on two Western Digital 120 gig hard drives in a Raid 0 array using the FIC an11's onboard Promise Raid. It's the data on the raid array, Drive E:, that is my number one concern. I'm afraid that a clean install of WinXP, which I guess would mean reinstalling the stuff on the MB CD, which I guess includes stuff for the raid, might result in losing my raid data. I haven't found a way to contact Promise, and FIC, my MB manufacturer, has ignored my email.

I now get even less far in attempts to start. After the bios screen and the onboard Promise
Raid array check, which detects no problem, I get a Session Initialization Failed message, Stop: 0x0000006f.

I have since pulled all my PCI cards and tried again, but I still get the Session Initialization Failed message.

Any Suggestions?


What should I do?
E.S.
Posted on Friday, March 21, 2003 - 8:39 am:   

I ran into this a while back, To save your data on the raid and not have XP installed on it or attempt to install on it your best solution is to remove the raid drives and run a complete diagnostic on your C: drive make sure there aren't any bad sectors than reinstall XP. after your done with that you should be able to migrate the raid setup back into XP and not lose any data. Good luck.
Vince Sadowski
Posted on Tuesday, April 8, 2003 - 5:00 pm:   

When I boot up my Gateways 133, I get a message VRAM invalid - VRAM cleared. I have to hit "Escape" to continue the boot up procedure.

Add Your Message Here
Post:
Username: Posting Information:
This is a public posting area. Enter your username and password if you have an account. Otherwise, enter your full name as your username and leave the password blank. Your e-mail address is optional.
Password:
E-mail:
Options: Enable HTML code in message
Automatically activate URLs in message
Action:

Administration Administration Log Out Log Out   Previous Page Previous Page Next Page Next Page