random cpu and hard disk usage spikes

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • maxim123
    PCHF Member
    • Aug 2017
    • 472

    #1

    🟢 Awaiting Response random cpu and hard disk usage spikes

    Hi, I have been getting random cpu and hard disk usage spikes. I know that it is sometimes due to windows updates, but I don't know why it spikes other times. Just to be sure, I would like to know if my laptop system is safe or not, and would like advice on how to determine that. Thank you.
  • xrobwx71
    PCHF Administrator
    • Mar 2023
    • 1066

    #2
    What have you done to diagnose so far?

    Comment


    • maxim123
      maxim123 commented
      Editing a comment
      I have checked with malwarebytes and windows defender, both found no issues.
  • jmarket
    PCHF Owner
    • Jan 2015
    • 7695
    • CachyOS
    • Intel Arc A770 (16 GB)

    #3
    Random CPU and disk spikes are fairly common on Windows systems — but it’s smart that you’re checking into it, especially since you’ve already ruled out malware with Malwarebytes and Windows Defender.

    Here are a few things you can do to pinpoint what’s causing the spikes and ensure your system is safe:
    1. Use Task Manager or Resource Monitor
      Open Task Manager (
      Code:
      Ctrl + Shift + Esc
      ) and go to the Processes tab.
      Sort by CPU and Disk usage to see what’s using the most resources when a spike happens.
      You can also open Resource Monitor by typing
      Code:
      resmon
      in Start.
    2. Check Windows Update and Background Services
      Sometimes Windows will run indexing, telemetry, or update services in the background.
      In Task Manager, check for processes like
      Code:
      Windows Modules Installer Worker
      or
      Code:
      svchost.exe
      hosting Windows Update.
    3. Scan with an Additional Tool (Optional)
      You can run a second opinion scan using Emsisoft Emergency Kit or Kaspersky Virus Removal Tool — both are free and portable.
    4. Check Startup Apps
      In Task Manager → Startup tab, disable unnecessary apps that start with Windows.
      Too many background programs can cause periodic usage spikes.
    5. Review Event Viewer Logs
      Type
      Code:
      eventvwr
      in Start and look under Windows Logs → System for recurring warnings or errors that coincide with the spikes.


    If you can, post a screenshot of your Task Manager → Processes tab during one of these spikes — that will help us identify the culprit more precisely. 👍

    — PCHF Malware Response Team

    Comment

    • maxim123
      PCHF Member
      • Aug 2017
      • 472

      #4
      Originally posted by jmarket

      If you can, post a screenshot of your Task Manager → Processes tab during one of these spikes — that will help us identify the culprit more precisely. 👍

      — PCHF Malware Response Team

      Thank you. I will report back when I see the spikes, usually what happens is the spikes don't last long. The spikes happen and go away immediately, I have checked my processes during those moments and everything is usually normal (or I can't remember a high usage.).
      I checked with emisoft and it shows no detection for both quick scan and malware scan.
      Attached is how the spike is like in my system. Happens and then stays calm immediately.
      Attached Files
      Last edited by maxim123; 10-29-2025, 04:31 AM.

      Comment

      • maxim123
        PCHF Member
        • Aug 2017
        • 472

        #5
        Hi, just reporting back. I have been away from my laptop these few days, so I wasn't able to check properly. am home now, and will be noticing any spikes while I use it.

        Comment

        • maxim123
          PCHF Member
          • Aug 2017
          • 472

          #6
          Click image for larger version

Name:	image.png
Views:	0
Size:	554.2 KB
ID:	205554

          Click image for larger version

