WEBVTT

00:00:03.280 --> 00:00:12.880
it's back so i promised you guys that the dual CPU eight core skull trail rig

00:00:10.160 --> 00:00:17.119
that tom from the uk sent over was going to be making another appearance and that

00:00:14.880 --> 00:00:21.439
we were going to be kicking things up a notch but i actually didn't think things

00:00:19.359 --> 00:00:24.400
were going to go quite this well so here's what i have in store for you

00:00:24.400 --> 00:00:31.439
we're going to be overclocking our cpus we're going to be upgrading to rtx

00:00:30.080 --> 00:00:37.840
graphics with sli for bonus points we're going to be

00:00:34.559 --> 00:00:39.520
going from 8 gigs to a whopping

00:00:37.840 --> 00:00:47.840
32 gigs of ddr2 memory thanks to paul from

00:00:44.079 --> 00:00:50.320
ontario who sent over these bad boys and

00:00:47.840 --> 00:00:53.440
thanks to our sponsor for today's video we are going to be hooking this whole

00:00:51.920 --> 00:00:59.280
thing up to samsung's latest curved 240 hertz

00:00:57.680 --> 00:01:03.440
gaming monitor so uh

00:01:01.199 --> 00:01:07.920
why don't we get started with that so let's start by getting our monitor

00:01:04.960 --> 00:01:13.920
cracked open the c27rg5 is the world's first 240 hertz curved gaming display

00:01:11.600 --> 00:01:19.520
and guys if you're regular viewers of this channel i probably don't have to

00:01:16.080 --> 00:01:21.119
explain the advantages of a 240hz

00:01:19.520 --> 00:01:26.320
display basically means smoother animations and you are getting more

00:01:23.680 --> 00:01:30.799
information per second to your eyeball holes which gives you a competitive

00:01:28.000 --> 00:01:35.520
advantage as we actually demonstrated in a recent video now another cool feature

00:01:33.439 --> 00:01:39.759
is that it happens to be g-sync compatible so that means that if you

00:01:37.600 --> 00:01:45.119
don't reach quite hertz which

00:01:42.560 --> 00:01:49.920
i think might happen today then you're gonna have g-sync as long as you've got

00:01:47.040 --> 00:01:54.560
an NVIDIA graphics card to help smooth out some of the uh

00:01:51.759 --> 00:01:58.240
some of the gaps there so on the back we've got a look at the i o we've got

00:01:55.920 --> 00:02:03.040
dual HDMI ports displayport a usb service port and a dc power in for the

00:02:01.119 --> 00:02:07.920
external power brick and the main standout features of this guy are really

00:02:04.960 --> 00:02:13.200
going to be the 3001 contrast ratio thanks to its va panel the bezel-less

00:02:10.720 --> 00:02:17.520
design and this is a cool one it's actually got a special low input lag

00:02:15.599 --> 00:02:22.319
mode which for a 240hz gaming monitor i would certainly hope that

00:02:19.599 --> 00:02:28.720
everyone would enable that i'm hoping to pair with some of NVIDIA's new driver

00:02:24.640 --> 00:02:31.760
optimizations to get a a smoother more

00:02:28.720 --> 00:02:32.640
responsive overall gaming experience on

00:02:31.760 --> 00:02:36.800
well very dated hardware here so just like

00:02:35.040 --> 00:02:41.760
last time our underpowered CPU is already apparent

00:02:39.040 --> 00:02:47.120
when we're doing something as simple as downloading and installing a graphics

00:02:44.480 --> 00:02:52.080
driver we're sitting at 80 percent CPU utilization and 40 of it is google

00:02:50.080 --> 00:02:56.400
chrome which surprisingly wasn't even open that's a new one

00:02:54.319 --> 00:02:59.440
good job google chrome how even what even

00:02:58.080 --> 00:03:04.930
happened that oh there's another one wait why is there another one what even is this and what do i even have open

00:03:03.440 --> 00:03:10.000
i have two pages open while we're off to a flying start here

00:03:07.920 --> 00:03:15.360
after an excruciatingly slow driver install our titan x is still not showing

00:03:12.400 --> 00:03:19.440
up with the infamous code 43 error so that's fine we weren't really intending

