WEBVTT

00:00:00.800 --> 00:00:08.320
my custom water blocks from swiftech are here

00:00:04.799 --> 00:00:10.800
but perhaps more importantly my email

00:00:08.320 --> 00:00:15.679
from ASUS giving me the guidance that i need to overclock

00:00:13.200 --> 00:00:22.000
the 56 core system is also here so what do we stand to gain

00:00:19.760 --> 00:00:26.160
according to ASUS's guidance anywhere from three

00:00:23.279 --> 00:00:31.679
to nine percent performance and what do we stand to lose twenty thousand dollars

00:00:28.720 --> 00:00:34.960
in cpus 750 dollars in motherboards and about five grand worth of RAM

00:00:34.000 --> 00:00:40.139
so what are we waiting for

00:00:43.120 --> 00:00:49.440
anker's new powerwave 7.5 pad and stand

00:00:46.800 --> 00:00:53.920
both offer faster wireless charging easy alignment for your device and the pad is

00:00:51.920 --> 00:00:56.480
coated with an anti-slip material check them out on amazon through the links

00:00:55.440 --> 00:01:02.960
below so one of the most exciting things about this board to me other than the

00:00:59.760 --> 00:01:05.680
hilariously broken uh web page for it

00:01:02.960 --> 00:01:11.119
with this placeholder text in it is the fact that jesus advertises it as

00:01:08.280 --> 00:01:16.400
overclocking capable so this is the exact same platform that we had set up

00:01:13.439 --> 00:01:20.400
from our holy so we've got a system that

00:01:17.600 --> 00:01:24.880
seems to be locked up and we're back everything seems to be working fine so

00:01:21.920 --> 00:01:29.600
56 processing cores and completely inadequate cooling so we're

00:01:28.080 --> 00:01:34.159
getting some baseline readings here so we're sitting at around 6 700 and

00:01:31.680 --> 00:01:38.640
cinebench let's go ahead and restart it and key in what ASUS figures is gonna

00:01:36.320 --> 00:01:42.320
give us a three percent overclock and then we're gonna go from there so we go

00:01:40.400 --> 00:01:45.880
into ai overclock tuner set that to manual change this

00:01:44.640 --> 00:01:50.640
to 103. spread spectrum gets disabled xeon

00:01:49.119 --> 00:01:54.799
turbocharger gets enabled and then

00:01:53.520 --> 00:01:57.759
wow that's not good oh that's not good at

00:01:56.640 --> 00:02:03.119
all well that didn't work just going to fire them over a quick email saying thank you

00:02:01.600 --> 00:02:07.439
for the instructions by the way they were this is one of the challenges with

00:02:06.000 --> 00:02:11.440
overclocking by base clock rather than by adjusting

00:02:09.520 --> 00:02:15.840
the multiplier when you adjust the base clock you actually throw a bunch of

00:02:13.680 --> 00:02:20.640
other system frequencies out of whack including pci express and what can

00:02:18.239 --> 00:02:24.640
happen is if you go too far out of spec you can make it so that certain devices

00:02:22.400 --> 00:02:28.959
won't be detected anymore i've never heard of

00:02:26.080 --> 00:02:33.840
one percent out of spec causing a storage controller to stop showing up

00:02:31.599 --> 00:02:38.560
but our SATA drive is not showing up at 101 base clock

00:02:36.480 --> 00:02:41.680
i hope it didn't break the drive yeah see there's no there's no drive

00:02:40.080 --> 00:02:45.599
boot options here okay we're gonna go back to 100 and see if this shows up

00:02:43.360 --> 00:02:49.920
again there it's back see ata device

00:02:47.040 --> 00:02:53.760
so that's a good sign you know you could get absolutely like

00:02:52.400 --> 00:02:58.319
shredded if like every time you had to wait around for a server board to post you're

00:02:57.120 --> 00:03:00.720
just like yeah i'm gonna do some crunches

00:03:03.680 --> 00:03:09.280
that seems like a lot of work though okay here's what we're gonna do is we're

00:03:07.840 --> 00:03:15.280
gonna switch over to an m.2 ndme SSD because we know our

00:03:12.959 --> 00:03:19.280
video card was still working so so some stuff

00:03:16.560 --> 00:03:23.840
still might work okay this is good so our 960 pro is here let's go ahead and

00:03:22.400 --> 00:03:29.440
save our changes and see if at 101

00:03:27.280 --> 00:03:33.480
we can boot up into Windows nice

00:03:30.400 --> 00:03:36.120
okay check this out this is good

00:03:33.480 --> 00:03:38.959
101 megahertz 75.94

00:03:38.080 --> 00:03:44.959
wait is that much higher oh

00:03:43.120 --> 00:03:49.200
looks like just some of the things we've tuned

