• Happy holidays, folks! Thanks to each and every one of you for being part of the Tom's Hardware community!

[SOLVED] IRQL BSOD when launching Valorant ?

Toggle sidebar Toggle sidebar
C

Cynscapes

Nov 12, 2024
21
0
20
Hello all, I am not to sure what is going on or what program may be causing this issue. Recently when I go to launch Valorant it BSOD with IRQL_NOT_LESS_OR_EQUAL. This is the only game to do this. I have done SFC and MEMTEST both are good with no issues. I have also made sure all drivers and windows is up to date but still get the issue. I am attaching the pastebin with my minidump. I personally don't understand it. Any and all help is appreciated.

https://pastebin.com/4SRA46zW
 
Sort by date Sort by votes
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.
 
Upvote 1 Downvote
I did a Pastebin with the dump I doubt the hardware is not the issue, but I have a Ryzen 7700x with a 4060ti 16gb, an 32gb ram ddr5 https://pastebin.com/4SRA46zW (minidump)
Lutfij said:
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.
Click to expand...
 
Last edited:
Upvote 0 Downvote
Thanks for that, dump analysis is way more detailed than just the output of analyze -v, that's just the starting point. Always upload the dump files when seeking help with a BSOD, and upload all the relevant dump files too, the more dumps we have the better the diagnosis.

I think this BSOD is most likely down to bad RAM. There are no third-party drivers called in the lead-up to the bugcheck and that's a good indication of a hardware cause. In addition, the operation in progress at the time of the bugcheck was memory (RAM) related. The Windows memory manager was trimming a process working set and updating the PTE to reflect the trim, the bugcheck happened when the page table lock was obtained and was caused by 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 used to point into memory (probably at the lockword) results in an invalid memory reference (indicated by the ????????????????) and that's why you had the bugcheck. The most likely cause for this is bad RAM, so I suggest you run a RAM test...
  1. Download Memtest86 (free), use the imageUSB.exe tool extracted from the download to make a bootable USB drive containing Memtest86 (1GB is plenty big enough). Do this on a different PC if you can, because you can't fully trust yours at the moment.
  2. Then boot that USB drive on your PC, Memtest86 will start running as soon as it boots.
  3. If no errors have been found after the four iterations of the 13 different tests that the free version does, then restart Memtest86 and do another four iterations. Even a single bit error is a failure.
BTW: The RAM you have installed, two sticks of G.Skill 16GB F5-6000J3238F16G, clocked at 4800MHz, are not on the QVL for your Gigabyte B650 GAMING X AX V2 motherboard. Whilst that doesn't mean they won't work it does mean they've not been tested and validated as fully compatible. Non-QVL RAM always raises a red flag when we see BSODs that are potentially RAM related.
 
Upvote 0 Downvote
ubuysa said:
Thanks for that, dump analysis is way more detailed than just the output of analyze -v, that's just the starting point. Always upload the dump files when seeking help with a BSOD, and upload all the relevant dump files too, the more dumps we have the better the diagnosis.

I think this BSOD is most likely down to bad RAM. There are no third-party drivers called in the lead-up to the bugcheck and that's a good indication of a hardware cause. In addition, the operation in progress at the time of the bugcheck was memory (RAM) related. The Windows memory manager was trimming a process working set and updating the PTE to reflect the trim, the bugcheck happened when the page table lock was obtained and was caused by 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 used to point into memory (probably at the lockword) results in an invalid memory reference (indicated by the ????????????????) and that's why you had the bugcheck. The most likely cause for this is bad RAM, so I suggest you run a RAM test...
  1. Download Memtest86 (free), use the imageUSB.exe tool extracted from the download to make a bootable USB drive containing Memtest86 (1GB is plenty big enough). Do this on a different PC if you can, because you can't fully trust yours at the moment.
  2. Then boot that USB drive on your PC, Memtest86 will start running as soon as it boots.
  3. If no errors have been found after the four iterations of the 13 different tests that the free version does, then restart Memtest86 and do another four iterations. Even a single bit error is a failure.
