WHEA_UNCONTROLLABLE_ERROR BSOD when playing Destiny 2
WHEA_UNCONTROLLABLE_ERROR BSOD when playing Destiny 2
The BSOD (Blue Screen of Death) with the WHEA_UNCONTROLLABLE_ERROR message is consistently triggered when playing Destiny 2 on your system. This indicates a hardware-related issue, specifically related to memory management or CPU interaction during graphically intensive tasks. Here’s a breakdown and potential solutions based on the provided information:
The system encountered a fatal microarchitectural error due to an internal timer malfunction (Proc 4 Bank 4). This resulted in a specific hexadecimal status code indicating a critical hardware failure. The root cause is likely related to overheating or power supply issues, potentially exacerbated by incompatible drivers. Diagnostic steps include monitoring processor temperatures, verifying BIOS voltage settings against specifications, and investigating potential driver conflicts that might be contributing to the instability.
I received a PM asking me to reflect on why I might not have gotten any answers. I'm not sure what other info I could've given, and there isnt anyone to tell me what else I could offer.
This document outlines a common issue encountered when updating the BIOS on an ASRock Fatal1ty Z97X Killer motherboard. The core problem stems from outdated BIOS firmware, specifically version P1.00 dated 04/24/2014, failing to correctly manage voltage and clock rates for the CPU. This can lead to a system crash reported as a “bugcheck” due to excessive voltage application. The solution is to update the BIOS to the latest version (v2.60 dated March 2018), which incorporates revised voltage tables optimized for the CPU’s specifications released in June of 2014. The older BIOS, created prior to the release of the CPU, does not accurately reflect current requirements and causes instability. The updated BIOS addresses this mismatch by providing an appropriate voltage setting that aligns with the CPU's design, resolving the crash and ensuring stable operation.
johnbl :
the bugcheck info indicates that the cpu called a bugcheck because of a internal problem. Most likely the wrong voltage was being applied for the clock rate.
the first fix attempt would be to update your bios version from the p1.00 version dated 04/24/2014
to the current one v 2.60 dated march of 2018
the most likely cause of this bugcheck is the old bios is applying too high of a voltage to the cpu.
your cpu came out june of 2014 and uses a lower voltage than the cpus that were released before it.
you bios came out 4/2014 and will have the wrong voltage/clock rate table.
the bios update should fix the problem.
I think this is the motherboard:
https://www.asrock.com/MB/Intel/Fatal1ty...x.asp#BIOS
Oh I feel dumb. I had no idea you had to update your bios. Makes sense though. I will work out how to do that and update on whether its still crashing once I have.
That is the correct motherboard as far as I can tell.
Here’s a rewritten version of the text, aiming for clarity and flow:
The system is experiencing a recurring crash indicated by the WHEA-UNCONTROLLABLE_ERROR blue screen error. This typically occurs after approximately one hour of usage. Initial troubleshooting focused on updating the motherboard BIOS from version P1.00 (dated 04/24/2014) to version 2.60 (dated March 2018), as an outdated BIOS can cause incorrect voltage settings for the CPU. The affected motherboard is an ASRock Fatal1ty Z97X Killer.
Despite the BIOS update, the crashes persist with the same error code. Furthermore, debugging tools, specifically Windbg, have stopped functioning correctly and are no longer installable via the Windows Store, preventing the creation of readable dump files.
A dump file has been provided (http://s000.tinyupload.com/?file_id=0787...3959098716) and is being offered as a potential resource for analysis, although the inability to utilize Windbg presents a challenge.
The bugcheck information indicates that the CPU called a bugcheck because of a internal problem. Most likely the wrong voltage was being applied for the clock rate. The first fix attempt would be to update your bios version from the p1.00 version dated 04/24/2014 to the current one v 2.60 dated march of 2018. The most likely cause of this bugcheck is the old bios is applying too high of a voltage to the cpu. Your CPU came out June of 2014 and uses a lower voltage than the cpus that were released before it. Your bios came out 4/2014 and will have the wrong voltage/clock rate table. The bios update should fix the problem. I think this is the motherboard: https://www.asrock.com/MB/Intel/Fatal1ty...x.asp#BIOS Okay I updated the bios, and everything with that went fine, but I’m still crashing and getting the same WHEA_UNCONTROLLABLE_ERROR BSOD after about an hour of playing. On top of that the debugger I was using (Windbg) stopped working and now wont install off the windows store anymore so I’m don't know how to make any new dump files readable. Here’s the dump file itself. http://s000.tinyupload.com/?file_id=0787...3959098716 Let me know if there’s a better way to get you that file in the future. Chris.freshmaker : johnbl : the bugcheck info indicates that the cpu called a bugcheck because of a internal problem. Most likely the wrong voltage was being applied for the clock rate. the debugger I was using (Windbg) stopped working and now wont install off the windows store anymore so I'm don't know how to make any new dump files readable. Here’s the dump file itself. http://s000.tinyupload.com/?file_id=0787...3959098716 most of these issues will mess up virus scanners and usb devices, streaming software and the gpu but should not cause this bugcheck. again none of these would normally cause this bugcheck. but it can not hurt to do the updates. you should also change your memory dump type to kernel and provide the next kernel memory dump. it will include info on your hardware, the timer tables and the internal error logs. the file will be stored as c:\windows\memory.dmp (different directory and file name) most of these issues will mess up virus scanners and usb devices, streaming software and the gpu but should not cause this bugcheck. again none of these would normally cause this bugcheck. but it can not hurt to do the updates. you should also change your memory dump type to kernel and provide the next kernel memory dump. it will include info on your hardware, the timer tables and the internal error logs. the file will be stored as c:\windows\memory.dmp (different directory and file name)