[SOLVED] DNSCACHE (i.e., dns client: a Windows service) high cpu. FIX: I disabled the Wi-Fi Adapter.

Triple Helix

Microsoft MVP
Contributor
Joined
Feb 3, 2013
Posts
183
Location
Ontario, Canada
Hello,

I have had this issue for a couple of years and I tried many things to try to correct it so I need some help please! Some info I looked at: https://www.tenforums.com/performan...y-high-cpu-usage-service-host-dns-client.html

Redirecting
Read More:
Thanks,
 

Attachments

  • 2023-06-27_19-32-05.jpg
    2023-06-27_19-32-05.jpg
    25.8 KB · Views: 14
  • 2023-06-27_19-32-39.jpg
    2023-06-27_19-32-39.jpg
    57.5 KB · Views: 15
Last edited by a moderator:
Hello @xilolee

May I ask what logs and what tab from Speccy as I have the Pro version. It has nothing to do with Malware if that's what your thinking? And no BSOD or DMP files.

Thanks,

Okay I Manually Dumped the Process!
 

Attachments

To get started, do the following:
  • In the command prompt (admin), type (copy/paste): cleanmgr /sageset:1
    A cleanmgr window will be presented, in which you can choose the items to be deleted. I'd select them all...
    To start the cleanup, you need to launch this other command: cleanmgr /sagerun:1
    And the cleanup will start: wait until it finishes.
  • In the command prompt (admin), type (copy/paste): Dism /Online /Cleanup-Image /CheckHealth
    If the result is No component store corruption detected, then launch this other command: dism /online /cleanup-image /startcomponentcleanup /resetbase
    Otherwise, don't run this second command and let me know the result of the first one.
  • Download and install iobit driver booster free.
    Open it, click tools, click Clean invalid device data, scan, clean, close.
    Use only this function of it.
  • In the command prompt (admin), type (copy/paste): chkdsk c: /scan /perf
    Wait until it finishes.
    If Windows has scanned the file system and found no problems, let me know it.
    Otherwise, post the result.
  • Launch SFC /scannow from an elevated command prompt, wait until it finishes and post its result.
  • Wait a day or two and then tell me if this changed something.
 
I did all you asked but iobit is a PITA with it's extras! :rolleyes:

Microsoft Windows [Version 10.0.19045.3155]
(c) Microsoft Corporation. All rights reserved.

C:\Windows\system32>cleanmgr /sagestet:1

C:\Windows\system32>dism /online /cleanup-image /checkhealth

Deployment Image Servicing and Management tool
Version: 10.0.19041.844

Image Version: 10.0.19045.3155

No component store corruption detected.
The operation completed successfully.

C:\Windows\system32>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection found corrupt files and successfully repaired them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
repairs, details are included in the log file provided by the /OFFLOGFILE flag.

C:\Windows\system32>

C:\Windows\Logs\CBS\CBS.log
 

Attachments

C:\Windows\system32>cleanmgr /sagestet:1

C:\Windows\system32>dism /online /cleanup-image /checkhealth

From the quote, it seems you typed incorrectly sageset.
And that you didn't run the "cleanmgr sagerun" and the "dism startcomponentcleanup" commands.
The cbs log is not necessary given that "WRP found corrupt files and successfully repaired them.".
 
Last edited:
Yes I see I a redid them!

Microsoft Windows [Version 10.0.19045.3155]
(c) Microsoft Corporation. All rights reserved.

C:\Windows\system32>cleanmgr /sageset:1

C:\Windows\system32>cleanmgr /sagerun:1

C:\Windows\system32>dism /online /cleanup-image /checkhealth

Deployment Image Servicing and Management tool
Version: 10.0.19041.844

Image Version: 10.0.19045.3155

No component store corruption detected.
The operation completed successfully.

C:\Windows\system32>dism /online/ cleanup-image /startcomponetcleanup /resetbase

Error: 87

DISM doesn't recognize the command-line option "cleanup-image".
For more information, refer to the help by running DISM.exe /?.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
 

Attachments

  • 2023-07-01_14-13-03.jpg
    2023-07-01_14-13-03.jpg
    30.1 KB · Views: 6
Sorry! :whistle:



Microsoft Windows [Version 10.0.19045.3155]
(c) Microsoft Corporation. All rights reserved.

C:\Windows\system32>dism /online /cleanup-image /startcomponentcleanup /resetbase

Deployment Image Servicing and Management tool
Version: 10.0.19041.844

Image Version: 10.0.19045.3155

[===== 10.0% ]
[==========================100.0%==========================]
The operation completed successfully.

C:\Windows\system32>
 
Here you go! Thanks!

Microsoft Windows [Version 10.0.19045.3155]
(c) Microsoft Corporation. All rights reserved.

