Ensured BSOD each time I launch demanding games.
Ensured BSOD each time I launch demanding games.
Thank you for the update. I've included the Minidumps.zip in Google Drive. Here’s the direct link to the folder: https://drive.google.com/file/d/1jjhBMAT...drive_link. I couldn’t locate the Memory.dmp file in C:\Windows, even after enabling hidden files. I searched using "Memory.dmp" but it was taking over 15 minutes. I’ll let you know once it’s resolved.
It seems the situation turned out as expected, but I'm relieved the issue stems from the drive's cloning rather than the hardware. I hope it isn't the GPU or CPU causing it. I attempted to reset the PC, but it displayed an error: "There was a problem resetting your PC." A forum post suggested checking the drive and reinstalling Windows via USB instead. I'll reach out later when I can grab a USB drive and reformat the system.
This file isn't present on your C drive at all. The file explorer didn't find anything.
Initially, I understand this might connect to cloning. I’ll keep that in mind for the rest of the discussion, but I’m focusing here on the basics. The goal is to ensure the system can generate dump files. None of these files come from the Critical_Process_Died crashes, which hints at a storage problem. It can create dump files, but not during that crash. The two dumps from May 6th and April 6th were USB devices labeled "USB\ROOT_HUB30". They might relate to a connected USB controller. This note is included just in case external storage is involved. If Windows moves the page file to an external drive, it can lead to various complications. Execute this command in PowerShell: Get-CimInstance -ClassName Win32_PageFileUsage -Property * To verify if you have any WHEA events. When NVMe issues arise, WHEA logs often appear. If you see any (and they reference storage), it strongly suggests a storage fault. Open Event Viewer, navigate to Windows Logs → System. In the dropdown, select "WHEA-logger". Highlight any events and right-click to save them. Share the file if needed.
Apologies for the late reply. Here's what I get after running the command: It looks like it is using the 980Pro drive. I checked Event Viewer and I indeed have 1 event. I have included it in my Google Drive Folder. Here is the direct link to the file itself: https://drive.google.com/file/d/1uLu4DSa...drive_link I do have to note that I have one external nvme inside an enclosure. It is my E: drive. I never used it to store Windows files, only for work, assignments and game related files. It was previously installed in the first Nvme slot of my motherboard, before it got replaced with the 980Pro. Weirdly enough, Windows also detects my internal AS340 Sata SSD as an external SSD for almost a year now despite it being connected with Sata cables to the internal Sata port on the motherboard. However, this never really caused any issues whatsoever and reseating the cable didn't change anything, therefore I ignored it. That AS340 is also where I originally stored my Windows 11 software for more than 3 years now.