11-22-2014
08:49 AM
- last edited on
03-06-2024
03:40 AM
by
ROGBot
11-29-2014 11:32 PM
Lelouchvi wrote:
1.770 input
Just a typo 1.16 =p
at 4.2Ghz 100x 42
2666 g skill ram xmp settings
idle around mid 30s on the cpu and 40 on the gpu
loads temps just touching 60s with realbench after 4 hours of it. and 47 on the gpu
12-03-2014 11:14 AM
ERIU-OC wrote:
looking really good right now, keep on tuning!
you might wanne find out if your OC is stable when using AVX instruction set at this point?!
if so run prime95 (Ver. 27.9) on custom FFT length 1344, 1344 FFT length is usually good for checking Vcore requirements and FFT length 448 for checking input voltage requirements
EDIT: pay attention on your temps when using prime95, it produces more heat than realbench...
if you run into BSOD:
0x124 Weha uncorrectable blabla -> usually more Vcore is needed
0x101 Clock Watchdog blabla -> usually to high or low input voltage
these are recommendations to watch on and not to be taken as hammered in stone
Cheers
12-03-2014 11:20 AM
Lelouchvi wrote:
Thanks, I got it pretty stable now, but core2 and 4 on HW monitor shows a large temp gap between the other cores which got me worry as they go up to 9 degree higher than the others sometimes. Realbench didnt appear to have similar issue.
12-03-2014 12:33 PM
Lelouchvi wrote:
Thanks, I got it pretty stable now, but core2 and 4 on HW monitor shows a large temp gap between the other cores which got me worry as they go up to 9 degree higher than the others sometimes. Realbench didnt appear to have similar issue.
I also found this which was an interesting read.
http://tatoismus.net/asus-x99-deluxe-i7-5930k-prime95/
12-03-2014 12:45 PM
12-03-2014 02:08 PM
ERIU-OC wrote:
well realbench is a completely different thing compared to prime95.
realbench put's crossloads on your chip and bus's to simulate more realistic loads like in normal use but more extreme
because of this cross loads the temperature behavior is a complete different thing there.
Prime lets your chip do the exactly same thing over and over again especially when running one FFT length. the only thing that changes is where the data fits in (L1-L2-L3 Cache, memory) with the different fft length.
Hope this clears it up a bit, for you...
12-04-2014 09:30 AM
12-12-2014 02:47 PM
ERIU-OC wrote:
it comes down to what you wanne do with your chip.
in the guide you posted are many useful things to look on and the guide is mainly meant as a guide line for those who want to squeeze the last drop of blood out of their chip.
if you want a 24/7 system with some benefits of the features this platform and chips have, you probably don't want to set everything possible to the max or extreme and disable everything that has a function depending on the current cpu load requirements.
maybe this is an example:
your chip is the driver of a car on the road, he can drive faster or slower depending on the traffic, he can choose a higher gear on a given speed to save fuel, or he can choose lower gear to have quick access to acceleration depending on the current situation.
what the guide does is to put the driver in a car on a single lane racing track, giving him only one specific gear , no break and the gas pedal nailed to the bottom. so the only choice is to drive in the hope of being able to handle the speed...
with that being said I mean user preference starts when you choose what to do with your chip.
Cheers