Name:	image.png
Views:	0
Size:	452.3 KB
ID:	205552

          there was no warning in event viewer at that time. this was right after I closed league of legend game and went into its client.
          Attached Files

          Comment

          • maxim123
            PCHF Member
            • Aug 2017
            • 472

            #7
            Just opened laptop today and saw an issue. the whole screen was gray after the windows booted. The mouse cursor showed, so I opened task manager, and in a while, the desktop loaded.

            Comment

            • jmarket
              PCHF Owner
              • Jan 2015
              • 7695
              • CachyOS
              • Intel Arc A770 (16 GB)

              #8
              Originally posted by maxim123
              Just opened laptop today and saw an issue. the whole screen was gray after the windows booted. The mouse cursor showed, so I opened task manager, and in a while, the desktop loaded.
              It sounds like your system was slow to load the desktop environment after startup. When Windows shows only a gray or blank screen with a mouse cursor, it typically means the Windows Explorer process was delayed or temporarily hung during boot.

              Here are a few things to check:
              1. Check for Startup App Delays
                Open Task Manager (
                Code:
                Ctrl + Shift + Esc
                ) → go to the Startup tab and disable unnecessary programs.
                Too many startup apps can delay Explorer and cause a temporary gray or black screen before the desktop appears.
              2. Restart Windows Explorer Manually
                If it happens again, press
                Code:
                Ctrl + Shift + Esc
                , find Windows Explorer under the Processes tab, right-click it, and select Restart.
                If the desktop appears right after that, it confirms Explorer was hanging.
              3. Check for Corrupted Files
                Run the following in an elevated Command Prompt:
                Code:
                sfc /scannow
                and then:
                Code:
                DISM /Online /Cleanup-Image /RestoreHealth
                These commands repair missing or corrupted system files that could cause slow logins.
              4. Update Display Drivers
                Outdated or partially corrupted display drivers can cause a gray/black screen during initialization.
                Check your laptop manufacturer’s website or use Windows Update to install the latest graphics drivers.
              5. Event Viewer Logs
                Open Event Viewer (
                Code:
                eventvwr
                ) → Windows Logs → System and Application to look for warnings or errors that correspond with the time of the gray screen.


              Once you’ve checked these, let us know what you find — especially if the issue repeats or if you notice slow startup times continuing.

              — PCHF Technical Response Team

              Comment

              • maxim123
                PCHF Member
                • Aug 2017
                • 472

                #9
                I disabled most of the startup apps.
                sfc did find corrupted files and says it has repaired them. running DISM now, it is stuck at 62.3%.

                I updated nvidia earlier and have restarted the system.

                In eventviewer, I did find an error in system subsection of windows logs at the time of the gray screen.

                Click image for larger version  Name:	image.png Views:	0 Size:	341.7 KB ID:	205566
                Attached Files

                Comment

                • jmarket
                  PCHF Owner
                  • Jan 2015
                  • 7695
                  • CachyOS
                  • Intel Arc A770 (16 GB)

                  #10
                  The Event Viewer entry shows:

                  Source: NDIS
                  Event ID: 10317
                  Description: "Miniport Microsoft Wi-Fi Direct Virtual Adapter #2 had event Fatal error: The miniport has failed a power transition to operational power."
                  This error relates to your Wi-Fi adapter’s power management rather than the display or Windows Explorer. It usually occurs when the adapter fails to wake up properly from sleep or hibernation.

                  Here’s what to do next:
                  1. Disable Power Saving for the Network Adapter
                    1. Press
                    Code:
                    Win + X
                    Device Manager.
                    2. Expand Network adapters.
                    3. Right-click your wireless adapter → Properties.
                    4. Under the Power Management tab, uncheck "Allow the computer to turn off this device to save power."
                  2. Update or Reinstall the Network Drivers
                    Visit your laptop manufacturer’s support page and download the latest Wi-Fi driver.
                    If it’s already current, try uninstalling the device from Device Manager and rebooting — Windows will reinstall it automatically.
                  3. Check Fast Startup Settings
                    Fast Startup can sometimes cause device drivers to fail during power transitions.
                    Go to
                    Code:
                    Control Panel → Power Options → Choose what the power buttons do
                    → click "Change settings that are currently unavailable" → uncheck "Turn on fast startup."
                  4. Monitor After These Steps
                    Once you’ve disabled the adapter power saving and checked the driver, reboot and see if the gray screen issue returns.
                    If it doesn’t, the delay was likely caused by the Wi-Fi adapter hanging during initialization at startup.


                  Please let us know if the Event Viewer still logs the same NDIS 10317 error after these changes.

                  — PCHF Technical Response Team

                  Comment


                  • maxim123
                    maxim123 commented
                    Editing a comment
                    thank you. I have done all those steps and will monitor to see if it continues.
                Working...