Blue screen error in azure VM

Question

Blue screen error in azure VM

Aritra Basu 15

I am trying to login to one server and it is showing error in boot diagnostics. Error attached.image.png

Please raise a separate case for troubleshooting and solution for this.

Aritra Basu 15 Reputation points

2026-02-25T03:27:44.06+00:00

Azure Virtual Machine
Aritra Basu 15 Reputation points

2026-02-25T03:28:16.1066667+00:00

Please treat this on priority as it is in production environment.
Ankit Yadav 12,205 Reputation points Microsoft External Staff Moderator

2026-02-25T04:00:53.21+00:00
Hello @Aritra Basu

The blue screen error message indicates that the underlying OS for the VM is not booting properly.

To fix it,

please go to the Azure Portal, select the affected VM, then navigate to Help > Redeploy + Reapply. First, click Re-apply on the VM, and then Redeploy the VM. This process often resolves OS and host issues that can prevent the VM from booting.

Faster way;

If you have a backup of your VM from before the blue screen error, you can restore the VM to that previous state using the backup.

Additionally, please confirm:-

What OS is running on the VM?

Are you able to connect the server/website running inside the VM?
Aritra Basu 15 Reputation points

2026-02-25T04:22:38.7533333+00:00
Windows server 2016 datacenter

No
Aritra Basu 15 Reputation points

2026-02-25T05:24:26.48+00:00

I have tried to reapply then redeploy, whether it was successful but still I am not able to login through serial console, serial console not responding
Aritra Basu 15 Reputation points

2026-02-25T07:10:04.4533333+00:00

Hello Ankit, Could you please raise a case with Microsoft to look into this issue. Please share the link to raise case with Microsoft. It is a business critical machine and we need immediate solution.
Ankit Yadav 12,205 Reputation points Microsoft External Staff Moderator

2026-02-25T16:57:52.56+00:00

Hello @Aritra Basu

I sent you a Private Message regarding this. Please take a look and let me know if you can help.
Navneet Kumar 165 Reputation points

2026-02-25T19:26:02.3733333+00:00

BSOD error: NTFS_FILE_SYSTEM on Windows Server 2016. This usually indicates OS disk corruption.

Steps to fix:

Stop the VM from Azure Portal.

Detach the OS disk:

VM → Disks → Select OS disk → Detach.

Attach the OS disk to a healthy Windows VM as a data disk.

On the healthy VM, open Command Prompt as Administrator and run:

chkdsk X: /f /r

(Replace X with the drive letter of the attached disk.)

After it completes, run:

sfc /scannow /offbootdir=X:\ /offwindir=X:\Windows

Detach the disk from the healthy VM.

Reattach it back to the original VM as OS disk.

Start the VM.

In most cases, chkdsk fixes the NTFS_FILE_SYSTEM blue screen.
Ankit Yadav 12,205 Reputation points Microsoft External Staff Moderator

2026-02-27T07:55:22.39+00:00

Hello @Aritra Basu, Just checking in if you are still blocked with the issue, if yes, kindly review the Private Message and share the required details for us to help you out further.
Kwikiriza Tevin 0 Reputation points

2026-03-04T03:44:23.1933333+00:00
From Boot Diagnostics → Screenshot, identify:

STOP Code (e.g., INACCESSIBLE_BOOT_DEVICE, CRITICAL_PROCESS_DIED)

Any driver file mentioned (e.g., ntfs.sys, vhdmp.sys)

This determines the root cause.

Step 2: Attempt Azure Serial Console (Recommended)

Go to VM → Help → Serial Console

Enable if not already enabled

Attempt:

Safe Mode boot

Recovery options

If accessible:

sfc /scannow

Step 3: Use Azure “Repair VM” Feature (Most Effective)

In the Azure Portal:

Go to Virtual Machine

Select Support + Troubleshooting

Click Repair

This creates a repair VM and attaches the OS disk for offline repair.

Inside the Repair VM:

Mount the OS disk (usually as D: or E:)

Run:

chkdsk D: /f /r

If boot corruption suspected:

bootrec /fixmbr

Step 4: Check for Recent Changes

Common root causes:

Windows Update failure

Disk corruption

Driver updates

Antivirus conflicts

Disk space full

Storage performance issues

If recent updates caused it:

Uninstall latest updates via:

dism /image:D:\ /cleanup-image /revertpendingactions

Step 5: If Issue is INACCESSIBLE_BOOT_DEVICE

This is common in Azure.

Actions:

Verify disk type matches VM (Premium/Standard SSD)

Check if disk was moved between VM sizes

Ensure no storage controller mismatch

You may need to:

Detach OS disk

Create new VM

Attach existing OS disk

Repair boot configuration

Step 6: Last Resort – Restore from Backup

If available:

Restore from Azure Backup

Restore from Snapshot

Redeploy VM

🚨 When to Raise Microsoft Case

Raise a support case with Microsoft if:

Repair VM fails

Disk corruption severe

Serial console inaccessible

Production workload impacted

Include:

VM name

Subscription ID

Region

Screenshot of BSOD

Exact STOP Code

Timestamp of failure

📌 Recommended Immediate Action (Most Successful Path)

Use Repair VM

Run offline chkdsk + sfc

Rebuild BCD if needed

Reattach disk to original VM

Start VM

This resolves ~70% of Azure BSOD boot issues.

From Boot Diagnostics → Screenshot, identify:

STOP Code (e.g., INACCESSIBLE_BOOT_DEVICE, CRITICAL_PROCESS_DIED)

