Windows error occurs during startup.
Windows error occurs during startup.
This BSOD has been occurring for some time. I've attempted various solutions recommended for ntoskrnl crashes. Dates when these BSODs appeared: 01/05/24, 17/04/24, 23/03/24, 20/03/24. Computer details: ASUS ROG STRIX - G15 Model NO.: G513QY-SG15.R96800, running MS Windows 11 Home - 10.0.22631, Build 22631, AMD Ryzen 9 5980HX, AMD Radeon RX 6800M. MOBO: ASUSTeK G513QY. Purchased 11/23. Attached minidumps for the listed dates are included. Files: 050124-14312-01.dmp.txt, 041724-15375-01.dmp.txt, 032324-16281-01.dmp.txt, 032024-14296-01.dmp.txt
Hello. The Asus Armoury Crate is installed and active in BIOS? If yes, obtain the uninstall tool for Armoury Crate. Before proceeding with uninstallation, switch to BIOS and turn off Armoury Crate. https://www.asus.com/supportonly/armoury crate/helpdesk_download/ If you have any customization changes in RAM, disable DOCP/XMP. If PBO is enabled, set it to auto. Restart the system and apply updates: https://www.amd.com/en/support/download/drivers.html
Check the C:\Windows\Minidump directory for any minidump files. If present, move the entire folder to the Downloads folder on your desktop (or use OneDrive if available). Compress the copied folder and send it along with the instructions. Follow all steps carefully as Windows restricts file handling there.
Apologies for the mistake. I noticed after sharing that I uploaded the incorrect files... my error. The proper dump files are included. minidumps.zip
I was busy handling things during the exam period, so details are fuzzy. I think I tried some basic fixes like checking drivers and ended up deleting an ASUS bloatware app, though I can't recall its name. It didn’t seem to help. I’m really sorry for the confusion.
These issues point to a storage memory problem, probably involving the page file. It behaves similarly to RAM, so checking which drive it uses is important. You can run a PowerShell command to identify the drive: Get-CimInstance -ClassName Win32_PageFileUsage -Property * The faulty drive would likely be the one with the issue.
I only have that one SSD (Intel SSDPEKNU512GZ), so that addresses the issue. I installed Windbg, examined the dump file, and discovered a relevant thread using the failure bucket ID. I'm attempting to use it now.