Share via

High CPU instances detected on the VM nm-0 in the last 24 hours

Fredi Nonyelu 40 Reputation points
2025-11-25T15:39:03.23+00:00

My VM is not reachable. I restarted and could access for about 1 hour before it became inaccessible again. It says there is Instances of High CPU detected on the VM in last 24 hrs but nothing is running and it is still not reachable.

Azure Virtual Machines
Azure Virtual Machines

An Azure service that is used to provision Windows and Linux virtual machines.


Answer accepted by question author

  1. Jilakara Hemalatha 12,755 Reputation points Microsoft External Staff Moderator
    2025-11-25T22:21:30.2533333+00:00

    Hi Fredi Nonyelu

    Thank you for sharing the details. Based on our analysis we have performed the below checks

    We inspected Boot Diagnostics and accessed the Serial Console. Both tools confirmed that the operating system was healthy, and the VM booted correctly without underlying OS corruption or disk-related issues.

    Upon review, the VM’s provisioning state was "Updating," and an extension was in a "Failed" state. This platform updating or extension failure can temporarily impact VM accessibility until resolved.

    We reviewed Performance Insights and CPU metrics, which showed that CPU utilization was consistently high. This confirms that the current VM size was not sufficient for the workload. Due to this sustained utilization, the VM was under resource pressure, which contributed to the access issue.

    After redeployed and restarted the VM, access was restored after ~20 minutes. Resizing from Standard_D2as_v5 → Standard_D4as_v5 (4 vCPU, 16 GiB) helped stabilize performance and cx able to access the RDP.

    Reference: https://learn.microsoft.com/en-us/azure/virtual-machines/sizes/resize-vm?tabs=portal

    Troubleshoot high-CPU issues on Azure Windows virtual machines

    Best Practices Before Resizing

    To ensure a smooth and safe resize operation, please follow these steps:

    • Create a snapshot of the OS disk as a backup: Go to VM → Disks → Select OS Disk → Create snapshot.
    • Make sure the VM is in a Deallocated state: Stop the VM → Resize → Start the VM again.

    Following these steps helps avoid failures during resizing and ensures you have a recovery option in case anything goes wrong.

    Reference: https://learn.microsoft.com/en-us/azure/virtual-machines/windows/expand-disks

    1 person found this answer helpful.

0 additional answers

Sort by: Most 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.