- Jun 18, 2014
- 11
- 0
- 4,520
So I've been doing a lot of fiddling with my bios settings to try and achieve a stable OC for my new build, but I have some questions regarding a few things I've ran into so far. I have an ASrock Z270 Killer SLI/ac Motherboard and obviously an i7 6700k, with a Corsair h115i AIO water cooler, but I can't seem to find a proper margin of stability due to some other questions I need answered. By the way my Memory is g.skill tridentz 3200mhz on XMP 2.0.
So far, I've gotten 4.6 GHz/1.36v to boot, but when I benchmarked it with my 1080 Ti on Unigine Valley, I got a BSoD at about 25 seconds in. I've gotten multiple BSoDs during this stability-finding process, some of which I'm not sure how to manage. I have my Voltage on Fixed at the moment to find a good balance point, multiplier was at 46 and BCLK on default 100, cpu-cache ratio is also on auto (40), and my Load Line Calibration has been moved between level 1 and 2 but I have yet to see anything differ.
I'm currently on 4.5Ghz/1.33v because I thought 4.6 was unstable, but if I booted on 4.6 then it's just user error right?
I'm just not sure what to do at this point, because every software I download has inaccurate stats, even in the voltage areas. AIDA64 seems to be the only one that picks up my cpu voltage correctly when I set it to a fixed numberin the bios. I've tried HWMonitor, CPU-Z, CPUID, and SpeedFan. Another odd thing to note is that CPU-Z and HWMonitor both say my Vcore is at 2.6v. Yes I said 2.6, not 1.6. I'm not sure if this is an issue within the application, or if my Motherboard is actually taking a beating right now. I'd really like to know because this is the second 6700k that I've worked with that seems to have problems exceeding 4.6GHz. The silicon lottery can't be that poor, I've seen so many people hit 5+
Here is a picture of 3 Hardware Monitoring programs, I've highlighted the areas of interest.
http://
As you can see, the AIDA64 application has my cpu voltage pretty close to what I have it set to in my bios, but HWMonitor caps at 1.25. This may just be the program itself, which is nothing to worry about, but that doesn't answer the 2.6V VCore issue. I'm just trying to get as much out of this PC as I can without being near the danger line, and I know this is not the best it can do.
So far, I've gotten 4.6 GHz/1.36v to boot, but when I benchmarked it with my 1080 Ti on Unigine Valley, I got a BSoD at about 25 seconds in. I've gotten multiple BSoDs during this stability-finding process, some of which I'm not sure how to manage. I have my Voltage on Fixed at the moment to find a good balance point, multiplier was at 46 and BCLK on default 100, cpu-cache ratio is also on auto (40), and my Load Line Calibration has been moved between level 1 and 2 but I have yet to see anything differ.
I'm currently on 4.5Ghz/1.33v because I thought 4.6 was unstable, but if I booted on 4.6 then it's just user error right?
I'm just not sure what to do at this point, because every software I download has inaccurate stats, even in the voltage areas. AIDA64 seems to be the only one that picks up my cpu voltage correctly when I set it to a fixed numberin the bios. I've tried HWMonitor, CPU-Z, CPUID, and SpeedFan. Another odd thing to note is that CPU-Z and HWMonitor both say my Vcore is at 2.6v. Yes I said 2.6, not 1.6. I'm not sure if this is an issue within the application, or if my Motherboard is actually taking a beating right now. I'd really like to know because this is the second 6700k that I've worked with that seems to have problems exceeding 4.6GHz. The silicon lottery can't be that poor, I've seen so many people hit 5+
Here is a picture of 3 Hardware Monitoring programs, I've highlighted the areas of interest.
http://
As you can see, the AIDA64 application has my cpu voltage pretty close to what I have it set to in my bios, but HWMonitor caps at 1.25. This may just be the program itself, which is nothing to worry about, but that doesn't answer the 2.6V VCore issue. I'm just trying to get as much out of this PC as I can without being near the danger line, and I know this is not the best it can do.
Facebook
Twitter
Instagram