Any driver file mentioned (e.g., ntfs.sys, vhdmp.sys)

This determines the root cause.

Step 2: Attempt Azure Serial Console (Recommended)

Go to VM → Help → Serial Console

Enable if not already enabled

Attempt:

Safe Mode boot

Recovery options

If accessible:

sfc /scannow

Step 3: Use Azure “Repair VM” Feature (Most Effective)

In the Azure Portal:

Go to Virtual Machine

Select Support + Troubleshooting

Click Repair

This creates a repair VM and attaches the OS disk for offline repair.

Inside the Repair VM:

Mount the OS disk (usually as D: or E:)

Run:

chkdsk D: /f /r

If boot corruption suspected:

bootrec /fixmbr

Step 4: Check for Recent Changes

Common root causes:

Windows Update failure

Disk corruption

Driver updates

Antivirus conflicts

Disk space full

Storage performance issues

If recent updates caused it:

Uninstall latest updates via:

dism /image:D:\ /cleanup-image /revertpendingactions

Step 5: If Issue is INACCESSIBLE_BOOT_DEVICE

This is common in Azure.

Actions:

Verify disk type matches VM (Premium/Standard SSD)

Check if disk was moved between VM sizes

Ensure no storage controller mismatch

You may need to:

Detach OS disk

Create new VM

Attach existing OS disk

Repair boot configuration

Step 6: Last Resort – Restore from Backup

If available:

Restore from Azure Backup

Restore from Snapshot

Redeploy VM

Raise a support case with Microsoft if:

Repair VM fails

Disk corruption severe

Serial console inaccessible

Production workload impacted

Include:

VM name

Subscription ID

Region

Screenshot of BSOD

Exact STOP Code

Timestamp of failure

Use Repair VM

Run offline chkdsk + sfc

Rebuild BCD if needed

Reattach disk to original VM

Start VM

This resolves ~70% of Azure BSOD boot issues.

Your answer

Aritra Basu 15 Reputation points

2026-02-25T03:27:44.06+00:00

Azure Virtual Machine
Aritra Basu 15 Reputation points

2026-02-25T03:28:16.1066667+00:00

Please treat this on priority as it is in production environment.
Ankit Yadav 12,205 Reputation points Microsoft External Staff Moderator

2026-02-25T04:00:53.21+00:00

Hello @Aritra Basu

The blue screen error message indicates that the underlying OS for the VM is not booting properly.

To fix it,

please go to the Azure Portal, select the affected VM, then navigate to Help > Redeploy + Reapply. First, click Re-apply on the VM, and then Redeploy the VM. This process often resolves OS and host issues that can prevent the VM from booting.

Faster way;

If you have a backup of your VM from before the blue screen error, you can restore the VM to that previous state using the backup.

Additionally, please confirm:-

What OS is running on the VM?

Are you able to connect the server/website running inside the VM?
Aritra Basu 15 Reputation points

2026-02-25T04:22:38.7533333+00:00

Windows server 2016 datacenter

No
Aritra Basu 15 Reputation points

2026-02-25T05:24:26.48+00:00

I have tried to reapply then redeploy, whether it was successful but still I am not able to login through serial console, serial console not responding
Aritra Basu 15 Reputation points

2026-02-25T07:10:04.4533333+00:00

Hello Ankit, Could you please raise a case with Microsoft to look into this issue. Please share the link to raise case with Microsoft. It is a business critical machine and we need immediate solution.
Ankit Yadav 12,205 Reputation points Microsoft External Staff Moderator

2026-02-25T16:57:52.56+00:00

Hello @Aritra Basu

I sent you a Private Message regarding this. Please take a look and let me know if you can help.
Navneet Kumar 165 Reputation points

2026-02-25T19:26:02.3733333+00:00

BSOD error: NTFS_FILE_SYSTEM on Windows Server 2016. This usually indicates OS disk corruption.

Steps to fix:

Stop the VM from Azure Portal.

Detach the OS disk:

VM → Disks → Select OS disk → Detach.

Attach the OS disk to a healthy Windows VM as a data disk.

On the healthy VM, open Command Prompt as Administrator and run:

chkdsk X: /f /r

(Replace X with the drive letter of the attached disk.)

After it completes, run:

sfc /scannow /offbootdir=X:\ /offwindir=X:\Windows

Detach the disk from the healthy VM.

Reattach it back to the original VM as OS disk.

Start the VM.

In most cases, chkdsk fixes the NTFS_FILE_SYSTEM blue screen.
Ankit Yadav 12,205 Reputation points Microsoft External Staff Moderator

2026-02-27T07:55:22.39+00:00

Hello @Aritra Basu, Just checking in if you are still blocked with the issue, if yes, kindly review the Private Message and share the required details for us to help you out further.

Share via

Blue screen error in azure VM

Step 2: Attempt Azure Serial Console (Recommended)

Step 3: Use Azure “Repair VM” Feature (Most Effective)

Inside the Repair VM:

Step 4: Check for Recent Changes

Step 5: If Issue is INACCESSIBLE_BOOT_DEVICE

Step 6: Last Resort – Restore from Backup

🚨 When to Raise Microsoft Case

📌 Recommended Immediate Action (Most Successful Path)

Step 2: Attempt Azure Serial Console (Recommended)

Step 3: Use Azure “Repair VM” Feature (Most Effective)

Inside the Repair VM:

Step 4: Check for Recent Changes

Step 5: If Issue is INACCESSIBLE_BOOT_DEVICE

Step 6: Last Resort – Restore from Backup

Your answer