Causes and solutions for Windows ECS instance downtime -

If your Windows ECS instance has a kernel panic, an OOM (Out of Memory) error, a blue screen, or an operating system crash reported by a system event, the instance has experienced downtime. You can use the self-service diagnostics tool or system events to diagnose the cause and resolve the issue.

Identify the cause of downtime

Use the following methods to identify the cause of the downtime.

Self-service diagnostics

Go to ECS Console - Troubleshooting.
In the upper-left corner of the page, select a region and resource group.
In the Instance Performance Abnormality card, click Initiate Diagnosis. In the Create Diagnostic Task dialog box, select the instance ID and a time range, then click Initiate Diagnosis.
Use the diagnostic results and recommended solution to resolve the issue. For more information, see Common causes and solutions.

System events

Go to ECS console - Events.
In the navigation pane on the left, click Unexpected O&M Events.
Click Diagnose Operating System Issue for the instance with the downtime event to identify the cause of the downtime.

Use the diagnostic results and recommended solution to resolve the issue. For more information, see Common causes and solutions.

Common causes and solutions

Instance downtime with error code 0000003b

Problem description
Cause

A core system service process exited unexpectedly.
Solution
- Uninstall any unreliable third-party software or drivers. For more information, see How do I view the third-party software and drivers that are installed on an ECS instance?.
- Install the latest system patches. For more information, see How do I update system patches to the latest version?.
- Follow the steps in the Bug Check 0x3B: SYSTEM_SERVICE_EXCEPTION documentation.

Instance downtime with error code 0000000a

Problem description
Cause

The kernel or a driver accessed invalid memory.
Solution
- Uninstall any unreliable third-party software or drivers. For more information, see How do I view the third-party software and drivers that are installed on an ECS instance?.
- Install the latest system patches. For more information, see How do I update system patches to the latest version?.
- Follow the steps in the Bug check 0xA: IRQL_NOT_LESS_OR_EQUAL documentation.

Instance downtime with error code 00000101

Problem description
Cause

The processor timed out while responding to a clock interrupt.
Solution

Follow the steps in the Bug check 0x101: CLOCK_WATCHDOG_TIMEOUT documentation.

Instance downtime with error code 00000133

Problem description
Cause

A system DPC (Deferred Procedure Call) timed out.
Solution

Follow the steps in the Bug Check 0x133: DPC_WATCHDOG_VIOLATION documentation.

Instance downtime with error code 000000ef

Problem description
Cause

A critical system process exited unexpectedly.
Solution
- Uninstall any unreliable third-party software or drivers. For more information, see How do I view the third-party software and drivers that are installed on an ECS instance?.
- Install the latest system patches. For more information, see How do I update system patches to the latest version?.
- Follow the steps in the Bug check 0xEF: CRITICAL_PROCESS_DIED documentation.

Instance downtime with error code 00000050

Problem description
Cause

The kernel or a driver accessed invalid memory.
Solution
- Uninstall any unreliable third-party software or drivers. For more information, see How do I view the third-party software and drivers that are installed on an ECS instance?.
- Install the latest system patches. For more information, see How do I update system patches to the latest version?.
- Follow the steps in the Bug Check 0x50: PAGE_FAULT_IN_NONPAGED_AREA documentation.

Instance downtime with error code 0000001e

Problem description
Cause

An unhandled kernel exception occurred.
Solution
- Uninstall any unreliable third-party software or drivers. For more information, see How do I view the third-party software and drivers that are installed on an ECS instance?.
- Install the latest system patches. For more information, see How do I update system patches to the latest version?.
- Follow the steps in the Bug check 0x1E: KMODE_EXCEPTION_NOT_HANDLED documentation.

Instance downtime with error code 0000007e

Problem description
Cause

An unhandled system thread exception occurred.
Solution
- Uninstall any unreliable third-party software or drivers. For more information, see How do I view the third-party software and drivers that are installed on an ECS instance?.
- Install the latest system patches. For more information, see How do I update system patches to the latest version?.
- Follow the steps in the Bug Check 0x7E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED documentation.

Instance downtime with error code 00000139

Problem description
Cause

A kernel data structure was corrupted.
Solution
- Uninstall any unreliable third-party software or drivers. For more information, see How do I view the third-party software and drivers that are installed on an ECS instance?.
- Install the latest system patches. For more information, see How do I update system patches to the latest version?.
- Follow the steps in the Bug Check 0x139: KERNEL_SECURITY_CHECK_FAILURE documentation.

Instance downtime with error code 0000013a

Problem description
Cause

A kernel data structure was corrupted.
Solution
- Uninstall any unreliable third-party software or drivers. For more information, see How do I view the third-party software and drivers that are installed on an ECS instance?.
- Install the latest system patches. For more information, see How do I update system patches to the latest version?.
- Follow the steps in the Bug check 0x13A: KERNEL_MODE_HEAP_CORRUPTION documentation.

Instance downtime with error code 00000135

Problem description
Cause

A registry filter driver handled an exception incorrectly. This issue is typically caused by a third-party driver.
Solution
- Uninstall any unreliable third-party software or drivers. For more information, see How do I view the third-party software and drivers that are installed on an ECS instance?.
- Install the latest system patches. For more information, see How do I update system patches to the latest version?.
- Follow the steps in the Bug Check 0x135: REGISTRY_FILTER_DRIVER_EXCEPTION documentation.

Instance downtime with error code 00000019

Problem description
Cause

A system memory pool data structure was corrupted.
Solution
- Uninstall any unreliable third-party software or drivers. For more information, see How do I view the third-party software and drivers that are installed on an ECS instance?.
- Install the latest system patches. For more information, see How do I update system patches to the latest version?.
- Follow the steps in the Bug Check 0x19: BAD_POOL_HEADER documentation.

FAQ

Note

The following steps use Windows Server 2019 as an example. The steps for other versions may vary slightly. Adjust them accordingly.

View third-party software and drivers

Third-party software
1. In the Windows operating system, open the Control Panel.
2. In Control Panel, go to Programs > Programs and Features.
3. View the third-party software in the list.
  
  Note
  Third-party software is from publishers other than Microsoft. You can also find some applications and their publishers in the system tray.
Third-party drivers
1. In the Windows operating system, open Device Manager.
2. Expand each device category to view installed third-party drivers.

Update system patches

In the Windows operating system, open Windows Update settings.
On the Windows Update tab of the Update & Security page, click check for updates.
Click Install to apply the latest system patches.