Why does dllhost.exe Com surrogate consumes memory untill crash

I also have an HTPC or multimedia machine I am going to check with My TV card vendor and see if They have also made a patch.

Ill post an update with link if so.

Thanks for the info.

I'm having this same problem. It started exactly when I started working with 3D movie files that have certain tags in the meta data in the file that indicate the 3D nature for playback (either SBS or TB). Dllhost.exe balloons and explodes, stuck in some kind of infinite loop trying to generate a thumbnail for it. Very frustrating, thank you to those who posted here that helped me solve the mystery.

Why does dllhost.exe  Com surrogate consumes memory untill crash.

It happens when I highlight or view a folder containing video files, Even if I close the folder or select a different folder the memory keeps getting consumed.

It seems to happen mostly with 3D Video files but it has done the same with 2D files.

So it seems to be a problem with the windows thumb nail system dealing with these files.

By the way trying to delete or move the file or folder while the Com Surrogate is consuming memory Delete can not complete the task.

What I have been doing is finding offending file selecting Delete, then go to task manager stopping Com Surrogate, then the file will delete.

OK, I got this! I have most likely found the solution to your problem, if all the other normal things have been done to your system to ensure its proper operation, and you have plenty of resources such as RAM and processor speed. 

I had the same problem as you and I have 32GB of memory and a decent 8 core processor. dllhost.exe would grow like the blob and slow everything down, especially if I did a search or just my desktop was showing with thumbnails of video or still images.

Solution:  download and run autoruns by sysinternals. It will take you maybe 20 minutes till you have your problem solved and will be error free.  When you uncheck a box in the left, it prevents a program or module from starting when windows starts.  It doesn't prevent you from using the program, it just prevents the small programs from running all the time in the background, like the acrobat reader tray, even though you don't spend all your days opening and reading acrobat PDFs.

I uncheck any and all references to MS Office and the associated Kaspersky program that gives that program protection. Also any references to Adobe.  Save the file, name it,  and restart. Done!

This is the fix:  Download and run "Autoruns" by Systinternals.  Carefully go through the list, uncheck any programs that you feel don't need to run automatically when you start windows.  I, for instance, unchecked any and all references to MS office, Adobe acrobat, and a few others that I had no idea were starting.  Now, all of my MS office programs work just fine and so does acrobat for that matter.  There were Kaspersky modules that started with each of those items also and I unchecked those, since they were no longer going to be running when Windows starts. 

All of the other mundane ideas and checks to ensure your system are helpful I'm sure, but did nothing to solve this issue-- as this did.  Also, my computer is running much faster in general. Please post here if you try this issue, let me know the result of your attempt using Autoruns.

The issue is already solved.

Either deinstall update KB2670838 or deactivate the thumbnailsystem.

So if this tinkering with autorun programs stops the memory leak on your system I am wondering if you have KB2670838 on your system (is also part of IE10) and a 3d-mp4 and can see the thumbnail instead of the media icon for this file.

--

If you expierience a "slow" system with an 8-core and 32 gig ram in a way that tinkering with autostart programs gives you a "faster" system, I strongly suggest buying a ssd.

I transcode Mediafiles (uses all cpu it can get) while recording several tv streams (heavy load on i/o, for the data hdd) and my office expierience is not impaired. No little lags or stutters or what else gives the feeling of a "slow" system. This is on a quadcore with "only"  7 gig + 1 gig for the onChip graphic with os and all non-data on a ssd.