IRQL_NOT_LESS_OR_EQ BSOD playing Rainbow Six Siege

Hi All,

I recently started having issues where my game would freeze and then close for no reason. Soon after I started getting memory related BSOD errors including MEMORY_MANAGEMENT and IRQL_NOT_LESS_OR_EQUAL

I have tried running windows memory diagnostic but it found no problems with my RAM.

This sounds like a driver issue. Make sure all your drivers are up to date. If they already are you may want to install the original drivers for your motherboard if they are Windows 10 compatible.

Did the problems start after recently adding new memory modules? If so I would like you to try running the system with just a matched pair of modules rather than all four. It is usual to put the matched pairs in slots 1 and 3 or 2 and 4.

There is also a newer BIOS for your motherboard which was released to provide better system stability. That would be another thing to try.

philc43 said:

Did the problems start after recently adding new memory modules? .

Hey PhilC,

No i havent touched my ram in over a year. And thanks Ill look into upgrading my bios. This was a recent install of Windows 10, so my drivers should be up to date for the most part.

cmatt10123 said:

Hey PhilC,

No i havent touched my ram in over a year. And thanks Ill look into upgrading my bios. This was a recent install of Windows 10, so my drivers should be up to date for the most part.

Nevertheless, I would still recommend exploring your system with the matched pairs of RAM to see if it makes a difference.

Thanks Phil. I went ahead and matched my RAM like you said. I also updated my bios. I havent had a BSOD again yet, but R6 is still crashing. It may be unrelated. Ill keep testing and let you know if i experience another BSOD.

I had this problem when I had my memory running on higher frequency than default values. I thought I could change the frequency without overclocking the cpu. A while ago, when I was in a computer service store, one of the technician's said that overclocking the dram is possible without the cpu however through trial & error, I can state that it's still impossible.
The question is, is your's overclocked?

Hi All,

So it seemed like for a while the issue went away. I havent had the game crash at all, but just a few minutes ago I got another memory management BSOD while playing.

I have attached the dump file.

Any other ideas? I already matched ram and updated the bios. Do i need to buy new ram altogether?

This crash dump tends to suggest you do have memory problems. You have had what is known as a bit flip. Let me explain.

The crash analysis shows the following:

Code:

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041792, A corrupt PTE has been detected. Parameter 2 contains the address of
	the PTE. Parameters 3/4 contain the low/high parts of the PTE.
Arg2: ffff8000e2c4abb8
Arg3: 0000400000000000
Arg4: 0000000000000000

We can examine the PTE (page table entry):

Code:

7: kd> dt nt!_MMPFN ffff8000e2c4abb8
   +0x000 ListEntry        : _LIST_ENTRY
   +0x000 TreeNode         : _RTL_BALANCED_NODE
   +0x000 u1               : <unnamed-tag>
   +0x008 PteAddress       : ???? 
   +0x008 VolatilePteAddress : ???? 
   +0x008 PteLong          : ??
   +0x010 OriginalPte      : _MMPTE
   +0x018 u2               : _MIPFNBLINK
   +0x020 u3               : <unnamed-tag>
   +0x024 NodeBlinkLow     : ??
   +0x026 Unused           : ??
   +0x026 Unused2          : ??
   +0x027 ViewCount        : ??
   +0x027 NodeFlinkLow     : ??
   +0x028 u4               : <unnamed-tag>
Memory read error ffff8000e2c4abdf

The parameter 3 has the bit flip:

Code:

7: kd> .formats 0000400000000000
Evaluate expression:
  Hex:     00004000`00000000
  Decimal: 70368744177664
  Octal:   0000002000000000000000
  Binary:  00000000 00000000 01000000 00000000 00000000 00000000 00000000 00000000
  Chars:   ..@.....
  Time:    Fri Mar 23 11:41:14.417 1601 (UTC + 1:00)
  Float:   low 0 high 2.29589e-041
  Double:  3.47668e-310

If you look at the memory records for the stack at the time of the crash you will see that it shows the page table was being "walked" i.e. searching the table for valid addresses. When it finds an invalid one it throws the crash. I would appreciate it if others can correct me but that is more or less what I understand has happened. In most cases this is due to bad RAM.

Code:

Start memory scan  : 0xffffb2094bc21e08 ($csp)
End memory scan    : 0xffffb2094bc23000 (Kernel Stack Base)

0xffffb2094bc21f18 : 0xfffff8036b88ab79 : nt!MiWalkPageTablesRecursively+0x299
0xffffb2094bc21fa0 : 0xfffff8036b88c740 : nt!MiDeleteVa
0xffffb2094bc21ff8 : 0xfffff8036b88af82 : nt!MiWalkPageTablesRecursively+0x6a2
0xffffb2094bc22048 : 0xfffff8036b84bd00 : nt!MiInsertPageInFreeOrZeroedList+0x190
0xffffb2094bc22068 : 0xfffff8036bbff948 : nt!NonPagedPoolDescriptor+0x8
0xffffb2094bc22080 : 0xfffff8036b88c740 : nt!MiDeleteVa
0xffffb2094bc22088 : 0xfffff8036b85f7d8 : nt!MiReturnNonPagedPoolVa+0x44
0xffffb2094bc220d8 : 0xfffff8036b88af82 : nt!MiWalkPageTablesRecursively+0x6a2
0xffffb2094bc22160 : 0xfffff8036b88c740 : nt!MiDeleteVa
0xffffb2094bc221b8 : 0xfffff8036b88af82 : nt!MiWalkPageTablesRecursively+0x6a2
0xffffb2094bc22240 : 0xfffff8036b88c740 : nt!MiDeleteVa
0xffffb2094bc22248 : 0xfffff8036bd24adf : nt!MiRemoveVadCharges+0x15f
0xffffb2094bc22298 : 0xfffff8036b889497 : nt!MiWalkPageTables+0x1e7
0xffffb2094bc22388 : 0xfffff8036b8853b3 : nt!MiDeleteVad+0x8d3
0xffffb2094bc22538 : 0xfffff8036bbeb000 : nt!MiSystemPartition
0xffffb2094bc22588 : 0xfffff8036b88c740 : nt!MiDeleteVa
0xffffb2094bc22590 : 0xfffff8036b889920 : nt!MiDeleteVaTail
0xffffb2094bc22690 : 0xfffff8036bbeb000 : nt!MiSystemPartition
0xffffb2094bc226b8 : 0xfffff8036bcc4391 : nt!MiCleanVad+0x4d
0xffffb2094bc226e8 : 0xfffff8036bcc41b3 : nt!MmCleanProcessAddressSpace+0x11f
0xffffb2094bc22738 : 0xfffff8036bcc5f28 : nt!ObKillProcess+0x54
0xffffb2094bc22768 : 0xfffff8036bcc3efd : nt!PspRundownSingleProcess+0x129
0xffffb2094bc227b8 : 0xfffff8036bcf38d3 : nt!ExWnfExitProcess+0x4f
0xffffb2094bc227e8 : 0xfffff8036bccbd38 : nt!PspExitThread+0x5ac
0xffffb2094bc22868 : 0xfffff8036b89e23b : nt!KiDeliverApc+0x27b
0xffffb2094bc228e8 : 0xfffff8036bdbb103 : nt!KiSchedulerApcTerminate+0x33
0xffffb2094bc228f8 : 0xfffff8036b89c101 : nt!KiSwapThread+0x2e1
0xffffb2094bc22928 : 0xfffff8036b89e360 : nt!KiDeliverApc+0x3a0
0xffffb2094bc22960 : 0xfffff8036b83caf0 : nt!KiSchedulerApc
0xffffb2094bc229b8 : 0xfffff8036b9ac500 : nt!KiInitiateUserApc+0x70
0xffffb2094bc22af8 : 0xfffff8036b9b8aea : nt!KiSystemServiceExit+0x9f
0xffffb2094bc22b00 : 0xffff9f83fffd8700 :  Trap @ ffffb2094bc22b00

The stack trace:

Code:

7: kd> kL
 # Child-SP          RetAddr           Call Site
00 ffffb209`4bc21e08 fffff803`6b9ea7aa nt!KeBugCheckEx
01 ffffb209`4bc21e10 fffff803`6b88ab79 nt!MiDeleteVa+0x15e06a
02 ffffb209`4bc21f20 fffff803`6b88af82 nt!MiWalkPageTablesRecursively+0x299
03 ffffb209`4bc22000 fffff803`6b88af82 nt!MiWalkPageTablesRecursively+0x6a2
04 ffffb209`4bc220e0 fffff803`6b88af82 nt!MiWalkPageTablesRecursively+0x6a2
05 ffffb209`4bc221c0 fffff803`6b889497 nt!MiWalkPageTablesRecursively+0x6a2
06 ffffb209`4bc222a0 fffff803`6b8853b3 nt!MiWalkPageTables+0x1e7
07 ffffb209`4bc22390 fffff803`6bcc4391 nt!MiDeleteVad+0x8d3
08 ffffb209`4bc226c0 fffff803`6bcc41b3 nt!MiCleanVad+0x4d
09 ffffb209`4bc226f0 fffff803`6bcc3efd nt!MmCleanProcessAddressSpace+0x11f
0a ffffb209`4bc22770 fffff803`6bccbd38 nt!PspRundownSingleProcess+0x129
0b ffffb209`4bc227f0 fffff803`6bdbb103 nt!PspExitThread+0x5ac
0c ffffb209`4bc228f0 fffff803`6b89e360 nt!KiSchedulerApcTerminate+0x33
0d ffffb209`4bc22930 fffff803`6b9ac500 nt!KiDeliverApc+0x3a0
0e ffffb209`4bc229c0 fffff803`6b9b8aea nt!KiInitiateUserApc+0x70
0f ffffb209`4bc22b00 00007ffe`6711d7a4 nt!KiSystemServiceExit+0x9f
10 000000bc`8a2ffba8 00000000`00000000 0x00007ffe`6711d7a4

Without a full dump of kernel memory it's hard to say exactly why the PTE is invalid, but I will echo what @philc43 said, it's most likely a bad DIMM.

Please run memtest86+ over night to check for errors.