WEBVTT

00:00:01.600 --> 00:00:09.559
perfect completely unresponsive hard lock system this is great I finally

00:00:06.799 --> 00:00:15.120
finish the Intel Arc challenge I go back to my RTX 39 I'm like yeah I'm going to

00:00:12.440 --> 00:00:20.279
have a stable system again and actually had nothing but problems with it but I

00:00:17.439 --> 00:00:25.359
told myself between NVIDIA's price hikes and their attitude I am skipping the 40

00:00:23.279 --> 00:00:31.240
series which leaves me with what for options I mean Once Upon a Time 15 years

00:00:28.560 --> 00:00:36.559
ago I daily drove the radio on 3870 but I haven't touched an AMD GPU at least

00:00:33.879 --> 00:00:41.399
not in my daily driver system for 15 years have they reached the point where

00:00:39.399 --> 00:00:45.680
they're usable they've certainly reached the point where they're my only feasible

00:00:43.480 --> 00:00:52.079
option for an upgrade so this is it that's right folks it's time for the AMD

00:00:48.960 --> 00:00:55.280
challenge sponsored by cic I will be

00:00:52.079 --> 00:00:58.079
running AMD for the next 30 days and I

00:00:55.280 --> 00:01:04.000
will be bringing along with me two of my very picky Tech enthusiast friends Jake

00:01:01.440 --> 00:01:09.360
and Luke to share with you our experience so come along for the ride

00:01:06.680 --> 00:01:13.240
and uh I hope you've got a great power supply did I mention this is brought to

00:01:11.080 --> 00:01:17.320
you by seic because whether you're team green or team red these

00:01:15.119 --> 00:01:19.720
days you're going to need something pretty

00:01:26.400 --> 00:01:34.640
powerful in all seriousness I am not really expecting this to be as much of a

00:01:31.439 --> 00:01:36.840
Gong Show as the Intel version was AMD

00:01:34.640 --> 00:01:41.600
unlike Intel has been doing dedicated graphics for well ever since they

00:01:38.880 --> 00:01:46.799
acquired ATI which is I guess over 15 years now but in that time their

00:01:44.079 --> 00:01:51.280
software team has made enormous strides in terms of both compatibility and

00:01:49.040 --> 00:01:56.719
performance that is at least if the community's reviews of radi on graphics

00:01:54.399 --> 00:02:00.840
cards are anything to go by they've certainly ran into some challenges with

00:01:58.719 --> 00:02:05.039
the 7,000 series they had some issues with defective Vapor Chambers causing

00:02:02.960 --> 00:02:09.360
unusually high temperatures but that shouldn't affect me because I'm not

00:02:06.600 --> 00:02:13.800
using an AMD reference card so with confidence I'm going ahead to why is

00:02:11.640 --> 00:02:17.400
this still on you guys watched me turn it off what can I say I'm just a lot

00:02:15.879 --> 00:02:21.879
better at turning things on than turning them off all three of us went with the

00:02:19.480 --> 00:02:27.680
R9 7900 XTX so the more premium version and you

00:02:25.319 --> 00:02:32.120
know normally you don't look at the top tier card and go hm yeah that one's

00:02:30.000 --> 00:02:37.440
probably the better value but somehow AMD managed to pull it off the 7900 XT

00:02:35.120 --> 00:02:41.519
is cut down so much that for the $100 you're saving compared to the XTX it

00:02:39.959 --> 00:02:46.879
really doesn't look like a very compelling option the XTX on the other

00:02:44.120 --> 00:02:52.319
hand as long as a major Focus for you isn't Ray traced titles its performance

00:02:49.599 --> 00:02:56.560
in traditional games is extremely compelling you can get more details

00:02:54.159 --> 00:03:00.599
about it in our full review of the 7900 series that we uploaded a little while

00:02:58.560 --> 00:03:08.000
back now of course the card that we were covering was the reference card from AMD

00:03:03.640 --> 00:03:10.720
this one uh is quite a bit beefier to

00:03:08.000 --> 00:03:16.080
the point where oh God we might actually have a clearance issue here oh god um

00:03:13.799 --> 00:03:20.000
Jake can I help you what I'm just ohing for the same reason you're o goting

00:03:17.720 --> 00:03:24.360
we've come up with a solution massive thanks to Gigabyte for sending over this

