Windows drive letter change & reboot loop

[jefbak]

While trying to overclock my system I ended up not being able to boot at all and I had to reset the bios.
Now windows trys to start and then reboots in an endless loop.
I tried replacing the kernel file by expanding it from the windows xp pro cd but no luck.
Then I noticed in recovery console that the drive letter had changed from c: to d:
D:\Windows
It needs to be C: but there is no assign command available in recovery console.

The boot drive is 2 sata drives in hardware raid. There are other sata and IDE drives on the system. Using the MAP command I saw that C: drive had been routed to one of the non bootable drives.

If I unplug all my drives except the boot drive will it go back to C: ? Is this cause of my reboot loop?

 

[Smilin]

This can be corrected pretty easy.

Short story: change the path where userinit is located to allow you to logon. then edit the mounted devices key to fix.


249321 Unable to log on if the boot partition drive letter has changed
http://support.microsoft.com/default.aspx?scid=kb;EN-US;249321

 

[jefbak]

Since I am only able to access the recovery console the SET command mentioned in the link above will not work for me it is disabled.
I don't seem to have any network access in recovery console either so I can't get to this computer from another on the network as far as I can tell.
I am using a workgroup not a domain if that is on any help.

 

[Smilin]

What exactly happens when you boot?

Do you get to a logon screen and get a logon loop?
Pagefile error?

What is the exact error and when does it happen?

 

[jefbak]

No error Just a reboot when windows beings starting.
I just tried F8 and chose to boot without automatic restart and I recieved the error:
STOP: c000021a
The session manage initialization system process terminated unexpectedly

 

[BadThad]

Why not just reinstall windows?

 

[jefbak]

Because that means I will be spending 2 days reloading my software as I had not had a chance to Ghost it yet.
I use a lot of video editing software with lots and lots of plugins (they are the killers) and it is a huge headache it that is what I have to do.
But this error might mean I still have a bios issue with my memory settings? They are set to auto right now but does auto always figure the settings out?
My case is this antec p180 quiet case which puts the power supply on the bottom and that means it is really hard to get to anything on the motherboard (not to mention it is super heavy). So it hard to for instance just reset the bios jumper (I have to reach in with needlenose pliers as there is no room for my fingers.
Any more ideas?

 

[Smilin]

Originally posted by: jefbak
No error Just a reboot when windows beings starting.
I just tried F8 and chose to boot without automatic restart and I recieved the error:
STOP: c000021a
The session manage initialization system process terminated unexpectedly

That error is more likely (but not certainly) due to the fact that you swapped the kernel without the other five files that have to match versions.

If you want to take a hammer to this problem and fix it once and for all, you can simply put a system restore point version of your System and Software registry hives in place and this issue will be fixed without a doubt.

Follow the steps in this KB:
307545 How to recover from a corrupted registry that prevents Windows XP from starting
http://support.microsoft.com/default.aspx?scid=kb;EN-US;307545

The symptoms are completely different and don't apply at all to your situation. However, the steps taken to correct the error given will also correct your problem.

 

[jefbak]

Thanks Obsidian, I have been thur this process before, but did not this it applied to this situation. I will give it a try.
Update:
nope, copy the stystem restore files just put me back into the same looping error I had before. I wonder if I could have fried my memory, but then how come I can get windows to being the loading process at all?
I used up my last free incident with microsoft having them tell me this was a hardware problem... Grrrrr.

 

[Smilin]

Originally posted by: jefbak
Thanks Obsidian, I have been thur this process before, but did not this it applied to this situation. I will give it a try.
Update:
nope, copy the stystem restore files just put me back into the same looping error I had before. I wonder if I could have fried my memory, but then how come I can get windows to being the loading process at all?
I used up my last free incident with microsoft having them tell me this was a hardware problem... Grrrrr.

If you swap your registry and it doesn't correct this then it's not due to a drive letter shift.

If Microsoft tech support told you it is a hardware problem then it is. Unlike other tech support (your hardware manufacturer perhaps) they won't finger point the problem to someone else unless its true.

Start doing some hardware troubleshooting. Memtest, swap components etc...

 

[jefbak]

I could not complete the restore point swap in the recovery console because I could not gain access to the c:\system volume infomation folder.
I am going to re-install windows. If it works, then this was not a hardware problem. I really don't think it is as a had a working system before and there is no indication of a broken component. so here goes.
I disable all the other drives in my BIOS so the raid boot drive has returned to c:\windows...

 

[Smilin]

use hives from your windows\repair folder to get you booting.

Once in the gui, copy hives over from the restore point (you'll have to grant yourself permission to system volume info). Drop back into recovery console and put the restore point hives in place.

 

[Smilin]

Originally posted by: Smilin
If Microsoft tech support told you it is a hardware problem then it is. Unlike other tech support (your hardware manufacturer perhaps) they won't finger point the problem to someone else unless its true.

By the way, if we find this is NOT a hardware issue please PM me the case number you had with Microsoft.

Thanks.


edit: Actually go ahead and do this now if you don't mind. I'll check the notes to see what the tech found.

 

[jefbak]

I went ahead and performed are reinstall of windows using the repair option. Of course most of my apps do not work now, but windows is working fine again and it was not a hardware issue. I knew the person at microsoft just did not want to lead me thru the recovery process (it does take a some time), still I am ticked off about it.

 

[Smilin]

Originally posted by: jefbak
I went ahead and performed are reinstall of windows using the repair option. Of course most of my apps do not work now, but windows is working fine again and it was not a hardware issue. I knew the person at microsoft just did not want to lead me thru the recovery process (it does take a some time), still I am ticked off about it.

MS tech support is some of the best available. If you've bumped into a weak tech this needs corrected.

First, reflect your ticked offness if you are surveyed. Those things are HUGE. Your feedback will be listened to.

Second, your case owner provided his manager's contact information in his signature when you first opened the case and also in the closing email. Call the manager, tell him what you found and ask for a refund.

Third, PM me your case number. I'll look into it if you would like.

 

[jefbak]

Thanks I sent you the PM and I will look into the refund.
They need to fix the recovery information so that it is clear how all the steps can be performed at the command line.
Bottom line of course is that I must start Ghosting more often.

Oh and Microsoft seem uncomfortable that I had 1)built my own system. and 2) was using a raid drive for system boot.

These should not be problems for MS techs.

 

[Smilin]

Cool, got your PM. I'm gonna check it out.

Keep in mind these guys are paid to make you happy. If you are not, work with them and their manager and let them know what it will take to make you happy.

The only way the process breaks down is if they don't know there is a problem.


I'll let you know what I find.

 

[jefbak]

So after reinstalling windows with the repair option I was able to copy the some of my previous installations system recover files from the System Volume. But the results are not complete, all the apps icons are back but many no longer work and my antivirus has competely choked.
So guess I am in for a complete reinstall. Darn.