Overclock.net banner

Intel Core i7-6800K Overclocking troubles

20K views 72 replies 11 participants last post by  freaky35 
#1 ·
Hello, everyone!
I have just built my first PC, and I wanted to overclock the CPU, but so far no luck.
I am a complete newbie when it comes to overclocking and I have no idea what I'm doing, I mostly followed youtube videos and online tutorials.
I tried to overclock the i7 6800K to 4.2Ghz and 1.3 voltage, it run stable for 5-6 hours but as soon I started playing overwatch it went blue screen.
The second time I tried to use the settings from this YouTube video: 4.2 Ghz and 1.299 voltage and other custom settings, no luck this time also.
I tried at 4.1 Ghz and 1.225voltage and still no luck, 4.2Ghz and 1.35 and it was the same story, looks like I got the CPU from a bad bin or I totally have no idea what I am doing.

My Specs are:

CPU: Intel Core i7-6800K
MOBO: MSI X99A GAMING 7
COOLING: NZXT Kraken X62
RAM: DDR4 Corsair VENGEANCE LED 32GB (4x8) 2666MHz
GPU: MSI GTX 1080 GAMING X 8G
SSD: Samsung 960 PRO 512GB
HDD: WD Black 2Tb
PSU: Corsair RM850i
and a Dark Base Pro 900 Case from be quiet! (if that matters).

I really hope that someone will be able to help me.
I did few benchmarks but that told me nothing
And I did a stress test using Prime95 and all it told me that there was a fatal error but not why or I just can't understand what it want's.


I kindly ask for your help!
Thanks.
 
See less See more
1 1
#2 ·
Welcome to OCN.

First I advice to run the RAM at stock settings with no XMP enabled and keep the cache at stock and start step by step.
Start the core from 4 GHz (100x40) and put CPU Voltage at 1.2.

If you got BSOD 0x124 or system frooze that usually means you need more Vcore, (try to not go above 1.40V). If that didn't work it means you either reached a wall or your CPU needs more VCCIN/VRIN/ Input Voltage (Max 1.95). The usual BSOD if the VCCIN is too low is 0x101. You might also want to adjust Vdroop to increase stability (Please note this can reduce the life span of the CPU if aggressive level has been selected).

I advice using Asus Realbench and/or custom x264 for stress testing.

RealBench
http://dlcdnmkt.asus.com/rog/RealBench_v2.54RC1.zip?_ga=1.198386863.1687831461.1490305449

Custom x264 stress test.
https://mega.nz/#!ywAFDQQQ!hEQCeRXDKpHoeRYEaspux3ZA9Smx6tp8h0leb7ZHdJo
 
#4 ·
Quote:
Originally Posted by Varcan View Post

Thank you for your fast response!

The RAM that I have is 2666 MHz but my MOBO stock settings are 2133 MHz, should I change it to my RAM frequency or keep it as the MOBO suggest?
I did not enable XMP.
Keep it at 2133 MHz atm to rule out the reason behind BSOD.

We need as less variables as possible to get things under control.

I suggest to start the core from 4 GHz and stress test with realbench/ x264 and conservative vcore setting like 1.2 Vcore and 1.8 Vccin.
 
#5 ·
Quote:
Originally Posted by Varcan View Post

Good summary, look up an OC guide or use common sense. Don't use values found somewhere on the net, that's just plain stupid if you do not know what you're doing.

You can find guides on OCN, AVC and HEVC stress tester is in my signature, the AVC/H264 has been used on OCN for validating overclocks for years.

If I were you, I would return the 6800K + mobo + liquid cooler + 4x8 RAM and get an R7 1700 + AM4 B350 mobo + 2x16 RAM, just my 2 cents.
 
#6 ·
Quote:
Originally Posted by JackCY View Post

Good summary, look up an OC guide or use common sense. Don't use values found somewhere on the net, that's just plain stupid if you do not know what you're doing.

You can find guides on OCN, AVC and HEVC stress tester is in my signature, the AVC/H264 has been used on OCN for validating overclocks for years.

If I were you, I would return the 6800K + mobo + liquid cooler + 4x8 RAM and get an R7 1700 + AM4 B350 mobo + 2x16 RAM, just my 2 cents.
Can't really return it, got the PC for my job, all was bought by my employer.
 