00:03:21.680 --> 00:03:28.239
aors card but I guess I get to use a reference card now the last thing we

00:03:26.560 --> 00:03:32.239
want is for any of this coolant to get into our highquality seic power supply

00:03:30.360 --> 00:03:35.360
did I mention they sponsored this video so I'm just going to put this

00:03:33.680 --> 00:03:40.640
highquality ShortCircuit hoodie very absorbent in the way and make sure that

00:03:38.360 --> 00:03:45.760
we don't get any water in it oh this is going to be so easy because AMD's

00:03:42.760 --> 00:03:47.920
drivers are not going to be a problem at

00:03:45.760 --> 00:03:53.480
least that's my hope because in my review of this card I kind of committed

00:03:50.640 --> 00:03:57.840
to switching to team red so I really regardless of whether it's an aorus card

00:03:55.439 --> 00:04:02.599
or a reference card I really need this thing to be good it uses amds rdna 3

00:04:00.760 --> 00:04:08.400
architecture which is all new for the 7000 series it brings with it a huge

00:04:05.680 --> 00:04:14.040
uplifting clock speed cus or compute units AI accelerators and perhaps for me

00:04:11.799 --> 00:04:18.680
most importantly their video encoding engine has gotten a complete overhaul

00:04:15.840 --> 00:04:22.639
including support for av1 which isn't supported on streaming platforms like

00:04:20.079 --> 00:04:27.400
twitch yet but will hopefully be coming very very soon one of the other things

00:04:25.240 --> 00:04:32.240
that's really cool about AMD's rdna A3 cards is I mean not necessarily going to

00:04:30.199 --> 00:04:36.120
excite you from a performance standpoint but could excite you from a cost

00:04:33.800 --> 00:04:41.280
standpoint instead of building these cards using a monolithic or a single

00:04:38.680 --> 00:04:45.680
large die they used a chiplet approach similar to what they've done with their

00:04:42.639 --> 00:04:47.759
ryzen CPUs so instead of using the

00:04:45.680 --> 00:04:52.240
latest manufacturing process for the entire Die they actually used tsmc's 6

00:04:50.240 --> 00:04:54.919
nanometer for their memory and cache dieses since they found that there

00:04:53.360 --> 00:04:59.440
wasn't really a benefit to shrinking it down and then they used their 5

00:04:56.639 --> 00:05:03.240
nanometer process for their compute die so so that's where you're actually still

00:05:01.240 --> 00:05:09.720
getting good scaling in terms of power consumption and performance I mean

00:05:06.600 --> 00:05:11.880
they're still really expensive but like

00:05:09.720 --> 00:05:15.919
guess we'll take the little W's when we can get them another thing we can do

00:05:13.720 --> 00:05:21.960
while we wait is refill the loop because the parts aren't actually here for

00:05:18.600 --> 00:05:24.520
my 79 50x upgrade I'm just going to be

00:05:21.960 --> 00:05:29.120
running a bypass so the GPU will not be water cooled during this experiment this

00:05:26.720 --> 00:05:32.680
also allows me to like just go back to the 30 90 if I decide yeah you know what

00:05:31.479 --> 00:05:36.759
it's really not worth the extra performance Jake we cheated a little bit

00:05:35.240 --> 00:05:40.600
he's actually already done his upgrade we're shooting out of order he says it's

00:05:38.520 --> 00:05:45.000
pretty good though right off the bat I'm running into a bit of an issue because

00:05:42.680 --> 00:05:53.560
my current graphics card this RTX 380 from EVGA rest in peace just barely fits

00:05:49.360 --> 00:05:57.400
fortunately it's close this

00:05:53.560 --> 00:05:59.080
guy not even close so I think what I'm

00:05:57.400 --> 00:06:03.120
going to do there's a little bit of extra space on this bracket I think I'm

00:06:00.680 --> 00:06:09.840
going to take the pump out and this bracket and drill new holes just about

00:06:06.919 --> 00:06:13.919
that much higher so that the GPU in this slot can clear

00:06:11.199 --> 00:06:21.720
it hello wait

00:06:16.080 --> 00:06:21.720
no is that the one L of stripped damn

00:06:24.400 --> 00:06:32.000
it hey who know it could be this much work

00:06:28.680 --> 00:06:34.479
just to swap an air cooled graphics card

00:06:32.000 --> 00:06:38.080
originally the pump Circle bracket thing was using those two holes but what I

