Kill.exe

[Guest]

Has anyone encountered the following error on Windows 2k and XP when kill.exe is executed

"Microsoft Process Kill Utility has encountered a problem and needs to close. We are sorry for the ..."

Error signature
AppName: kill.exe AppVer: 5.0.1475.1 ModName: ntdll.dll ModVer: 5.1.2600.1217 Offset: 000441d

 

[Guillaume Genest]

Yes i have,
To bypass the problems i have developped my own vb
apps that kill a process.

e-mail me and i will send it to you.

-----Original Message-----
Has anyone encountered the following error on Windows 2k

and XP when kill.exe is executed?

"Microsoft Process Kill Utility has encountered a

problem and needs to close. We are sorry for the ...".

Error signature:
AppName: kill.exe AppVer: 5.0.1475.1 ModName:

ntdll.dll ModVer: 5.1.2600.1217 Offset: 000441db

 

[GateKeeper]

No offense, but I would never email someone I don't know so they can
send me software I don't know. It is better policy to post the software
on the Web so that anyone can download it. This allows the
prospective user to check out the file anonymously and scan it for viruses.

Again, I mean no offense, but we should all practice safe computing, yes?

 

[Yakov Kaydanov]

Microsoft Process Kill Utility problem

Yes i have,
To bypass the problems i have developped my own vb
apps that kill a process.

e-mail me and i will send it to you.


>-----Original Message-----
>Has anyone encountered the following error on Windows 2k
and XP when kill.exe is executed?
>
>"Microsoft Process Kill Utility has encountered a
problem and needs to close. We are sorry for the ...".
>
>Error signature:
>AppName: kill.exe AppVer: 5.0.1475.1 ModName:
ntdll.dll ModVer: 5.1.2600.1217 Offset: 000441db
>
>.
>

I have this problem on my computer. Please help me.
Thank you,
Yakov

 

[extorted]

What solved it for me

After traversing the whole internet for a solution... no seriously

Do a search for kill.exe. See the owner of the file (as in, c:\program files\badprogram). If you are lucky and find only 1 like in my case, you will probably have found the culprit.

For me, it was a faulty driver version of a Level1 wireless nic (model WNC0301).

Your solutions are 2. Either:

• Download the latest version of the driver off Level1's site

OR

• Use Microsoft's offering instead of Level1's driver

Cheers

Conrad Aquilina