Screen issues after BIOS update during overclocking
Screen issues after BIOS update during overclocking
I have a z370-p motherboard with an i5 8600k CPU. After updating my BIOS to 2801, when I overclock, I encounter bluescreens. I have turned off the overclocking in the BIOS. I'm wondering if this is normal and whether it's a hardware issue or just related to the BIOS update. The blue screen displayed was WHEA uncorrectable error and DPC watchdog violation.
Kind regards,
I transitioned from the previous BIOS release.
Components include: PSU Corsair RMX 750X Modular 80 PLUS GOLD V2, i5 8600k, GTX 1070 ti, 32gb DDR4 3200mhz RAM, and Noctua NH-D15.
The system also features an ASUS Prime Z370-P.
Do you have a standard performance reference? Which parts are you boosting? How much are you raising each component? Are you applying excessive voltage?
Only CPU. I was able to overclock with the earlier BIOS without issues, both at v1.335 at 4.8ghz and 5ghz at 1.415v. Now I experience a blue screen after doing this. I also passed the Prime95 test for about 1-2 hours, but the blue screens occur randomly. I didn’t have this problem with my previous BIOS version.
Have you checked the release notes for the Bios update?
These updates often involve microcode changes to support newer CPUs, particularly on older boards.
It's likely that using your CPU at high voltage has reduced its performance. It might no longer be able to reach the intended overclock.
Occasionally, software updates can cause significant overclocking (adjustments). This needs to be considered. A few updates ago, I experienced an Uncore Voltage offset of -0.03v. After updating the BIOS and resetting the CMOS—this board handled it automatically—I entered the BIOS and applied my custom settings from a pendrive, then restarted. The device failed to boot and displayed an orange LED indicating RAM issues.
[panik]
After several minutes of adjusting Vcore, cache, and uncore voltages individually, I noticed the update successfully lowered the uncore voltage to its minimum value; even at -0.001v it didn’t work. Therefore, I reset the offset to zero.
It seems we’re starting from scratch—everything needs re-testing because we don’t know what changes were made.
What others have said is also valid: 1.415v is quite high for Intel’s 14nm chips. If your LLC setting was unusually high—often due to following a beginner’s guide or not paying close attention—the Vcore might have been even higher.
Since you’re using an Asus board, the levels were likely set between 1 and 7/8. Levels 4 or 5 should be safe for air-cooled VRMs...
I’m getting ahead of myself—depends on how long you ran that 5.0ghz at 1.415v setting. In short: after the BIOS update, OC stability is compromised.
Current settings are no longer reliable.
Voltage degradation has become noticeable. Either this frequency can’t be sustained, or you’ll need to apply even more voltage—which isn’t advised.
I'm at the ATM trying to optimize with 4.7ghz at 1.27v and using LLC at level 4. Hope you're doing well.
I'm currently running Prime95 stress tests.
Are there any additional BIOS settings I should adjust?
I'm still just a beginner learning about the CPU.
A friend helped me with OC, but we did it at level 7.
I'm hoping the system stays stable at this current setting.
Prime95 isn’t a trustworthy tool for checking CPU voltage. It’s more suitable for evaluating the efficiency of the CPU cooler. Cinebench R23 is a better option for assessing Vcore performance. It’s challenging to express this clearly without referring to CompuTronix’s Intel Temperature Guide: https://forums. According to Intel’s datasheets, TDP and thermal specs are confirmed “without AVX”. When Prime95 runs with AVX enabled, it assigns an excessive 130% workload, potentially raising core temperatures by up to 20°C. To ensure Prime95 accurately simulates your CPU under full load, select the AVX test options that aren’t grayed out, verifying all three AVX boxes as needed. More details on AVX instruction sets will follow later. Tools that avoid overloading or underloading the processor will provide a reliable thermal baseline. A comparison of utilities categorized by thermal and stability tests is shown below, based on TDP percentages across six Intel generations at default settings, rounded to the nearest 5%: Figure 11-2. These evaluations cover workloads from 70% to 130% of TDP. However, Windows Task Manager treats every test as 100% CPU usage, which reflects processor activity rather than actual %TDP load. Core temperatures are influenced by power draw (Watts), which depends on the workload. Prime95 Small FFTs with AVX disabled deliver the appropriate workload for thermal analysis. If core temps stay below 80°C, your CPU should handle demanding real-world tasks without overheating. Thanks to CompuTronix for the guidance.