This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
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.
Fix
"MS are aware of problems with certain chipset/driver combinations and the KB2670838 update
They are also aware of problems with the IE10 install
They are working on both issues, and will update as and when they are satisfied that they have solved the problems.
The recommendation in the meantime is that if the update doesn't install first time, make sure it's uninstalled, and then hide it - Windows Update will unhide it when it is updated."
So Uninstall IE10 and KB2670838 update, hide them from auto updating when thy pop back up to be updated the problem should be fixed.
Proof that MS knows that IE10 has problems on some hardware platforms is here.
http://technet.microsoft.com/en-us/ie/jj898509.aspx
Hope this helps Every One.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
This has been around, unfixed by Microsoft for years.
It's never been related to a virus or malware in the past. But the evildoers could be at work.
3D content was the cause of mine... as MS's thumbnail creator got hung up. The permanent solution for me was to uninstall then re-install all versions of .NET.
What's the logic? None that I can see, but along the way, the memory leak disappeared.
Good luck.
The KB2670838 is a Windows Update. Not a program. So search for it in your Windows Update History log.
When I removed the update, the leak disappeared. But KB2670838 seems to be required for Internet Explorer updates in some computers.
Thanks DavisLiu999. I created a new account, the dllhost.exe still pops up but so far, only one popped and and it hasn't reoccurred since I killed. I've been reading a lot of threads and the one that scares me stated that this virus (if that's what it is) copies key strokes. I can't remember who reported that occurrence. Thanks again!
Thanks David.Lum... I can't seem to locate this update. I'll try again. Thanks again!
The KB2670838 is a Windows Update. Not a program. So search for it in your Windows Update History log.
When I removed the update, the leak disappeared. But KB2670838 seems to be required for Internet Explorer updates in some computers.
Ok so I both removed KB2670838 and installed Media Preview. I also put the killdllhost script into my Startup folder.
The killdllhost script gives me errors at Line 3, something about it can't get the object called 'GetObject'.
Upon doing this it set me to a different version of Internet Explorer, which is fine because I am switching to Chrome.
Initially, doing all of this didn't work. As it is I just had to manually kill a few of the COM Surrogates that show up...although it doesn't seem like they're coming back.
As I type this, a Surrogate shows up currently at 8,600K which isn't going away on its own - this means the killdll script isn't working. As I type this sentence - another shows up for 28K.
Something is definitely not right here....if implementing all 3 of the major fixes on this thread aren't working...then what will?
I would also like to indicate that I am now unable to run a simple game (Hearthstone) since I made these changes, as the Battle.net Update Agent is repeating itself in Task Mgr like dllhost is. For some reason I am also unable to use System Restore to go to a point before all of this started happening...
It is becoming very irritating.