00:06:36.560 --> 00:06:43.440
found out is there's an extra set of holes in the middle so if I put the

00:06:40.319 --> 00:06:46.360
bottom holes of the Ring thing in the

00:06:43.440 --> 00:06:51.840
middle hole then I probably don't even need to drill anything I'm I think I'm

00:06:48.360 --> 00:06:53.160
going to anyways but um I could just put

00:06:51.840 --> 00:06:59.039
those two screws in and that would probably be

00:06:55.120 --> 00:07:01.039
enough look at that a hole which

00:06:59.039 --> 00:07:10.160
hopefully hits the screw it looks mint I mean the

00:07:05.879 --> 00:07:12.759
holes were a little too close

00:07:10.160 --> 00:07:18.680
together but it'll work and that's that's what matters hi AR and there it

00:07:15.080 --> 00:07:20.240
is the top of the res hits these tubes

00:07:18.680 --> 00:07:24.319
it's only screwed in with the top two holes here which don't line up with

00:07:22.240 --> 00:07:31.520
anything on the bottom because all of the holes are stripped out and now

00:07:28.039 --> 00:07:31.520
theoretically this

00:07:32.639 --> 00:07:40.319
fits hey it works I don't know why the lights

00:07:37.680 --> 00:07:44.720
are in like seizure mode right now but we can get that sort of this is less of

00:07:42.599 --> 00:07:49.479
an installation video and more of a aftermath explanation video I decided

00:07:47.440 --> 00:07:53.720
that either the GPU or the reservoir was going to have to go and as the GPU going

00:07:51.639 --> 00:08:00.280
was less work that was kind of where I landed so I got this really long PCI

00:07:57.080 --> 00:08:04.720
Express Riser cable and decided to mount

00:08:00.280 --> 00:08:07.520
the GPU on top of the computer so the

00:08:04.720 --> 00:08:11.319
graphics card just sits there except that it was overloading my power supply

00:08:08.840 --> 00:08:17.280
all the time so there's another power supply in the back powering just the

00:08:14.400 --> 00:08:22.080
graphic card and it's all mounted on the top would C Sonic trust someone

00:08:19.599 --> 00:08:28.599
irresponsible enough to pour water over a powered on computer stop it's fine

00:08:26.639 --> 00:08:35.719
they make high quality power supplies great efficiency long warranties super

00:08:31.080 --> 00:08:38.360
quiet IP can't go wrong well no not that

00:08:35.719 --> 00:08:42.120
thing no matter what your computer is SE Sonic's got you covered even if you got

00:08:39.919 --> 00:08:46.720
a big Power hog like this thing no that's a only reference one we have a

00:08:43.800 --> 00:08:52.519
very bad idea hope you catch it oh my gosh it would have come right out like

00:08:49.480 --> 00:08:52.519
it just opens

00:08:52.560 --> 00:09:00.839
Jake these people set me up for failure you know doesn't take much holy crap is

00:08:58.240 --> 00:09:08.360
this still too long Jake it's too long hold on okay no it fits it fits is it

00:09:03.519 --> 00:09:11.440
too tall though oh no it's not too slots

00:09:08.360 --> 00:09:12.839
it's two and change oh no we have to use

00:09:11.440 --> 00:09:21.959
the Riser all along wait what no oh no no no no we're

00:09:17.920 --> 00:09:23.760
not using a riser I'm not catching that

00:09:21.959 --> 00:09:27.760
okay it's just going to hit you then I got another one here you

00:09:27.880 --> 00:09:36.839
ready oh no fine oh my God that's the only one we

00:09:34.640 --> 00:09:43.120
have F that way I get to use the cool aorus one too dual bio so you got the

00:09:39.760 --> 00:09:44.480
silent and the OC version triple fans

00:09:43.120 --> 00:09:49.519
yeah triple fan I mean they're both triple fans but this one's triple fans

00:09:46.320 --> 00:09:51.519
on a big fat heat sink are you going to

00:09:49.519 --> 00:09:57.320
secure that GPU down how am I going to secure the GPU David do you ever think

00:09:53.560 --> 00:09:59.560
of that double-sided tape honestly what

00:09:57.320 --> 00:10:04.360
I was planning to do was put it right here really I mean on top of the water

00:10:01.839 --> 00:10:09.079
tube well why not it's a it's a solid it's a Hardline water cooling tube yeah

