WEBVTT 00:00:01.760 --> 00:00:10.639 War. 00:00:10.639 --> 00:00:17.840 This episode of Scrapyard Wars was brought to you by Dbrand. 00:00:15.120 --> 00:00:23.680 All right, Scrapyard Wars day three. Our internet is down. 00:00:20.720 --> 00:00:27.599 Basically, we're upgrading to one gig. And I don't know how many of you are 00:00:25.600 --> 00:00:32.480 Canadian or have heard of Telus, but they're sort of legendarily terrible. 00:00:30.160 --> 00:00:38.160 And there was apparently some kind of data entry error while they were 00:00:35.360 --> 00:00:43.120 changing our internet. I guess they were probably typing with their faces as 00:00:39.840 --> 00:00:45.600 usual. So that kind of probably hampers 00:00:43.120 --> 00:00:49.840 me a lot more than anyone else, which really sucks because now was supposed to 00:00:47.520 --> 00:00:56.800 be the time that I was finishing downloads and installs. So, I guess um 00:00:53.840 --> 00:01:01.039 what I'm going to do now is try to install everything onto the 00:00:58.399 --> 00:01:08.000 board, which is actually what I wanted to do later, but whatever. This is 00:01:04.400 --> 00:01:11.520 ridiculous. But if it works, who cares? 00:01:08.000 --> 00:01:13.040 DisplayPort, no signal. Oh, good call. 00:01:11.520 --> 00:01:19.360 So, let's get the graphics card out of the out of the equation. Oh. Oh, I saw 00:01:17.520 --> 00:01:26.080 something flash for like half a second. Yes, we have video. Okay. Okay, guys. 00:01:23.520 --> 00:01:29.759 Ah, okay. That's kind of what I was afraid of. 00:01:28.240 --> 00:01:34.200 That four pin is probably not going to be enough to keep the CPU fed. 00:01:34.880 --> 00:01:44.439 Like I expected, my wood thing is not really tall enough because I didn't take 00:01:39.439 --> 00:01:44.439 into account the height of the Velcro. 00:01:47.920 --> 00:01:58.159 Okay. Well, that's good. It's mounted and it still posts. So, that's that's a 00:01:54.960 --> 00:02:00.560 good sign. So, we moved where we were, 00:01:58.159 --> 00:02:04.159 if you didn't notice, uh because it will hopefully be better for filming reasons 00:02:02.240 --> 00:02:09.599 or whatever yet, but we should be theoretically sitting at about 3 GHz and 00:02:07.439 --> 00:02:16.959 I think our memory is still at about 720 MHz. So, CPU is running at 3 3.24 00:02:14.720 --> 00:02:22.879 GHz. I must have screwed up, but I made it 00:02:19.440 --> 00:02:25.660 faster than I expected. 00:02:22.879 --> 00:02:29.879 And it's not crashing. 00:02:30.239 --> 00:02:36.800 Might need a bigger pilot hole, but we're going to see. The wood was not 00:02:34.319 --> 00:02:41.200 super happy about that. I can't wait for the comments on this. Oh my god, Luke, 00:02:39.440 --> 00:02:45.680 you did that so wrong. I literally have no idea what I'm doing. 00:02:43.280 --> 00:02:50.879 I really don't know if this is going to help me tie the fishing line at all. I 00:02:48.480 --> 00:02:55.599 was hoping these were grippier than my skin, but I don't know if that's true 00:02:52.720 --> 00:03:01.200 anymore. Oh, it does totally seem to be true. 00:02:57.360 --> 00:03:04.480 That's awesome. Okay, that's good. If 00:03:01.200 --> 00:03:07.040 this overclock works, honestly, I'd be 00:03:04.480 --> 00:03:11.440 happy, I think, with this overclock and the overclock that I have on the CPU, 00:03:09.200 --> 00:03:15.200 but I'll have about 3 hours left. So, what I need to do is save this 00:03:13.200 --> 00:03:20.800 overclocked to a profile. I already have my CPUs overclocked saved to a profile 00:03:18.080 --> 00:03:24.159 and uh hopefully doing a little bit more cable management stuff just to make it 00:03:22.080 --> 00:03:31.560 look better. Even though that's not a metric, it would be nice. 00:03:26.720 --> 00:03:31.560 Vync off. Apply. 00:03:33.360 --> 00:03:37.920 It did not like that. 00:03:36.400 --> 00:03:44.080 Okay. After the benchmark ran, it crashed. and 00:03:41.040 --> 00:03:45.680 I don't know why it crashed. So, what I 00:03:44.080 --> 00:03:50.959 need to do now is figure out if it was my GPU or if it was my CPU. And so, what 00:03:48.560 --> 00:03:56.760 I just did was I changed my overall total power limit from 150% to 00:03:56.799 --> 00:04:04.000 uh 25% and I changed my applied voltage 00:04:00.159 --> 00:04:07.760 from 100 mts to 50 m. 00:04:04.000 --> 00:04:10.959 Whoa. What? 00:04:07.760 --> 00:04:13.360 Okay. And my GPU is not very happy right 00:04:10.959 --> 00:04:18.160 now. It's not hot. I think it doesn't have 00:04:15.680 --> 00:04:23.440 enough voltage or something. Okay, so I turned things down and they're actually 00:04:19.759 --> 00:04:26.560 running faster. So at $310, 00:04:23.440 --> 00:04:29.759 I just got 00:04:26.560 --> 00:04:31.759 Damn it. Why does it keep doing that 00:04:29.759 --> 00:04:36.560 at the same part after like the same amount of time? Okay, so after some 00:04:34.639 --> 00:04:40.320 troubleshooting, I think I know what's going on. So, we instead of using our 00:04:38.639 --> 00:04:43.520 two like really crappy power supplies, we're using one power supply that's 00:04:41.759 --> 00:04:48.160 somewhat decent. And this is now powering the graphics card and it's got 00:04:45.040 --> 00:04:49.680 eight pins to the CPU. So, the 8 pin was 00:04:48.160 --> 00:04:53.360 absolutely the problem. The four pin it was enough to get it to post, but it's 00:04:51.440 --> 00:04:57.600 not enough to actually do anything. So, the CPU I feel like is good as long as 00:04:55.280 --> 00:05:01.040 we have an 8 pin. Um, we've now switched around the power supplies so that the 00:04:59.199 --> 00:05:05.520 graphics card has its own dedicated power supply. The power supply is enough 00:05:02.800 --> 00:05:08.320 to spin the fan fully up. That's good. So, we're still using the floor pin. 00:05:06.960 --> 00:05:13.039 It's not going to be stable whatsoever. But this is more to just see if our two 00:05:10.320 --> 00:05:16.160 power supplies Yes, it's posted. Okay, we're we're in business. We're in 00:05:14.400 --> 00:05:22.720 business. So, the only thing we basically need to do right now is get 00:05:18.639 --> 00:05:25.840 the uh 4 pin to 4 pin plus molex 00:05:22.720 --> 00:05:27.919 adapter. Okay, success. We have the one 00:05:25.840 --> 00:05:32.720 tiny adapter that cost $7 that we needed. So, with our new 8 pen, we can 00:05:30.479 --> 00:05:37.680 see that the CPU is boosting up to like 3.6 GHz or so. And it's coming back 00:05:35.280 --> 00:05:42.240 down. But it seems to be working. Look at this. We're stable 100%. With only 00:05:40.160 --> 00:05:47.919 the four pin, this immediately crashed. Oh no. 00:05:44.560 --> 00:05:50.080 Memory management. No, 00:05:47.919 --> 00:05:56.320 it didn't do anything. It's just as unstable as with the four pin. Oh no. 00:05:54.639 --> 00:06:00.960 Maybe it's the power supply. Maybe the just this this 300 watt supply is just 00:05:58.000 --> 00:06:05.680 not enough to to power it. Okay, so basically right now we've swapped out 00:06:03.520 --> 00:06:10.560 memory we bought with some other memory just to see if it's the RAM that's the 00:06:07.919 --> 00:06:13.039 problem. Um I mean this is a brand new stick. This is like the only brand new 00:06:11.919 --> 00:06:18.240 component in the build. So it' be really weird if this was the part that didn't work. This is longer than it was before. 00:06:16.720 --> 00:06:23.280 The memory may have been the issue. We may have got some defective brand new 00:06:19.919 --> 00:06:25.360 memory. Wow. The only other thing we can 00:06:23.280 --> 00:06:28.720 think about is trying this RAM in a different slot. So I'm go ahead and 00:06:26.560 --> 00:06:33.360 start the stress test. So, it only lasted like 5 seconds before. 00:06:31.440 --> 00:06:37.199 Wow. Is this going to be stable? Was it literally just changing the slot in the 00:06:34.800 --> 00:06:42.639 motherboard? I'm a genius, dude. High five. Yes. Okay, at this point, let's 00:06:41.120 --> 00:06:48.319 tear this stuff down. Oh, no. We should probably play a game. Let's play a game. Okay. Download. 00:06:46.160 --> 00:06:52.639 Yes. Uh, which one thing with this build, something is weird with this 00:06:50.080 --> 00:06:56.639 motherboard. It freaks out every sing Oh, no. 00:06:55.039 --> 00:07:04.000 So, we have to go return this memory because it's broken. and it just fell out. That's awesome. 2:00. We have less 00:07:01.120 --> 00:07:07.840 than 2 hours to make sure this works and build the whole computer, get benchmarks 00:07:06.000 --> 00:07:13.360 ready. We do not have another opportunity. If this does not work, we 00:07:10.000 --> 00:07:16.160 might just be out of it. Oh man, coming 00:07:13.360 --> 00:07:20.160 down to the wire. Scrapyard Wars will be right back after 00:07:18.000 --> 00:07:23.680 these messages. This episode of Scrapyard Wars is brought to you by 00:07:21.759 --> 00:07:27.120 Dbrand, makers of the precision cut vinyl skins that you'll see on the 00:07:25.039 --> 00:07:30.479 phones and notebooks of our contestants. They offer a wide variety of styles and 00:07:28.960 --> 00:07:35.440 colors and support for the coolest devices, including the PlayStation 4, 00:07:32.479 --> 00:07:39.680 Galaxy Note 5, and iPhone 6S. Protect the body of your devices and make them 00:07:37.039 --> 00:07:45.360 look great at dbrand.com/scrapyard wars. Okay, she posts is a good sign. 00:07:43.280 --> 00:07:52.639 Well, either our motherboard has two dead PCI slots or our Sound Blaster 00:07:48.240 --> 00:07:55.759 Odigy 2 is dead. Fortunately, we grabbed 00:07:52.639 --> 00:07:58.639 a couple sound cards at the time. So, 00:07:55.759 --> 00:08:03.199 let's go ahead and try another one. So, our internet's down at the office this 00:08:00.479 --> 00:08:07.360 morning, which has made progress a little slower than I'd like. But, there 00:08:05.280 --> 00:08:12.720 is good news. I've got Windows 7 installed. My graphics card seems to be 00:08:10.400 --> 00:08:16.960 working for the most part. Uh although I haven't run anything 3D yet because I 00:08:14.479 --> 00:08:23.280 don't have drivers for it at the moment. Um there's some bad news though. Both my 00:08:19.919 --> 00:08:27.120 Ody 2, which I had high hopes for, and 00:08:23.280 --> 00:08:30.560 my Sound Blaster Live are dead. So I 00:08:27.120 --> 00:08:32.640 will have to accept that I will be 00:08:30.560 --> 00:08:37.599 running a system that only has HDMI audio. Oh. Oh. Whoa. Oh, he said, "Oh, 00:08:35.680 --> 00:08:44.399 we're up. We're up. Internet's up." Yay. So, this 00:08:41.279 --> 00:08:48.959 is exciting because 00:08:44.399 --> 00:08:51.120 I am many hours away from competition 00:08:48.959 --> 00:08:54.880 crunch time and I've got almost all of my benchmarks installed, all my drivers 00:08:53.120 --> 00:08:58.880 installed. I can start getting baseline readings and then tuning things and 00:08:56.800 --> 00:09:02.000 finding out how it goes from there. Okay, 00:09:00.480 --> 00:09:07.120 76.5 FPS average. I'm feeling a little tense 00:09:04.800 --> 00:09:15.040 today. It's 12. I haven't started my build yet. And this initial Cinevenge 00:09:10.320 --> 00:09:18.160 run is really ugly. Like if those guys 00:09:15.040 --> 00:09:21.360 ran out and got a 3770K or something 00:09:18.160 --> 00:09:23.279 like that, they'll be pulling off triple 00:09:21.360 --> 00:09:27.760 my score thanks to the improved architecture and hyperthreading. And at 00:09:25.440 --> 00:09:32.320 least unlike Austin, I'm not running around picking up components now because 00:09:30.000 --> 00:09:37.279 I'm fairly certain they did not go out for lunch. So, for the benefit of our 00:09:35.040 --> 00:09:42.240 competitor over there, I'm going to do a quick run through of all the awesome 00:09:40.240 --> 00:09:49.040 components that I've got over on my side. First, 00:09:44.880 --> 00:09:51.279 this gaming grade motherboard. Oh, yeah. 00:09:49.040 --> 00:09:56.399 Oh, yeah. Look at that. 00:09:54.080 --> 00:10:01.680 So many games. That's a gaming sound. Can I play Pac-Man? 00:09:58.399 --> 00:10:03.920 It can be Pac-Man. 00:10:01.680 --> 00:10:08.800 Oh, no. No. Nope. Nope. Nope. Nope. Nope. 00:10:05.600 --> 00:10:10.959 Next up, we have the finest power supply 00:10:08.800 --> 00:10:16.800 ever made. I mean, it was a miracle that I was even able to find these, let alone 00:10:13.920 --> 00:10:27.680 afford it with my budget. Next up, this genuine USB 2.0 4 port 00:10:22.079 --> 00:10:29.120 expansion card and 56K modem. Going to 00:10:27.680 --> 00:10:38.399 need one of these. I don't want to tell them about that, though. That's my secret weapon. Massive cooler for like 00:10:34.399 --> 00:10:41.440 wicked overclocking. Intel 750 series 00:10:38.399 --> 00:10:45.279 PCI Express SSD. We didn't even pay for 00:10:41.440 --> 00:10:48.800 that. And this put Put the 750 series 00:10:45.279 --> 00:10:51.600 SSD down again. 00:10:48.800 --> 00:10:55.519 Yeah, that doesn't really sound right. I don't think that's a 750 series SSD. 00:10:53.760 --> 00:11:00.160 Blah blah blah blah blah. I'm just standing over here lying about what 00:10:57.200 --> 00:11:06.240 computer parts I have. My name's Lionus. My voice isn't quite that high. 00:11:03.920 --> 00:11:10.640 Let's put one of our 750 series SSDs away for now. Now you have two. I always 00:11:08.240 --> 00:11:16.480 had two. So, this is actually broken. 00:11:12.480 --> 00:11:19.760 Fortunately, we have so much extra 00:11:16.480 --> 00:11:22.079 hardware that literally half of our 00:11:19.760 --> 00:11:25.440 parts could be broken and we would have no problem whatsoever. So, I'm just 00:11:23.760 --> 00:11:30.160 going to go get another one. All right. So, just in case, I brought some of our 00:11:27.440 --> 00:11:34.320 extra extra hardware that isn't the stuff that we actually need. You know, 00:11:31.920 --> 00:11:38.959 right now, just installing our bolt-on Hemi. 00:11:36.640 --> 00:11:44.399 They're lying to us. And we were so honest with them about the computer that 00:11:41.920 --> 00:11:50.240 we're building. You mean you don't believe that I have a Hemi? 00:11:47.040 --> 00:11:52.640 Well, I did believe you. 00:11:50.240 --> 00:11:57.040 I wanted to believe. I was just moving stuff around to try to 00:11:54.160 --> 00:12:02.720 do cable management and the computer froze up. Hopefully 00:12:00.399 --> 00:12:09.480 that's not actually a problem. It's probably just random 00:12:05.360 --> 00:12:09.480 old hard drives and stuff. 00:12:23.680 --> 00:12:30.160 My computer straight up doesn't boot properly anymore. 00:12:27.519 --> 00:12:34.399 I have no idea what happened. It blue screened randomly and now it doesn't 00:12:31.760 --> 00:12:40.399 properly turn on. So, I'm pretty disappointed. 00:12:36.720 --> 00:12:42.399 So, we just went from our game benchmark 00:12:40.399 --> 00:12:47.839 acting weird to our computer completely not turning on to our computer turning 00:12:45.120 --> 00:12:53.600 on, but now Windows is freaking out and super unhappy. I moved the graphics card 00:12:50.880 --> 00:12:57.519 down one slot because uh FreeGeek Vancouver said that that top slot wasn't 00:12:55.360 --> 00:13:01.839 working. I had no problems with that top slot working, but I'm just trying to 00:12:59.760 --> 00:13:07.600 minimize issues at this point because there's about 3 hours to go and I really 00:13:05.360 --> 00:13:11.120 want to be running all of the benches that I have to run and know what my 00:13:09.360 --> 00:13:16.160 scores are going to be before I walk into the final. So, I'm in the process 00:13:13.760 --> 00:13:22.800 of building my troll system, which has all of the worst of every component that 00:13:19.839 --> 00:13:25.920 I have. Like, this is like legit like one of the most stressed moments of my 00:13:24.399 --> 00:13:30.480 whole life. Okay, maybe that's a slight exaggeration, but like I'm super 00:13:28.320 --> 00:13:33.839 hardcore stressed right now. Oh man, did do we actually do it? I don't I don't 00:13:32.560 --> 00:13:38.800 want to get my hopes up right now, but like this looks good. This is the only 00:13:36.399 --> 00:13:41.680 CPU intensive test. If it finishes this, that's pretty much means that we're 00:13:40.160 --> 00:13:46.959 good. Nothing else should hit the CPU this hard for this long. All right, 00:13:44.399 --> 00:13:53.880 we're in business, dude. That's awesome. Connect it up. Oh, look at that. Like 00:13:49.839 --> 00:13:53.880 butter. Wow. 00:13:54.399 --> 00:13:59.040 This work. 00:13:59.040 --> 00:14:04.830 Yeah, I think that works. 00:14:08.959 --> 00:14:14.399 It's perfect. It's actually not that bad. Everything else has just been like 00:14:12.320 --> 00:14:18.399 typical sort of like random computer problems like dead memory or like not 00:14:16.560 --> 00:14:22.720 having the right adapter or whatever. But if it works together, we did a great 00:14:20.880 --> 00:14:25.760 job. It is terrible. But you just literally told me to do this like 5 00:14:24.000 --> 00:14:32.480 seconds ago and I agreed. What have we done, dude? This is not cool. What have 00:14:29.040 --> 00:14:34.079 we done? You your idea. 30 seconds ago 00:14:32.480 --> 00:14:37.920 you were taking credit. Like this is all Austin Ed. We're such a great team. Then 00:14:36.240 --> 00:14:42.880 we actually see what it is. Like I have nothing to do with this. 00:14:40.399 --> 00:14:48.079 This is the greatest thing ever. Thermal paste looks fine. 00:14:45.519 --> 00:14:52.000 There's a lot of it, but it looks fine. Oh my god. Yeah, there's still gunk in 00:14:50.000 --> 00:14:58.680 the CPU socket, that could super be what it is. Oh, wow. 00:14:54.880 --> 00:14:58.680 It's currently 2:26, 00:14:59.440 --> 00:15:06.560 meaning assuming it's 2:30, we've got an hour and a half left. So, if that was 00:15:04.720 --> 00:15:11.279 the problem, I think I'm still doing okay. If that wasn't the problem, I 00:15:08.720 --> 00:15:14.800 could be totally screwed. At this point, my computer doesn't make it through Fire 00:15:12.800 --> 00:15:19.199 Strike. If I completely fail a benchmark, 00:15:16.639 --> 00:15:24.800 I'm done. So, right now we're testing CPU overclock only, no GPU overclock. We 00:15:22.880 --> 00:15:29.920 just did a successful Fire Strike run completely all the way through with no 00:15:26.800 --> 00:15:31.680 overclock. Now, we're testing 3.24 on 00:15:29.920 --> 00:15:38.800 this guy. I can't believe it just crashed. 00:15:35.519 --> 00:15:41.279 I feel like sick. Like, I don't feel 00:15:38.800 --> 00:15:45.760 good at all. If that just crashed because of the overclock, that's fine. 00:15:44.160 --> 00:15:50.560 If that just crashed for any other reason, I'm screwed. 00:15:48.079 --> 00:15:56.880 So, as of right now, if I apply literally any amount of overclock to my 00:15:53.360 --> 00:15:59.120 CPU, my memory, or my graphics card, 00:15:56.880 --> 00:16:02.480 even one at a time, I can't ruin a benchmark. 00:16:00.720 --> 00:16:06.959 150 gigs. That's not right. Oh, it is 15 gig hard drive. Oh, no. It's not big 00:16:05.040 --> 00:16:11.279 enough. We only have 15 gig hard drive and there's a 200 gig SSD. We're going 00:16:09.279 --> 00:16:14.079 to have to install Windows from scratch cuz we don't have any way of finding 00:16:12.560 --> 00:16:19.199 Windows. No, we have a We don't have time, dude. 00:16:16.560 --> 00:16:21.920 Uh yeah, I've got it. Give me a sec. We have a flash. You have a flash drive? I 00:16:20.399 --> 00:16:26.959 got it from Lions. Oh, you should have told me that. I did. Oh, just now. And 00:16:24.639 --> 00:16:31.360 upstairs, too. Thank you. I'm going to be slightly late. So, slightly late. You 00:16:29.279 --> 00:16:36.560 don't have an operating system. You're also live. Okay. Okay. So, our CPU 00:16:34.000 --> 00:16:40.720 temperatures are well within reason. And we're going to do some stability testing 00:16:38.160 --> 00:16:47.360 at 3.2 GHz and go back and work on our troll system. Here we go. 00:16:45.360 --> 00:16:51.920 That sounds good. Um, I don't know if our troll system is going to end up 00:16:48.959 --> 00:16:56.720 working. I have tried to get it to post. I've tried two separate motherboards and 00:16:54.399 --> 00:17:01.040 honestly, we're at the point now where I don't have a ton of extra time to spend 00:16:58.480 --> 00:17:05.280 on it. So, I'm still going to go over there and like be working on it from 00:17:02.800 --> 00:17:10.959 time to time, but I'm probably better off focusing right now on my main system 00:17:08.720 --> 00:17:16.959 because I only have an hour and 40 minutes to dial in a GPU overclock and 00:17:14.160 --> 00:17:22.319 mod the case and build in it. Those are the three main mods. Make the 00:17:19.520 --> 00:17:29.840 motherboard fit, make the power supply fit. I guess that's only two. 00:17:25.600 --> 00:17:31.440 With a couple of drill holes, 00:17:29.840 --> 00:17:36.559 um, we can make this work. Now, here's 00:17:34.480 --> 00:17:43.830 something that I actually had sort of forgotten about. We need to make sure 00:17:39.120 --> 00:17:45.200 that this baby is going to fit here, 00:17:45.200 --> 00:17:51.880 which so far is looking like a bit of a 00:17:48.880 --> 00:17:51.880 no-go. 00:17:56.480 --> 00:18:04.960 I've never trusted this kind of standoff, so it's fine. But I'm going to 00:18:02.640 --> 00:18:10.960 tape over them just in case. I cannot afford to kill any more components at 00:18:07.840 --> 00:18:12.799 this stage in the game. So, apparently 00:18:10.960 --> 00:18:19.120 overclocking my CPU but not applying voltage kind of worked. Overclocking my 00:18:15.679 --> 00:18:21.520 GPU and not applying voltage, no, not 00:18:19.120 --> 00:18:25.840 even like a little bit. Barely got into that binch at all. So, we're going to 00:18:23.919 --> 00:18:32.320 reset the graphics card overclock. Just run it at stock. Whatever. So, there's 9 00:18:29.440 --> 00:18:36.640 minutes left. I'm just going to set it to the last overclock that worked. You 00:18:34.720 --> 00:18:41.760 can do it. Believe in yourself. 00:18:38.720 --> 00:18:46.080 Come on. 00:18:41.760 --> 00:18:49.360 Wow. Done. Hands down. It's 4:00. Minus 00:18:46.080 --> 00:18:51.039 stop. I'm done. 00:18:49.360 --> 00:18:54.400 Okay. Okay, so Windows is installing right now. Basically, after this, we 00:18:52.640 --> 00:19:01.600 need to install our benchmarks. We need to install our Hi, what's up? It's 4:00. 00:18:59.200 --> 00:19:06.240 Next time on Scrapyard Wars, Austin becomes a wizard. Lionus doesn't have to 00:19:03.840 --> 00:19:15.919 cheat, but he does. Luke's house burns to the ground. And that's all. Come see 00:19:10.080 --> 00:19:15.919 it next time on Scrapyard Wars. Yeah.