Why does dllhost.exe Com surrogate consumes memory untill crash

Most of the MS API's, .dlls and .exe were left in tact.  I did not stop all start up programs. I chose the ones that I could identfiy easily, such as acro reader updating programs, and MS office project sharing programs that I don't use. Now my system is running perfectly.  

Sorry, but I cannot believe this!

Firstly, I do not use any MS office products, Kaspersky or Adobe reader. So disabling them could not possibly help me.

Sedondly, what kind of advice is this? Randomly and without deeper knowledg disabling automatically started programs?! That is not something that could be reliable reproduced for a specific fix and it is dangerous and can have any number of side effects.

Thirdly, if you really have that kind of hardware, you should be ably to run dozens of preloaders, schedulers and bloatware and not even notice them. With my 7 gigs it took over an hour to notice the memory leak. And even then it was only because there was a short freeze and then an error that I have not enough memory.

If your system was not "running perfectly" before, there is the possibilty that you had malware, that you now have disabled from starting. And maybe you had features on, that reduce the perceived performance. When I first upgraded my old xp system to a ssd, the load time of the navigation bar in my browser took about a second to show suggestions based on my chronic and with the ssd it went down to instantly. Those little waiting times make the perception of a system "slow". But you say you aldread have eliminated this bottleneck. Waiting times for responses over the net might be another source for perceived slowness. Or if you define "fast system" with booting. A ton of schedulers and such to load on boot time would slow down the responsiveness shortly after booting, but no more.

So to summarize: you claim you have KB2670838 on your system, have 3D-mp4 files and could not generate thumbnails for them but can now, because you deactivated MS Office / Adobe preloaders, schedulers and the like? But you cannot link this fix to any specific autostart program you deactivated?

Note: the leak on my system could be "fixed" by renaming my only 3D-mp4 to mkv, because there are no thumbnails generated for mkvs on my system.

Most of the MS API's, .dlls and .exe were left in tact.  I did not stop all start up programs. I chose the ones that I could identfiy easily, such as acro reader updating programs, and MS office project sharing programs that I don't use. Now my system is running perfectly.

I have 2 SLC SSDs, and they're blazing fast.  Try using Autoruns by Sysinternals, disable the start up programs you do not need to start such as MS Office programs.   There were many items in that last that I simply didn't need to run.  

Note:  I have all thumbnails enabled.  All my thumbnails work perfectly, and dllhost.exe stays at bay.  Try it before you knock it.  It's on Filehippo

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.

What You are doing is basically disabling the associated code that dllhost.exe uses to operate securely.

I can just turn off thumbnails and just show icons, but that Is not what I want I want My thumbnail-cache

to work properly without hacking it or loosing system security.

Almost all the MS API's, .dll's, and exe's are in the startup routine for a reason and most of the time it is for security and to bring up Your programs quickly.

Disabling things at random may be a patch for now, but may cause problems later like not being able to further update the OS.

As it is right now an update patch is causing this problem with mostly PC's using AMD/Radion hardware. I believe both parties are now aware of this and I am hopeful it will be fixed on the next IE update or system platform update.

Please be careful what You turn off  and Safe Computing guys.