Gigabyte AERO 16 YE5 experiences crashes, BSODs, and screen issues accompanied by a buzzing noise.
Gigabyte AERO 16 YE5 experiences crashes, BSODs, and screen issues accompanied by a buzzing noise.
I bought this laptop in Canada and have been residing in Southeast Asia for six months now. It began showing problems just one month after purchase. The screen would freeze or glitch with a loud buzzing noise at random moments. If it didn’t freeze, a BSOD would appear with numerous error messages, mostly the “Memory Management” issue. I sent it back for replacement in Thailand, and after waiting a month, they returned it. They replaced several parts and upgraded the internal components—originally an XE5 model with an i7-12700K CPU and 3070 Ti GPU. They gave me a YE5 motherboard along with new parts: an i9-12900HK processor and a 3080 Ti GPU. After using it for a couple of days post-repair, the screen still froze. I was really frustrated. One month later, many components were replaced, but the problem continued. I tried fixing it myself, but after several failed attempts, someone on Reddit suggested replacing the RAM. I bought new RAM and it seemed to resolve the issue. The laptop worked smoothly for two full months without interruptions. Unfortunately, this fix wasn’t lasting. The display glitch/freeze returned with even stronger force. Could the RAM have become corrupted again? I’ve checked drivers and they’re all up to date. I reinstalled them and still faced the same problem. I’m currently negotiating with Gigabyte Thailand for a solution, but they’re unwilling to let me wait another month. If anyone has suggestions or advice, it would be greatly appreciated. Here’s a video link showing the issue, and I’ve attached a photo for reference.
Visit C:\Windows\Minidump to see if any minidump files exist. If present, return to the Windows directory and transfer the Minidump folder to the Downloads folder (use your desktop if needed). Compress the copied folder and include it in a post. Please adhere strictly to instructions since Windows doesn't allow file changes there.
Thank you for your guidance. The minidump file is included. Feel free to share any additional details you'd like. Minidump.zip
Thanks for your prompt response. It's quite unusual that the RAM I bought recently is causing the same problems I faced earlier. Could another factor be responsible for the defect? I plan to test the RAM sticks individually and will share the findings soon. IMAGE_NAME: ntkrnlmp.exe This file appears in the dump files and is linked to the BSOD I'm experiencing. After reviewing it, it seems to be related to RAM issues. "ntkrnlmp.exe is an executable tied to the Windows OS. When Windows begins, any programs using ntkrnlmp.exe are loaded into RAM and function as part of the NT kernel." Could this be connected to my situation? Appreciate your help.
ntkrnlmp.exe represents the Windows kernel, the essential part of the operating system. In dump files, it doesn’t assign blame directly—it describes what happened and which process triggered the problem or caused the crash. Often, the kernel is involved when RAM issues appear because it manages memory access. Many users assume a kernel fault without examining deeper details. To identify the real cause, examine patterns across multiple dump files and review the stack trace. The stack provides a brief record of events, starting from the bottom and moving upward. In this case, the active process was RuneLite. Image_Name functions similarly to Process_Name but can also reference drivers. Something must signal an issue and initiate the BSOD, as indicated by "KiBugCheckDispatch" in the stack text. A page fault in the virtual memory area points to corruption, prompting a BSOD. Since the page file resides on disk, this could relate to storage problems, though such occurrences are uncommon. It’s unusual for RAM to behave this way, especially after replacing hardware, and the memory controller itself doesn’t appear to be the main culprit.
You're welcome on the topic. I found the information very helpful. I'm currently checking one RAM stick in my laptop to determine if only one is affected. Gigabyte RMA can replace the EOM RAM, so I'll wait for their parts and installation. I'm hoping it won't be a recurring problem. It would have been easier to have older backup files for comparison. Appreciate your clear instructions, Bkatt!
The latest dump file from today was generated despite the laptop crashing several times. Under Event Viewer it appears the dump wasn't saved because of an error. The issue happened while testing a single RAM slot, and it continues after testing both slots. Could you check Event Viewer for more details that might explain the crashes? Thanks again for your support. Minidump.zip
I've included a screenshot showing the EventViewer error related to the dumpfile creation issue. You have two 1TB NVMe SSDs installed in your laptop; I'm uncertain about moving the page file or its location, which will be something you'll explore later. Also, considering removing the C: Drive might help determine if the SSD is faulty. What are your thoughts?