00:03:47.200 --> 00:03:54.319
are we even without any base clock overclocking forcing the processor to

00:03:51.760 --> 00:03:57.519
run at a higher turbo frequency let's see if we can push for more

00:03:58.799 --> 00:04:06.480
so this is it the turbo ratio lock this right here is sort of similar to the

00:04:04.000 --> 00:04:09.840
multi-core optimization that caused that whole

00:04:07.439 --> 00:04:13.280
scandal during the coffee lake launch so it was effectively causing higher power

00:04:11.439 --> 00:04:16.880
consumption but higher performance overclocking the processors out of the

00:04:14.879 --> 00:04:20.160
box now that it's not enabled by default i don't think there's any scandal there

00:04:18.160 --> 00:04:25.520
but that's why we got so much more performance it was taking the expected

00:04:22.560 --> 00:04:29.840
turbo for all cores active and just setting it to like a higher turbo that

00:04:27.280 --> 00:04:34.240
was for not all the cores being active with that said according to ASUS's

00:04:31.680 --> 00:04:37.440
guidance we should expect more than one percent on top of that

00:04:36.000 --> 00:04:40.720
so we're trying three percent

00:04:39.280 --> 00:04:45.360
what the reset button stopped working

00:04:43.040 --> 00:04:49.040
i did i didn't even touch it there i don't know if this is a good sign yet

00:04:47.120 --> 00:04:54.400
it's doing this thing where it like keeps trying and it makes a little bit

00:04:52.800 --> 00:05:00.000
further every time but then it keeps just resetting itself

00:04:57.440 --> 00:05:04.400
this RAM is already running at like the balls to the wall speed for

00:05:01.759 --> 00:05:07.280
this platform 2600 maybe we dial that back

00:05:05.199 --> 00:05:10.880
and see if maybe trying to not run the memory out

00:05:09.120 --> 00:05:14.080
of spec will help us get booted up at 103 and

00:05:12.720 --> 00:05:19.280
i would have thought it possible but i made it worse postcode

00:05:17.360 --> 00:05:23.600
zero i got an email from ASUS different

00:05:21.520 --> 00:05:28.240
contact this time jacqueline who suggested i try her exact configuration

00:05:26.479 --> 00:05:32.160
but we're gonna need to make a couple of changes first of all

00:05:30.000 --> 00:05:34.880
no say to drive that's gotta go second of all i've gotta rip out most of the

00:05:34.080 --> 00:05:39.199
RAM and she also suggested that i try with

00:05:37.440 --> 00:05:43.280
the onboard graphics wow these are hot cut my computer into

00:05:42.160 --> 00:05:48.240
pieces it is a piece of chin

00:05:45.840 --> 00:05:53.600
oh come on the only thing worse

00:05:50.400 --> 00:05:57.120
than slow posting server boards

00:05:53.600 --> 00:06:00.080
is when slow posting server boards

00:05:57.120 --> 00:06:02.960
post and then reset themselves as part of like i don't know if this is a memory

00:06:01.759 --> 00:06:08.639
training exercise or something i don't know what it's doing did it just turn off again

00:06:06.000 --> 00:06:13.199
so now from a second source yeah no problem

00:06:10.479 --> 00:06:16.639
all i did was dial in these settings and bippity boppity

00:06:17.440 --> 00:06:24.160
well well now i'm in even worse position

00:06:21.280 --> 00:06:27.360
overclocking failed and i have no keyboard detected

00:06:26.400 --> 00:06:35.199
yes i have another idea we're going to give it more voltage

00:06:32.240 --> 00:06:39.759
and we're straight to zero zero so i've got a couple more ideas stop it

00:06:37.919 --> 00:06:44.880
there are a few other things here that maybe we could look at we could turn on

00:06:41.840 --> 00:06:48.080
load line calibration extreme

00:06:44.880 --> 00:06:50.000
phase stop it

00:06:48.080 --> 00:06:54.560
three again get some help it's time for a hail mary

00:06:52.560 --> 00:06:58.319
to be clear i don't think this is thermals related but let's water cool

00:06:57.280 --> 00:07:02.560
this thing let's see what happens

00:07:01.120 --> 00:07:10.080
is this brand new nope and whoever put it back didn't put the

00:07:05.680 --> 00:07:10.080
hardware back with it thank you guys

00:07:11.680 --> 00:07:17.680
wow this was left over from whole room water

00:07:14.720 --> 00:07:21.280
cooling oh gross to be clear the rust isn't from

00:07:19.599 --> 00:07:25.199
the pump itself these don't these don't rust the worst part is i know everything i'm

00:07:24.000 --> 00:07:30.319
doing right now is almost definitely for not okay come

