after complete uninstall of flyakite 2.0 comp crashes completely at logon (c000021a)

please guys, help me out because i'm at a loss what to do...

After using version 2.0 for ages without any trouble (some fresh installs after windows updates, that's all), i saw that 3.5 was out and decided to install that. Having had bad experience with installing updates over older versions (not flyakite, but nvidia drivers) i decided to do a complete uninstall of version 2.0 before installing 3.5. The problem is that now when i try to login to windows i get the blue screen:

STOP: c000021a {Fatal System Error}

The Windows Logon Process system process terminated unexpectedly with a status of 0xc0000005 (0x00000000 0x0000000)

remarkable also is the fact that i now have to supply my user name and password whereas before i didn't have to, as i have a single user system. The problem occurs right after clicking ok. (leaving the password empty, as i have never set any)

I tried to go to last settings that work, boot in safe mode and use debugger (though i have no experience using debugger), but nothing worked. Also tried the windows recovery but it doesn't detect my sata hdd and since i hate the recovery mode I will save that as an absolute last resort.

I have the suspicion that the smss.exe is the key, because now that i have hooked my hd to another computer and am exploring the windows folder, i see a folder named F:$WIN_NT$.~BT, which seems to me is a temporary folder (im not sure as im not really expert), which contains a system32 folder with only smss.exe and ntdll.dll in it....could it be that this is a bad hangover from the uninstallation of flyakite and that i just have to delete this folder to get my computer working again?

p.s. I also uninstalled the uninstaller, etc. as i wanted a completely fresh install...if only i had just installed the new verson OVER it:(((((((((((

#386315

Does Safe Mode not work at all? (I don't know what you mean by "nothing worked").

Try installing Flyakite 3 in Safe Mode...maybe that'll work.

-NC

#386555

I meant that in safe mode the same happens as normal mode: right (about 3 seconds) after entering the password (in my case nothing) to logon, the blue screen appears and the system is shut down.

#387226

Actually this appears to e a very common error.

Look at this first: http://support.microsoft.com/?scid=156669

and then I read this: http://www.tek-tips.com/viewthread.cfm?qid=821514

So maybe there is some hardware problem that it coughed up now.

#387275

I reinstalled windows so the problem is over now, hardware was never the issue.

It would be VERY unlikely in my opinion that a software change would cough up a hardware problem suddenly, but maybe i dont fully understand you.

Also, the status ( 0xc0000034) that your links refer to is not correspondant with the status i submitted (0xc0000005)

#390939