Home News How To Fix Blue Screen When Overclocking? 124

How To Fix Blue Screen When Overclocking? 124



Today’s user manual was written to help you if you receive Overclock Blue Screen error 124.

BSoD errors can be caused by poorly written device drivers or faulty hardware, for example: B. Bad memory, power problems, overheating components, or hardware out of specification. In the Windows 9x era, incompatible DLLs or bugs in the operating system kernel can also cause BSoDs.



I will return home


NOT RELATED: This is one of the reasons why I don’t like glossy screens


BIOS voltages look good, perhaps slightly underestimated for the 12 V bus. Install HWmonitor and check the voltages under Windows (they should not go below 11.8 V).

For 2400 MHz, the RAM voltage should be 1.65 V. This could be the BIOS value, and in Windows it will change to 1.65 V, as in the XMP profile. Try loading the XMP profile at 2400 MHz and leaving the memory alone (you won’t see any benefit from overclocking the memory above its 2400 MHz value).

One more thing: if you are overclocking the processor, turn off TURBO in BIOS and gradually increase the processor frequency using the default processor voltage first. If you are unable to switch to higher frequencies, slightly increase the processor voltage and repeat the process. Try not to exceed 1.25 V …

You will find more information here:


http: //www.tomshardware.co.uk/answers/id-2046473/4770k-dz87klt-75k-deepcool-lucifer-overclocking-guide.html

http://www.thinkcomputers.org/intel-ivy-bridge-overclocking-guide/ (Haswell is comparable to Ivy when it comes to overclocking, but it makes more sense to change voltage as it has built-in VRM and power dissipation dramatically increases with overclocking)


(old but gold …)

Remember that each chip has its own overclocking limits. Perhaps 4.7 GHz is too much for this, and lowering the frequency to 4.5 GHz is enough for stable system operation.


Haha, my girlfriend takes pictures of me at work

Common Overclocking BSODs, Including Steps To Mitigate Them!

0x101 = increase vcore
0x124 = first increase / decrease QPI / VTT, otherwise increase / decrease vcore … you need to check to determine which one ison i7 45nm usually means too little VVT ​​/ QPI for Uncore speed
on i7 32nm SB usually means too little vCore
0x0A = RAM / IMC unstable, first increase QPI, e If it doesn’t work, increase vcore
0x1A = memory management error. This usually means a bad ram. Test with Memtest or whatever. Try to increase your ram’s stress0x1E = increase vcore
0x3B = increase vcore
0x3D = increase vcore
0xD1 = QPI / VTT, increase / decrease as needed, may also be unstable RAM, increase RAM voltage
0x9C = QPI / VTT, most likely, but increasing vcore helped in some cases
0x50 = RAM / Frequency or Uncore Multi Multi Unstable timings, increase RAM voltage or adjust QPI / VTT or decrease Uncore if greater than 2x
0x109 = insufficient or too high memory voltage
0x116 = Low I / O Voltage (NB), GPU issue (most common when GPU is running multiple GPUs / overclocking)
0x7E = Corrupted operating system file, possibly due to overclocking. Run sfc / scannow and chkdsk / r

Unless the specific code is listed above, the most complete list of BSODs on the Internet can be found here – http://www.aumha.org/a/stop.php#0x9c

If you find it useful, you can share it, etc.promote on social networks. Exchange is important!