System frequently stops unexpectedly due to unfixable error code WHEA_UNCORRECTABLE_ERROR
System frequently stops unexpectedly due to unfixable error code WHEA_UNCORRECTABLE_ERROR
After the release of starfield, I've experienced strange BSODs that appear consistently. Many crashes don't trigger a blue screen; instead, they seem to wipe what's visible on the screen (refer to the video at the link provided). These issues appear across all games, though some are more frequent than others. I can play multiple MW2 matches without problems, but on Payday 3, I often fail before reaching the menus. I managed to retrieve both minidump and MEMORY.DMP files from the crash in a previous video (linked here). When starfield was updated, I turned on reBar support, enabled above 4G decoding, and activated XMP in my BIOS—though I later reverted those settings. I played around 70 hours of Starfield via Steam before these problems started, suggesting the settings might not be the cause. Still, they are now disabled. I also completely cleared my SSD and reinstalled Windows. A detailed list of my current hardware is available here. I’m aware this isn’t an optimal configuration, and I’ve been inconsistent with upgrades. It was built by me. I used XTU to undervolt the CPU (a change I made around 2019) and later went back to default settings without success. I tried re-seating my memory and SSD, even using compressed air to clear dust, but nothing helped. This could point to a CPU hardware problem, given the BSOD code and the failure_bucket_id in the DMP files (0x124_16_GenuineIntel__UNKNOWN_IMAGE_GenuineIntel.sys). However, I’ve run prime95 for extended periods without issues.
Execute InSpectre, turn off Spectre and Meltdown protections. Next, disable the Multiplane Overlay MPO. Update your GPU with the newest Vbios and install the latest BIOS for the motherboard. Apply the newest chipset drivers. If issues persist, inspect storage for firmware updates and verify its status using Hard Disk sentinel.
While exploring Hard Disk Sentinel, I noticed the "information" section appeared when my SSD was chosen. Each time I pressed the "Short Self-Test: Supported, Click to start" button, the application would pause for a few seconds before displaying a blue error message on the screen.
Seems perfectly ordinary, no surprises in the application. I saved the report and uploaded it here. This passage gives the impression everything is alright—it’s a 2tb T-force CARDEA Z44Q, model TM8FPQ002T0C327. Its product page is available there. The download button leads straight to their support area. On their downloads page, if you narrow it down to their T-FORCE SSDs, none of the listings match. There’s a Windows 7 driver, an installation guide, and a firmware update tool for the z340 SSD, though I’m not certain compatibility exists. That section is accessible via this link.
I don’t have another SSD, but I just ordered a different one. Best buy says it should arrive on Tuesday. If it turns out bad, I’ll try contacting TeamGroup to see if they can fix or replace it. In that case, my chances aren’t great because I removed the “warranty void if removed” label when installing its heatsink. If the SSD still doesn’t work, I’ll keep working on fixing the issue.
I received the Samsung NVMe drive today. After installing, reinstalling, and setting up Windows again, I experienced another BSOD when launching a gamespass game. I searched Samsung's site for drivers or firmware updates and found their NVMe drivers, which I installed successfully. Since then, I haven't encountered a BSOD during actual gameplay (about three hours of playtime). However, I haven't reinstalled the TeamGroup drive yet. Could the Samsung NVMe drivers affect the TeamGroup drive? Should I look for TeamGroup NVMe drivers as well? On their website, I only found Windows 7 drivers, making it hard to locate the correct ones.
It shouldn't happen, and I think I assisted you on Reddit. If the crash linked to Samsung resumes, it might restart again after connecting the Teamgroup, so I'd wait a few days to verify stability.
Yep, You've got the same username on both sites I figured I'd cast the net and see if I could gain some insight from one community that I couldn't from the other. Well, Ill continue using just the Samsung drive for the next week, but for the past ~6 hours I've been using it somewhat heavily without any BSODs In the event that my system remains stable, how will I want to proceed? Would I just reinstall the teamgroup nvme? And will the samsung nvme drivers that I installed work for (or maybe negatively interfere with) the teamgroup drive? Since prior to installing the Samsung nvme drivers, I got a BSOD with just the Samsung drive installed but none since I installed the Samsung nvme drivers, I'm wondering if maybe the issue with the teamgroup drive was also driver related? If that is the case, since I am unable to find any teamgroup nvme drivers, how would I go about solving that issue?