00:03:17.200 --> 00:03:23.599
to use that anyway so let's go ahead and restart it

00:03:20.560 --> 00:03:25.440
and throw in an rtx 2080 ti

00:03:23.599 --> 00:03:28.800
okay so here we go ladies and gentlemen

00:03:31.360 --> 00:03:36.319
you know what we're just gonna we're just gonna go full yolo we're gonna

00:03:34.640 --> 00:03:39.760
upgrade the RAM we're gonna overclock the snot out of this thing let's just

00:03:38.480 --> 00:03:44.720
let's just holy ow

00:03:42.159 --> 00:03:48.400
so we're gonna put these eight gig sticks in so these are two gig sticks

00:03:47.120 --> 00:03:54.640
that we're replacing we'll be handling those by the edges wow those get really hot

00:03:52.959 --> 00:03:59.920
i guess that makes sense they did draw a lot more power than normal ddr2 modules

00:03:57.599 --> 00:04:04.720
with of course the benefit being these high capacities

00:04:01.599 --> 00:04:07.040
32 gigs of RAM in four slots was a

00:04:04.720 --> 00:04:13.040
freaking lot back then meanwhile now Corsair has gaming kits

00:04:09.040 --> 00:04:15.040
with 32 gig sticks in them

00:04:13.040 --> 00:04:19.759
now before we go any further i actually want to throw some active cooling

00:04:18.079 --> 00:04:24.560
on my memory here let's see can i just kind of wedge that

00:04:21.600 --> 00:04:24.560
you know it should be fine

00:04:24.880 --> 00:04:31.520
there it is skull trail with 32 gigs the stupidest

00:04:29.520 --> 00:04:36.160
configuration ever let's overclock this thing

00:04:33.600 --> 00:04:39.199
so in the interest of time efficiency we're not going to be dialing in the

00:04:38.000 --> 00:04:44.400
world's most uh careful overclock or anything like

00:04:42.080 --> 00:04:47.840
that we're basically going quick and dirty

00:04:45.360 --> 00:04:53.919
boom we're going for four gigahertz just like that and at the same time

00:04:50.160 --> 00:04:56.639
memory ratio boom one to one

00:04:53.919 --> 00:05:00.800
okay wish me luck and we're posted

00:04:58.639 --> 00:05:04.479
okay window stability is a whole other story though oh

00:05:02.479 --> 00:05:07.600
i need a drink from this water bottle ltdstar.com

00:05:06.000 --> 00:05:11.120
so let's verify that everything is working as intended we've got our RAM

00:05:09.919 --> 00:05:16.720
running at 400 megahertz wait

00:05:14.240 --> 00:05:22.720
times one equals 400 megahertz that's weird task manager shows it at 667 which

00:05:19.919 --> 00:05:29.039
would be a double pump 333 which is what it's rated for what this is

00:05:26.800 --> 00:05:34.800
oh god

00:05:31.360 --> 00:05:36.560
okay so we bumped our mch voltage and

00:05:34.800 --> 00:05:39.840
hopefully that'll be enough to get us stable no

00:05:41.600 --> 00:05:49.199
try the 16 gig kit so i bump the front side bus voltage and

00:05:46.639 --> 00:05:53.440
i am changing these CPU fans to just run at the full 12 volts rather than be

00:05:51.600 --> 00:05:58.880
speed controlled which should give us a little bit more chipset cooling

00:05:55.759 --> 00:05:58.880
better finish this run

00:05:59.039 --> 00:06:08.240
yes okay check out this score

00:06:03.919 --> 00:06:09.520
733 okay it's not amazing but

00:06:08.240 --> 00:06:15.680
but that is a mere 90 points less than a

00:06:13.360 --> 00:06:18.800
4770k so

00:06:16.479 --> 00:06:22.400
if we can find games that are suitably multi-threaded

00:06:20.319 --> 00:06:24.960
we might actually have a decent gaming experience

00:06:26.319 --> 00:06:32.000
not the younglings you're not supposed to hold the lightsaber

00:06:29.600 --> 00:06:36.880
and this is how i always get myself into freaking trouble because you get it

00:06:34.080 --> 00:06:41.000
working good enough i mean we've got 16 gigs of RAM in the thing

00:06:38.880 --> 00:06:45.199
but i want more

