Jump to content
Search In
  • More options...
Find results that contain...
Find results in...


  • Content Count

  • Joined

  • Last visited


This user doesn't have any awards

About althepal01

  • Title


  • CPU
    Intel Core i3-6100 @ 3.70GHz
  • Motherboard
    ASRock Z170 Pro4S
  • RAM
    Corsair Vengeance LPX 8GB DDR4 2666MHz (CMK8GX4M1A2666C16)
  • GPU
    NVIDIA Geforce GTX 1060 3GB
  • Case
    Cooler Master HAF 912
  • Storage
    Seagate 1TB HDD SATA 6Gb/s 64Mb Cache (ST1000DM003)

    ADATA Premier SP550 120 GB 2.5" SATA SSD
  • PSU
    EVGA SuperNOVA 650 Watt G2 Power Supply
  • Display(s)
    Acer Predator XB241H
  • Cooling
    Cooler Master Hyper 212 EVO

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Although isn't kinda weird to make a Motherboard that supports and is intended to BCLK OC yet have an NVME slot that doesn't like BCLK OC. I have to look into this more to find out if my motherboard has something that supports NVME with high BCLK OC's.
  2. I didn't know that, good thing I didn't buy one, I was actually thinking of purchasing one to store my games. I'll probably buy a new rig soon and this one is pretty outdated (4 years in use). I'm happy for how long it lasted and after all that Oc's well. Considering I bought this CPU for 78 dollars during Black Friday/Cyber Monday 4 years ago, pretty amazing.
  3. https://forums.tomshardware.com/threads/asrock-motherboard-and-x-boost-sky-oc.2722999/ They probably removed this feature in the newer motherboards because Intel sucks and they complained about it. I even updated my BIOS and found out that with the new update that I could not OC greater than 4.0 GHz. I don't know about those motherboards, but the Z170s with older BIOS versions can utilize the sky boost oc feature to enable much greater OCs.
  4. I know you said officially just messing with you. I got it stable close to 4.4 GHz (4.375 GHz) but I didn't want to run core voltage 1.4V for 24/7 use. Apparently, some people can get their i3-6100s to 4.7 GHz on air with no problem, I doubt they tested for stability. They probably just booted into windows and crash under any stress tests. Then again what's the point to OC to instability and claim you achieved that oc.
  5. It may have something to do with your motherboard not able to bypass the Microcode Intel uses to lock these CPU's or limiting your BCLK to only 102. I used the Z170 Pro4S and I think all Z170s are designed to bypass these microcodes through the "enable x sky boost oc" feature as soon as the system boots. Which motherboard did you use?
  6. Oh really... Toothpaste looks pretty dry to me... Razor blade only costs a dollar (nothing if you have one laying around) and liquid metal just around 10 bucks. While others have gotten their i3-6100s to 4.7 GHz, which is pretty insane, I hit my limit at 4.4 GHz (using the Hyper Evo 212) and decided to settle for a final oc of 4.3 which allowed me to lower my Core voltage to 1.34 - 1.36 V ( load - idle ). I guess I got the bad batch of the silicon lottery. C15 score of 460 and 182 single core. Most importantly, I enjoyed delidding and it was a fun process, not bad for a first-time oc. Unfortunately, my oc was silicon-limited and not temperature limited because my max temps at 4.3 GHz only reached 60 C. I understand your point about low power cpu. It really didn't help my CPU frequency/OC. However, at stock 3.7 GHz I saw max temps decrease 10 degrees under load and after oc'ing I saw max temps decrease 20> degress under load. Pretty good gains nonetheless.
  7. 4.7 GHz on the i3-6100 at 1.2 V is insane! You must have won the silicon lottery. To even get your system to boot with those numbers is really unbelievable. The highest oc that I could get was 4.4 GHz and that was raising the core voltage just below 1.4 V. My chip literally hits it's limit at 4.4 GHz no matter how much I try to raise the voltage within the Intel specified safe range of 1.52 V, I could not get it to even boot at 4.5 GHz and above (I didn't go above 1.42 V for Core voltage). I settled for a 4.3 GHz final overclock, which allowed me to decrease my voltage to 1.36 V idle and 1.34 V at load. This is also with my FCLK(1.162 GHz), Cache(4.3 GHz), and RAM(2943 MHz as well as tightened timings 13-15-15-28-2T-270) oc'ed as well. I still can't believe that you got a 4.7 GHz oc at 1.2 V, unless CPU-z did not read your voltage correctly, that is quite out of the ordinary. Clearly, 4.7 GHz at 1.2V is not going to run stably let alone boot. And yes, BCLK overclock increases not only CPU speed but also FCLK, RAM, and Cache. I was not able to isolate FCLK frequency(only three settings in UEFI 400, 800, & 1000 MHz) multipliers and Cache multipliers. However, RAM I was able to decrease frequency as I was increasing BCLK. I later OC'ed RAM from its stock 2133 MHz and above its XMP Profile of 2666 MHz to 2964 MHz with shortened timings as stated above. I had to increase DRAM, VCCIO, & VCCSA ( 1.39 V, 1.24 V, & 1.25 V ) voltages to achieve overall stability as well. My stock 3.7 GHz CB15 score was 387 pts. A 26 point difference, let's say 6 points for the difference of 73 MHz. A 20 point difference, you definitely won the silicon lottery or maybe I just got the worst of the batch. I got a 460 score oc'ed and 182 single core. I'm quite the opposite, I don't really care about AVX performance. I only game, stream videos, code, and browse. At the same time, I admit that I don't know which applications actually utilize AVX and depend on that to the extent that if I disable AVX it won't run efficiently or very slow. As for the temperature problem, i3-6100 definitely gets really hot once you increase the voltage which is inevitable for higher oc's. In fact, I could not sustain a 4.2 GHz oc without hitting max temperatures of 63-66 degrees at idle on HWiNFO and keep in mind that HWinfo doesn't report actual core temps and the reported package temperatures were probably giving me a margin of error of 5-10 degrees Celsius (according to a yt video made by Der8auer on OC'ing the i3-6100). So, I didn't dare try to even stress test 4.2 GHz knowing that the temperatures would sky rocket to above 80 degrees on HWiNFO. Luckily there was a solution for that, DELIDDING!!! So I went out and spent 14 dollars on the good ole liquid metal thermal compound conductonaut. Along with a simple performance razor blade for less than a dollar. Now, the safest option would be to go purchase that 40 dollar delidding tool, however, it's not worth spending 40 dollars for a kit I'm only going to probably use once. Anyways the razor blade did the job, no scratches and the process went by very smooth, not too bad for the first time delidding. I actually enjoyed delidding a lot more than the actual OC, it was fun! Before and after photos: After delidding, my temps at idle under stock 3.7 GHz didn't go down much just a mere 1-2 degrees at idle however under load/stress tests max temps went down 10 degrees at 3.7 GHz. Now OC'ed to 4.3-4.4GHz at 1.36 - 1.40 V under stress tests like RealBench (I have found this test to the most stressful, heats up the system the most, and also throws blue screens much quicker if your oc is not stable), Prime95, & IntelBurnTest the system held up a whopping max temperature of 60 degrees. Keep in mind all these temps were recorded on HWinfo, however I do recommend using a digital multi-meter as HWiNFO is not reliable when reading voltages sometimes underestimating and sometimes overestimating voltages. While Temperature you can always assume a 10 degree margin of error for CPU core temps. That was impressive, I probably achieved a 20 or more degree temperature drop as a result of delidding, given that at idle 4.2 GHz I was experiencing max temps at 66 degrees.
  8. Very quick and simple question, should I delid after or before overclocking? Or does it even matter at all?
  9. I didn't test my CPU at 3.7GHz on CineBench R15 before I overclocked so I will need to restore CPU back to 3.7 and test it to tell if the scores are higher. My goal is to try to get my CPU to overclock to 4.4GHz if possible given that I have a basic cooler Hyper 212 EVO. I am trying to keep my voltage and temps as low as possible while keeping stable. I have tried to OC to 4.4GHz with voltage around 1.375-1.395 range and it booted into windows and I noticed my CPU temps was unstable fluctuating from 30 C to 61-63 C at idle and it eventually blue screened several times just sitting idle. Maybe 4.25 is the max I can achieve with this CPU, given my CPU cooling and how old my system is (around 3-4 years). My performance is being limited by having a single channel memory, which I should have thought about when I bought this PC but it was my first build.
  10. I am using Cinebench R20. I don't know what AVX means but you're probably right about that. I will go ahead and test it with Cinebench R15. Here is a screenshot in the meantime of CPUz and Hwinfo64. Thanks for the quick response, I was expecting not to get an answer for weeks. First time using these types of forums.
  11. So, I just overclocked my cpu(non-k Skylake in 2020) to 4.25GHz and ram to 3067mHz and when I run 3DMark, it is reporting my stock core clock at 3.2 and maximum turbo core clock at 4.25. Why is it not reporting my stock core clock at 3.7? Cinebench R20 does something similar. Cinebench reports my CPU with this title, "2C/4T @ 3.2 GHz, Intel Core i3-6100 CPU" in the Rankings Table. Before the overclock my Cinebench was reporting 3.7, and surprisingly my score was higher before I overclocked my cpu. That was not the case for 3DMark, as my score greatly increased on 3DMark after the overclock. I would appreciate someone's expertise on this :)))))))))) Operating System: Windows 10 build 17763 (64-bit) CPU Type: Intel Core i3-6100 @ 3.70GHz Number of CPUs: 1 Cores per CPU: 2 Hyperthreading: Enabled Motherboard: Z170 Pro4S Memory: 8GB Corsair CMK8GX4M1A2666C16 Videocard: NVIDIA GeForce GTX 1060 3GB Hard Drive: ADATA SP550 (120GB) Hard Drive: ST1000DM003-1SB102 (1TB)