dllhost.exe High CPU Usage (Ole32.dll)

Hello!

Recently, I have been experiencing high CPU usage by DLLHost, and I am unaware of how to fix it.

I think I may know why it's been happening, and let me explain:

I was exporting sound files for my DJ program via Audacity, and I accidentally opened the file in the DJ program before it was finished exporting, hence, corrupted file. Now whenever I use Windows Explorer (probably 90% of the time), it lags behind until I close out either Windows Media Player or dllhost.exe, but sometimes explorer.exe does the same CPU usage.

Anyway, here's the stuff I've tried:

1. Reinstalled Audacity.
2. SFC /SCANNOW returned that all files were good.
3. Scanned for Malware and Viruses via Malwarebytes and MSE, nothing detected.
4. Rebooted my computer multiple times.
5. ProcessExplorer*

*About ProcessExplorer:
When I use ProcessExplorer to try and find out the problem, which means going to the properties of Dllhost.exe and clicking Threads, the one with the most Cycles Delta and CPU usage is ole32.dll!ObjectStublessClient24+0x18d8 and the stack lists:

Code:

ntoskrnl.exe!KeWaitForMultipleObjects+0xc0a
ntoskrnl.exe!KeAcquireSpinLockAtDpcLevel+0x732
ntoskrnl.exe!KeWaitForSingleObject+0x19f
ntoskrnl.exe!_misaligned_access+0xba4
ntoskrnl.exe!_misaligned_access+0x1821
ntoskrnl.exe!KiCheckForKernelApcDelivery+0x25
ntoskrnl.exe!ObReferenceObjectByHandleWithTag+0x3ce
ntoskrnl.exe!NtReadFile+0x7e
ntoskrnl.exe!KeSynchronizeExecution+0x3a23
ntdll.dll!NtReadFile+0xa
KERNELBASE.dll!ReadFile+0x7a
kernel32.dll!ReadFile+0x59
SHLWAPI.dll!StrCmpNIA+0x46f
mf.dll!MFCreateUrlmonSchemePlugin+0x45ebb
mf.dll!MFCreateUrlmonSchemePlugin+0x46030
mf.dll!MFCreateUrlmonSchemePlugin+0x46172
mf.dll!MFCreateSourceResolver+0x11253
SHELL32.dll!DriveType+0xf63
SHELL32.dll!Ordinal902+0x1882
SHELL32.dll!DriveType+0xe0a
SHELL32.dll!Ordinal902+0x1995
SHELL32.dll!DriveType+0xcc9
SHELL32.dll!Ordinal241+0x21dc
SHELL32.dll!Ordinal241+0x1fb1
SHELL32.dll!DriveType+0x3a72
SHELL32.dll!Ordinal902+0x137a
SHELL32.dll!Ordinal902+0x1494
SHELL32.dll!Ordinal684+0x37280
RPCRT4.dll!RpcBindingSetAuthInfoW+0xe5
RPCRT4.dll!Ndr64AsyncServerCallAll+0x120e
RPCRT4.dll!NdrStubCall3+0xc6
ole32.dll!CoGetInstanceFromFile+0x4cd3
ole32.dll!CoGetInstanceFromFile+0x511d
ole32.dll!CoGetInstanceFromFile+0x5093
ole32.dll!CoSetState+0x1450
ole32.dll!GetErrorInfo+0x599
ole32.dll!CoGetInstanceFromFile+0x78ce
ole32.dll!CoGetInstanceFromFile+0x567b
ole32.dll!CoGetInstanceFromFile+0x7992
ole32.dll!GetErrorInfo+0x475
ole32.dll!GetErrorInfo+0x21e
USER32.dll!TranslateMessageEx+0x2a1
USER32.dll!TranslateMessage+0x1ea
ole32.dll!GetErrorInfo+0xf3
ole32.dll!CoUnloadingWOW+0x117
ole32.dll!ObjectStublessClient24+0x1876
ole32.dll!ObjectStublessClient24+0x18f2
kernel32.dll!BaseThreadInitThunk+0xd
ntdll.dll!RtlUserThreadStart+0x21

and I'm not sure what the problem lays on.

If anyone can help me with this, that would be great. Thanks in advance.

having multiple dllhost.exe instances in taskmanager is a classic symptom of a Poweliks infection....(unsure if this is what you were seeing, or if you only had some sort of corruption)

Norton's Poweliks tool... Trojan.Poweliks Removal Tool | Symantec

The problem is still going on for me, and it's giving me headaches. My computer's CPU usage is going off the charts randomly. I even installed Windows 7 on an SSD for the sake of fixing it, but the problem came back. explorer.exe still uses 50% of CPU at times, and so does dllhost and windows media player. Does anyone have any idea what the problem is here? I can provide logs, anything if you ask.

mdd1963 said:

having multiple dllhost.exe instances in taskmanager is a classic symptom of a Poweliks infection....(unsure if this is what you were seeing, or if you only had some sort of corruption)

Norton's Poweliks tool... Trojan.Poweliks Removal Tool | Symantec

Also, I ran that tool a while back and it didn't detect anything wrong.

Try a clean startup and see if it helps Troubleshoot Application Conflicts by Performing a Clean Startup

Same problem on 2 OS installations - either hardware (fault or configuration) or some program/driver you used on both

Try CMOS clear/load optimized defaults in BIOS.