00:06:45.199 --> 00:06:54.000
758 oh that is dangerously close to 3770

00:06:52.440 --> 00:06:57.759
4770 processor performance territory all

00:06:56.000 --> 00:07:03.599
right sli then

00:06:59.520 --> 00:07:06.080
sli is enabled so okay we couldn't do

00:07:03.599 --> 00:07:11.360
our tx 2080 ti but we were able to do dual titan x pascals

00:07:09.919 --> 00:07:16.800
and g-sync boom g-sync is working enabled for both

00:07:15.120 --> 00:07:20.960
windowed and full screen mode so that means we'll be able to run our games

00:07:18.319 --> 00:07:24.800
without any screen tearing stuttering or lag because our samsung monitor here

00:07:22.880 --> 00:07:29.360
changes its refresh rate to match up perfectly with the frames being rendered

00:07:26.560 --> 00:07:34.000
by the GPU is this a lock on the sli connector oh oh my god it has this wait

00:07:32.639 --> 00:07:38.319
ah it's a color switch wait what the

00:07:36.720 --> 00:07:42.720
it's funny unless you look close you'd never know this is like not a modern

00:07:40.160 --> 00:07:47.360
system you know these gpus look pretty modern that memory amount looks pretty

00:07:45.039 --> 00:07:51.199
modern that core count looks pretty modern

00:07:48.880 --> 00:07:56.479
now before we get into games i wanted to give adobe premiere pro another shot

00:07:54.400 --> 00:08:02.000
just because like hey we got 32 gigs of RAM now right

00:07:58.560 --> 00:08:04.879
maybe it'll be a little better yeah huh

00:08:02.000 --> 00:08:08.479
yeah wow that's actually a really good slideshow that we're watching here

00:08:06.879 --> 00:08:13.360
that's at full resolution though that's at 8k try one quarter

00:08:11.280 --> 00:08:17.440
and we're done bud although we did manage to use more than eight gigs of

00:08:14.879 --> 00:08:20.479
RAM so hey it wasn't all completely for nothing-ish sort of let's play some

00:08:19.199 --> 00:08:24.479
video games i figure we should start

00:08:22.240 --> 00:08:27.919
with rocket league i just want to see if it runs a little better this time than

00:08:26.080 --> 00:08:33.680
it did last time okay so this was probably a mistake i

00:08:30.720 --> 00:08:36.640
cranked the details up and that was a mistake

00:08:35.120 --> 00:08:42.000
performance we're still sitting at about 40 FPS

00:08:39.760 --> 00:08:46.720
however one key difference here is that i'm not getting the same

00:08:44.800 --> 00:08:50.480
really bad stutters that i was before it's like actually kind of playable well

00:08:49.120 --> 00:08:54.800
that doesn't give me much hope for our second game but i did promise you guys

00:08:52.320 --> 00:09:00.399
more game testing today so let's go ahead and give doom a shot here do you

00:08:57.920 --> 00:09:03.760
see it skipping around like that whoa

00:09:01.839 --> 00:09:08.640
so technically we are running at 50 frames per second

00:09:06.480 --> 00:09:13.040
right now but you guys you can look at it even through the camera i'm sure you

00:09:10.720 --> 00:09:18.240
guys can tell that that is some chop-tastic

00:09:15.760 --> 00:09:22.360
animation going on there so now we can see our frame times here

00:09:20.080 --> 00:09:28.640
you can see there is a ton of inconsistency in them which is why we're

00:09:24.880 --> 00:09:31.040
getting these really ugly skips however

00:09:28.640 --> 00:09:34.560
doom has a trick up its sleeve now as far as i know this is going to

00:09:32.320 --> 00:09:38.959
completely brick our compatibility with sli but

00:09:36.880 --> 00:09:43.519
one of the key advantages of the next-gen apis like vulcan is supposed to

00:09:42.480 --> 00:09:50.640
be is supposed to be better handling of multiple CPU threads

00:09:49.519 --> 00:09:57.279
so maybe we'll be able to take advantage of

00:09:53.279 --> 00:09:57.279
our eight CPU cores a little better here

00:09:57.519 --> 00:10:00.080
oh

00:10:01.279 --> 00:10:06.720
that is looking quite a bit more consistent

