- Software and digital services
- Operating system
IRQL_NOT_LESS_OR_EQUAL
IRQL_NOT_LESS_OR_EQUAL (0xA) on Windows: invalid memory access at raised priority
Risk level
Medium
Proceed carefully and stop if the check is unclear.
Urgency
High
Quick answer
Windows or a driver tried to read memory at an invalid address while running at a raised interrupt level. Think of the last driver, service, antivirus or BIOS you changed and start there.
Safety first
Stop and check this first
- Driver Verifier uses a lot of CPU, can slow the PC and cause more blue screens; only IT support should run it, verifying a few drivers at a time.
Safe checks you can perform
- Last software or hardware change
- Test without third-party antivirus
- Critical errors in the System log
Leave these tasks to a qualified professional
- Do not attempt this professional task: Dump analysis in WinDbg
- Do not attempt this professional task: Driver Verifier
What a technician must be able to justify
Technician visit
These are the steps they must carry out and show you. Tick them as they work: if steps are skipped, do not accept a part swap.
These are not instructions for opening or handling the equipment yourself. They are the checks that should support a technical conclusion.
Dump analysis in WinDbg
What they doIT support runs !analyze -v and reviews the stack; the parameters give the address that could not be accessed, the IRQL, whether it was a read, write or execute, and the faulting instruction.
They must show youthe output with the module involved and the four parameters.
In writingwhich driver or service was identified and what was changed.
Driver Verifier
What they doIf the dump is not enough, they enable Driver Verifier (verifier) on as few suspect drivers as possible so the culprit code fails in the act.
They must show youthe settings applied and the dump it produced.
In writingwhich drivers were verified, the result, and that verification was turned off afterwards.
Before accepting a part or repair
Nothing has been shown yet. Do not accept a part swap based on the code alone.
Follow these steps
Note: Follow the documented order. An error code identifies the affected system, but it does not prove by itself which part has failed.
Last software or hardware change
- Who:
- you.
- How:
- note the code, the .sys file if one is shown and which driver, service, BIOS update or hardware you added before the first crash.
- Result that matters:
- whether a change lines up in time.
- If one does:
- remove that hardware or uninstall that driver and see if it repeats.
- If none does:
- go on to antivirus and logs.
- Evidence to keep:
- photo of the code and list of changes.
Evidence: Bug Check 0xA IRQL_NOT_LESS_OR_EQUAL · Troubleshooting Windows unexpected restarts and stop code errors
Test without third-party antivirus
- Who:
- you.
- How:
- if you use an antivirus other than Windows Security, temporarily disable or uninstall it and use the PC normally.
- Result that matters:
- whether the blue screen stops without it.
- If it stops:
- contact its maker for a compatible version.
- If it repeats:
- turn it back on; it is not the cause.
- Evidence to keep:
- test dates and antivirus version.
While it is off, keep Windows Security on and avoid dubious sites.
Evidence: Bug Check 0xA IRQL_NOT_LESS_OR_EQUAL
Critical errors in the System log
- Who:
- you.
- How:
- in Event Viewer open Windows Logs, System, and look for critical errors in the same time window as the blue screen.
- Result that matters:
- whether a device or driver appears just before.
- If one does:
- it points to the component IT support should review.
- If not:
- the dump will be the main evidence.
- Evidence to keep:
- screenshot of the event.
Evidence: Bug Check 0xA IRQL_NOT_LESS_OR_EQUAL
Still not solved
If the error persists, stop here. See what the technician must do and show you.
Where this code applies
A code is meaningful only inside the right product and version context.
Primary scope
- System
- Software and digital services
- Brand
- Microsoft Windows
- Product type
- Operating system
Known code variants
- 0x0000000A
- 0xA
- IRQL NOT LESS OR EQUAL
- STOP 0x0000000A
- stop code IRQL_NOT_LESS_OR_EQUAL
What it means
Microsoft defines 0x0000000A as Windows or a kernel-mode driver accessing paged memory at an invalid address while at a raised interrupt request level (IRQL). The typical cause is a bad pointer or a pageability problem in the driver code. It usually follows installing a faulty driver, system service or BIOS, and during Windows upgrades also an incompatible antivirus or backup tool. The code does not identify the component.
Warnings and stop conditions
- Mediumsource verified
Driver Verifier uses a lot of CPU, can slow the PC and cause more blue screens; only IT support should run it, verifying a few drivers at a time.
Evidence: Stop code error or bug check troubleshooting (IT professionals)
Symptoms and causes
Probable causes · in order
- Recently installed driver, service or BIOSCommon
Microsoft says the error usually follows installing one of these. If crashes began right after, undoing it confirms it.
Evidence: Bug Check 0xA IRQL_NOT_LESS_OR_EQUAL
- Incompatible antivirus or backup toolPossible
Especially if the error shows up while upgrading to a new Windows version. Disabling the program tests it.
Evidence: Bug Check 0xA IRQL_NOT_LESS_OR_EQUAL
- Added or failed hardwarePossible
If removing new hardware stops the crashes, it was the cause; for existing hardware only the maker's diagnostics confirm it.
Evidence: Bug Check 0xA IRQL_NOT_LESS_OR_EQUAL
Virtual technician
Does IRQL_NOT_LESS_OR_EQUAL still appear after these checks?
Answer a few questions to narrow down the likely cause and the safest next action. Guidance only - it never replaces a professional.
Sources and technical references
- 1
Bug Check 0xA IRQL_NOT_LESS_OR_EQUAL
Microsoft · 2026 · official_doc
- 2
Stop code error or bug check troubleshooting (IT professionals)
Microsoft · 2026 · official_doc
- 3
Troubleshooting Windows unexpected restarts and stop code errors
Microsoft · 2026 · official_doc
Was this entry useful?