A kernel-mode driver accessed pageable memory at an invalid interrupt level. The identifier alone does not establish a user-specific cause or a failed part.
Protect your files first
Back up important files when possible. If the drive is encrypted, locate the BitLocker recovery key before recovery changes. Stop if storage appears to be failing or this is a work or school managed PC.
What this code tells you
A kernel-mode driver accessed pageable memory at an invalid interrupt level.
This is a researched code brief, not a confirmed diagnosis for your PC. Verify the exact code and any device-specific action against the official references below.
The next useful clue is the exact screen, app, device, or log where it appeared. Record the Windows build and what changed just before the error. Do not treat a matching number from another error family as the same problem.
Check the context
The useful investigation focus is driver version, identified driver module, recent updates.
- Does Windows start normally, only in Safe Mode, or not at all?
- What Windows build and device model are affected?
- What changed before the problem appeared?
- What exact error text, driver name, KB number, or Event Viewer provider accompanies the code?
Safer checks to try
Record the exact error and when it happened Low risk
- Copy the full code, text, Windows version (winver), and any driver name shown.
- Note whether Windows boots normally, starts only in Safe Mode, or does not boot.
- Record what changed immediately before the issue and any relevant log timestamp.
After this check, see whether the original error appears again. If it does, record the new timestamp and continue with the next evidence-based step.
Use only official and model-correct drivers Medium risk
- Identify the exact hardware model and Windows version in Device Manager or the PC manufacturer utility.
- Check Windows Update and the manufacturer support portal for a compatible driver or documented rollback.
- Create a backup/restore option before firmware or storage-controller changes; do not use unverified driver packages.
After this check, see whether the original error appears again. If it does, record the new timestamp and continue with the next evidence-based step.
Use dump evidence instead of guessing the culprit Medium risk
- If a dump exists, identify its date and the stop code; redact personal or proprietary information before sharing.
- Use Microsoft WinDbg and !analyze -v to inspect the stop code and stack with appropriate technical expertise.
- A named driver in a stack trace is evidence to investigate, not automatic proof that the vendor is responsible.
After this check, see whether the original error appears again. If it does, record the new timestamp and continue with the next evidence-based step.
When to stop
Back up data and locate any BitLocker recovery key before advanced recovery steps. Stop for unstable storage or signs of electrical damage.
If Windows will not start repeatedly, the drive is unstable, or the device belongs to work or school, ask the appropriate manufacturer or IT team for help. Do not share a BitLocker key, product key, password, or full memory dump in a public search box.
Keep track of your checks
This checklist stays in this browser session. It is not sent to WinErrors.