00:10:04.560 --> 00:10:12.480
this is doom running on a 10 year old computer

00:10:10.399 --> 00:10:15.920
we're at medium details right now so i guess man we could probably push this

00:10:14.640 --> 00:10:22.160
harder but that is actually butter smooth this

00:10:19.440 --> 00:10:28.000
is actually awesome can you believe the CPU running this is 11 years old you

00:10:24.959 --> 00:10:31.720
know what let's push for more

00:10:28.000 --> 00:10:31.720
oh oh

00:10:35.360 --> 00:10:42.959
dude not responding power usage very high

00:10:41.360 --> 00:10:47.760
stage two is everything on high except motion blur

00:10:45.519 --> 00:10:53.760
on low because i hate motion blur let's see how this goes

00:10:50.079 --> 00:10:55.040
oh that is looking real good oh i

00:10:53.760 --> 00:11:01.440
thought i felt a little stutter there for a second it's definitely not bad though

00:10:58.959 --> 00:11:07.519
we are running at anywhere from 80 to 100 plus frames per second

00:11:04.240 --> 00:11:08.959
and uh oh i died so now i was thinking

00:11:07.519 --> 00:11:14.800
let's try something a little bit more modern we're gonna fire up apex legends

00:11:11.440 --> 00:11:17.279
which isn't CPU does not have popkins

00:11:14.800 --> 00:11:20.800
next up minecraft now i have to confess i have played very little minecraft

00:11:19.279 --> 00:11:26.240
couldn't really figure out what the hell i was supposed to do this is a test for

00:11:22.959 --> 00:11:29.760
what may eventually be a like LMG

00:11:26.240 --> 00:11:32.640
minecraft thing who binds run to control

00:11:29.760 --> 00:11:35.839
now the good news here is that wow now the good news here is that we are

00:11:34.320 --> 00:11:42.720
actually running at anywhere from 100 all the way up to

00:11:38.800 --> 00:11:45.440
well over 200 FPS here which is pretty

00:11:42.720 --> 00:11:49.920
freaking sweet so for the first time today

00:11:46.480 --> 00:11:52.399
we are actually getting the proper

00:11:49.920 --> 00:11:58.320
full smooth gaming experience of this monitor huh

00:11:55.200 --> 00:11:59.760
here's here's a good segue subscribe

00:11:58.320 --> 00:12:03.760
yeah why aren't you subscribed to Linus tech tips yet minecraft told you to do

00:12:02.000 --> 00:12:08.160
it you know my biggest problem is with minecraft though the realism this

00:12:05.839 --> 00:12:13.760
clearly wouldn't be burning in the rain so we should probably how do i ride the

00:12:10.399 --> 00:12:14.800
horse somebody else's horse who cares

00:12:13.760 --> 00:12:19.600
do you need to just teleport you somewhere far away so you don't screw anything up no i don't care if i screw

00:12:18.000 --> 00:12:24.600
anything up can you build stuff under water yeah

00:12:21.279 --> 00:12:24.600
how do you breathe

00:12:29.600 --> 00:12:34.079
that's not swimming if you go down to the bottom it's sinking

00:12:32.639 --> 00:12:37.920
see this is what i'm talking about it's not realistic

00:12:36.320 --> 00:12:42.240
to give our poor system a fighting chance we wanted to fire up a vulcan

00:12:40.320 --> 00:12:46.880
game so this is the talos principle and you can see it's actually not running

00:12:43.839 --> 00:12:50.480
great right now anywhere from 20 to

00:12:46.880 --> 00:12:53.839
45 FPS so we're running directx 11 now

00:12:50.480 --> 00:12:55.920
and we're gonna change that in hopes of

00:12:53.839 --> 00:12:59.120
here we go seeing a little bit of a better result

00:12:58.079 --> 00:13:03.920
here all right we're vulcan now boys

00:13:02.079 --> 00:13:08.560
that's not bad that's not bad at all dang vulcan you

00:13:07.360 --> 00:13:13.440
cool breathing fresh life into ancient

00:13:11.200 --> 00:13:16.639
hardware so this is the new wolfenstein ii

00:13:15.839 --> 00:13:21.600
oh oh crap you know it feels a little stupid to be

