Share via

Fix system process constant high cpu usage >20% after windows 11 upgrade?

keg415 0 Reputation points
2025-08-19T21:03:32.68+00:00

system process has constant high cpu usage >20% after windows 11 upgrade. Steps taken so far:

  • Update MSI PRO Z690-A DDR4 BIOS E7D25IMS.1M0
  • Disable Realtek Audio driver
  • Set Power Mode = Best Performance
  • Update TP-Link Archer TX401 PCIe 10GbE Network Adapter aqnic650
  • Switching to built-in network interface did not fix
  • Clean install NVIDIA RTX 3060 580.97 driver
  • Switching to integrated GPU did not fix

OK in Safe Mode with NVIDIA GPU and TX401 NIC enabled.

Not OK after clean boot with all startup and non-MS services disabled.

sfc /scannow does not find any integrity violations.

Dism /Online /Cleanup-image /RestoreHealth did not make changes.

Clean install of Windows 11 is not an acceptable solution.

Windows for home | Windows 11 | Performance and system failures
0 comments No comments

6 answers

Sort by: Most helpful
  1. keg415 0 Reputation points
    2025-08-21T21:33:25.6166667+00:00

    Windows Performance Recorder/Analyzer showed high CPU% by aksdf.sys, a component of Sentinel LDK License Manager. ChatGPT found these related drivers:

    • aksdf.sys → Data filter driver
    • akshhl.sys → Hardlock device driver.
    • aksfridge.sys → Freezing protection driver (rare, older).
    • hardlock.sys → Old parallel/USB dongle driver.
    • aksusb.sys → USB filter driver for HASP dongles.
    • akshasp.sys → Core HASP driver.

    Some of these were still being loaded. These commands identified which ones:

    sc query akshhl
    sc query aksfridge
    sc query hardlock
    sc query aksusb
    sc query akshasp
    sc query hasplms
    

    The following commands deleted the active drivers:

    sc delete aksdf
    sc delete aksfridge
    sc delete hardlock
    sc delete hasplms
    

    Also deleted aksdf.sys, aksfridge.sys, and hardlock.sys from C:\Windows\System32\drivers. These files were dated 2014. System process CPU usage now low.

    Was this answer helpful?


  2. Igor Leyko 110.8K Reputation points Independent Advisor
    2025-08-20T20:57:10.8966667+00:00

    Please check if the load decreased after Internet disconnection.

    Was this answer helpful?


  3. Igor Leyko 110.8K Reputation points Independent Advisor
    2025-08-20T09:16:10.9366667+00:00

    Unfortunately, deeper analysis may be done with debugger.

    Let's try a bypass. Check if the problem exists during clean boot.

    https://support.microsoft.com/topic/how-to-perform-a-clean-boot-in-windows-da2f9573-6eec-00ad-2f8a-a97a1807f3dd

    Was this answer helpful?


  4. Igor Leyko 110.8K Reputation points Independent Advisor
    2025-08-19T21:57:33.6866667+00:00

    Hi,

    My name is Igor, it's a pleasure for me to help others and I'll try to help you. I am merely a fellow user trying to provide insight and information that may be helpful to others.

    System process may do some work on behalf of running programs. Please analyze CPU load using Process Explorer. https://learn.microsoft.com/en-us/sysinternals/downloads/process-explorer

    You may save its data to a file and share it to OneDrive for analysis.

    Was this answer helpful?


  5. Kimberly Olaño 23,545 Reputation points
    2025-08-19T21:42:46.8133333+00:00

    Hello! keg415. I'm glad to assist you with this.

    Thanks for the detailed breakdown of what you’ve tried.

    Since the System process (PID 4) is chewing >20% CPU constantly after your Windows 11 upgrade, but runs fine in Safe Mode, we can narrow this down to a kernel-mode driver or low-level service that still loads even in a clean boot.

    Confirm the offending thread in System

    Use Process Explorer (from Microsoft Sysinternals):

    Run as admin, hover over the System process.

    Press Ctrl+D (to show DLLs/drivers) or Ctrl+H (to show handles).

    Then go to View → System Information → CPU and double-click the System process.

    In the Threads tab, sort by CPU.

    Look at the Start Address and Module name. This usually reveals which driver (e.g., ndis.sys, storport.sys, dxgkrnl.sys, acpi.sys, etc.) is eating cycles.

    That’ll tell you whether it’s network, storage, graphics, ACPI, or something else.

    Best regards,

    Kimberly

    Was this answer helpful?


Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.