00:07:28.479 --> 00:07:32.479
on okay

00:07:33.199 --> 00:07:37.199
ouch ah

00:07:37.759 --> 00:07:46.080
got myself in the scissors cut my life into pieces and you know what if we're

00:07:44.000 --> 00:07:49.440
gonna go full hail mary let's just put all the RAM back in

00:07:48.160 --> 00:07:54.000
this is an advanced water cooling technique

00:07:51.840 --> 00:07:58.960
this is known as the uh the pump and fill

00:07:56.240 --> 00:08:03.120
look at this mess i better get some good results out of it

00:08:01.680 --> 00:08:08.720
okay cpus are still detected all the RAM is

00:08:05.599 --> 00:08:10.840
still detected bad news is on first boot

00:08:08.720 --> 00:08:16.800
we get an overclocking failed message so that's flipping wow those are much

00:08:13.759 --> 00:08:19.840
better CPU champs 30 and 36 so we have

00:08:16.800 --> 00:08:22.240
dropped just about 30 degrees about 25

00:08:19.840 --> 00:08:27.680
degrees off of our cpus we're going full hem on the CPU voltage

00:08:24.240 --> 00:08:29.759
let's hit it hey 103. it might have been

00:08:27.680 --> 00:08:33.440
the auto voltage not going high enough the whole time holy let's hit it

00:08:32.000 --> 00:08:37.519
with a load we're back to the same score we got

00:08:35.360 --> 00:08:42.479
before we just tuned those bio settings and ran

00:08:39.919 --> 00:08:47.680
it at 101. okay let's try restoring our defaults and

00:08:45.200 --> 00:08:52.320
keying everything in manually again okay here we go we're at 3.3 gigahertz

00:08:50.240 --> 00:08:55.920
this time 75.96 okay even if we could get another four

00:08:54.640 --> 00:09:01.839
percent we wouldn't be able to crack eight thousand but i mean we have to try

00:09:00.160 --> 00:09:05.279
i mean it's funny like we preach the importance of cooling all the time

00:09:04.000 --> 00:09:08.500
around here but i've never seen it have this

00:09:07.040 --> 00:09:11.519
profound impact

00:09:11.519 --> 00:09:16.720
and straight to postcode 0-0 okay maybe i shouldn't have changed so many things

00:09:15.360 --> 00:09:20.480
at once so without tooling around with any of

00:09:18.640 --> 00:09:24.880
that other stuff this time let's go for 105 again

00:09:22.959 --> 00:09:28.720
come on baby come on baby

00:09:26.800 --> 00:09:31.600
and zero zero

00:09:30.160 --> 00:09:36.480
all right you can

00:09:33.519 --> 00:09:39.360
overclock a workstation or a server but

00:09:37.360 --> 00:09:44.080
you're gonna affect your system in ways that you might not otherwise foresee

00:09:41.279 --> 00:09:47.920
like making it so your SATA SSD doesn't show up

00:09:45.360 --> 00:09:51.680
and the performance gains are probably fairly

00:09:48.839 --> 00:09:54.640
negligible my recommendation based on the performance we were able to achieve

00:09:53.600 --> 00:10:00.480
is just go with some kind of like turbo manipulation like ASUS's turbo locking

00:09:58.959 --> 00:10:05.800
thing and if that's stable

00:10:02.320 --> 00:10:05.800
call it a day

00:10:05.839 --> 00:10:11.120
see that's f right there

00:10:09.040 --> 00:10:15.760
rip rip the dream new from mass drop is a new keyboard

00:10:13.760 --> 00:10:21.440
modeled after the super successful k-type it's fully programmable with RGB

00:10:18.720 --> 00:10:25.760
lighting and qmk firmware which makes it much easier to program and gives you

00:10:23.279 --> 00:10:30.560
more control at checkout you can choose between cherry mx kaiwa and halo

00:10:28.399 --> 00:10:35.279
switches which will affect the pricing depending on your choice and there are a

00:10:32.880 --> 00:10:40.079
few first production perks that you get if you join this drop now including a

00:10:37.839 --> 00:10:45.440
free novelty keycap behind the scenes live q a with the designer and 10 bucks

00:10:42.720 --> 00:10:49.600
free for your next keycap set so pick it up today on massdrop for a limited time

00:10:47.680 --> 00:10:52.480
through the link below so thanks for watching guys if you disliked this video

00:10:51.200 --> 00:10:56.800
you can hit that button but if you liked it hit like get subscribed maybe consider checking out where to buy the

00:10:55.040 --> 00:10:59.839
stuff we featured at the link in the description also down there is our merch

00:10:58.480 --> 00:11:05.440
storage has cool shirts like this one and our community forum which you should

00:11:02.399 --> 00:11:05.440
totally join