My ASUS TUF Gaming A15 (FA506IU, BIOS FA506IU.320) keeps crashing with IRQL_NOT_LESS_OR_EQUAL, KMODE_EXCEPTION_NOT_HANDLED, and several other stop codes. The crashes can happen while browsing, idle, gaming, or coding, and I've lost work because of them. The system runs Windows 11 Home 64-bit build 26200 with a Ryzen 7 4800H, GeForce GTX 1660 Ti, 16 GB of RAM, a 256 GB WDC SN530 SSD, a 1 TB Seagate hard drive, and a Realtek 8822CE wireless adapter. I have several minidumps available for analysis. What hardware or driver should I investigate first?
3 Answers
The dump pattern does not strongly point to the SSD or hard drive; storage-related crashes usually identify a storage driver in at least some of the dumps. Memory can also mean the CPU’s integrated memory controller or another driver overwriting memory, not just defective RAM. Remove all performance tweaks and test the system with each RAM stick individually. Standard memory tests can miss intermittent DDR4 faults, so practical one-stick testing is useful.
Ryzen 7 4800H systems have been reported to develop failures that appear as random memory-related blue screens. As a diagnostic workaround, limiting the processor’s performance or power can sometimes reduce the crashes, although it lowers performance and is not a permanent repair. If the crashes continue with stock settings and each RAM module tested separately, the CPU or motherboard may need professional diagnosis or replacement.
The crashes look more like memory corruption than a straightforward storage failure. Start by disabling any XMP, overclocking, or undervolting. If the laptop has two RAM modules, run it with one module at a time and swap slots if possible. If only one module causes crashes, that module is likely faulty; if both behave the same way, the CPU’s memory controller could be involved. Also consider removing or updating low-level software such as ASUS hardware utilities, Ryzen Master components, VirtualBox or HAXM drivers, Npcap, TAP networking, and old NVIDIA, AMD, virtual-bus, or storage drivers.
Checking the memory settings first makes sense. Disabling XMP and testing each module separately should help distinguish unstable settings from a bad component.