BTW: The RAM you have installed, two sticks of G.Skill 16GB F5-6000J3238F16G, clocked at 4800MHz, are not on the QVL for your Gigabyte B650 GAMING X AX V2 motherboard. Whilst that doesn't mean they won't work it does mean they've not been tested and validated as fully compatible. Non-QVL RAM always raises a red flag when we see BSODs that are potentially RAM related.
Click to expand...
I can do that that but when i did the memtest built in to windows 11 it said there was no issues with my ram plus valorant is the only game this happens on
 
Upvote 0 Downvote
I ran Memtest86 and it passed no errors. By any chance could it be microsoft hyper-v thats causeing the issue. Can resetting windows like a fresh install work?
 
Last edited:
Upvote 0 Downvote
A security update for Defender isn't going to cause BSODs, otherwise we'd all be having problems. In addition, if you reinstalled Windows and you still get BSODs then it's a hardware issue - and most likely RAM as I've said.

Hopw did you reinstall? Did you use the Windows Reset feature (which is NOT a resinstall) or did you clean install from bootable media?

Also, you weren't very forthcoming whaen asked for detailed system specs in post #2, so I'll ask again...
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.

We need exact details, like mnotherboard model, exact RAM type(s), make and model of SSDs, make an model of GPU, etc. etc.
 
Upvote 0 Downvote
ubuysa said:
A security update for Defender isn't going to cause BSODs, otherwise we'd all be having problems. In addition, if you reinstalled Windows and you still get BSODs then it's a hardware issue - and most likely RAM as I've said.

Hopw did you reinstall? Did you use the Windows Reset feature (which is NOT a resinstall) or did you clean install from bootable media?

Also, you weren't very forthcoming whaen asked for detailed system specs in post #2, so I'll ask again...
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.

We need exact details, like mnotherboard model, exact RAM type(s), make and model of SSDs, make an model of GPU, etc. etc.
Click to expand...
Again im new to this how ever i fixed my issue thanks
 
Upvote 0 Downvote
CPU:Ryzen 7770x
CPU cooler: liqn li acl360 aio
Motherboard: Gigabyte b650 gaming x ax v2
Ram: 32gb ram g.skill flare x4
SSD/HDD: 2 inland ssds one is 500 the 9ther is a 2tb
GPU: nvidia 4060 ti 16gb
PSU: super Leadex III
Chassis: montech air 903
Monitor: MSI 32 in curved monitor forgot model

Im trying to figure out the exact update i rolled back to fix my issue
 
Upvote 0 Downvote
I was wrong on what 2 updates i rolled back i reinstalled them to get a picture then uninstalled them again

2024-11 Cumulative Update for Windows 11 Version 24H2 for x64-based Systems (KB5046617)

And

Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.421.322.0) - Current Channel
(Broad)

I uninstalled these and issue was fixed game works and no crashes
 
Upvote 0 Downvote
ubuysa said:
A security update for Defender isn't going to cause BSODs, otherwise we'd all be having problems. In addition, if you reinstalled Windows and you still get BSODs then it's a hardware issue - and most likely RAM as I've said.

Hopw did you reinstall? Did you use the Windows Reset feature (which is NOT a resinstall) or did you clean install from bootable media?

Also, you weren't very forthcoming whaen asked for detailed system specs in post #2, so I'll ask again...
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.

We need exact details, like mnotherboard model, exact RAM type(s), make and model of SSDs, make an model of GPU, etc. etc.
Click to expand...
I don't get how its a ram issue if after i uninstalled updates fixed my issue
 
Upvote 0 Downvote
That is a bit vague don't you think? The writer doesn't name the update, they just say the 'latest' update and that's going to be different for many people. I'm always wary of posts like this that contain no external links as evidence of what they're saying.

Still, you seem happy so I'll move on.
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom