{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by Apple:
9/17/2021 10:35:23 PM
3
Blue Screen - WHEA_UNCORRECTABLE_ERROR
Like a few other people, I've been having the same BSoD issue ever since the second week of Season 15. Things I've tried:
- Updating drivers
- Rolling drivers back
- Installing windows updates
- Reinstalling drivers
- Verifying game files
- Reinstalling the game
- Reinstalling BattlEye
- Reseating every piece of hardware in the PC and cleaning for dust
- Checked RAM for corruption and faults
- Checked boot drive health and health of other hard drives
- Changing NAT types
- Antivirus scans
- System file diagnostics
- BIOS update
- Ensured that Windows Driver Verifier was disabled
- Ensuring that the system is not thermal throttling or overheating (the PC is not overclocked)
Every piece of hardware is working exactly how it it was working in the months leading up to the current season (minus driver updates). The only thing that has changed was the update to the game. As sure as I am that a reinstall of Windows may fix the problem, I'm more interested in finding out why such a drastic step would be necessary and exhausting all the possible steps and solutions before putting myself in a situation where I may potentially lose important data.
I know that the WHEA_UNCORRECTABLE_ERROR is supposed to be a hardware error and that if it were truly the case there isn't much Bungie can do. But with several people having the same issue, some with even higher-end PCs than I, there has to be a connection. It seems strange to me a hardware issue would manifest at around the same time for seemingly separate people. A lot of people are pointing fingers at the implementation of BattlEye and while I don't necessarily agree I would like to point out that Rainbow Six: Siege never blue screened my PC.
I haven't seen a way to upload MEMORY.DMP files and I'm not sure if Destiny 2 had any sort of crash logs but if there is some other source of information that I, or others, can submit please let me know.
My DxDiag from the most recent crash:
https://pastebin.com/bnpixmsF
EDIT 9/17/2021:
It looked promising yesterday after the hotfix but I got another crash today. This time WinDbg listed OverWolf as the source of the crash, I think. Strange seeing as its an addon manager for other games but what do I know? Uninstalled it and giving it another go.
DxDiag for the most recent crash:
https://pastebin.com/1gsx7Vpg
-
I was also thinking is wasn't battle eye as some point just bc rainbow works for me as well. However, the game "Unturned" uses battle eye or you can play without it. I tried with battle eye and it bluescreens every time without fail, then without battle eye it works 100% of the time. I am inclined to believe battle eye is so imbedded into the systems as it starts, that if it detects anything it does not like, it just blue screens the computer. I have been trying for a few weeks now and it sometimes works. To conclude, battle eye was not the way to go if they have no idea how to use it.
-
1 ReplyEverytime I’ve seen this error it usually comes from a failed drive or partition on the drive causing corruption
-
1 ReplyI'm not sure if this is relevant or not to your specific issue but give this a shot and see if it helps.
