I've been experiencing frequent blue screen of deaths (BSODs) on my Lenovo LOQ 15AR9 laptop, to the point where I can't even download Windows from a USB stick anymore—the only thing I can access is the BIOS. It all started with Hyper-V errors, which progressed to IRQL errors, kernel errors, and issues with storage, among other codes. I tried swapping the SSD with a different one to rule that out, but the BSODs persisted. Whenever I attempt to install a fresh version of Windows, it either freezes or leads to another BSOD, especially during the boot process. I've reseated the RAM, tested each stick individually, and switched their positions, but nothing seems to work. I'm looking for advice on how to identify which component might be faulty so I can either give up and assume it's the CPU or consider buying new RAM sticks.
5 Answers
First, you should gather the dump files from BSODs if you can boot into Windows or Safe Mode. Check the C:WindowsMinidump directory for any files and zip them. You can upload them to a file-sharing site for further analysis. Having multiple dump files helps to pinpoint the issue better. If you’re not able to get to Windows at all, then we might need to look at the hardware directly.
I'm betting on the RAM being the issue since CPUs typically fail completely. Try running Memtest86 to test your RAM. Another thing you can try is downclocking the RAM in BIOS to see if that improves stability. It could help if the memory is unstable due to overclocking.
Diagnosing issues in a laptop can be tricky. If this were a desktop, I would check the power supply voltages first since incorrect values can cause crashes. If the power supply is fine, clean the RAM pins to ensure a good connection. If you still have issues, there’s a good chance it could be a motherboard problem. Testing the GPU in another computer could also help pinpoint if that's an issue.
To determine if it's the CPU or RAM, you can test the RAM sticks one at a time. If the crashes continue with both sticks, then it likely isn't the RAM. Regarding your initial Hyper-V errors, if you suspect they're related to the CPU, the dump files could provide more insight. Look out for any non-maskable interrupts (NMIs)—they can often indicate hardware issues, with the CPU being a usual suspect alongside memory or storage.
Memtest has passed so far. Are there other USB-bootable tools for testing CPUs?