Hey guys I'll try to keep this short but first let me thank you for any help. Here goes, the other day I booted up my PC and it showed "windows can not boot, ntfs.sys is missing or corrupt" so I did this. http://support.microsoft.com/kb/822800 I replaced the file in the recovery console and everything copied over fine. Then I booted up again and I received an error message before windows displayed my login screen --lsass.exe "endpoint is invalid" click ok and my computer reboots. Windows at that time was booting all the way up though. I found this support article but did not help http://support.microsoft.com/kb/893712 I could not get into safe mode or regular windows boot because of the error. I then tried my last attempt at this support article, http://support.microsoft.com/kb/307545 of rewriting the registry to fix my issue and now is where I have my trouble. Windows will boot up past the blue bar loading screen on me but after that my screen stays blank and I never get my login. It sits blank for hours. When I attempt to boot back into safe mode it haults at loading ntfs driver and will not go any further. Because I rewrote my registry I can not get into the recovery console, it keeps telling me that the password is invalid and I can't try any support articles because they use the registry. I am in need of any help anyone can offer on how to get back into the registry or how to fix my loading problem. Thank you for any and all help and I apologize for the long thread. -Specificiations- Raid 0 Seagate 320GB Intel Core 2 Duo 2.13Ghz EvGA 680i Motherboard EvGA 8800GTS Corsair 4GB XMS2 Novak

Can you take the drive out and connect it as a slave to another working computer? If so, you can then manually copy and paste lsass and ntfs files you were getting errors about from the XP cd to the hard drive. If you need more specific details, let me know and I'll walk you through the process. If you can't pull the drive, there is a freeware program out there that you burn to a cd. You then boot your computer from that CD, it accesses the registry file on your hard drive and removes the requirement to log in from the recovery console. You can then reboot, and use the recovery console as normal with no need for a password. I'll look for a link to the program now... -Ryan Adams http://RyanTAdams.com

Thank you for your help. As for pulling out the hard drive I Don't believe I can do that because I'm running raid 0 and it is two hard drives. as for your second idea, I have tried using BartPE's virtual world builder and I booted to my desktop and I did the registry modification that is supposed to take the password off but I don't know if BartPE is the real registry or just a "Virtual" registry and changes don't take affect. Thank you for your help though Novak

Alright, here is where you can download that recovery console password remover ISO: http://home.eunet.no/pnordahl/ntpas... If i understand you correctly, your system (when booting into safe mode) currently hags after loading "ntfs.sys". If so, that probably means that there is an issue with the sys file that loads right after ntfs.sys. In my experience, that is NDIS.sys. Once you get into the recovery console (or connect your drive to another computer) you should try replacing the NDIS.sys file. -Ryan Adams http://RyanTAdams.com

Thank you for your help it's much appreciated. I will let you know if it works Novak

The BartPE was a good idea. I personally am not familiar enough with it to know which registry it loads by default. However, you should be able to open the file called "software" located in "%SystemRoot%\System32\Config\". In that file is a registry key located at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ WindowsNT\CurrentVersion\Setup\RecoveryConsole that when set to "1" will prevent the recovery console from asking for a password. This is the same thing the link I provided for you does automatically. -Ryan Adams http://RyanTAdams.com

Hey, I did a registry fixer in BartPE and I am I got back to my point of where I'm getting the lsass issue, any ideas? atleast I got rid of the ntfs issue. Novak