#7 ·
Quote:
Originally Posted by HeadlessKnight View Post

Keep it at 2133 MHz atm to rule out the reason behind BSOD.

We need as less variables as possible to get things under control.

I suggest to start the core from 4 GHz and stress test with realbench/ x264 and conservative vcore setting like 1.2 Vcore and 1.8 Vccin.
Will try that and post the results.
Thank you!
 
#9 ·
  • Rep+
Reactions: Varcan
#10 ·
Quote:
Originally Posted by HeadlessKnight View Post

Keep it at 2133 MHz atm to rule out the reason behind BSOD.

We need as less variables as possible to get things under control.

I suggest to start the core from 4 GHz and stress test with realbench/ x264 and conservative vcore setting like 1.2 Vcore and 1.8 Vccin.
So, I used those settings and the PC would go straight to BSOD, the BIOS was freezing and couple of times the PC would not even boot, something here is not right,
maybe I have fried something when I was using settings from the internet. I really have no idea what the hell I am suppose to do and what settings to change.
I managed to restore to optimal settings and after few tries the PC booted up, I am getting worried.

This are the settings that i used, following your directions:|



Thank you.
 
#11 ·
Quote:
Originally Posted by Varcan View Post

So, I used those settings and the PC would go straight to BSOD, the BIOS was freezing and couple of times the PC would not even boot, something here is not right,
maybe I have fried something when I was using settings from the internet. I really have no idea what the hell I am suppose to do and what settings to change.
I managed to restore to optimal settings and after few tries the PC booted up, I am getting worried.

This are the settings that i used, following your directions:|



Thank you.
If it froze during BIOS or couldn't boot it means the vcore was too low for the OC, you might need to push it more. Try going to 1.25-1.30.

This is overclocking you discover things through trial and error, if you are not ready/ don't have the heart to do it or have sensitive files in your system that might get corrupt then don't do it.
 
#12 ·
Quote:
Originally Posted by HeadlessKnight View Post

If it froze during BIOS or couldn't boot it means the Vcore was too low for the OC, you might need to push it more. Try going to 1.25-1.30.
The first Overclock I did for that PC was 4.2 and 1.3 Vcore, that worked fine for 8+ hours until it went BSOD while playing a game, all of this is very confusing
frown.gif


Could you also look at the Image that I have uploaded and check if any settings are off/should be changed?

Thank you for your help!
 
#13 ·
Quote:
Originally Posted by Varcan View Post

The first Overclock I did for that PC was 4.2 and 1.3 Vcore, that worked fine for 8+ hours until it went BSOD while playing a game, all of this is very confusing
frown.gif


Could you also look at the Image that I have uploaded and check if any settings are off/should be changed?

Thank you for your help!
You have other variables changed from the video no (@ your old OC)? I opened that video and he put VCCIN to 2.0 which in my opinion is crazy high for 24/7. Asus suggests in my mobos BIOS description to not go above 1.95V at LLC7 and in that video he is running 2.0V with enthusiast +1 Vdroop.

Disable SVID. And try 4 GHz @ 1.25-1.30V If that didn't work and you got freezes during BIOS / boot issues then try increasing VCCIN to 1.85V-1.90V.

After a few resets the BIOS will usually start in fail safe mode and ask you to adjust your overclock but if that didn't work you might want to clear your CMOS.
 
#14 ·
Quote:
Originally Posted by HeadlessKnight View Post

You have other variables changed from the video no (@ your old OC)? I opened that video and he put VCCIN to 2.0 which in my opinion is crazy high for 24/7.
No, all of the settings are default factory, for now, need to backup some files until I try OC again.

Thank you
 
#16 ·
Quote:
Originally Posted by shner21 View Post

I'm exacly on the same boat but with msi x99a gaming carbon ...can't make it pass 4.0 stable..how are u testing the stability of the oc
I'm using MSI Kombustor, RealBench and x264, so far everything looks stable at 4.0 with 1.25 voltage, my CPU temp does not go over 50c that's kinda weird I guess?
 
#17 ·
Quote:
Originally Posted by HeadlessKnight View Post

