The system experienced an IRQL BSOD during the launch of Valorant.
The system experienced an IRQL BSOD during the launch of Valorant.
Hello everyone, I'm not quite sure what's happening or which program might be responsible for this problem. Recently, when launching Valorant, I encountered a BSOD with IRQL_NOT_LESS_OR_EQUAL. This is the only game that triggers this issue. I've run SFC and MEMTEST both without any problems, and I've confirmed all drivers and Windows are up to date, yet the problem persists. I'm attaching my pastebin with the minidump for reference. I don't fully understand it myself, but any assistance would be greatly appreciated.
Welcome to the forums, newcomer!
Recently when I go to launch Valorant it BSOD with IRQL_NOT_LESS_OR_EQUAL.
Try and uninstall the game, then manually reinstall it and see if the issue persists. There's also an anti-cheat module/installer for the game, uninstall that and see if the issue persists.
You might want to include the .dmp files if you have access to them, for us to see them ourselves.
We will need additional info. Please list the specs to your build like so:
CPU:
CPU cooler:
Motherboard:
Ram:
SSD/HDD:
GPU:
PSU:
Chassis:
Monitor:
include the age of the PSU apart from it's make and model. BIOS version for your motherboard at this moment of time.
I completed a Pastebin with the dump file. The hardware seems fine, but I have a Ryzen 7700x with a 4060ti and 16GB RAM, plus 32GB of DDR5 memory.
https://pastebin.com/4SRA46zW
Upload the dump files directly, excluding the analysis output.
The analysis goes beyond the basic output of analyze -v, representing just the initial phase. Always ensure you upload the dump files when dealing with a BSOD, and include all relevant dumps for a more accurate diagnosis.
I believe this BSOD is likely linked to insufficient RAM. There were no third-party drivers mentioned before the bugcheck, which suggests a hardware issue. Moreover, the process running at that time was memory-related. During the bugcheck, the Windows memory manager was removing a working set and updating the PTE, but the problem occurred when the page table lock was acquired due to an invalid memory reference...
Code:
0: kd> .frame /r 3
03 ffffd50c`3c29e8c0 fffff804`a438933b nt!MiLockPageTableInternal+0x121
rax=0000000000020000 rbx=ffffa18015d85b20 rcx=ffffe60df5c134c0
rdx=ffffe60df5c134c0 rsi=fffffc7e3f00f000 rdi=ffffe60df4649b30
rip=fffff804a4389471 rsp=ffffd50c3c29e8c0 rbp=ffffe60df5c134c0
r8=fffffc7e3f1f8000 r9=fffffc7e3f1f8fff r10=0000004000000000
r11=ffff7f78eae00000 r12=fffffc0380000000 r13=fffffc0000000000
r14=0000000000000001 r15=fffffc7e3f00e000
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00040286
nt!MiLockPageTableInternal+0x121:
fffff804`a4389471 488b1e mov rbx,qword ptr [rsi] ds:002b:fffffc7e`3f00f000=????????????????
The RSI register pointed to memory (likely the lockword) generated an invalid reference, which triggered the bugcheck. The probable reason points to faulty RAM, so I recommend a RAM diagnostic...
Download
Memtest86 (free), use the extracted imageUSB.exe tool from the download to create a bootable USB with Memtest86 (1GB is sufficient). Perform this on another PC if possible, as you can't fully rely on your current system.
After booting the USB, run Memtest86; it should begin immediately. If no errors appear after completing four iterations of the 13 tests in the free version, restart Memtest86 and repeat the process. Even a single bit error indicates failure.
By the way, the RAM you installed—two 16GB sticks from G.Skill (F5-6000J3238F), 4800MHz)—is not listed for your Gigabyte B650 GAMING X AX V2 motherboard. Although this doesn't guarantee compatibility, it signals that these units haven't been thoroughly verified and may not be fully suitable. Non-QVL RAM often raises concerns when BSODs are RAM-related.
I can handle that, though during the memtest built-in to Windows 11 it reported no problems with my RAM. Valorant is the only game where this occurs.
I see this occurred shortly after installing the ethernet adapter. Might the Realtek driver be the cause?