dllhost.exe crash / com surrogate

hepek said:

Hi everybody i had the same problem and fixed it on this way. control panel won't start because 2 things in my case neroburnrights and adobeversioncue. i fixed it by simply removing icons from control panel. it's not complicated.
1. if you have nero go to nero burnrghts folder (probably located in somewhere like this C:\Program Files (x86)\Nero\Nero 9\Nero BurnRights), then find NeroBurnRights_cpl.cpl and rename it to NeroBurnRights_cpl.nocpl or something like that
2. if you have adobe collection go to probably same folder like me C:\Program Files (x86)\Common Files\Adobe\Adobe Version Cue CS4\Server\bin and rename VersionCueCS4.cpl to VersionCueCS4.nocpl

that fixed my problem and i hope that will fix your also. if this doesn't help, maybe you have something else installed that integrates in cp. simply rename it's cpl.
cheers

Click to expand...

thanks, when people were going on about the .cpl file beign to blame i couldnt find it anywhere, thanks for finding it for me

I just went to add/remove programs for CS4 and uninstalled just VersionCue and that fixed the problem immediately with no restart or anything. I left all other CS4 apps intact.

Version Cue

i just did uninstall the Adobe Version Cue and it worked fine here, you can try it.

Hey guys i just came across this error, can someone please help me:
Faulting Application Path: D:\Windows\System32\dllhost.exe

Problem signature
Problem Event Name: APPCRASH
Application Name: DllHost.exe
Application Version: 6.1.7000.0
Application Timestamp: 49431fe1
Fault Module Name: StackHash_dc55
Fault Module Version: 6.1.7000.0
Fault Module Timestamp: 49433e67
Exception Code: c0000374
Exception Offset: 000c0853
OS Version: 6.1.7000.2.0.0.256.1
Locale ID: 2057
Additional Information 1: dc55
Additional Information 2: b618d5a4cec788acaa11d8c1d97b5229
Additional Information 3: 1b12
Additional Information 4: b011936cb2244890599b515a8b684172

Extra information about the problem
Bucket ID: 1197193871

Basically it only happens when i do this:

Ive recorded some videos using Camtasia Studio 6 once i come close to those files even before i open them i get a window com surragate already causing problems, most of the times when i open these files, my windows crashes and has to restart.

Anyway to fix this?

A Quick Fix but not sure why it happens.

I been using Windows 7 x32 Home 7600 (RTM) for some time now but recently since the release on 10.22.09 i been getting this same error. i have found a way to make it stop appearing but I'm still not sure why it appears in the first place.

Step 1) Start --> Computer --> right click and go to Properties
Step 2) Click on Advanced System Setting in the left task pane
Step 3) Click on the Advanced Tab and under performance click on Settings
Step 4) Click on the Data Exclusion Prevention Tab
Step 5) Turn on DEP for all programs and services except those i select
Step 6) Click ADD and go to C:Windows/System32/dllhost.exe
Step 7) Now you should see Com Surrogate in the window and click OK

Now Restart your PC and you never see the error message again. I also want to restate that this will remove the error message from appearing but I'm sill not sure why this error message appears.

Hopefully this help.

FROST99

frost99 said:

I been using Windows 7 x32 Home 7600 (RTM) for some time now but recently since the release on 10.22.09 i been getting this same error. i have found a way to make it stop appearing but I'm still not sure why it appears in the first place.

Step 1) Start --> Computer --> right click and go to Properties
Step 2) Click on Advanced System Setting in the left task pane
Step 3) Click on the Advanced Tab and under performance click on Settings
Step 4) Click on the Data Exclusion Prevention Tab
Step 5) Turn on DEP for all programs and services except those i select
Step 6) Click ADD and go to C:Windows/System32/dllhost.exe
Step 7) Now you should see Com Surrogate in the window and click OK

Now Restart your PC and you never see the error message again. I also want to restate that this will remove the error message from appearing but I'm sill not sure why this error message appears.

Hopefully this help.

FROST99

Click to expand...

This is "killing the messenger", not that I blame you for wanting a computing experience without crashes.

DEP is one way to detect and prevent a class of malware attack which would seek to gain control of your machine, at least to an extent. Think of it as a way to detect trial-and-error behaviour in code, perhaps analogous to lock picking. You jiggle the pick this way a bit, then that way... and if you know what you're doing sometimes the lock goes 'click' and opens.

DEP is like a lock-picking detection mechanism for the software lock. Kinda. If it detects that an attempt is being made to do things perceived as experimental, the attempt is caught and flagged in the manner configured.

As the name implies, the DLLHost process is a container for so-called "COM" DLLs whose purposes are many and varied. There is an absolute crudload of software in the form of COM DLLs, some "of the OS", but a lot of it 3rd-party. Apparently, with DEP enabled, one of those COM DLLs on your machine sometimes does things which are a little bit avant garde and experimental, in terms of code execution.

That generally means one of two things:

1) Your machine has been pwned by malware and DEP is catching attempts to pwn you even more.

2) The COM DLL in that DLLHost is just buggy, to the point where something it's doing just looks experimental and amateurish.

Assuming a deep anti-malware scan gives you the all-clear, you're probably in the second category.

I'm running Windows 7 pre-release (yeah I know I should buy the real thing) ... 32bit. I recently installed Adobe Premiere and PhotoShop Elements 8, and immediately began having the problem described above. So I went looking in the Services for anything related to these installs and found one called "Adobe Active File Manager" ... the Adobe organizer uses this. I switched the Service to a Manual start option and the problem no longer occurs.

So this I feel identifies the problem and provides a work around. Adobe need to fix this as a complete solution. Hope this helps.

I know this thread is old, but apparently the "com surrogate" is still very much a pain. I have to crash it (sometimes twice) to open images in Photoshop CS3 or even to print. Nero is not on this pc and the com surrogate doesn't eat ram or hog the cpu.

is the only way to resolve this to disable dep like in this thread?

my solution

hi,

i had the same problem,

com surrogate crashed every time i was looking to my pictures. Windows 7 x64 photo viewer crashed all time.
I was unable to even restart my machine.
The solution i found was in Kaspersky forums. KIS 2011 caused to com surrogate "dllhost.exe" to crash.

I had to exclude com surrogate from being wathed by application monitor in KIS settings.

if you think your problem is related to kaspersky internet security

here's a link to the forum,

you might have a solution here,

i had minde

Yet another reason to avoid Kaspersky...

sorry,

KIS 2011 Photo Viewer COM Surrogate bug - Kaspersky Lab Forum

Com Surrogate

Had same problem on my pc. I had uninstalled WMP and IE 8 from the outset and installed Firefox and VLC, but everytime I opened a image file in Windows Image Viewer, pc crashed with com surrogate error and even when I went to Task Manager to kill the process "dllhost.exe" the process would not shut down. And since I had not installed Nero or any other codecs, I was a bit baffled.

I have now installed Ifranview and use that instead of Windows Image Viewer.

I am running Kaspersky 2011, which is causing this fault. A quick check on Kaspersky forums state that the hotfix is in Beta testing at the moment.

Maybe one day, all things being fair, software manufacturers will carry out proper testing before releasing their software. OPPPS!!! a squadron of flying pigs just past overhead. :sarc:

But hey let's be fair, I was using AVG Pro, and that was constantly hogging the CPU, which made trying to work on computer impossible; and Symantec just kept switching itself off and the only way I could get it back on was to uninstall it and re-install.