Disable SVID. And try 4 GHz @ 1.25-1.30V If that didn't work and you got freezes during BIOS/boot issues then try increasing VCCIN to 1.85V-1.90V.
I used those settings and running Stress Tests now with MSI Kombustor and x264, it looks stable at 4.0 GHz and 1.25V with Disabled SVID and VCCIN at 1.85V.
CPU Temperature at 47°C-50°C, it never goes past 50°C.
I will upload x264 log soon.

Ideally, I would want a 4.2 GHz and run my RAM at its frequency of 2666MHz, do you think this would be possible?

Again, thank you for helping me with this.
 
#18 ·
Quote:
Originally Posted by Varcan View Post

I used those settings and running Stress Tests now with MSI Kombustor and x264, it looks stable at 4.0 GHz and 1.25V with Disabled SVID and VCCIN at 1.85V.
CPU Temperature at 47°C-50°C, it never goes past 50°C.
I will upload x264 log soon.

Ideally, I would want a 4.2 GHz and run my RAM at its frequency of 2666MHz, do you think this would be possible?

Again, thank you for helping me with this.
Yup I think it will be possible with further tweaking, as for running memory XMP profile you might need to tweak VCCSA/ VCCIO.

Glad to help
thumb.gif
.
 
#19 ·
Quote:
Originally Posted by HeadlessKnight View Post

Yup I think it will be possible with further tweaking, as for running memory XMP profile you might need to tweak VCCSA/ VCCIO.

Glad to help
thumb.gif
.
How would I do that? Could you also help with that if that's not a problem? Also, while running x264 now, on 9th loop failed and windows said that x264 stopped working, I clicked ok and it started a new loop, looks like not stable?
 
#20 ·
Quote:
Originally Posted by Varcan View Post

How would I do that? Could you also help with that if that's not a problem? Also, while running x264 now, on 9th loop failed and windows said that x264 stopped working, I clicked ok and it started a new loop, looks like not stable?
Yup. That shouldn't happen. BTW when you click "CPU Vdroop offset control". what are the available options for you? Playing with Vdroop can help with stability and make the VCCIN either throttle less/ retain voltage/ or overvolt itself underload.
High LLC levels can create voltage spikes that can affect the longevity of the CPU.

I will try to help you once we get the CPU stable at least at default Memory/ cache, one you find your stable core OC you can tweak those things further.
 
#21 ·
Quote:
Originally Posted by HeadlessKnight View Post

Yup. That shouldn't happen. BTW when you click "CPU Vdroop offset control". what are the available options for you? Playing with Vdroop can help with stability and make the VCCIN either throttle less/ retain voltage/ or overvolt itself underload.
High LLC levels can create voltage spikes that can affect the longevity of the CPU.
I don't see "CPU Vdroop offset control" anywhere
frown.gif
 
#22 ·
Quote:
Originally Posted by Varcan View Post

I don't see "CPU Vdroop offset control" anywhere
frown.gif
It is in the video in your initial post. You have same board no? Go to the same location in the video.
 
#23 ·
Quote:
Originally Posted by HeadlessKnight View Post

It is in the video in your initial post. You have same board no? Go to the same location in the video.
I found it, Yes I have the same MOBO. When I click on the CPU Vdroop Offset Control it gives me these options:
Auto
Light (+25%)
Medium (+50%)
Ultra (+75%)
Extreme (+95%)
Enthusiastic (+100%)

This is the log from x264, I run 12 loops, one failed:
================================================================
x264-64 Stability test
================================================================

x264 0.148.2597 e86f3a1
(libswscale 3.0.0)
(libavformat 56.21.0)
built on Aug 19 2015, gcc: 4.9.2
x264 configuration: --bit-depth=8 --chroma-format=all
libx264 configuration: --bit-depth=8 --chroma-format=all
x264 license: GPL version 2 or later
libswscale/libavformat license: LGPL version 2.1 or later

==== Configuration =============================================

Log name = x264-log_PC Build test.rtf
Loops = 12
Threads = 12
Priority = high

==== Results ===================================================

Start: 21:08:53,06 24.03.2017

Loop 1: 21:08:53,17
encoded 2121 frames, 5.23 fps, 35940.36 kb/s

Loop 2: 21:15:39,47
encoded 2121 frames, 5.22 fps, 35940.36 kb/s

Loop 3: 21:22:26,16
encoded 2121 frames, 5.24 fps, 35940.53 kb/s

Loop 4: 21:29:11,45
encoded 2121 frames, 5.18 fps, 35940.36 kb/s

