F5F Stay Refreshed Software Operating Systems Error BSOD - IRQL Not Less or Equal

Error BSOD - IRQL Not Less or Equal

Error BSOD - IRQL Not Less or Equal

R
rexcow1
Junior Member
Find
15
02-19-2021, 05:47 PM
#1
Hi Folks,
My partner's computer has been encountering a number of BSODs, mainly IRQL Not Less or Equal, though prior to the BIOS update, I was also seeing Hypervisor Errors, though Hyper-V was not installed. There doesn't seem to be any rhyme or reason to them, regardless of system load or uptime. This is a fresh Windows 11 install from early August. Machine hardware is as follows:
Motherboard: Asus Prime B450M-A (BIOS 4202)
CPU: AMD Ryzen 5-3600
RAM: Silicon Power 32GB (16GBx2) XPOWER Turbine Gaming DDR4 3200MHz
SSD1: Samsung 970 EVO Plus 2TB NVMe
SSD2: Crucial MX500 2TB SATA
GPU: Nvidia GTX 1060 6GB
Troubleshooting Steps are as follows:
Updated BIOS from 4002 to 4202 (There are some changed BIOS settings for Secure Boot, Fastboot Off, CSM Off. I don't have the machine in front of me to check at the moment)
Ensured latest drivers from AMD Download/Support Tool
Clean Uninstall/Reinstall of Nvidia Driver using DDU
Checked SSD Firmware/Drivers via Samsung Magician & Crucial Storage Executive
Removed iCue Software/Driver
Ran DISM Scan/Check/RestoreHealth - OK
Ran SFC /Scannow - OK
Ran Chkdsk C: /F - OK
Enabled Driver Verifier for all Non-MS drivers (Special pool, Force IRQL checking, Pool tracking, Deadlock detection, security checks, Miscellaneous checks, Power framework delay fuzzing, DDI compliance checking)
Recorded 5 Minidumps once Verifier was enabled:
https://1drv.ms/f/s!AhbbggDci1sCnaxSxCfL...g?e=oyyQxN
The RAM and SSDs are the only recent changes, but they do line up with the new OS install. It's possible that it's bad RAM, but I haven't sat down to run Memtest86+ against it. Barring that, I'm running out of ideas.
Reply
Reply
R
rexcow1
02-19-2021, 05:47 PM #1

Hi Folks,
My partner's computer has been encountering a number of BSODs, mainly IRQL Not Less or Equal, though prior to the BIOS update, I was also seeing Hypervisor Errors, though Hyper-V was not installed. There doesn't seem to be any rhyme or reason to them, regardless of system load or uptime. This is a fresh Windows 11 install from early August. Machine hardware is as follows:
Motherboard: Asus Prime B450M-A (BIOS 4202)
CPU: AMD Ryzen 5-3600
RAM: Silicon Power 32GB (16GBx2) XPOWER Turbine Gaming DDR4 3200MHz
SSD1: Samsung 970 EVO Plus 2TB NVMe
SSD2: Crucial MX500 2TB SATA
GPU: Nvidia GTX 1060 6GB
Troubleshooting Steps are as follows:
Updated BIOS from 4002 to 4202 (There are some changed BIOS settings for Secure Boot, Fastboot Off, CSM Off. I don't have the machine in front of me to check at the moment)
Ensured latest drivers from AMD Download/Support Tool
Clean Uninstall/Reinstall of Nvidia Driver using DDU
Checked SSD Firmware/Drivers via Samsung Magician & Crucial Storage Executive
Removed iCue Software/Driver
Ran DISM Scan/Check/RestoreHealth - OK
Ran SFC /Scannow - OK
Ran Chkdsk C: /F - OK
Enabled Driver Verifier for all Non-MS drivers (Special pool, Force IRQL checking, Pool tracking, Deadlock detection, security checks, Miscellaneous checks, Power framework delay fuzzing, DDI compliance checking)
Recorded 5 Minidumps once Verifier was enabled:
https://1drv.ms/f/s!AhbbggDci1sCnaxSxCfL...g?e=oyyQxN
The RAM and SSDs are the only recent changes, but they do line up with the new OS install. It's possible that it's bad RAM, but I haven't sat down to run Memtest86+ against it. Barring that, I'm running out of ideas.

Reply
Reply
E
EdenMarie
Member
Find
190
02-23-2021, 10:45 PM
#2
I believe it's the RAM. All the dumps fail for the same reason, though in different situations...
Code:
FAILURE_BUCKET_ID: AV_STACKPTR_ERROR_nt!SwapContext
A stack pointer error doesn't always point to a RAM problem, but it strongly suggests one. No third-party drivers were involved in any of the dumps, which also points toward a hardware issue.
One of the dumps provides further insight...
Code:
FAILURE_BUCKET_ID: 0x1E_c0000005_R_STACKPTR_ERROR_nt!SwapContext
This exception code indicates a memory access violation. If you simply replaced the RAM, that would be the starting point. Try swapping in the old RAM and see if the issue resolves. Alternatively, remove one stick of the new RAM to test. If it still doesn't work, swap the other stick and try again.
You might consider using a memory tester—Memtest86 is recommended. Given you have ample RAM, removing a stick seems like the most reliable approach.
Have you verified that the RAM is fully compatible with your motherboard?
Reply
Reply
E
EdenMarie
02-23-2021, 10:45 PM #2

I believe it's the RAM. All the dumps fail for the same reason, though in different situations...
Code:
FAILURE_BUCKET_ID: AV_STACKPTR_ERROR_nt!SwapContext
A stack pointer error doesn't always point to a RAM problem, but it strongly suggests one. No third-party drivers were involved in any of the dumps, which also points toward a hardware issue.
One of the dumps provides further insight...
Code:
FAILURE_BUCKET_ID: 0x1E_c0000005_R_STACKPTR_ERROR_nt!SwapContext
This exception code indicates a memory access violation. If you simply replaced the RAM, that would be the starting point. Try swapping in the old RAM and see if the issue resolves. Alternatively, remove one stick of the new RAM to test. If it still doesn't work, swap the other stick and try again.
You might consider using a memory tester—Memtest86 is recommended. Given you have ample RAM, removing a stick seems like the most reliable approach.
Have you verified that the RAM is fully compatible with your motherboard?

Reply
Reply
Y
YourBoyAndrew
Junior Member
Find
30
03-13-2021, 01:38 AM
#3
Thanks for checking! I was also thinking that way, but I wasn’t sure it was the right direction.
We replaced the old RAM last night, and it looks like it might have helped, though we won’t be certain until this evening.
I’ll need to run more tests to figure out if the problem is with compatibility, faulty components, or something else like improper installation or dust in the contacts.
Reply
Reply
Y
YourBoyAndrew
03-13-2021, 01:38 AM #3

Thanks for checking! I was also thinking that way, but I wasn’t sure it was the right direction.
We replaced the old RAM last night, and it looks like it might have helped, though we won’t be certain until this evening.
I’ll need to run more tests to figure out if the problem is with compatibility, faulty components, or something else like improper installation or dust in the contacts.

Reply
Reply