Boot up Failure -- STOP:c000135 {unable to locate Component}

[BoukenRed]

I'm a current Windows XP user that's running Windows XP Professional on
a Dell OptiPlex G1. However, I encountered this problem when I was
booting up my computer this morning:

STOP: c0000135 {Unable to locate Component}

This Application has failed to start because basehkttk32 was not found.
Re-installing the application may fix this problem.


Now, my problem is that I'm keeping very important software in the
system. What action could I take to solve the problem without having to
re-install XP Professional from scratch?




--
BoukenRed

[gerryf]

Sure would help to know what program that is coming from--it is not a
default windows file.

The first effort would be to load your computer with a Windows XP cd, enter
the recovery console and running a chkdsk /r command

After that, if that fails, have you tried loading in safe mode?

Here's what I guess is going on....some program is loading at startup, and
that is throwing an error...it's loading very early in the boot process
though, but I don't think it is a driver. If it is a driver, loading in
safe mode will allow you to load without that program running...you can then
investigate what that file is be reviewing your startup settings.





"BoukenRed" <BoukenRed.257bb19@pcbanter.net> wrote in message
news:BoukenRed.257bb19@pcbanter.net...
>
> I'm a current Windows XP user that's running Windows XP Professional on
> a Dell OptiPlex G1. However, I encountered this problem when I was
> booting up my computer this morning:
>
> STOP: c0000135 {Unable to locate Component}
>
> This Application has failed to start because basehkttk32 was not found.
> Re-installing the application may fix this problem.
>
>
> Now, my problem is that I'm keeping very important software in the
> system. What action could I take to solve the problem without having to
> re-install XP Professional from scratch?
>
>
>
>
> --
> BoukenRed

[Gerry]

Can you confirm that basehkttk32 is exactly as written as it appears to
be a file unique to you.

Why is software important? Data yes but you can always reinstall
software from the original source. If you mean data and you do not have
a backup then you should place the disk in another computer as a slave
and back up your data before doing anything else.

--



Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~



BoukenRed wrote:
> I'm a current Windows XP user that's running Windows XP Professional
> on a Dell OptiPlex G1. However, I encountered this problem when I was
> booting up my computer this morning:
>
> STOP: c0000135 {Unable to locate Component}
>
> This Application has failed to start because basehkttk32 was not
> found. Re-installing the application may fix this problem.
>
>
> Now, my problem is that I'm keeping very important software in the
> system. What action could I take to solve the problem without having
> to re-install XP Professional from scratch?

[Anna]

> ~~~~
> FCA
> Stourport, England
> Enquire, plan and execute
> ~~~~~~~~~~~~~~~~~~~
>
>
>
> BoukenRed wrote:
>> I'm a current Windows XP user that's running Windows XP Professional
>> on a Dell OptiPlex G1. However, I encountered this problem when I was
>> booting up my computer this morning:
>>
>> STOP: c0000135 {Unable to locate Component}
>>
>> This Application has failed to start because basehkttk32 was not
>> found. Re-installing the application may fix this problem.
>>
>>
>> Now, my problem is that I'm keeping very important software in the
>> system. What action could I take to solve the problem without having
>> to re-install XP Professional from scratch?


"Gerry" <gerry@nospam.com> wrote in message
news:uT15Wz3pIHA.4280@TK2MSFTNGP02.phx.gbl...
> Can you confirm that basehkttk32 is exactly as written as it appears to be
> a file unique to you.
>
> Why is software important? Data yes but you can always reinstall software
> from the original source. If you mean data and you do not have a backup
> then you should place the disk in another computer as a slave and back up
> your data before doing anything else.
> --
> Hope this helps.
> Gerry

BR...
May I suggest that whenever you encounter a puzzling error-type message like
the one you came across, just Google for the item, e.g., enter "basehkttk32"
in Goggle's search box. There's a fair amount of info on this item out there
for your perusal.
Anna

[Gerry]

Anna

Take another look. They all relate to the current post. That is why I
asked my question.


--
Regards.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~


Anna wrote:
>> ~~~~
>> FCA
>> Stourport, England
>> Enquire, plan and execute
>> ~~~~~~~~~~~~~~~~~~~
>>
>>
>>
>> BoukenRed wrote:
>>> I'm a current Windows XP user that's running Windows XP Professional
>>> on a Dell OptiPlex G1. However, I encountered this problem when I
>>> was booting up my computer this morning:
>>>
>>> STOP: c0000135 {Unable to locate Component}
>>>
>>> This Application has failed to start because basehkttk32 was not
>>> found. Re-installing the application may fix this problem.
>>>
>>>
>>> Now, my problem is that I'm keeping very important software in the
>>> system. What action could I take to solve the problem without having
>>> to re-install XP Professional from scratch?
>
>
> "Gerry" <gerry@nospam.com> wrote in message
> news:uT15Wz3pIHA.4280@TK2MSFTNGP02.phx.gbl...
>> Can you confirm that basehkttk32 is exactly as written as it appears
>> to be a file unique to you.
>>
>> Why is software important? Data yes but you can always reinstall
>> software from the original source. If you mean data and you do not
>> have a backup then you should place the disk in another computer as
>> a slave and back up your data before doing anything else.
>> --
>> Hope this helps.
>> Gerry
>
> BR...
> May I suggest that whenever you encounter a puzzling error-type
> message like the one you came across, just Google for the item, e.g.,
> enter "basehkttk32" in Goggle's search box. There's a fair amount of
> info on this item out there for your perusal.
> Anna

[pdxgoofy]

I had a similar error after removing several Virus' from a clients computer. The Virus had substituted a dll file with what seemed to be a random name (Basegmiw32.dll in this instance) the genuine file is (basesrv.dll) which is the "Windows NT Base API Server DLL" however the registry had been changed to target the other file. I pulled the hard drive and installed it into another system and opened the registry editor. Next I mounted the "System" Hive into a Tree I called temp. I found the "windows" key that needed changed under:
\HKLM\System\Controlset001\control\session Manager\subsystems\

The correct value for the "Windows" String is:

%SystemRoot%\system32\csrss.exe ObjectDirectory=\Windows SharedSection=1024,3072,512 Windows=On SubSystemType=Windows ServerDll=basesrv,1 ServerDll=winsrv:UserServerDllInitialization,3 ServerDll=winsrv:ConServerDllInitialization,2 ProfileControl=Off MaxRequestThreads=16

The bold portion is the corrected form.
After changing the value, I selected the "Temp" tree and uloaded the hive.

I reinstalled the drive in the computer and voilla problem solved.

Hope this helps someone

[welkinator]

PDXGOOFY

Thanks for this fix. I have seen three computers in the last week infested with WinAntiVirus Pro and I reformatted the first one before I found your post. There was also a persistent entry in {registry path}\Notify that pointed to a DAT file that couldn't be removed from the booted hard drive.

Over 600 infected files including in Sys Restore and Recycle Bin. Two that kept coming back again and again were FTP24 and CTFMON.

I've been at in the PC business over fifteen years and I can't remember a more pernicious bit of vermin but I have a question for you: while your fix is straight forward - once you know what to look for - how did you chance to come upon that particular solution?

Thanks.

...welkinator

[pdxgoofy]

I Got several BSOD's with the dll noted. I did a Google search for the file name and there was no information about it. This led me to believe that I was dealing with a Virus that had generated a random name.

Next I did a registry search for the File name and found only one instance in the registry. Next I looked up the same registry entry in a known good Computer. I noted the correct filename in the good machine (basesrv) and then compared the version/size information on both machines. They were the same so I felt assured that the original file had not been corrupted. I fixed the registry entry in the bad machine, reinstalled the drive and booted up.

I just follow the breadcrumbs and use Google to point me in the right direction when I get Lost.