What IRQL_NOT_LESS_OR_EQUAL Actually Means

Stop code 0x0000000A fires when a kernel-mode driver or Windows itself tries to read or write paged memory while running at a raised interrupt request level (IRQL). Paged memory can be swapped out to disk at any moment, so the CPU cannot safely touch it above a certain IRQL threshold. When that rule is violated, Windows has no safe recovery path and halts immediately.

On a brand-new machine running Windows 11, this is one of the first BSODs we see come through the shop, and it is also one of the most frequently misread.

Microsoft’s kernel debugger documentation identifies two root causes: a bad pointer dereference or a pageability problem caused by kernel-mode code using an improper address. Both paths produce the same stop code, which is why the crash dump parameters matter more than the error name itself.

Reading the Two Diagnostic Branches

Parameter 1 in the minidump is the memory address that was accessed illegally. Two values tell you which branch you are on:

• Parameter 1 below 0x1000: almost certainly a NULL pointer dereference, meaning a driver passed an uninitialized or zeroed pointer into a kernel call.
• Parameter 1 in the paged pool range: the IRQL was too high to access that address, pointing to a driver that failed to lock memory before raising its interrupt level.

Minidump files land at C:WindowsMinidump and can be opened with WinDbg or NirSoft BlueScreenView to surface the offending module quickly.

Why RAM Is on the Suspect List

The instinct on a new build is to blame drivers, and drivers are a legitimate cause. But Microsoft’s own support guidance explicitly includes memory issues and hardware problems alongside faulty drivers in the fix path for IRQL_NOT_LESS_OR_EQUAL 0x0000000A memory fix Windows 11 scenarios.

A DIMM with a poor electrical contact produces corrupted reads that the kernel interprets as an invalid address access. The crash dump looks identical to a driver bug. That overlap is exactly why we always seat and test RAM before touching driver versions on any new build that arrives with this stop code.

Why a New PC Can BSOD Out of the Box

A brand-new system arriving with a BSOD feels like a defect, but the cause is almost never a failed component. In our experience, IRQL_NOT_LESS_OR_EQUAL on new PC first boot traces to one of three conditions: a DIMM that shifted in its slot during shipping, a driver stack that has not fully settled during the first Windows setup pass, or an XMP/EXPO memory profile that sits right at the edge of stability.

Shipping vibration is the most common culprit we see in the shop. A DIMM can pass every bench test before a system ships, then arrive with one module backed just far enough out of its slot to cause intermittent memory access faults. The module looks seated. The clips look closed. But the electrical contact is inconsistent, and the kernel notices before you do.

The Three Root Causes on a Fresh Build

The specific build this bulletin covers is an i9-14900KF paired with an RTX 5070 on an MSI Gungnir 111R chassis. The i9-14900KF runs 24 cores across 8 Performance-cores and 16 Efficient-cores, with a max turbo of 6.0 GHz, which means the interrupt load during first boot is substantial. The RTX 5070 brings its own driver initialization sequence on top of that. For RTX 5070 i9-14900KF build BSOD troubleshooting, ruling out the RAM contact issue first saves significant time before touching drivers or BIOS settings.

Shipping Vibration and DIMM Displacement

Freight carriers subject packages to sustained vibration across hundreds or thousands of miles. That vibration transmits directly through foam and cardboard into the motherboard, and the DIMM retaining clips are not immune. Under repeated low-frequency oscillation or a single sharp impact, a clip can partially release, allowing the module to rise a fraction of a millimeter out of the slot.

That fraction of a millimeter is enough to cause problems. A partially seated DIMM will often pass a visual inspection because the module still sits mostly flush and the clip appears engaged. The electrical contacts, however, are no longer making full, consistent contact across all pins. The system may POST and even boot into Windows before the instability surfaces under memory access load.

Why the Failure Is Intermittent

Marginal pin contact behaves differently than a completely missing module. With a fully absent DIMM, the system typically refuses to POST at all. With a partially seated one, the system reads the SPD data, trains the memory, and proceeds. The failure appears later, when a memory-intensive operation forces access to a region of the module that relies on the compromised contacts. That is exactly the scenario that produces loose RAM from shipping causing BSOD conditions, including IRQL_NOT_LESS_OR_EQUAL.

Reseating RAM after shipping is a standard first diagnostic step for this reason. The fix costs nothing and takes under five minutes, and it resolves the issue in a meaningful share of new-build BSOD cases we see in the shop.

Step-by-Step Diagnosis for This Specific Build

Before touching any hardware, pull the minidump file. Open File Explorer and navigate to C:WindowsMinidump. Load the most recent .dmp file into BlueScreenView (NirSoft) or WinDbg. On this i9-14900KF build, the offending module will typically point to a memory address rather than a named driver, which is a strong signal that the problem is hardware-level, not a software conflict.

Hardware Steps

1. Power down completely. Shut down, flip the PSU switch off, and hold the power button for three seconds to drain residual charge from the Gungnir 111R’s capacitors.
2. Reseat all DIMMs. Release both retention clips on each slot, pull the module straight out, then press it firmly back in until both clips snap closed. On the MSI board paired with this build, the slots require more force than most builders expect.
3. Clean the contacts if reseating alone does not hold. Wipe the gold edge connectors with a lint-free cloth dampened with 90%+ isopropyl alcohol. Follow with a short burst of compressed air into each slot before reinserting.

UEFI and Software Steps

1. Disable XMP in UEFI and test at JEDEC defaults. XMP profiles that are borderline-stable can fail under interrupt-heavy conditions, producing this exact BSOD. Dropping to JEDEC speeds isolates whether the profile itself is the trigger. This is the core reason we recommend you disable XMP to fix IRQL_NOT_LESS_OR_EQUAL before drawing any other conclusions.
2. Run Windows Memory Diagnostic. Press Win + R, type mdsched.exe, and schedule a restart. The built-in tool catches most single-bit errors on a first pass.
3. Test one stick at a time. If errors persist, seat only one DIMM in the primary slot and run the system through a full boot cycle. Rotate through each stick and each slot, noting whether the failure follows a specific module or a specific slot. A failure that follows the stick points to a damaged module; a failure that follows the slot points to the board.

Reseat Procedure for the MSI Gungnir 111R

The MSI MPG Gungnir 111R is a mid-tower supporting ATX, Micro-ATX, and Mini-ITX boards. The full-ATX layout gives you generous DIMM slot access once the side panel is off, but you need to orient yourself correctly before reaching inside.

Removing the Tempered Glass Side Panel

The left side panel is 4mm tempered glass. There are no thumbscrews on the face of the panel. Two screws sit at the rear edge of the panel. Remove both, then slide the panel straight back about half an inch before lifting it away. Set it flat on a padded surface, glass side up. Do not lean it against the desk.

Before reaching inside, ground yourself. Touch the bare metal of the PSU shroud or the unpainted steel of the chassis frame. A wrist strap clipped to the chassis is better. The Gungnir 111R ships with four ARGB 120mm fans pre-installed, and the front intake array plus the rear exhaust fan will be the first things you see. Use the rear 120mm fan as your orientation anchor: the DIMM slots on an ATX board sit roughly centered in the chassis, just inboard of that fan.

Accessing and Reseating the DIMMs

Check the magnetic dust filter on the top vent before you start. If it has shifted during shipping, reseat it now so it does not fall into the build while you work. With the panel off and the chassis on a stable surface, locate the DIMM slots. Press the retention clips at both ends of each slot outward until they click open. Pull the module straight up with even pressure on both ends.

To learn how to reseat RAM in the MSI Gungnir 111R correctly, the key step is alignment before force. Line up the module’s notch with the slot key, then press down firmly and evenly until both retention clips snap closed on their own. A clip that does not snap fully closed means the module is not fully seated. Repeat for each stick, then replace the glass panel before powering on.

When It Is Not the RAM

If reseating both DIMMs and running a full JEDEC-speed pass in MemTest86 comes back clean, the loose DIMM is not your culprit. At that point, shift focus to the driver stack. IRQL_NOT_LESS_OR_EQUAL crashes are frequently triggered by a driver executing an illegal memory access along an active code path, which is why they surface under load: gaming, large downloads, heavy USB activity, VPN use, or waking from sleep rather than at idle.

Driver Escalation Order

Work through this list in order. Each step is reversible, and each one narrows the cause before you consider swapping hardware.

ArsenalPC Support: How We Handle New-Build BSODs

When a customer contacts us with an IRQL_NOT_LESS_OR_EQUAL BSOD on a new system, our first move is remote diagnosis, not a return label. We ask for the minidump file, the full stop code string, and a description of when the crash occurs. In most cases, that information tells us exactly where to look before a single box gets packed.

This approach works because we know the exact component stack in every build we ship. We selected the board, seated the DIMMs, and ran the burn-in. A mass-market OEM ships thousands of configurations and often cannot tell you which DIMM slot was populated at the factory. We can. That specificity cuts triage time significantly, and it means we can walk a customer through a targeted fix, like a DIMM reseat, rather than issuing a blanket hardware swap that may not solve anything.

Our Workflow

Our team operates out of Willoughby, Ohio, and has handled boutique PC builder shipping damage support cases long enough to recognize patterns that generic support scripts miss. A loose DIMM after transit is one of the most common, and most misdiagnosed, new-build issues we see. Catching it remotely saves the customer days of downtime and avoids unnecessary component swaps.