Share via

Fortnite causes IRQL_Not_Less_Or_Equal BSOD error since update

Anonymous
2022-07-12T12:06:02+00:00

Hi! I've been playing Fortnite on my HP Pavilion 15-n002sh notebook, running Windows 8.1, with Intel Core i5-4200U CPU, 8 GB RAM and AMD Radeon HD 8670M GPU. Everything worked fine for months, then after the last update (v21.20) the game started causing an IRQL_Not_Less_Or_Equal stop code (Blue Screen of Death) whenever I join a game. Nothing else was changed on the PC, only Fortnite was updated.

Since then I tried fixing it by:

  • launching the game in different rendering modes
  • verifying the game files
  • completely uninstalling the game and launcher then reinstalling it
  • running it as an administrator
  • adjusting the compatibility settings
  • updating the graphics card drivers
  • checking for windows updates
  • disabling the antivirus software (Avast)
  • checking for viruses
  • repairing visual C++ redistributables
  • running diagnostics and stress tests on the memory and the graphics card (they're both working fine)

None of the above worked. Since then I found some other players on reddit who're saying that they encountered the same issue after the update, similarly on Windows 8.1 with AMD GPUs. Other games don't cause this error, only Fortnite, and Fortnite's been working fine until said update, so I'm guessing the problem's on their end, but their customer service insists it isn't and that I should contact Microsoft Support.

Any help would be greatly appreciated! Thank you very much in advance!

UPDATE: I also tried performing a Clean Boot but the problem persisted. I analyzed my crash dumps too: I couldn't make sense of the automatic memory dump's analysis, so I tried a complete memory dump with a different bugchecker. This is the result of the second analysis:

On Sun 2022.07.17. 14:50:01 your computer crashed or a problem was reported

Crash dump file: C:\WINDOWS\MEMORY.DMP (Full memory dump)
Bugcheck code: 0xA(0x10, 0x2, 0x1, 0xFFFFF801F5A74509)
Bugcheck name: IRQL_NOT_LESS_OR_EQUAL
Driver or module in which error occurred: Program.sys (FortniteClient_Win64_Shipping_7ffb056f0000!Ordinal0+0x2936230)
File path: C:\Program
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
Analysis: This is a typical software problem. Most likely this is caused by a bug in a driver.
Google query: FortniteClient_Win64_Shipping_7ffb056f0000 IRQL_NOT_LESS_OR_EQUAL

Can anyone help me how to proceed?

Windows for home | Previous Windows versions | Gaming

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

23 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2022-07-14T09:37:45+00:00

    Did this last suggestion fix the issue, I have had that problem since that update ( think it was July 5, 2022) and i run an Intel Core i 7 - 4500 U , ram 8 GB etc. I have tried all the fixes you had done as well. Please get back to me if that clean boot worked.

    0 comments
  2. Reza-Ameri 45,596 Reputation points Volunteer Moderator
    2022-07-14T15:21:36+00:00

    Did this last suggestion fix the issue, I have had that problem since that update ( think it was July 5, 2022) and i run an Intel Core i 7 - 4500 U , ram 8 GB etc. I have tried all the fixes you had done as well. Please get back to me if that clean boot worked.

    I should take a note that Clean Boot will not remove any program and it will just disable non-Microsoft services and it is to identify if third-party services might have caused the issue or not and you could simply enable services which you disabled. So, you may try it any time.

    0 comments
  3. Anonymous
    2022-07-15T22:30:09+00:00

    Just wondering if anyone has found a fix to this issue, as I am suffering from it as well.... Nothing seems to work....

    0 comments
  4. Anonymous
    2022-07-17T11:51:56+00:00

    I performed a Clean Boot but the problem unfortunately persisted. I also analyzed my crash dump, the result is below. It says he crash was probably caused by memory corruption but I ran memory diagnostics and stress tests and they didn't flag any problems. I'm too much of a noob to make sense of the analysis so I'd really appreciate some help!

    *******************************************************************************

    * *

    * Bugcheck Analysis *

    * *

    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck A, {10, 2, 1, fffff80166291509}

    Probably caused by : memory_corruption ( nt!MiLockPageAndSetDirty+21 )

    Followup: MachineOwner

    3: kd> !analyze -v

    *******************************************************************************

    * *

    * 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: 0000000000000010, 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: fffff80166291509, address which referenced memory

    Debugging Details:

    WRITE_ADDRESS: unable to get nt!MmNonPagedPoolStart

    unable to get nt!MmSizeOfNonPagedPoolInBytes

    0000000000000010

    CURRENT_IRQL: 2

    FAULTING_IP:

    nt!MiLockPageAndSetDirty+21

    fffff801`66291509 f00fba691000 lock bts dword ptr [rcx+10h],0

    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

    BUGCHECK_STR: AV

    PROCESS_NAME: FortniteClient

    ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

    TRAP_FRAME: ffffd000246a44f0 -- (.trap 0xffffd000246a44f0)

    NOTE: The trap frame does not contain all registers.

    Some register values may be zeroed or incorrect.

    rax=0000000000000002 rbx=0000000000000000 rcx=0000000000000000

    rdx=0000000080000000 rsi=0000000000000000 rdi=0000000000000000

    rip=fffff80166291509 rsp=ffffd000246a4680 rbp=000000a461f68000

    r8=80000000a00c682d r9=fffff6805230fb40 r10=fffffa8001e02520

    r11=00000000000007f8 r12=0000000000000000 r13=0000000000000000

    r14=0000000000000000 r15=0000000000000000

    iopl=0 nv up ei pl zr na po nc

    nt!MiLockPageAndSetDirty+0x21:

    fffff80166291509 f00fba691000 lock bts dword ptr [rcx+10h],0 ds:0000000000000010=????????

    Resetting default scope

    LAST_CONTROL_TRANSFER: from fffff8016636c769 to fffff8016635c4c0

    STACK_TEXT:

    ffffd000246a43a8 fffff8016636c769 : 000000000000000a 0000000000000010 0000000000000002 0000000000000001 : nt!KeBugCheckEx

    ffffd000246a43b0 fffff80166369ca8 : 000000005f000000 0000000000000000 bb67ae856a09e600 a54ff53a3c6ef372 : nt!KiBugCheckDispatch+0x69

    ffffd000246a44f0 fffff80166291509 : 000000a462431fff fffff801662931d5 fffff6805230fb40 fffff8016630dba1 : nt!KiPageFault+0x428

    ffffd000246a4680 fffff80166266d0e : 80000000a00c686f fffff6805230fb40 fffff68052312188 ffffd000246a4908 : nt!MiLockPageAndSetDirty+0x21

    ffffd000246a46b0 fffff80166404440 : 80000000a00c686f 80000000a00c686f ffffd000246a47f0 0000000000000000 : nt!MiRevertValidPte+0x1ce

    ffffd000246a46f0 fffff801666a5d2c : 000000000a462431 ffffd000246a4b80 0000000000000000 7ffffffffffffffc : nt!MiProtectPrivateMemory+0x510

    ffffd000246a48c0 fffff80166616a59 : ffffe00053ffd8c0 ffffe00053ffd8c0 ffffd000246a4a18 ffffd000246a4a08 : nt!MiProtectVirtualMemory+0x540

    ffffd000246a49c0 fffff8016636c6cf : 0000000000000404 000000a4181cecc0 000000a4181ced40 000000a4181ce2f8 : nt!NtProtectVirtualMemory+0x155

    ffffd000246a4a90 000000a417db0b76 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceExit+0x2e4

    000000a4181ce2d8 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x000000a4`17db0b76

    STACK_COMMAND: kb

    FOLLOWUP_IP:

    nt!MiLockPageAndSetDirty+21

    fffff801`66291509 f00fba691000 lock bts dword ptr [rcx+10h],0

    SYMBOL_STACK_INDEX: 3

    SYMBOL_NAME: nt!MiLockPageAndSetDirty+21

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    DEBUG_FLR_IMAGE_TIMESTAMP: 62b3f922

    IMAGE_NAME: memory_corruption

    BUCKET_ID_FUNC_OFFSET: 21

    FAILURE_BUCKET_ID: AV_nt!MiLockPageAndSetDirty

    BUCKET_ID: AV_nt!MiLockPageAndSetDirty

    ANALYSIS_SOURCE: KM

    FAILURE_ID_HASH_STRING: km:av_nt!milockpageandsetdirty

    FAILURE_ID_HASH: {06c06731-d6ea-b751-ad06-544f1aae8325}

    Followup: MachineOwner

    0 comments
  5. Anonymous
    2022-07-17T12:13:11+00:00

    Just wondering if anyone has found a fix to this issue, as I am suffering from it as well.... Nothing seems to work....

    Not yet, but still trying.

    0 comments