Loop 5: 21:36:01,42
encoded 2121 frames, 5.23 fps, 35940.36 kb/s

Loop 6: 21:42:47,32
encoded 2121 frames, 5.11 fps, 35940.36 kb/s

Loop 7: 21:49:42,71
encoded 2121 frames, 5.18 fps, 35940.36 kb/s

Loop 8: 21:56:33,07
encoded 2121 frames, 5.20 fps, 35940.36 kb/s

Loop 9: 22:03:21,43

Loop 10: 22:04:19,95
encoded 2121 frames, 5.23 fps, 35940.36 kb/s

Loop 11: 22:11:05,82
encoded 2121 frames, 5.21 fps, 35940.36 kb/s

Loop 12: 22:17:53,47
encoded 2121 frames, 5.13 fps, 35940.36 kb/s

Finish: 22:24:47,32 24.03.2017
 
#24 ·
Quote:
Originally Posted by Varcan View Post

I found it, Yes I have the same MOBO. When I click on the CPU Vdroop Offset Control it gives me these options:
Auto
Light (+25%)
Medium (+50%)
Ultra (+75%)
Extreme (+95%)
Enthusiastic (+100%)

This is the log from x264, I run 12 loops, one failed:
================================================================
x264-64 Stability test
================================================================

x264 0.148.2597 e86f3a1
(libswscale 3.0.0)
(libavformat 56.21.0)
built on Aug 19 2015, gcc: 4.9.2
x264 configuration: --bit-depth=8 --chroma-format=all
libx264 configuration: --bit-depth=8 --chroma-format=all
x264 license: GPL version 2 or later
libswscale/libavformat license: LGPL version 2.1 or later

==== Configuration =============================================

Log name = x264-log_PC Build test.rtf
Loops = 12
Threads = 12
Priority = high

==== Results ===================================================

Start: 21:08:53,06 24.03.2017

Loop 1: 21:08:53,17
encoded 2121 frames, 5.23 fps, 35940.36 kb/s

Loop 2: 21:15:39,47
encoded 2121 frames, 5.22 fps, 35940.36 kb/s

Loop 3: 21:22:26,16
encoded 2121 frames, 5.24 fps, 35940.53 kb/s

Loop 4: 21:29:11,45
encoded 2121 frames, 5.18 fps, 35940.36 kb/s

Loop 5: 21:36:01,42
encoded 2121 frames, 5.23 fps, 35940.36 kb/s

Loop 6: 21:42:47,32
encoded 2121 frames, 5.11 fps, 35940.36 kb/s

Loop 7: 21:49:42,71
encoded 2121 frames, 5.18 fps, 35940.36 kb/s

Loop 8: 21:56:33,07
encoded 2121 frames, 5.20 fps, 35940.36 kb/s

Loop 9: 22:03:21,43

Loop 10: 22:04:19,95
encoded 2121 frames, 5.23 fps, 35940.36 kb/s

Loop 11: 22:11:05,82
encoded 2121 frames, 5.21 fps, 35940.36 kb/s

Loop 12: 22:17:53,47
encoded 2121 frames, 5.13 fps, 35940.36 kb/s

Finish: 22:24:47,32 24.03.2017
Yup. That's mostly an indication of instability, if you have MSI Afterburner/ RivaTuner running through the stress test please close them. Try setting Vdroop control to Medium. and increase the vcore a bit more. Like 1.26V and stress test again.
As for the stress test run it on 16 threads and normal priority, as high will only make your PC laggy. For 8 hours at least.
 
#25 ·
Quote:
Originally Posted by HeadlessKnight View Post

Yup. That's mostly an indication of instability, if you have MSI Afterburner/ RivaTuner running through the stress test please close them. Try setting Vdroop control to Medium. and increase the vcore a bit more. Like 1.26V and stress test again.
As for the stress test run it on 16 threads and normal priority, as high will only make your PC laggy. For 8 hours at least.
16 threads? but my CPU has only 12, won't that run unstable?
 
#26 ·
Quote:
Originally Posted by Varcan View Post

16 threads? but my CPU has only 12, won't that run unstable?
Nope. It will stress the CPU harder and if it is not stable it will show faster.
 
This is an older thread, you may not receive a response, and could be reviving an old thread. Please consider creating a new thread.
Top