You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
#customer intent: As a DevOps Engineer, I want to set up an effective Seccomp profile so that I can run my workloads successfully while making them as secure as possible.
9
10
---
10
11
# Troubleshoot seccomp profile configuration in Azure Kubernetes Service
Copy file name to clipboardExpand all lines: support/azure/azure-storage/blobs/alerts/storage-explorer-troubleshooting.md
+7-4Lines changed: 7 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,8 +6,8 @@ author: jinglouMSFT
6
6
ms.author: jinglou
7
7
ms.service: azure-storage
8
8
ms.custom: sap:Alerts, Metrics, Logging and Monitoring, linux-related-content
9
-
ms.date: 12/23/2024
10
-
ms.reviewer: cralvord,richardgao
9
+
ms.date: 06/13/2025
10
+
ms.reviewer: cralvord,richardgao
11
11
---
12
12
13
13
# Azure Storage Explorer troubleshooting guide
@@ -478,6 +478,9 @@ If you accidentally attached by using an invalid shared access signature URL and
478
478
479
479
Storage Explorer comes packaged with all dependencies it needs to run on Windows.
480
480
481
+
> [!NOTE]
482
+
> Some components need command line access. If it's restricted, Storage Explorer might not work as expected. If you encounter issues, contact your system administrator.
483
+
481
484
## [macOS](#tab/macOS)
482
485
483
486
Storage Explorer comes packaged with all dependencies it needs to run on macOS.
You can also download the application as a *.tar.gz* file, but you have to install dependencies manually.
500
503
501
-
Storage Explorer requires the [.NET 6 runtime](/dotnet/core/install/linux) to be installed on your system. The ASP.NET runtime isn't required.
504
+
Storage Explorer requires the [.NET 8 runtime](/dotnet/core/install/linux) to be installed on your system. The ASP.NET runtime isn't required.
502
505
503
506
> [!NOTE]
504
507
> Older versions of Storage Explorer might require a different version of .NET or .NET Core. To determine the required version, refer to the release notes or in-app error messages.
@@ -676,7 +679,7 @@ AzCopy logs can be found easily via two different methods:
676
679
For some issues, you need to provide logs of the network calls made by Storage Explorer. On Windows, you can get network logs by using Fiddler.
677
680
678
681
> [!NOTE]
679
-
> Fiddler traces might contain passwords you entered or sent in your browser during the gathering of the trace. Make sure to read the instructions on how to sanitize a Fiddler trace. Don't upload Fiddler traces to GitHub. You'll be told where you can securely send your Fiddler trace.
682
+
> Fiddler traces might contain passwords you entered or sent in your browser during the gathering of the trace. Make sure to read the instructions on how to sanitize a Fiddler trace. Don't upload Fiddler traces to GitHub. Wait for instructions on how to securely send your Fiddler trace.
description: Provides solutions to an issue where an Azure virtual machine (VM) experiences the IRQL_NOT_LESS_OR_EQUAL bug check (0x0000001A).
4
+
ms.date: 06/13/2025
5
+
ms.reviewer: cwhitley, v-weizhu
6
+
ms.service: azure-virtual-machines
7
+
ms.collection: windows
8
+
ms.custom: sap:My VM is not booting
9
+
---
10
+
11
+
# VM startup is stuck on bug check 0x0000001A - IRQL_NOT_LESS_OR_EQUAL
12
+
13
+
**Applies to:**:heavy_check_mark: Windows VMs
14
+
15
+
This article helps you resolve an issue where a Microsoft Azure virtual machine (VM) experiences the **IRQL_NOT_LESS_OR_EQUAL** bug check with the stop code 0x0000001A.
16
+
17
+
## Symptoms
18
+
19
+
When you use [Boot diagnostics](./boot-diagnostics.md) to view the screenshot of a VM, the Windows operating system (OS) displays the **IRQL_NOT_LESS_OR_EQUAL** bug check (0x0000001A).
20
+
21
+
:::image type="content" source="media/interrupt-request-line-not-less-equal/interrupt-request-line-not-less-equal-bug-check-screen.png" alt-text="Screenshot of Windows operating system bug check IRQL_NOT_LESS_OR_EQUAL (0x0000001A).":::
22
+
23
+
## Cause
24
+
25
+
This bug check indicates that Windows or a kernel-mode driver tries to access paged memory at an invalid address while operating at a raised interrupt request level (IRQL).
26
+
27
+
This issue often occurs when the OS of a VM doesn't support more than 64 virtual CPUs (vCPUs), but the VM is configured with a higher vCPU count. For instance, Windows Server 2012 R2 supports a maximum of 64 vCPUs. If a VM running such an OS is provisioned with more than 64 vCPUs, the VM might fail to start and trigger the IRQL_NOT_LESS_OR_EQUAL bug check.
28
+
29
+
## Resolution
30
+
31
+
To resolve this issue, use one of the following methods:
32
+
33
+
- Reduce the number of vCPUs assigned to the VM to 64 or fewer.
34
+
- Rebuild the VM using an OS that supports more than 64 vCPUs, such as Windows Server 2016 or later.
35
+
36
+
If your VM is already running a supported OS version or is configured with 64 or fewer vCPUs, further investigation is required to determine the specific cause of this issue.
37
+
38
+
## Collect a memory dump for troubleshooting
39
+
40
+
To assist with further diagnosis, [collect an OS memory dump file](./collect-os-memory-dump-file.md) and then [create a support request](https://ms.portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/overview?DMC=troubleshoot) so that Azure support can investigate and help resolve the issue.
41
+
42
+
43
+
[!INCLUDE [Azure Help Support](../../../includes/azure-help-support.md)]
0 commit comments