Full Diagnostic Tree & Step-by-Step Overview
When does the IRQL_NOT_LESS_OR_EQUAL BSOD primarily occur on your gaming system?
- During heavy 3D gaming or GPU stress testing, citing drivers like nvkfltm.sys, amdkmdag.sys, or dxgkrnl.sys.
- Randomly at desktop idle or during memory-intensive tasks, without referencing a specific driver file.
- Immediately upon launching competitive multiplayer games protected by kernel anti-cheat (Easy Anti-Cheat, BattEye, Vanguard).
- During network-intensive gaming or high-bandwidth downloads, citing ndis.sys, netio.sys, or vendor Wi-Fi drivers.
GPU/Graphics Subsystem Crash. What specific error or module behavior is observed?
- Minidump cites nvkfltm.sys or amdkmdag.sys after updating graphics drivers or changing GPU power states.
- BSOD accompanied by screen tearing, visual artifacts, or GPU TDR (Timeout Detection and Recovery) resets.
- Crash occurs specifically when third-party GPU software (Afterburner, RGB sync, overlay hooks) is active.
- System crashes when PCIe Resizable BAR (ReBAR) or Hardware-Accelerated GPU Scheduling (HAGS) is enabled.
Corrupted Display Driver Kernel Handshake (`nvkfltm.sys` / `amdkmdag.sys`)
Solution:
Root Cause: Graphics Driver Kernel-Mode IRQL Violation
This crash occurs when a corrupted GPU driver attempts to access pageable memory at an invalid Interrupt Request Level (IRQL). Overwrites during routine driver updates often corrupt kernel handles in dxgkrnl.sys.
# Diagnostic Verification:
1. Open WinDbg or BlueScreenView.
2. Load the latest dump file from C:\Windows\Minidump.
3. Check if BugCheck 0xA specifies nvkfltm.sys, amdkmdag.sys, or dxgkrnl.sys.
# Step-by-Step Fix:
1. Clean Driver Removal in Safe Mode:
Boot into Windows Safe Mode.Run Display Driver Uninstaller (DDU) to wipe GPU drivers and shutdown.2. Install Clean WHQL Driver:
Boot normally and install the latest WHQL driver directly from NVIDIA or AMD.3. Reset Shader Cache:
Clear %LocalAppData%\NVIDIA\DXCache or AMD shader cache.# Prevention & Long-Term Monitoring:
Avoid installing beta drivers and use DDU when switching GPU vendor hardware.
PCIe Bus Power State Transition & VRAM Memory Instability
Solution:
Root Cause: VRAM Timing Mismatch or PCIe Power State Drop
Under load, GPU VRAM or PCIe bus power drops can force the display driver to access memory out of sequence, triggering a kernel IRQL fault.
# Diagnostic Verification:
1. Run OCCT or FurMark GPU Memory Stress Test.
2. Monitor HWInfo64 for VRAM errors or voltage dips on the +12V PCIe rail.
# Step-by-Step Fix:
1. Reseat GPU and Power Cables:
Ensure PCIe power cables are independent dedicated lines (avoid daisy-chains).2. Force Prefer Maximum Performance:
In NVIDIA Control Panel / AMD Software, set Power Management to *Prefer Maximum Performance*.3. Lower VRAM Clock:
Apply a -100MHz underclock to VRAM using MSI Afterburner to verify stability.# Prevention & Long-Term Monitoring:
Maintain adequate PSU headroom for GPU transient power spikes.
Third-Party Overlay Filter Driver Ring-0 Interception
Solution:
Root Cause: Kernel Hook Conflicts from Monitoring Overlays
Software like RivaTuner Statistics Server or RGB utilities inject hooks into the DirectX/Vulkan graphics pipeline at IRQL levels reserved for the OS kernel.
# Diagnostic Verification:
1. Check Event Viewer -> Application logs for crashes referencing RTSSHooks64.dll or RGB services.
# Step-by-Step Fix:
1. Update or Disable Overlays:
Update RTSS/Afterburner to the latest version or set application detection level to *None*.2. Disable Unnecessary RGB Services:
Stop background lighting services in services.msc.# Prevention & Long-Term Monitoring:
Limit active kernel-level monitoring software during competitive gaming sessions.
PCIe Resizable BAR / HAGS Memory Addressing Collision
Solution:
Root Cause: ReBAR / HAGS Base Address Register Overlap
Enabling Resizable BAR alongside Hardware-Accelerated GPU Scheduling can exhaust contiguous memory mapping allocations on certain motherboard platforms.
# Diagnostic Verification:
1. Check if disabling ReBAR in BIOS or HAGS in Windows Settings stops the BSOD.
# Step-by-Step Fix:
1. Toggle HAGS Off:
Go to Settings -> System -> Display -> Graphics -> turn off Hardware-accelerated GPU scheduling.2. Update Motherboard BIOS:
Flash the latest BIOS build to improve AGESA/microcode ReBAR compatibility.# Prevention & Long-Term Monitoring:
Verify motherboard vendor ReBAR compatibility lists before enabling large-BAR addressing.
Random / Idle Memory Crashes. What is the current system RAM configuration?
- System runs XMP, EXPO, or manual memory overclocks above JEDEC baseline (e.g., DDR4-3600+, DDR5-6000+).
- Mixed RAM kits or 4-DIMM configurations used on high-frequency DDR5 platforms.
- Physical RAM module hardware failure or memory slot socket contamination.
- CPU VDDCR / System Agent (VDD_SA) voltage droop under transient memory controller loads.
XMP / EXPO Overclock Instability & Signal Degradation
Solution:
Root Cause: Extreme Memory Profile Signal Timing Drift
XMP/EXPO profiles push memory timings beyond JEDEC specifications. Minor voltage fluctuations can cause bit flips, triggering an IRQL crash when the kernel reads page files.
# Diagnostic Verification:
1. Run MemTest86 or TestMem5 (Anta777 profile).
2. Errors detected within early loops indicate memory instability.
# Step-by-Step Fix:
1. Disable XMP/EXPO:
Enter BIOS and load default JEDEC profile.2. Increase DRAM / SOC Voltage:
If keeping XMP active, bump DRAM voltage slightly (e.g., 1.35V to 1.36V) or SOC voltage safely.3. Update BIOS:
Install motherboard firmware updates to improve AGESA / Memory Reference Code (MRC).# Prevention & Long-Term Monitoring:
Always test new memory overclocks with dedicated stress tools before daily use.
4-DIMM Topology Channel Load & Memory Controller Saturation
Solution:
Root Cause: High Dual-Rank / 4-DIMM Signal Bus Loading
Populating all four RAM slots on consumer platforms drastically increases load on the CPU Integrated Memory Controller (IMC), making high XMP frequencies unstable.
# Diagnostic Verification:
1. Test with 2 DIMMs in recommended slots (A2/B2). If stable, 4-DIMM bus loading is confirmed.
# Step-by-Step Fix:
1. Use 2-DIMM Configuration:
Prefer a 2x16GB or 2x32GB kit over 4 individual sticks.2. Lower Memory Frequency:
Reduce frequency manually (e.g., DDR5-6000 down to DDR5-5600) when running 4 DIMMs.# Prevention & Long-Term Monitoring:
Stick to matched 2-stick memory kits for optimal high-frequency stability.
Physical RAM Memory Bit Corruption & Hardware Fault
Solution:
Root Cause: Defective Memory Transistor Cells
Physical degradation in DRAM chips causes random bit flips that corrupt kernel data structures.
# Diagnostic Verification:
1. Run Windows Memory Diagnostic (mdsched.exe) or MemTest86.
2. Persistent errors at stock JEDEC speeds confirm physical RAM failure.
# Step-by-Step Fix:
1. Isolate Bad Stick:
Test each RAM stick individually in slot A2.2. RMA / Replace Defective Memory:
Replace damaged RAM sticks under manufacturer warranty.# Prevention & Long-Term Monitoring:
Ensure proper ESD safety when handling hardware components.
CPU VDDCR_SOC / VDD_IMC Transient Voltage Droop
Solution:
Root Cause: Memory Controller Voltage Starvation
When transitioning from load to idle, CPU SOC voltage can droop below the threshold required to maintain register states in the memory controller.
# Diagnostic Verification:
1. Check HWInfo64 logs for VDDCR_SOC or VDD_IMC voltage drops right before crashes.
# Step-by-Step Fix:
1. Adjust Load-Line Calibration (LLC):
In BIOS, set CPU SOC LLC to a medium setting to prevent transient droop.2. Set Fixed Voltage Offset:
Apply a small positive offset (+0.025V) to VDD_IMC / SOC in BIOS.# Prevention & Long-Term Monitoring:
Avoid aggressive negative Curve Optimizer offsets without stability testing idle transitions.
Kernel Anti-Cheat Triggered Crash. Which anti-cheat system or file is identified in the crash report?
- Easy Anti-Cheat (`EasyAntiCheat_KM.sys`) or BattEye (`BEDaisy.sys`).
- Riot Vanguard (`vgk.sys`) or Ricochet Anti-Cheat.
- Windows Virtualization-based Security (VBS) / Hypervisor Code Integrity (HVCI) conflict.
- System crashes only when launching games alongside third-party anti-virus or firewall software.
Easy Anti-Cheat / BattEye Kernel Service Corruption
Solution:
Root Cause: Anti-Cheat Kernel Filter Driver Hook Fault
Anti-cheat drivers execute at Ring 0 to block injection. If their service files are corrupted, they query protected memory addresses improperly, causing an IRQL crash.
# Diagnostic Verification:
1. Minidump files directly name EasyAntiCheat_KM.sys or BEDaisy.sys as the faulting module.
# Step-by-Step Fix:
1. Repair Anti-Cheat Service:
Navigate to the game's EasyAntiCheat directory and run EasyAntiCheat_Setup.exe -> select Repair.2. Verify Game File Integrity:
Verify integrity of game files via Steam / Epic Games Launcher.# Prevention & Long-Term Monitoring:
Keep anti-cheat client applications updated through their respective official game launchers.
Riot Vanguard Kernel Service (`vgk.sys`) Drivers Handshake Lock
Solution:
Root Cause: Boot-Start Kernel Driver Synchronization Failure
Riot Vanguard initializes at system boot. Interference from debugging tools or outdated motherboard software can trigger kernel panics.
# Diagnostic Verification:
1. Crash logs identify vgk.sys during system boot or game startup.
# Step-by-Step Fix:
1. Reinstall Vanguard:
Uninstall Riot Vanguard via Settings, then relaunch Valorant to force a fresh download.2. Disable Conflicting Background Tools:
Turn off legacy monitoring utilities like Asus Armoury Crate services.# Prevention & Long-Term Monitoring:
Ensure TPM 2.0 and Secure Boot remain properly enabled in BIOS for Vanguard compliance.
HVCI / Hypervisor Memory Integrity Protection Trap
Solution:
Root Cause: Memory Integrity Driver Block
Hypervisor-Protected Code Integrity (HVCI) blocks unsigned drivers from executing in high-priority memory space, forcing kernel panics if older anti-cheat modules try to load.
# Diagnostic Verification:
1. Check Windows Security -> Core Isolation -> Memory Integrity status.
# Step-by-Step Fix:
1. Update Non-Compliant Drivers:
Use Windows Update or vendor sites to update legacy drivers flagged by Core Isolation.2. Toggle Memory Integrity:
Temporarily test with Memory Integrity turned off to confirm driver incompatibility.# Prevention & Long-Term Monitoring:
Only use signed, modern drivers certified for Windows 11.
Third-Party Security Suite Network/Storage Filter Driver Conflict
Solution:
Root Cause: Dual Kernel Filter Driver Interception Lock
Third-party antivirus programs install filesystem filter drivers that conflict with kernel anti-cheat hooks trying to scan the same memory buffers.
# Diagnostic Verification:
1. Minidump lists antivirus filter drivers (e.g., epfw.sys, bdntwrk.sys) alongside anti-cheat modules.
# Step-by-Step Fix:
1. Add Game Exclusions:
Add game and anti-cheat directories to your antivirus exclusion list.2. Revert to Windows Defender:
Uninstall third-party antivirus utilities to rely on native Windows Security.# Prevention & Long-Term Monitoring:
Windows Defender provides robust security without introducing kernel filter driver collisions.
Network Subsystem Crash. What network interface or driver is implicated?
- Intel / Realtek Ethernet driver (`e2f68.sys`, `rt640x64.sys`) crashing during online gaming downloads.
- Wi-Fi adapter driver (`Netwtw10.sys`, `mtkwlex.sys`) crashing during packet bursts.
- Network packet prioritization software (Motherboard ROG GameFirst, Killer Control Center) active.
- Virtual TAP/TUN network adapters or VPN protocol drivers active during gaming.
Realtek / Intel Ethernet Controller Driver Buffer Overflow
Solution:
Root Cause: LAN Driver Receive Side Scaling (RSS) Memory Leak
Outdated LAN drivers can fail to process high packet rates under heavy throughput, causing memory allocation failures at high IRQLs.
# Diagnostic Verification:
1. Minidump specifies e2f68.sys, e1d68x64.sys, or rt640x64.sys.
# Step-by-Step Fix:
1. Install Generic Vendor Drivers:
Download clean driver packages directly from Intel or Realtek, avoiding OEM bloatware.2. Disable Energy Efficient Ethernet:
In Device Manager -> LAN Adapter Properties -> Advanced, disable *Energy Efficient Ethernet* and *Green Ethernet*.# Prevention & Long-Term Monitoring:
Keep network drivers updated directly from chip manufacturers.
Wi-Fi Adapter Power Management & Dynamic Frequency Selection Fault
Solution:
Root Cause: Wireless Driver Power State Desynchronization
Wi-Fi adapters entering low-power sleep states during active network requests can crash kernel network queues (ndis.sys).
# Diagnostic Verification:
1. Minidump points to Netwtw10.sys (Intel Wi-Fi) or mtkwlex.sys (MediaTek Wi-Fi).
# Step-by-Step Fix:
1. Disable Wi-Fi Power Saving:
In Device Manager -> Wi-Fi Adapter -> Power Management, uncheck *Allow the computer to turn off this device to save power*.2. Update Wi-Fi Firmware:
Download the latest wireless driver suite from Intel or your motherboard support page.# Prevention & Long-Term Monitoring:
Prefer wired Ethernet connections for lower latency and better stability during gaming.
Network Prioritization Software (Killer / GameFirst) Filter Lock
Solution:
Root Cause: Packet Shaping Filter Driver Crashes
OEM network utility suites install NDIS intermediate filter drivers to prioritize gaming packets, which frequently introduce memory leaks under heavy load.
# Diagnostic Verification:
1. Event Viewer shows crashes tied to KNetKb.sys or KFA.sys.
# Step-by-Step Fix:
1. Uninstall OEM Network Suites:
Uninstall Killer Control Center, ASUS GameFirst, or MSI LAN Manager via Settings.2. Install Driver-Only Package:
Install bare INF network drivers without utility software suites.# Prevention & Long-Term Monitoring:
Avoid installing companion software suites for network cards.
Virtual VPN TAP / TUN Driver Buffer Exhaustion
Solution:
Root Cause: Virtual Network Adapter Memory Leaks
VPN software uses virtual network adapters (TAP/TUN drivers) that can crash under heavy UDP gaming traffic if packet buffer queues overflow.
# Diagnostic Verification:
1. Crash occurs only while connected to a VPN service.
# Step-by-Step Fix:
1. Change VPN Protocol:
Switch protocol inside your VPN app (e.g., from OpenVPN to WireGuard).2. Reinstall Virtual Adapters:
Reinstall the VPN application to refresh its virtual network adapter drivers.# Prevention & Long-Term Monitoring:
Use modern protocols like WireGuard for higher throughput and lighter kernel footprints.