00:10:06.959 --> 00:10:14.720
until you put too much pressure on I was thinking just kind of like that and just

00:10:12.640 --> 00:10:19.160
put it on there that is significantly better than what you had

00:10:16.399 --> 00:10:24.120
before all right I'll allow it what is postcode F3 I'm looking it up F3 blah

00:10:22.480 --> 00:10:29.560
blah blah blah turn it on like while it's Q flash something something F3 we

00:10:28.000 --> 00:10:35.200
got it what did you change nothing I plugged in a keyboard I didn't change anything maybe F3 means plug in a

00:10:32.240 --> 00:10:39.839
keyboard do F3 just mean keyboard not found why would the system not post over

00:10:38.240 --> 00:10:46.360
that well hold on that's probably just cuz you turn it off a bunch of times oh

00:10:41.839 --> 00:10:49.680
uhoh uh oh no I bet the BIOS reset and

00:10:46.360 --> 00:10:52.360
I'm using like stupid AMD stupid NVMe

00:10:49.680 --> 00:10:58.959
stupid raid I better not have just lost my boot OS I vote we go to BIOS for a

00:10:55.800 --> 00:11:00.720
moment okay and we look at the PCIe

00:10:58.959 --> 00:11:06.760
device and maybe one of your nvmes just happened to die in this

00:11:02.680 --> 00:11:08.880
process did you raid zero of them yeah

00:11:06.760 --> 00:11:13.959
why for Speed it's like single threaded anyways

00:11:11.839 --> 00:11:17.720
AMD raid is garbage so it's not even a the card doesn't even have raid it's

00:11:15.040 --> 00:11:23.320
just one of those four oh my god oh lonus I know what the problem is

00:11:21.279 --> 00:11:28.120
you turn the power off like multiple times while was trying to do Windows

00:11:24.959 --> 00:11:29.600
updates you yes you did no I didn't it

00:11:28.120 --> 00:11:34.160
was trying to do Windows updates I turned the power off one time oh thanks

00:11:31.760 --> 00:11:36.440
Windows good timing Windows update yeah but then remember when you're doing the

00:11:35.200 --> 00:11:41.079
maintenance you turned it on and off and on and off like a bunch of times I guess

00:11:38.480 --> 00:11:45.600
this shouldn't be on right now okay just power it off a why is this still on I

00:11:44.279 --> 00:11:50.760
think you corrupted your own Windows install got a Windows install

00:11:48.399 --> 00:11:55.680
disc it's just it's one of those things where like

00:11:52.600 --> 00:11:58.079
honestly I don't know 95 times out of

00:11:55.680 --> 00:12:01.880
100 you interrupt a Windows update It'll like figure it out

00:12:00.480 --> 00:12:07.200
except when you're trying to film a video and you have a GPU on a rise or

00:12:04.560 --> 00:12:12.920
outside your computer and you've got water potentially dripping and it's

00:12:10.519 --> 00:12:15.800
after the end of the day and it's overtime

00:12:17.160 --> 00:12:24.639
now here's the update we have a completely different GPU with a

00:12:22.680 --> 00:12:29.360
completely different drive we have removed the drive that we think has the

00:12:27.160 --> 00:12:33.279
corrupted Windows on it and we are still getting that same error you know what it

00:12:31.240 --> 00:12:37.240
reminds me of it's behaving like the bootloader is on one storage device but

00:12:35.519 --> 00:12:42.240
then the actual operating system files are on another on two drives yeah which

00:12:40.279 --> 00:12:49.160
I've SE yeah which I've seen a lot of times but the problem is that I don't

00:12:44.680 --> 00:12:52.000
have two storage devices in here no so

00:12:49.160 --> 00:12:58.920
what is happening I don't know I'm at a loss man total loss especially since we

00:12:56.519 --> 00:13:03.920
put the 3090 back in like in the slot and still didn't

00:13:00.680 --> 00:13:05.920
go it's like an hour and a half later I

00:13:03.920 --> 00:13:09.040
think and the computer's working now so what ended up being the problem I'm

00:13:07.360 --> 00:13:12.360
pretty sure is there was some weird configuration in the BIOS because of the

00:13:10.800 --> 00:13:17.120
raid setup so I ended up taking the camos battery out putting it back in and the system booted right up installing

00:13:15.240 --> 00:13:20.720
the drivers went totally fine we had to install chipset drivers since this is

