Hey everyone! I'm really struggling with my Lenovo LOQ 2024 laptop—I've had 5 Blue Screen of Death (BSOD) crashes in the last 5 days, each happening unexpectedly while I was doing different tasks. I checked my BlueScreenViewer log and noticed that all the crashes are pointing to `ntoskrnl.exe`, which I've read is a core Windows process but not usually the root cause of the problem.
These crashes started occurring right after I upgraded my RAM from 16GB to 32GB, and the trouble began after I installed some Adobe software. My laptop seems to boot and run fine for a while but then randomly freezes and displays the BSOD. One strange occurrence was when I closed my laptop and later found it had restarted because of a BSOD during sleep mode.
I ran a Windows Memory Diagnostic and it came back clean. In the Event Viewer, I found a recurring Bluetooth-related error that says the Bluetooth driver expected a specific HCI event size but didn't get it. I've tried updating my NVIDIA and Bluetooth drivers and even flashed the BIOS, but nothing has worked. I disabled Bluetooth too, but I still got another BSOD after several hours of flawless use. In the most recent crash, the Event Viewer showed a new error regarding the Warsaw Technology service terminating unexpectedly. I'm not sure if that's the actual cause.
I'm at my wit's end! Any thoughts on what could be causing these BSODs and how to fix them? What steps can I take next to troubleshoot?
1 Answer
It sounds like you're having a pretty frustrating time with those BSODs! From what you described, it seems like a memory issue could be at the heart of this. Sometimes, the memory controller in the CPU might fail, which can lead to crashes that the system attributes to memory issues. Even though your memory test came back clean, I’d suggest testing your RAM sticks one at a time. Just use one stick and see if the crashes continue; if one stick seems faulty, it'll crash, and if crashes happen with either one, it may point to the CPU instead.
Also, make sure nothing is overclocked or undervolted, as that could be a culprit too!
Do you think it's a good idea to run Memtest86 for a thorough check?