00:13:20.160 --> 00:13:26.800
fighting with this eight cores total

00:13:23.680 --> 00:13:30.160
dual socket nonsense from 11 years ago

00:13:26.800 --> 00:13:32.399
when i have a 64 core 128 thread AMD

00:13:30.160 --> 00:13:37.200
epic that i like have to finish this video before i can play with really

00:13:34.480 --> 00:13:41.440
we're on we're on ultra jig does that seem

00:13:38.480 --> 00:13:45.519
kind of unfair yeah two type so this is a weird one because if i

00:13:43.360 --> 00:13:50.639
don't try to move the mouse you see that the animation is actually really smooth

00:13:47.920 --> 00:13:55.839
but if i try to move the mouse it just completely falls apart

00:13:53.680 --> 00:13:59.440
so many new and exciting ways for a system to be horribly horribly

00:13:57.680 --> 00:14:03.360
bottlenecked today thanks for the gun bro

00:14:01.600 --> 00:14:07.680
wow cool gun alright so that was fun but if i was

00:14:05.440 --> 00:14:12.800
samsung i would be crazy to let me showcase

00:14:09.680 --> 00:14:14.320
a 240 hertz wow this thing is heavy

00:14:12.800 --> 00:14:18.800
gaming display on only that so

00:14:16.959 --> 00:14:23.199
let's pull out the big guns and see what the experience

00:14:20.160 --> 00:14:25.839
is supposed to be like

00:14:23.199 --> 00:14:31.920
now doom ran okay on our other rig but that was at like medium details instead

00:14:28.240 --> 00:14:33.920
of having everything on high and

00:14:31.920 --> 00:14:38.320
this is a lot smoother like there's no doubt whatsoever

00:14:35.839 --> 00:14:42.839
that high refresh rate gives you a clear competitive advantage and when you have

00:14:40.480 --> 00:14:48.000
the FPS to back it up obviously the whole concept works a

00:14:45.680 --> 00:14:51.839
little bit better i'm actually pretty impressed with this

00:14:49.360 --> 00:14:55.600
monitor the pixel response times are quite

00:14:52.880 --> 00:14:59.440
satisfactory while we fire up csgo show you guys got all the usual you know

00:14:57.040 --> 00:15:03.279
different game modes black equalizer you can turn on a crosshair if you're a big

00:15:01.040 --> 00:15:05.760
fat cheater why would you pull out your knife like

00:15:04.639 --> 00:15:09.199
what even is the logic here

00:15:07.680 --> 00:15:13.920
like is it i'd love to see the dungeons and dragons

00:15:11.120 --> 00:15:18.399
rulebook version of how they programmed the bot behavior to not be good is there

00:15:16.160 --> 00:15:21.760
just like a 20-sided die that it rolls and it'll just like pull out a random

00:15:19.920 --> 00:15:26.399
weapon if it comes up you know what i mean

00:15:23.920 --> 00:15:31.199
oh man i got killed by it this is a lot smoother like there's no

00:15:28.959 --> 00:15:36.240
doubt whatsoever that high refresh rate gives you a clear competitive advantage

00:15:33.600 --> 00:15:40.079
and when you have the FPS to back it up obviously the whole concept works a

00:15:38.000 --> 00:15:44.880
little bit better so this monitor is equipped with both g-sync and a 240hz

00:15:42.959 --> 00:15:48.800
refresh rate so it's able to serve up every possible frame my pc is producing

00:15:46.959 --> 00:15:52.480
right now that means i'm getting however many more opportunities per second to

00:15:50.639 --> 00:15:56.639
beat my opponents i mean i think we can all agree with my skill if i was online

00:15:54.639 --> 00:16:00.399
right now i'd be winning for sure so massive thank you to samsung for

00:15:58.160 --> 00:16:03.440
sponsoring this video thanks to you guys for watching if you enjoyed this one

00:16:02.000 --> 00:16:08.160
because you love bottlenecks you can check out the video where we put a titan

00:16:05.920 --> 00:16:11.920
rtx on the latte panda i'll link that one for you

00:16:09.279 --> 00:16:17.079
if not then sorry i'll come up with a better

00:16:12.959 --> 00:16:17.079
recommendation for you next time