00:13:18.560 --> 00:13:24.720
from an Intel system that also went fine so it seems like everything's working

00:13:25.760 --> 00:13:31.600
great it looks like there were two contributing factors one I think Jake

00:13:30.160 --> 00:13:37.120
was right there must have been some kind of BIOS corruption and two he might have

00:13:35.240 --> 00:13:41.880
been also right about this it looks like there was a PCIe resource allocation

00:13:39.519 --> 00:13:47.560
problem so in order to get it to boot up reliably I not only had to enable above

00:13:44.240 --> 00:13:50.360
4G decoding but I also had to remove

00:13:47.560 --> 00:13:56.079
both my network card and my Thunderbolt card so I only have that carrier card

00:13:52.639 --> 00:14:00.079
for the 4 m.2 ssds and my GPU in here

00:13:56.079 --> 00:14:03.600
I'm using these Optical USB things from

00:14:00.079 --> 00:14:05.000
um uh iicon to handle USB and then I'm

00:14:03.600 --> 00:14:09.279
just running an optical DisplayPort cable straight up here Thunderbolt is

00:14:06.600 --> 00:14:12.160
not working at all after a couple small issues with the optical DisplayPort

00:14:10.680 --> 00:14:15.959
cable that's running downstairs to the gaming room I've got it running here so

00:14:14.480 --> 00:14:22.959
that seems to suggest there's no incompatibility with optical cables but

00:14:18.639 --> 00:14:25.399
I'm running into something entirely new

00:14:22.959 --> 00:14:30.839
um let see if I can get my mouse here here we

00:14:26.639 --> 00:14:33.800
go USB is just cutting out for you know

00:14:30.839 --> 00:14:38.399
3 to 5 Seconds at a time periodically here I'm moving my mouse

00:14:36.199 --> 00:14:43.920
continuously should there it goes yeah see hello

00:14:41.680 --> 00:14:49.160
nothing there it is and it's not just the mouse it's the keyboard as well just

00:14:46.320 --> 00:14:52.880
USB connectivity cuts out devices don't they don't disconnect and come

00:14:51.399 --> 00:14:59.680
back they just gone so I'm going to try a chipset driver update okay Mouse

00:14:56.800 --> 00:15:06.880
working fine chipset drivers who are what did the

00:15:01.600 --> 00:15:08.639
trick there it is wait what no

00:15:06.880 --> 00:15:12.639
um okay I

00:15:10.279 --> 00:15:16.759
mean I'm pretty sure this is running higher than I had it before with a 3090

00:15:15.279 --> 00:15:23.360
well I haven't played in a while that's for sure got him got him got him let's

00:15:24.079 --> 00:15:32.120
go no performance issues no hitching no

00:15:28.160 --> 00:15:34.440
nothing let let's go come on

00:15:32.120 --> 00:15:39.519
ah okay that was three ball kills though I'm feeling pretty good about that

00:15:36.800 --> 00:15:44.680
where's a ball someone have it what the hell are you guys

00:15:42.160 --> 00:15:51.560
doing bloody hell stop putting it

00:15:48.440 --> 00:15:53.600
down he threw it at me it's a bloody

00:15:51.560 --> 00:15:58.279
objective map you don't just go for kills what sucks is my teammates aren't

00:15:55.959 --> 00:16:03.600
even that bad from just like uh playing FPS standpoint they're just not playing

00:16:00.639 --> 00:16:08.319
the objective do these idiots not understand how the mode works hold the

00:16:05.880 --> 00:16:14.959
ball what where are you going can't blame my GPU game ran

00:16:12.120 --> 00:16:19.680
great just like this great segue to our sponsor all right well regardless the

00:16:17.160 --> 00:16:22.959
computer works but there's no segue to a sponsor cuz it's sponsored by seic so

00:16:21.240 --> 00:16:29.319
thanks to seic check them out on the link in the description if you liked

00:16:24.800 --> 00:16:32.880
this video maybe go watch the Intel AR

00:16:29.319 --> 00:16:34.240
one cuz that was just as much chaos I

00:16:32.880 --> 00:16:38.759
don't actually know if it no it wasn't as much this is

00:16:36.279 --> 00:16:43.680
awful no none of this has been AMD's fault so far the actual AMD experience

00:16:40.600 --> 00:16:43.680
has been totally fine