Idle temps don't make the least bit of difference, at all, to anything, unless the idle temps are like in the upper 40's or in the 50's. And if they are, then there is a problem.
Anything below 40°C at idle is fine. Of course, lower is better, but it really has no effect on what the load temps will be. Idle temps are largely related to what the ambient temperature is in the room, while load temps are strictly related to the cooling system, clock speed and voltage applied.
What are your load temps while running Prime95 version 26.6 on Small FFT option for 15 minutes?
I'm going out on a limb and say you will error out because I think your overclock is unrealistically high and your voltage is too low to be stable. I have one of the best 6700k's I've come across as judged by what I've seen 100's of others be able to achieve with theirs, and at 4.8Ghz I have to run like 1.4v to be stable. At 4.5Ghz I have to run 1.325v for stability. I'd bet you will find your OC is not stable running at that voltage. Run Prime95 and find out. It will also tell you if you are staying within the correct thermal envelope. If your temps go past 80°C while running Prime95, then you need to reduce your overcock because you sure as hell can't reduce the voltage any more.
Use HWinfo (NOT HWmonitor or Openhardware monitor, or any of the utilities that come with any of your hardware. They are pretty much all crap and are usually not accurate at all) to keep an eye on thermals and take screenshots of the CPU thermal sensors after about ten minutes, if it makes it that long. Post the results here. HWinfo or CoreTemp are the most accurate of all the utilities for monitoring that are out there. I actually like CoreTemp better, so it's up to you which one you use.
HWinfo:
https://www.hwinfo.com/download.php
Core Temp: http://www.alcpu.com/CoreTemp/
Prime95 v26.6 is THE primarily accepted way to do the majority of baseline stability and thermal limit testing running the Small FFT option.
Prime95 version 26.6:
http://windows-downloads-center.blogspot.com/2011/04/prime95-266.html
Further, as explained to me and many others on this forum by Computronix, who has far more experience with CPU architectures and testing procedures than 95% of the people you will ever meet, speak to or read about. He is also the author of the Intel temperature guide, found here:
http://www.tomshardware.com/forum/id-1800828/intel-temperature-guide.html
This pretty well sums things up and is equally relevant whether working with an Intel or an AMD system.
I can think of several reasons why x264 encoding or AVX / AVX2 / FMA3 apps won't work as a unilateral metric for thermal testing.
(1) A steady-state workload gives steady-state temperatures; encoding does not.
(2) Simplicity in methodology; most users would find encoding apps unfamiliar and cumbersome to accomplish a simple task.
(3) Most users such as gamers never run any apps which use AVX / FMA, so adaptive or manual voltage aside, it makes no sense to downgrade your overclock to accommodate those loads and temps.
(4) Standardization; Prime95 has been around since 1996; many users are familiar with it.
For the minority of users who routinely run AVX / FMA apps, then P95 v28.5 can be useful tweaking BIOS for thermal and stability testing.
regardless of architecture. P95 v26.6 works equally well across all platforms. Steady-state is the key. How can anyone extrapolate accurate Core temperatures from workloads that fluctuate like a bad day on the Stock Market?
I'm aware of 5 utilities with steady-state workloads. In order of load level they are:
(1) P95 v26.6 - Small FFT's
(2) HeavyLoad - Stress CPU
(3) FurMark - CPU Burner
(4) Intel Processor Diagnostic Tool - CPU Load
(5) AIDA64 - Tools - System Stability Test - Stress CPU
AIDA64's Stress CPU fails to load any overclocked / overvolted CPU to get anywhere TDP, and is therefore useless, except for giving naive users a sense of false security because their temps are so low.
HeavyLoad is the closest alternative. Temps and watts are within 3% of Small FFT's.