Overclock BSOD continues even when temperature is low.
Overclock BSOD continues even when temperature is low.
I increased my I7 6700 K to 4.5 ghz at 1.35 volts. After running Prime 95 for five seconds, it triggered a BSOD and the temperature reached about 65 degrees Celsius. Is it accurate that newer versions of P95 could be damaging to the CPU? Also, why is my system still experiencing BSOD even with higher voltages and temperatures?
when you increase the clock speed, you might break the setup and hold time rules for the hardware. for instance, each data point is stored using a voltage level, and when a bit switches from zero to one the circuit alters the voltage from low to high. if you boost the speed, the timing of reading the circuit changes, so the voltage may still be unstable. this causes the system to interpret the bit as either a one or a zero during its transition. when this happens, errors appear in the instructions sent to the CPU and faulty memory locations can trigger crashes.
Newer versions of Prime95 do not negatively affect CPUs. The problem lies with releases beyond version 26.6, as they don't match Intel's actual testing procedures. These updates tend to put more stress on the processor, so monitoring temperatures closely is essential. If your PC shows a blue screen, the system is unstable—consider reducing the multiplier and rechecking.
Stability and temperature are almost unrelated in today’s systems.
Thermal issues are rare when it comes to overclocking.
Concerning something being damaging – no. It’s not more damaging than driving a car too hard.
I’d begin anew. First, ensure your RAM meets the specifications. Check if XMP 2.0 is enabled; this will fine-tune timings and frequency. After that, proceed with your CPU.
Adjust the CPU slightly without changing voltage. Verify stability. Reach a point where it triggers a BSOD. Now increase the voltage incrementally. Test stability again. Once stable, return to adjusting the CPU slightly without altering voltage. If instability returns, raise the voltage further.
This process takes time, but after completion you won’t need to worry about it. I favor voltage offsets over manual adjustments.
When you increase the clock speed, you might breach the setup and hold time rules for the hardware components. For instance, each bit is defined by a voltage, and when it switches from 0 to 1, the circuit alters the voltage from low to high. If you boost the speed, the timing of sampling changes and the voltage may not be fully stabilized. This causes the circuit to interpret the bit as either a 0 or a 1 when it's still transitioning, leading to incorrect data being read. Consequently, mistakes appear in the CPU instructions, memory errors occur, and faulty addresses are used, potentially causing drivers to fail. The CPU’s internal memory controller attempts to handle these issues by triggering a bugcheck 0x124 shutdown.
Upon closer inspection of the circuit, it becomes apparent that it functions as intended. Higher clock rates increase error chances, while warmer components also contribute more errors. Overclocking involves many factors; synchronization between connections is crucial to prevent data corruption during cache memory transfers. This synchronization relies on voltage adjustments through a lookup table within the BIOS, which adapts to the clock frequency. Therefore, ensuring your BIOS is current and using updated overclocking software is essential. Older software often misapplies voltages for the intended clock rate.
Occasionally, encountering a bugcheck 0x124 can be resolved by examining memory dumps and reviewing system uptime timers to identify the root cause of shutdowns. Most shutdowns occur due to CPU memory controller detecting a bit error during data transfer inside the cache. In the Windows debugger, you can use the command `!errrec` at the specified address.
If overheating is suspected, checking the system uptime timer will reveal if it exceeds 15 seconds. A low or excessive voltage to the CPU will result in an uptime timer running under 15 seconds. Running `!sysinfo smbios` can display BIOS details, allowing you to compare with the CPU’s release date (search on Google). If the BIOS isn’t aware of your CPU model, it may incorrectly report a higher maximum speed than available.
Frequently, I avoid overclocking and instead aim for a balance—balancing crash risks from errors against acceptable performance before extended sessions. Always restart frequently to prevent errors from persisting in the pagefile after reboots.