WARNING: Overclocking a Bitmain L3+ invalidates the 6 month warranty!

Overclocking is pushing your computing components over the designed clock speed to achieve a faster rating. In the case of over clocking a miner you will increase the hashing speed of the L3+ miner from 504MH/s to what ever the overclock ceiling is of the unit. All computer components have a limit and this limit can vary from unit to unit.

Caution: Overclocking processing components increase risk of component failure, increases power usage and in some cases reduce the life of the component.

WARNING: Did I mention that overclocking a Bitmain L3+ invalidates the Bitmain 6 month warranty!

Disclaimer: Overclock at your own risk,  I am in no way responsible for any damage you may cause to your miner during overclocking.

Preparing to Overclock the Bitmain L3+

Overclocking the L3+ is very easy but this usually also means its very easy to damage your unit. DO NOT increase the miner frequency speed too much too quickly. Take your time and increase in small increments until you find the optimal setting.

You can find the setting under: Miner Configuration > Advanced Settings

L3+ Frequency Setting
L3+ Frequency Setting – Click to Enlarge

The default frequency is 384 giving your miner a speed of 504 MH/s. It is this setting you need to change to increase your hashing power. As you increase the hashing power the electricity the miner uses will also increase.  The idea is to slowly over clock until you find the optimal speed v power usage with the minimal amount of Hardware Errors. This may actually mean reducing the speed a fee frequency settings once you hit that ceiling.

DO NOT jump to a high clock frequency right away, slowly increase and wait for at least 15 minuets for the miner to settle at the new speed. Evaluate the readings and move on if you think its safe.

The table below shows all the variables as I underclocked then overclocked one of my miners.

FrequencyMH/s Per BoardMH/s TotalWattsMH/s Per wattTemp (PCB)Temp (Chip)Fan1 (RPM)Fan2 (RPM)
100321282550.501960784343318002580
200652604490.579064588384018002580
300973886490.597842835404524603270
3251044177000.595714286414524303270
3501154607560.608465608424826403480
3751234908060.607940447434926403480
3781244968150.608588957445029103750
3811255008200.609756098455029103750
3841265048390.600715137465130603840
3871275078550.5929824564651.532103930
391128.2512.88550.5997660824752.7531803930
394128.57514.38600.598023256475334504080
397129.92519.78700.59735632247.553.7533003990
400130.34521.348790.59310580247.755434204080
406133.08532.338900.5981235964854.2535704140
412134.46537.869090.59170517148.7555.2535704110
419136.79547.169230.59280606748.7555.7535704170
425138.82555.269340.59449678849.7556.536004110
431141.26565.019440.5985275424956.2536304140
437142.86571.439640.592769715057.2537204170
444144.85579.399780.59242331351.2558.538404290
450147.4589.599920.59434475851.558.2539304350
456149.6598.3910100.59246534752.2558.7539304320
462150.95603.7610250.58903414652.256039004320
469153.27613.110400.58951923152.2557.2540504410

I stopped overclocking this miner at a frequency of 469 (613MHz) as I was unhappy with the amount of hardware errors the miner started to produce within the 15min test phase. As you can see here one of the boards started to produce Hardware errors. When the miner produces hardware errors it is not sending completed results correctly to your pool and you can end up with a reduction in hashing power at your pool. You want to avoid this if possible. This is when you see a difference in the local hashing speed and the speed the pool is reporting

L3+ Overclock to 613mhs
L3+ Overclock to 613mhs – Click to Enlarge

You will always get some hardware errors even at stock speeds but I like to aim for as little as possible to give me good results on the pool, ensure the life of the miner and give me a little room with the temperatures in case the ambient room temperature should increase.

Overclocking the Bitmain L3+ 504Mh/s Miner – Part 2