Process gets not killed despite explicit rule

[M1000]

Hi

I'm using Proccess Tamer because when I open a Explorer folder with
some media files eventually the process dllhost.exe starts with
constantely 50% CPU (Windows 7 RC, Process Tamer v.2.11.01).

But although I set an explit rule to kill the process it only gets a
lower priority.

Any ideas?
Marc

[f0dder]

You'll probably want to clean up the media codecs you've installed on the computer - a prime reason for the behavior you explain is a codec that bugs out while trying to show a video thumbnail. I've often seen this on computer where people have installed codec packs instead of grabbing only the codecs they need.

It could also be an indication that some of your media files are (at least slightly) broken/corrupt, but decent codecs still shouldn't bug out that way.

[lanux128]

In WinXP, sometimes the Windows Explorer causes the system to freeze as it tries to read the info from the media files, especially if the files are too large or corrupted. It's probable that Win7 could be doing the same.

there is a tool called Windows XP AVI Fix which turned off this "feature" for WinXP users.

[M1000]

Thank you for both of your answers

I've monitored explorer.exe with "Process Monitor" and have seen
something related Pinnacle, so I uninstalled Pinnacle Studio 10
and now the bug is gone.

[pjsalmin]

Stumbled upon this program as I am trying to find some software which monitors processes, and if certain conditions is met it kills the wanted process.

I am doing distributed computing, and use GPU's for heavy duty calculations. Sometimes there is a "display driver reset" causing the GPU application to reset (shown in system tray, normal exe). I have tried to use process tamer to force kill the app if it uses more than 50% of CPU time. I tried starting the app with administrator privileges, but it just won't kill it. Using Win7x64. Here's a few screenshots:

[mouser]

ok look's like you guys have found a bug -- working on it.. do you have a link to this astronomy application that i can test on?
what i may do barring that, is upload a demo version for you that will save more verbose log messages to help figure out what's going wrong.