Start10 is adding 25% cpu usage with every search

from Stardock Forums

I boot my PC. CPU load is minimum (~5%). I open start10 and enter any search - explorer.exe starts consuming 25% of cpu. If I close search and go back to desktop and then input something into search bar - another 25% is added to CPU usage. If I do this 4 times, my cpu usage is 100%.

If I use ctrl+windows key to open standard Microsoft start menu and search using this - explorer.exe is fine. It jumps for a second and then it is quiet.

Only remedy for start10 cpu usage is to wait few minutes or restart explorer.exe - usage drops back to minimum fast.

I am using windows 10 1809 with latest updates and start 10 v1.71.

This problem appeared recently (I noticed it yesterday but I wasn't using my pc too much for last few days). I tried uninstalling all updates from last few days until I've reached update kb4509095 which is impossible to uninstall. It is called "Servicing stack update" so maybe it broke something with search. I tried to reinstall start 10. It said something about rebuilding control panel index, I clicked "yes" and nothing happened, so I do not know if program rebuilt that.

It is really annoying issue because it is making my ultrabook really loud and power-consuming (all 4 cores jump to max boost, fan starts spinning like crazy etc).

My opinion - something is wrong with search implementation after windows updates. Like it does not stop after I close menu or something? And if I open menu again it starts another search instead of terminating previous one?

I am of course searching only locally with cortana search disabled.

 

27,575 views 14 replies
Reply #1 from Stardock Forums Top

Hello,
Sorry to hear you are having issues. I don't see this problem on my system. But I am currently on Windows V1903. You can try to update yours to V1903. or try the purge and reinstall steps : https://forums.stardock.com/486022/start10-support-faq#reinstalling

Just make sure to re-download the latest version from your account. Reinstall it. Reboot and retest. Report back here.

Thanks

Basj,
Stardock Community Assistant.

Reply #2 from Stardock Forums Top

It did not help at all. I gues I'll have to wait until my manufacturer releases 1903 for me. I do not want to force install it.

Lastest windows update must have ruined it. It is not stardock fault. It is microsoft fault. I tried rebuilding windows index and disabling windows search but it did nothing. Troubleshooter says there are some problems with windows search catalog privileges.

Curtains - Customize Windows with additional styles
Reply #3 from Stardock Forums Top

Ok, do report back if you still have the same problem after the v1903 updates.

Thank you,

Basj
Stardock Community Assistant.

Reply #4 from Stardock Forums Top

I updated win 10 to 1903 and it is even worse - every search makes CPU load jump to 30-35%. When I open start menu, input search, close it and do it again 3 times it creates 90% cpu load for 40-70 seconds. This is ridiculous.

I will have to reinstall windows probably.

Btw. Using windows start menu search is still fine – cpu load jumps for 2 seconds, then it drops to minimum. But with start10 my battery will die much faster.

Reply #6 from Stardock Forums Top

I've noticed the same issue recently on Windows 10 1903 (18362.207). Process Explorer shows a new thread in explorer.exe adding CPU cycles rapidly after each search via Start10. Logging off and back on terminates those threads. They also seem to terminate after a while, but that usually takes 15-30 minutes at least.

Start address is usually "ntdll.dll!RtlInitializeResource+0x410".

Here's a sample stack:

ntoskrnl.exe!KeSynchronizeExecution+0x5aa6
ntoskrnl.exe!KeWaitForMutexObject+0x1422
ntoskrnl.exe!KeWaitForMutexObject+0xab4
ntoskrnl.exe!KeWaitForMutexObject+0x255
ntoskrnl.exe!KeGetProcessorNumberFromIndex+0xfc7
ntoskrnl.exe!KeWaitForMutexObject+0x34b8
ntoskrnl.exe!KeSynchronizeExecution+0x30cc
ntdll.dll!NtOpenThreadToken+0x14
KERNELBASE.dll!OpenThreadToken+0xb
windows.storage.dll!SHGetKnownFolderIDList_Internal+0x116
windows.storage.dll!DllGetClassObject+0x1a1c
windows.storage.dll!Ordinal95+0x2a
Windows.Storage.Search.dll!SHCreateAutoListWithID+0x1d393
Windows.Storage.Search.dll!Ordinal2001+0x38a8
Windows.Storage.Search.dll!Ordinal2000+0x1d
Windows.Storage.Search.dll!DllMain+0xded
Windows.Storage.Search.dll!DllGetClassObject+0x59e9
Windows.Storage.Search.dll!SHCreateScopeItemFromShellItem+0xef01
Windows.Storage.Search.dll!SHCreateScopeItemFromShellItem+0xdcdf
Windows.Storage.Search.dll!CreateDefaultProviderResolver+0x34fd
Windows.Storage.Search.dll!CreateDefaultProviderResolver+0x339f
Windows.Storage.Search.dll!CreateDefaultProviderResolver+0x3092
windows.storage.dll!Ordinal791+0x629
windows.storage.dll!Ordinal791+0x42a
shcore.dll!SHTaskPoolQueueTask+0x16e0
shcore.dll!SHTaskPoolQueueTask+0x1368
shcore.dll!GetFeatureEnabledState+0x1923
ntdll.dll!RtlDeleteCriticalSection+0x363
ntdll.dll!RtlInitializeResource+0xce4
KERNEL32.DLL!BaseThreadInitThunk+0x14
ntdll.dll!RtlUserThreadStart+0x21

Thread overview:

Threads in explorer.exe

Reply #7 from Stardock Forums Top

For me, this issue occurs whenever I press just Win and type a search term. If I use Win+S to open a search box, then type a search term, CPU usage remains normal.

Reply #8 from Stardock Forums Top

The following Start10 thread may be related to the issue: Start10_64.dll!Hook+0x7bb80 – there's two of these whenever a search is performed.

Stack 1:

ntoskrnl.exe!KeSynchronizeExecution+0x5aa6
ntoskrnl.exe!KeWaitForMutexObject+0x1422
ntoskrnl.exe!KeWaitForMutexObject+0xab4
ntoskrnl.exe!KeWaitForMutexObject+0x255
ntoskrnl.exe!KeGetProcessorNumberFromIndex+0xfc7
ntoskrnl.exe!KeWaitForMutexObject+0x34b8
ntoskrnl.exe!KeWaitForMutexObject+0x16fa
ntoskrnl.exe!KeWaitForMutexObject+0xab4
ntoskrnl.exe!KeDelayExecutionThread+0x4c0
ntoskrnl.exe!SeReleaseSubjectContext+0x14ef
ntoskrnl.exe!setjmpex+0x7af8
ntdll.dll!ZwDelayExecution+0x14
KERNELBASE.dll!SleepEx+0xa1
Start10_64.dll!NBString2+0x1f36e
Start10_64.dll!NBString2+0x48024
Start10_64.dll!Hook+0x7bb37
Start10_64.dll!Hook+0x7bbf0
KERNEL32.DLL!BaseThreadInitThunk+0x14
ntdll.dll!RtlUserThreadStart+0x21

Stack 2:

ntoskrnl.exe!KeSynchronizeExecution+0x5aa6
ntoskrnl.exe!KeWaitForMutexObject+0x1422
ntoskrnl.exe!KeWaitForMutexObject+0xab4
ntoskrnl.exe!KeWaitForMutexObject+0x255
ntoskrnl.exe!KeGetProcessorNumberFromIndex+0xfc7
ntoskrnl.exe!KeWaitForMutexObject+0x34b8
ntoskrnl.exe!KeWaitForMutexObject+0x16fa
ntoskrnl.exe!KeWaitForMutexObject+0xab4
ntoskrnl.exe!KeWaitForMultipleObjects+0x287
ntoskrnl.exe!ObWaitForMultipleObjects+0x2a9
ntoskrnl.exe!FsRtlCancellableWaitForMultipleObjects+0x215
ntoskrnl.exe!setjmpex+0x7af8
ntdll.dll!NtWaitForMultipleObjects+0x14
KERNELBASE.dll!WaitForMultipleObjectsEx+0x107
KERNELBASE.dll!WaitForMultipleObjects+0xe
Windows.Storage.Search.dll!DllGetClassObject+0xc1a
Windows.Storage.Search.dll!DllGetClassObject+0x8c7
windows.storage.dll!Ordinal923+0x3738
windows.storage.dll!ILFree+0x157e
windows.storage.dll!ILFree+0x13ff
windows.storage.dll!DllMain+0x3529e
windows.storage.dll!Ordinal923+0x1bc3
windows.storage.dll!Ordinal923+0x1891
Windows.Storage.Search.dll!SHCreateAutoListWithID+0x13b4e
Windows.Storage.Search.dll!SHCreateAutoListWithID+0xa92b
windows.storage.dll!DeserializeTextToLink+0xd67
Start10_64.dll!NBString2+0x1b4cc
Start10_64.dll!Hook+0x7bb37
Start10_64.dll!Hook+0x7bbf0
KERNEL32.DLL!BaseThreadInitThunk+0x14
ntdll.dll!RtlUserThreadStart+0x21

Hopefully this helps to narrow down the root cause.

 

Reply #9 from Stardock Forums Top

Hello,

I have forwarded your report to the Stardock support team for their review and recommendations.

Please keep an eye on this thread for any updates.

We really do appreciate your feedback, thanks.

AzDude
Stardock Community Assistant

+1 Loading…
Reply #10 from Stardock Forums Top

Hello,

Sorry to hear you are having trouble.

While I can observer a slight spike on a search, it quickly comes back down when complete:

https://cdn.stardock.us/support/uploads/2019-07-15_14-12-55.mp4

I would like to see if a purge and reinstall helps either of you:

https://forums.stardock.com/486022/start10-support-faq#reinstalling

And a possible reindex:

https://www.tenforums.com/tutorials/58569-rebuild-search-index-windows-10-a.html

Sean Drohan
Stardock Support Manager

Reply #11 from Stardock Forums Top

Rebuilding index did not help. But I found solution: check if C drive has "allow indexing on this drive" enabled. I enabled it - index has grown from 300 to 120 000 entries and now searching is fast and fine - cpu load drops fast. However start 10 is searching in some strange folders but I have "search in different locations" (or something like that) disabled in start10 options.

Update - I rebuilt index after this. Now it has only 20 000 entries (searches only in documents and start menu), searching is longer and creates cpu load for 15-20 seconds. Strange... So I guess I have to add whole C drive to make it fast again.

In my opinion start10 settings are faulty. They search whole drive even if it is disabled in options. Whole drive is not indexed and this creates problems. I tried reducing index to start menu only (<200 elements) but it made whole thing worse. It does not change anything if I check or uncheck "enable search outside standard libraries" it is still searching not only menu start programs but also in my files. Please update start10 to to fix this.

P.S. When I reset index I have some strange catalog added to indexed locations:

When I hoover my mouse over it it says "this item is currently unavailable. Untick it to stop finding items that used to be here". What the hell is this folder?

 

Reply #12 from Stardock Forums Top

Purging and reinstalling Start10 hasn't resolved the issue here. Rebuilding the index hasn't either. Are there specific index locations that should or shouldn't be included?

Here are my current search and index settings:

Search/index

Reply #13 from Stardock Forums Top

I may have fixed this on my system by reverting the index locations to default. In Registry Editor, set SetupCompletedSuccessfully = 0 in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Search and restart your system. This will set the locations to:

Indexing options

CPU usage remains normal so far after pressing Win or Win+S and typing a search term.

Update: Couple hours later, and still no issues. I've added a couple other index locations back to the list without further problems.

Reply #14 from Stardock Forums Top

It was not enough for me. I had to also index all folders on C except for windows folder to make it run decently. It was working even better with whole drive indexed. Start10 keeps searching in "documents" and "files and folders" whatever it means like it was completely ignoring my setting to only search in start menu. It also adds start10ctrlpnl to indexed locations which probably means it indexes control panel.

Maybe it is my language fault and button is not working as it should.