My Lenovo IdeaPad Gaming 3 Type 82EY has been randomly freezing, crashing, and restarting. It has a Ryzen 5 4600H, 16 GB of DDR4-2133 memory, a 256 GB SK hynix NVMe SSD, integrated AMD graphics, a dedicated NVIDIA GPU, Windows 11 Pro, and UEFI firmware. The crashes produce different errors, including IRQL_NOT_LESS_OR_EQUAL (0xA), UNEXPECTED_KERNEL_MODE_TRAP with a DOUBLE FAULT (0x7F), and SYSTEM_THREAD_EXCEPTION_NOT_HANDLED mentioning FLTMGR.SYS (0x7E). It has also frozen at the Windows welcome screen and during restarts. One dump referenced nt!MiLockOwnedProtoPage, while another double-fault dump did not identify a specific third-party driver. I have already reinstalled Windows and drivers, updated the chipset, graphics, and Wi-Fi drivers, removed and reinstalled the Wi-Fi device, tried Safe Mode, disconnected an external hard drive, checked Reliability Monitor, and analyzed several minidumps. Windows Setup itself also crashed with an unexpected restart error while attempting a fresh installation. MemTest86 is currently running from a USB drive and has not reported errors so far, although the test is not complete. What should I test next to determine whether the problem is faulty RAM, the NVMe drive, the motherboard or BIOS, or a driver issue?
2 Answers
The variety of crashes, freezes outside normal Windows use, and the installer failing all point more toward hardware than a single driver. Reset the BIOS to its defaults, then test each RAM module separately rather than testing both together. Also check the SSD or temporarily install to a known-good replacement drive. If possible, boot a Linux live USB; instability there would further support a hardware problem. Back up important files first, since drive and BIOS troubleshooting can make existing data inaccessible.
If Windows is still usable, collect all files from C:WindowsMinidump and review several dumps together rather than relying on one failure bucket. Different stop codes can result from memory corruption, so the driver named in an individual dump may only be a victim. Configure Windows to create small memory dumps if it is not already doing so, then compare the results after each hardware change.
I tested the memory modules individually and found that one was defective. I replaced the SSD with a 512 GB drive and replaced the RAM with a single 32 GB module. Windows installation is currently running, so I am waiting to see whether the system remains stable.