Windows 10: Very high temporary memory usage when doing right-click Properties

I have an odd problem, and I'm not sure when it started (my system did not used to behave this way). When I do a right click on a file and select properties, it takes about 30 seconds to display the file properties.

Using the Resource Monitor, I see that during this 30 sec., a dllhost.exe process is launched that gradually ramps up to a working set of over 13 GB of memory, then gradually ramps back down, and then finally, the properties window is displayed.

This same odd delay also started happening when I launch WinZip... with the WinZip64.exe doing the same sort of ramp-up/ramp-down of the memory working set. Few other application launches create this delay or exhibit these symptoms. Any guesses as to what might be happening here?

:)

 

very high cpu and memory usage when playing games

very high cpu and memory usage when playing games. I have recently change mobo and cpu.

 

Antimalware Service Executable How To Fix

Antimalware High Memory Usage Please Help I Cant My Games Right When There's Another Program That Keeps Eating My Memory

 

Can you please post a screenshot of the dllhost.exe and it's file properties, the one that absorbs 13 GB of ram?

dllhost is responsible for Component Object Models and handles application queues and process handles among a few things.

This sounds like it may be a corrupted system component.

 

Thanks for your initial assessment, but the sfc /scannow indicates that there are no integrity violations. And the dllhost.exe appears to be properly digitally signed.

 

Very well.

This rules out individual file corruption, can you try to boot into safe mode and see if the right click memory usage overflow occurs when you repeat the same process that causes memory overflow?

Boot to Advanced Startup Options in Windows 10 Windows 10 Installation Upgrade Tutorials

 

I appreciate your help Hydrate.

I rebooted in safe mode (minimalist), and the same symptoms are present. I also discovered that explorer is exhibiting this same behavior when starting up--but this doesn't happen with every application. For example, Chrome starts up without a hitch.

Also, if I do a right click and "Properties" on My Computer, it does not exhibit this behavior.

A very odd problem indeed... anything else I could look at to try to pin down the culprit?

Tnx,
Mark

 

I want to run a preliminary scan on your system before we proceed to working on it. Log in to your regular system and :

Open PowerShell and Run As Admin:

Code: sfc /scannow & Dism /Online /Cleanup-Image /CheckHealth & Dism /Online /Cleanup-Image /ScanHealth & Dism /Online /Cleanup-Image /RestoreHealth[/quote] Now post the results and see if the issue persists in normal mode.

 

I ran the ps commands... same results. I also did a pretty thorough disk cleaning and tidied up some directories with huge numbers of files in it, thinking that might be a cause.

Didn't fix it--same results. I'm trying to see if there's any other disk/network activity accompanying the ramping up of RAM usage, but I don't see anything out of the ordinary there... maybe I can focus in on the threads when I open WinZip to see what's going on... I don't know what else to look for. Are there any log files that might tell me what's going on?

 

I used procexp to try to find out a bit more about what is going on.

When WinZip is starting up, it looks like the following thread is the one chewing up all of the CPU:

clr.dll!GetPrivateContextsPerfCounters+ox10af0

When I'm doing a right-mouse properties activity, it looks like the following thread is the culprit:

shell32.dll!SHGetItemFromObject+0xae0

Here's a stack dump from that thread:

ntdll.dll!RtlGetCurrentServiceSessionId+0x44a3
ntdll.dll!RtlGetCurrentServiceSessionId+0x3944
ntdll.dll!RtlGetCurrentServiceSessionId+0x239a
ntdll.dll!RtlFreeHeap+0x41d
ntdll.dll!RtlQueryHeapInformation+0x17db
ntdll.dll!RtlQueryHeapInformation+0x1767
ntdll.dll!RtlFreeHeap+0x373
tishell64.dll!DllGetClassObject+0x1a7b4
tishell64.dll!DllGetClassObject+0xdf8f
tishell64.dll!ProcessTibUrl+0x22e79
tishell64.dll!ProcessTibUrl+0x236d9
tishell64.dll!ProcessTibUrl+0x2364e
tishell64.dll+0x1cd86
tishell64.dll+0x1db88
combase.dll!CoGetClassObject+0x3e44
combase.dll!CoGetStandardMarshal+0xa6fd
combase.dll!CoGetClassObject+0x44e1
combase.dll!CoGetClassObject+0x34c2
combase.dll!CoGetClassObject+0x3560
combase.dll!CoGetClassObject+0x36b3
combase.dll!CoGetClassObject+0x38bb
combase.dll!CoGetStandardMarshal+0xa73b
combase.dll!Ordinal153+0x4d2a
combase.dll!CoGetStandardMarshal+0xa707
combase.dll!RoActivateInstance+0x884d
combase.dll!RoActivateInstance+0x90ab
combase.dll!CoCreateInstance+0xc3
shell32.dll!SHELL32_LookupBackIconIndex+0x2942
shell32.dll!SHELL32_IconOverlayManagerInit+0x217f
shell32.dll!SHELL32_IconOverlayManagerInit+0x1ed0
shell32.dll!SHELL32_IconOverlayManagerInit+0xe33
shell32.dll!SHELL32_IconOverlayManagerInit+0x14df
shell32.dll!SHELL32_IconOverlayManagerInit+0x1001
shell32.dll!SHELL32_IconOverlayManagerInit+0x88
windows.storage.dll!NeverProvidedByJunction+0x16a58
windows.storage.dll!NeverProvidedByJunction+0xe87b
windows.storage.dll!NeverProvidedByJunction+0x1c6d
shell32.dll!StrStrW+0x74382
shell32.dll!SHGetFileInfoW+0x169
shell32.dll!Ordinal888+0xdec
shell32.dll!SHOpenPropSheetW+0x47c
shell32.dll!Ordinal888+0x912
shell32.dll!Ordinal888+0x522
shell32.dll!SHGetItemFromObject+0x1a5e
shell32.dll!SHGetItemFromObject+0x1436
shell32.dll!SHGetItemFromObject+0xae9
KERNEL32.DLL!BaseThreadInitThunk+0x14
ntdll.dll!RtlUserThreadStart+0x21

This doesn't seem to be going in a direction I have the skills to deal with...

 

This seems to be connected to an issue from MP4 thumbnail previews, causing dllhost.exe to amp its memory usage from a loop.

Please enter PowerShell once more and uninstall this update if it's available - first close all application and save your work, this will restart the box once its complete:

Code: wusa.exe /uninstall /kb:2670838 /quiet /forcerestart[/quote] Test dllhost.exe and see if it still persists.

If the update is not available, please let me know and we will proceed to another option.

 

Thanks for the suggestion, Hydrate. I followed your suggestion and still no luck.

I tried a couple of other things too. I disabled thumbnail view, and the problem persisted. I tried creating a new user account. When I log into the new user account, everything works fine... no problem--so it doesn't seem like it's a system-rooted problem. I looked at some of the log files too, but again, I'm kind of lost in knowing what to look for and how to interpret it.

 

Let me clarify, in a new user account, the dllhost.exe issue does not exist?

 

After trying a number of things over the past few weeks, I finally did something that solved it... the fix was one of these three things, but I'm not sure which:

Uninstalled Acronis 2017 (I'll reinstall it and see if the problem returns)
Updated Visual Studio Community 2017
Ran subinacl.msi to reset proper ACLs on system folders

Wow... tricky one to solve!

 

Wow, well, if we can get specifics let us know about this issue further, most likely an issue with ACLs.