C:\Windows\system32>chkdsk c: /scan /perf
The type of the file system is NTFS.
Volume label is Windows 10 Pro for Workstations.

Stage 1: Examining basic file system structure ...
818944 file records processed.
File verification completed.
Phase duration (File record verification): 5.77 seconds.
14111 large file records processed.
Phase duration (Orphan file record recovery): 0.00 milliseconds.
0 bad file records processed.
Phase duration (Bad file record checking): 0.25 milliseconds.

Stage 2: Examining file name linkage ...
371 reparse records processed.
1170726 index entries processed.
Index verification completed.
Phase duration (Index verification): 10.92 seconds.
0 unindexed files scanned.
Phase duration (Orphan reconnection): 2.66 seconds.
0 unindexed files recovered to lost and found.
Phase duration (Orphan recovery to lost and found): 0.32 milliseconds.
371 reparse records processed.
Phase duration (Reparse point and Object ID verification): 5.27 milliseconds.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
Phase duration (Security descriptor verification): 48.36 milliseconds.
175892 data files processed.
Phase duration (Data attribute verification): 1.30 milliseconds.
CHKDSK is verifying Usn Journal...
34567440 USN bytes processed.
Usn Journal verification completed.
Phase duration (USN journal verification): 162.24 milliseconds.

Windows has scanned the file system and found no problems.
No further action is required.

499986431 KB total disk space.
65558204 KB in 332845 files.
216084 KB in 175893 indexes.
0 KB in bad sectors.
940431 KB in use by the system.
65536 KB occupied by the log file.
433271712 KB available on disk.

4096 bytes in each allocation unit.
124996607 total allocation units on disk.
108317928 allocation units available on disk.
Total duration: 19.59 seconds (19596 ms).

C:\Windows\system32>
 
Run the following (unique) command from an elevated command prompt, reboot your machine, then post the result of the Netsh-reset.txt (that should appear) on your desktop (or upload it here):
Warning
If you have set a static IP in internet protocol version 4 (tcp/ipV4) properties of your ethernet/wireless network adapter, you'll have to set it anew, after the reboot.

(netsh interface tcp reset & netsh interface udp reset & netsh winhttp reset proxy & netsh winsock reset & netsh interface ipv4 reset & netsh interface ipv6 reset) > "%userprofile%\desktop\Netsh-reset.txt"

I get:
Read More:
 
Last edited:
Code:
Reset of all TCP parameters OK!
Ok.


Reset of all UDP parameters OK!
Ok.


Current WinHTTP proxy settings:

    Direct access (no proxy server).


Sucessfully reset the Winsock Catalog.
You must restart the computer in order to complete the reset.

Resetting Compartment Forwarding, OK!
Resetting Compartment, OK!
Resetting Control Protocol, OK!
Resetting Echo Sequence Request, OK!
Resetting Global, OK!
Resetting Interface, OK!
Resetting Anycast Address, OK!
Resetting Multicast Address, OK!
Resetting Unicast Address, OK!
Resetting Neighbor, OK!
Resetting Path, OK!
Resetting Potential, OK!
Resetting Prefix Policy, OK!
Resetting Proxy Neighbor, OK!
Resetting Route, OK!
Resetting Site Prefix, OK!
Resetting Subinterface, OK!
Resetting Wakeup Pattern, OK!
Resetting Resolve Neighbor, OK!
Resetting , OK!
Resetting , OK!
Resetting , OK!
Resetting , OK!
Resetting , failed.
Access is denied.

Resetting , OK!
Resetting , OK!
Resetting , OK!
Resetting , OK!
Resetting , OK!
Resetting , OK!
Resetting , OK!
Resetting , OK!
Restart the computer to complete this action.

Resetting Compartment Forwarding, OK!
Resetting Compartment, OK!
Resetting Control Protocol, OK!
Resetting Echo Sequence Request, OK!
Resetting Global, OK!
Resetting Interface, OK!
Resetting Anycast Address, OK!
Resetting Multicast Address, OK!
Resetting Unicast Address, OK!
Resetting Neighbor, OK!
Resetting Path, OK!
Resetting Potential, OK!
Resetting Prefix Policy, OK!
Resetting Proxy Neighbor, OK!
Resetting Route, OK!
Resetting Site Prefix, OK!
Resetting Subinterface, OK!
Resetting Wakeup Pattern, OK!
Resetting Resolve Neighbor, OK!
Resetting , OK!
Resetting , OK!
Resetting , OK!
Resetting , OK!
Resetting , failed.
Access is denied.

Resetting , OK!
Resetting , OK!
Resetting , OK!
Resetting , OK!
Resetting , OK!
Resetting , OK!
Resetting , OK!
Resetting , OK!
Restart the computer to complete this action.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top