How to fix IRQL_NOT_LESS_OR_EQUAL error on Windows 10?

Даниил Панарин 0 Reputation points
2025-07-25T20:05:00.3+00:00

Previously, the computer would simply freeze and not respond, and I had to reboot it. Quite recently, it stopped doing this, about a week ago, and started giving a blue screen with the error I mentioned earlier in the title.

Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: ffff8000000004f8, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
	bit 0 : value 0 = read operation, 1 = write operation
	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff804376fb767, address which referenced memory

Debugging Details:
------------------


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2796

    Key  : Analysis.Elapsed.mSec
    Value: 18181

    Key  : Analysis.IO.Other.Mb
    Value: 0

    Key  : Analysis.IO.Read.Mb
    Value: 1

    Key  : Analysis.IO.Write.Mb
    Value: 0

    Key  : Analysis.Init.CPU.mSec
    Value: 625

    Key  : Analysis.Init.Elapsed.mSec
    Value: 3457

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 106

    Key  : Analysis.Version.DbgEng
    Value: 10.0.27871.1001

    Key  : Analysis.Version.Description
    Value: 10.2505.01.02 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2505.1.2

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0xa

    Key  : Bugcheck.Code.TargetModel
    Value: 0xa

    Key  : Failure.Bucket
    Value: AV_nt!MiRestoreTransitionPte

    Key  : Failure.Exception.IP.Address
    Value: 0xfffff804376fb767

    Key  : Failure.Exception.IP.Module
    Value: nt

    Key  : Failure.Exception.IP.Offset
    Value: 0x2fb767

    Key  : Failure.Hash
    Value: {37d4886d-fd49-86e8-3405-f2978c32f33e}

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Version
    Value: 10.0.19041.1


BUGCHECK_CODE:  a

BUGCHECK_P1: ffff8000000004f8

BUGCHECK_P2: 2

BUGCHECK_P3: 1

BUGCHECK_P4: fffff804376fb767

FILE_IN_CAB:  072625-28421-01.dmp

FAULTING_THREAD:  ffffb18e252a5040

WRITE_ADDRESS: fffff804380fb390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
 ffff8000000004f8 

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:  
ffffea8b`c40d86a8 fffff804`37811aa9     : 00000000`0000000a ffff8000`000004f8 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
ffffea8b`c40d86b0 fffff804`3780d478     : 00000000`00000666 ffffb18e`2465d080 ffffb18e`252a5040 000000cb`0fbffae0 : nt!KiBugCheckDispatch+0x69
ffffea8b`c40d87f0 fffff804`376fb767     : ffff9800`00000000 7fffffff`ffffffff ffff9800`00000000 00000000`00000000 : nt!KiPageFault+0x478
ffffea8b`c40d8980 fffff804`37784f88     : 00000000`00000000 ffff9800`00000000 00000000`00000001 00000000`00000000 : nt!MiRestoreTransitionPte+0x147
ffffea8b`c40d89f0 fffff804`37950d09     : fffff804`38050dc0 00000000`00000000 00000000`00000000 fffff804`38051880 : nt!MiRemoveLowestPriorityStandbyPage+0x648
ffffea8b`c40d8a90 fffff804`37950f63     : fffff804`38050dc0 00000000`00000000 fffff804`00000000 00000000`000002b6 : nt!MiPruneStandbyPages+0x265
ffffea8b`c40d8b20 fffff804`376418f5     : ffffb18e`252a5040 fffff804`37950ed0 ffffb18e`1bf35c50 fffff804`38052660 : nt!MiRebalanceZeroFreeLists+0x93
ffffea8b`c40d8b70 fffff804`3775d5f5     : ffffb18e`252a5040 00000000`00000080 ffffb18e`1be67040 0003a4ef`b59bbfff : nt!ExpWorkerThread+0x105
ffffea8b`c40d8c10 fffff804`37806278     : fffff804`33158180 ffffb18e`252a5040 fffff804`3775d5a0 640b3c67`05c69349 : nt!PspSystemThreadStartup+0x55
ffffea8b`c40d8c60 00000000`00000000     : ffffea8b`c40d9000 ffffea8b`c40d3000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME:  nt!MiRestoreTransitionPte+147

MODULE_NAME: nt

IMAGE_VERSION:  10.0.19041.6157

STACK_COMMAND: .process /r /p 0xffffb18e1be67040; .thread 0xffffb18e252a5040 ; kb

IMAGE_NAME:  ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET:  147

FAILURE_BUCKET_ID:  AV_nt!MiRestoreTransitionPte

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {37d4886d-fd49-86e8-3405-f2978c32f33e}

Followup:     MachineOwner
---------
Windows for home | Windows 10 | Performance and system failures
0 comments No comments

5 answers

Sort by: Most helpful
  1. Даниил Панарин 0 Reputation points
    2025-07-26T13:14:29.25+00:00

    This time another error popped up, namely PFN LIST CORRUPT

    Was this answer helpful?


  2. Даниил Панарин 0 Reputation points
    2025-07-26T13:05:07.63+00:00

    No, the error still hasn't gone away. It just appeared and rebooted my computer.

    Was this answer helpful?

    0 comments No comments

  3. Даниил Панарин 0 Reputation points
    2025-07-26T08:43:27.57+00:00

    I did all the steps you indicated, except for updating the drivers for the motherboard. Even on the website, the latest driver is from 2019-2020. Now I'm monitoring the computer and seeing what happens.

    Was this answer helpful?

    0 comments No comments

  4. Alvise C 56,036 Reputation points Volunteer Moderator
    2025-07-25T20:45:48.6366667+00:00

    hi, welcome in community

    follow these steps:

    Troubleshoot blue screen errors

    https://support.microsoft.com/en-US/windows/resolving-blue-screen-errors-in-windows-60b01860-58f2-be66-7516-5c45a66ae3c6

    also perform a clean boot

    https://support.microsoft.com/en-us/kb/929135

    then, this error is usually associated with one of the following problems:

    • Something might be wrong with a device driver.
    • Something might be wrong with the Windows device's memory.

    in addition, i suggest you to update all the driver, download them from the support website of the manufacturer, if you don't know how, tell me the exact model of your notebook or motherboard (if desktop pc)

    let me know

    Elvis

    Was this answer helpful?


  5. Даниил Панарин 0 Reputation points
    2025-07-25T20:20:29.7533333+00:00

    Was this answer helpful?

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.