new created VM server keep stop running daily

Hello @Stephen Stephens,

Thank You for using Q & A forum.

In Azure, if your virtual machine (VM) is frequently going into an off status after running for a few hours and you are seeing kernel crash errors in the event viewer, it may indicate that the VM is experiencing internal issues or hardware-related problems. These issues can lead to VM crashes or restarts. Specifically, kernel crashes can occur due to various reasons, such as bugs in the guest operating system, resource exhaustion, or hardware failures.

To diagnose the cause of the kernel crashes, you should check the system and application logs for more details. Additionally, collecting a memory dump can help identify the root cause of the crashes. If the problem persists, consider reaching out to Azure support for further assistance in diagnosing and resolving the issue.

If this answers your query, do click Accept Answer and Up-Vote for the same. And, if you have any further query do let us know.

Dear @Stephen Stephens

One of the most common causes of a VM consistently stopping after a similar runtime period is an Auto-shutdown configuration applied to the virtual machine. First check the Auto-shutdown settings in the Azure portal under Virtual Machine → Operations → Auto-shutdown to verify whether a scheduled shutdown has been configured.

In addition, please review the VM's Activity Log in Azure, as it records all management operations performed against the resource and can help determine whether the shutdown was initiated by a user, automation process, policy, or another Azure service. If no scheduled or external shutdown activity is identified, the kernel crash events observed in Windows Event Viewer should be investigated further, as they may indicate an operating system, driver, or application-level issue causing the VM to shut down unexpectedly.

Hello Stephen Stephens

Based on the information shared, the VM enters a stopped state after approximately 7-8 hours of uptime. Event Viewer indicates a kernel crash event; however, additional investigation is required to determine whether the shutdown is related to a guest OS event, an Azure platform event, or an automated operation.

1. Confirm what is stopping the VM (Azure-side)

Even if a kernel crash is visible inside the guest OS, it is important to verify whether Azure recorded a stop, restart, or deallocation event.

Azure Portal → Virtual Machine → Activity Log

Look for events around the time the VM turns off each day:

• Start / Stop / Deallocate operations
• Automation / Runbook activity
• Policy actions
• Platform-initiated maintenance or restart events

If the Activity Log shows the VM was stopped or deallocated by an authorized user, policy, or automation process, this information can help identify the source of the shutdown.

2. Review scheduled automation and provisioning state

If Azure Automation, Logic Apps, Event Grid, or other automation solutions are being used to manage the VM lifecycle, review the associated schedules and execution history.

Verify:

• Service Principal or Managed Identity permissions
• VM provisioning state during execution
• Schedule conflicts or workflow logic issues

Compare shutdown timestamps with automation job history and Activity Log entries.

3.Review guest operating system logs

Since a kernel crash event is present in Event Viewer, review logs generated around the shutdown timeframe, including:

• Event Viewer / Syslog entries
• Scheduled jobs, updates, monitoring agents, or recurring workloads
• Resource utilization such as CPU, memory, and disk activity

Correlating these events with the VM shutdown time may provide additional context regarding the kernel crash event.

4. Review Resource Health diagnostics

Check:

Virtual Machine → Resource Health

Review any platform-reported health events recorded during the timeframe of the issue. Resource Health can help determine whether Azure detected an infrastructure-related event affecting the VM.

Also review:

Azure Monitor → Metrics / Diagnostics

• CPU
• Memory
• Disk I/O
• Heartbeat

Correlate the metrics with the reported shutdown time.

5. Validate configured start/stop schedules

If Auto-shutdown or scheduled VM management configurations are enabled, validate the configuration and schedule settings to rule out expected shutdown actions.

6. If the issue is persistent and appears platform-related

If Resource Health shows recurring platform-related events affecting the VM, consider the following actions:

• Redeploy the VM to move it to a new Azure host while retaining the VM configuration and associated resources where applicable. This can help determine whether the issue is related to the underlying host infrastructure. Can you please update us if the action plan provided was helpful? Should there be any follow-up questions or concerns, please let us know and we shall try to address them. If these answer your question, click "Upvote" which may be beneficial to other community members reading this thread.