1 00:00:00,160 --> 00:00:05,120 So, we've all got that friend, right? You know, the one who spent all his 2 00:00:03,280 --> 00:00:09,840 money on a sick gaming PC, but then you're gaming together and he's all 3 00:00:06,480 --> 00:00:12,240 like, "Man, my PC sucks. It's no good." 4 00:00:09,840 --> 00:00:16,240 But then you're all like, "Bro, you got to get your hitching and starters under 5 00:00:13,679 --> 00:00:20,000 control. We lost again cuz of you." But then your other buddy's like, "That's 6 00:00:18,160 --> 00:00:23,600 good hardware, though. He probably just built it wrong or he misconfigured 7 00:00:21,760 --> 00:00:29,519 something." But then buddy's all like, "No way. I watched Lionus. I got all his 8 00:00:26,480 --> 00:00:31,519 tech tips." But here's the thing. Even 9 00:00:29,519 --> 00:00:36,160 when you're following a guide, it's easy to miss a small detail that can have a 10 00:00:33,840 --> 00:00:41,040 big impact on your gaming experience. And that is what we think is going on 11 00:00:38,320 --> 00:00:46,879 with Connor's computer. He's got a sick rig with an RTX 3080 Ti and an X3D 12 00:00:44,160 --> 00:00:51,760 gaming CPU. And yet, he's constantly bogged down by performance issues. Well, 13 00:00:49,520 --> 00:00:58,800 I think we can fix them. And I've got just the man for the job. Blof. That's 14 00:00:55,039 --> 00:01:00,640 right. It's time to fix Conor's 15 00:00:58,800 --> 00:01:06,320 computer. >> But first, I'm gonna have to segue to 16 00:01:04,479 --> 00:01:12,880 our sponsor, >> MSI. Their MAG 272 QP QD OLED X50 17 00:01:10,240 --> 00:01:17,360 monitor has it all from a 500Hz refresh rate to a 0.03 18 00:01:15,439 --> 00:01:22,040 millisecond greater gray response time. Check it out at the link in the video 19 00:01:19,040 --> 00:01:22,040 description. 20 00:01:27,439 --> 00:01:35,280 My name is Connor and I'm a video editor here at Linus Media Group. Inside my PC, 21 00:01:32,079 --> 00:01:38,560 I've got a 3080 Ti, a 5800 X3D, and 22 00:01:35,280 --> 00:01:40,720 about not about exactly 32 GB of RAM. I 23 00:01:38,560 --> 00:01:45,840 got two of my friends to build my PC for me back in 2019. They watched Linus Tech 24 00:01:43,759 --> 00:01:50,079 Tips, so they knew how to build PCs. Currently, what's wrong with my computer 25 00:01:47,520 --> 00:01:54,240 is that it just slows down all the time. Like I can play one match of a game and 26 00:01:51,680 --> 00:01:58,000 then I start experiencing stutters and the game takes too long to load. The 27 00:01:56,079 --> 00:02:02,799 weirdness isn't only in games. It also happens outside of games as well. So if 28 00:02:00,399 --> 00:02:07,280 I if my computer is stuttering and feeling quite poor, it translates to 29 00:02:05,360 --> 00:02:11,599 like my browser as well. It's not exclusively in games. Today I'm hoping 30 00:02:09,520 --> 00:02:15,120 to just find anything wrong with my PC. I've thrown my head against the wall a 31 00:02:13,040 --> 00:02:18,400 million times and I always get jealous when I use other people's computers. So, 32 00:02:16,560 --> 00:02:23,120 I just want to figure out something that I did wrong over the past 6 years 33 00:02:21,599 --> 00:02:28,959 >> or something that your two friends did. >> Ah, yeah. Something that my friends messed No, it's honestly something that 34 00:02:25,680 --> 00:02:30,959 LT messed up 6 years ago. 35 00:02:28,959 --> 00:02:34,959 >> Connor, we decided to do this video because I was watching the Steam Average 36 00:02:32,879 --> 00:02:41,440 PC and I noticed that you thought that computer with a 3060 and I can't not a 37 00:02:37,920 --> 00:02:42,560 5800 X3D uh was better than this and I 38 00:02:41,440 --> 00:02:46,640 thought that can't be right. >> Yeah, me neither. I don't know. It just felt better. I don't know. What can I 39 00:02:45,440 --> 00:02:50,879 say? I'd be more than happy to play it like this. Probably runs better than my home 40 00:02:49,760 --> 00:02:56,160 PC. >> How long does it take for you to start experiencing issues in a match? 41 00:02:54,480 --> 00:03:00,080 >> A few matches in. It also depends on the game I'm playing, but a few matches in. 42 00:02:57,840 --> 00:03:04,159 Tarov is notoriously bad for memory leaks and everything. Um, but even with 43 00:03:01,920 --> 00:03:06,319 Valerant, a few matches in. Um, I'm teleporting around corners and not in a 44 00:03:05,920 --> 00:03:10,959 good way. >> Oh, that's really bad. >> To be fair, if it's teleportation and 45 00:03:09,200 --> 00:03:14,080 stuff, it might be a network issue. >> Yeah. >> But we'll look at your computer at least 46 00:03:13,360 --> 00:03:19,360 today. M >> we'll try to find out what's wrong with it. Best case scenario, it's something 47 00:03:17,200 --> 00:03:22,879 easy and we fix it almost immediately. In which case, I'll go through the rest 48 00:03:21,040 --> 00:03:28,000 of our beautiful troubleshooting Connor's computer list. 49 00:03:26,400 --> 00:03:32,159 I just want to take a quick look at it and see if there's anything out of the 50 00:03:29,680 --> 00:03:36,239 ordinary. And um I see this fan's not spinning. I don't think I had enough um 51 00:03:35,360 --> 00:03:41,360 fan headers. >> Yeah. Or I'm just Well, on the plus 52 00:03:38,959 --> 00:03:44,319 side, we have a lot of splitters. So, at the very least, I'll make sure all your 53 00:03:43,360 --> 00:03:47,040 fans are spinning. >> Okay. And I see you've got neighbor media capture card. 54 00:03:46,640 --> 00:03:52,959 >> Yeah. >> And then, yeah, power supplies up top. You have any extra hard drives? These 55 00:03:50,400 --> 00:03:54,799 are just empty bays. Oh, no. I believe there's one in each. 56 00:03:54,400 --> 00:04:00,480 >> Yeah. >> Okay. >> And then at least one SSD on this side. 57 00:03:57,920 --> 00:04:03,439 >> It's a little dusty, but it's definitely not the worst I've seen. I do love all 58 00:04:02,560 --> 00:04:07,920 your stickers. >> Thank you. >> I'm a big sticker bomb guy myself. If 59 00:04:06,080 --> 00:04:11,200 anything, I'd put more stickers. I'm a big weeb, so I had to take one off 60 00:04:10,239 --> 00:04:17,040 before coming in, though. >> Why'd you have to take it off? 61 00:04:13,439 --> 00:04:18,880 >> I don't want HR coming after me. 62 00:04:17,040 --> 00:04:22,560 >> I might need you to come back to log into Steam or something for me. Um, but 63 00:04:20,799 --> 00:04:29,080 otherwise, get out of here. >> Bye. >> Get out of here, Connor. 64 00:04:24,320 --> 00:04:29,080 >> Don't type P in the search bar. 65 00:04:29,600 --> 00:04:35,840 >> Step one, check to see if things are just in the wrong spots. Uh, you 66 00:04:34,320 --> 00:04:38,960 wouldn't believe how many times I've looked at a computer that my friend or 67 00:04:37,440 --> 00:04:44,479 someone else has built and they've got the graphics card in the bottom x16 slot 68 00:04:42,000 --> 00:04:50,400 or something like that. His first top x16 is like what I'm assuming is is uh 69 00:04:47,199 --> 00:04:53,440 filled by his GPU. Um, so that's fine. 70 00:04:50,400 --> 00:04:55,040 The memory is in two and four. That's 71 00:04:53,440 --> 00:04:59,600 probably correct, but I will confirm once I get the exact board details and 72 00:04:56,960 --> 00:05:06,240 take a look at the manual. His cables seem nice and seated. Um, he is running 73 00:05:02,320 --> 00:05:08,320 a pigtail on his 3080 Ti. It's unlikely 74 00:05:06,240 --> 00:05:13,199 but possible that that's not enough juice for the single cable. So, if we 75 00:05:10,400 --> 00:05:16,160 have an extra PCIe 8 pin cable, then I might swap one of these out. But 76 00:05:14,639 --> 00:05:20,160 otherwise, you know, it looks pretty normal. That's it for step one. 77 00:05:18,240 --> 00:05:23,440 Everything is connected and it looks like it's all connected in the right 78 00:05:21,520 --> 00:05:27,919 spot. Before we move on, I'm just going to make sure that yes, the RAM is in the 79 00:05:25,919 --> 00:05:31,120 right or wrong slot. I'm going to first figure out what board it is. You don't 80 00:05:29,440 --> 00:05:35,520 need to turn it on. Most of the time, markings are pretty easily identifiable 81 00:05:33,199 --> 00:05:41,759 right on the PCB. And you can see it here, silk screened on, is X470 Gaming 82 00:05:38,880 --> 00:05:46,800 M7, uh, Gaming M7 there. And then there's some MSI logos on the back. And 83 00:05:43,680 --> 00:05:49,440 I just popped that exact X470 Gaming M7 84 00:05:46,800 --> 00:05:53,600 into Google and got the web page from MSI. And it does look 85 00:05:51,680 --> 00:05:57,680 like they're populated in the correct slots, A2, B2. So, the next thing we're 86 00:05:55,840 --> 00:06:00,560 going to do is make sure that nothing's thermal throttling. All right, first 87 00:05:59,199 --> 00:06:04,880 things first. We're going to boot up Task Manager just to make sure 88 00:06:02,320 --> 00:06:11,120 everything is as it should be. We've got our 5800 X3D. Uh, everything looks 89 00:06:07,759 --> 00:06:14,240 correct. It's barely being utilized. Um, 90 00:06:11,120 --> 00:06:15,840 seems fine. Memory though, it is 32 91 00:06:14,240 --> 00:06:21,919 gigs, but Connor does not have XMP enabled, 92 00:06:18,720 --> 00:06:24,240 and it's running at 2133. Uh, for DDR4, 93 00:06:21,919 --> 00:06:30,560 that's the Yep, that's what DDR4 does without XMPP. Um, this is almost 94 00:06:27,840 --> 00:06:33,919 definitely the problem. Let's take a quick look at everything else. It all 95 00:06:32,000 --> 00:06:36,400 kind of seems good. Ethernet is really going. He's probably just downloading a 96 00:06:35,440 --> 00:06:45,120 game or something. It's probably just like some update going on right now. And then his GPU 41C. It's a 3080 Ti. All 97 00:06:41,919 --> 00:06:48,560 right. Not doing anything. Seems totally 98 00:06:45,120 --> 00:06:51,759 fine. Let me get uh Cinebench 99 00:06:48,560 --> 00:06:54,080 and firmware installed. We got Cinebench 100 00:06:51,759 --> 00:06:56,720 R23 installed. Could use R24. Doesn't matter. They're both going to hit the 101 00:06:55,199 --> 00:07:00,880 CPU super hard. And I'm just going to hit CPU multi-core. And I've got 102 00:06:58,560 --> 00:07:06,000 hardware info open so we can watch our temperatures as it runs. Start. It's 103 00:07:03,360 --> 00:07:10,960 going. You know, the Wraith Stealth is not a 104 00:07:08,319 --> 00:07:16,240 bad cooler for a 5800X 3D, I got to say, because while, yeah, we hit like 90 C on 105 00:07:13,599 --> 00:07:21,120 the T die, that's totally fine for Cinebench, we're not going to see those 106 00:07:17,919 --> 00:07:22,560 temps in games. And it's barely 90. This 107 00:07:21,120 --> 00:07:26,800 thing could go even hotter and it'd be totally performant. So, this is probably 108 00:07:24,720 --> 00:07:30,880 fine. Let's run Firmark and see if our GPU has any issues with it. Give this a 109 00:07:28,720 --> 00:07:34,479 good like 10 plus minutes just for it to kind of soak up all those thermals and 110 00:07:33,199 --> 00:07:37,479 then we'll come back and see how it's doing. 111 00:07:38,639 --> 00:07:46,160 We're only maxing out on the GPU hotspot around like 84C. Memory is saying 96. 112 00:07:44,080 --> 00:07:50,400 That's totally fine. GPU temp overall 74. So, I'm going to go ahead and say 113 00:07:48,319 --> 00:07:53,680 that both our CPU and our GPU are running at perfectly normal 114 00:07:52,160 --> 00:07:58,800 temperatures. But you always want to check because it's a really easy way to 115 00:07:56,720 --> 00:08:03,840 lose performance. We're not overheating. So, let's check out our BIOS. I'm going 116 00:08:00,720 --> 00:08:05,759 to turn this on. 117 00:08:03,840 --> 00:08:09,840 Where's this power button? There we go. And then, uh, I'm not going to check. 118 00:08:07,440 --> 00:08:14,000 I'm just going to mash delete. Hope it goes to BIOS. 119 00:08:12,319 --> 00:08:18,160 All right. We got our BIOS up here. It's a little dated. You know, it's say M4. 120 00:08:16,080 --> 00:08:24,319 Uh, but we're going to go to advanced and then actually overclocking probably 121 00:08:21,280 --> 00:08:26,319 OC explore mode normal. Uh, sure. Let's 122 00:08:24,319 --> 00:08:29,840 keep it a normal. That's fine. Game boost switch. I don't know what game 123 00:08:28,479 --> 00:08:37,200 boost switch is. We're going to leave that. But AXMP DRAM setting. Oh god. 124 00:08:34,000 --> 00:08:41,120 Okay. So, we're going from 2133 125 00:08:37,200 --> 00:08:43,120 CL16 to 3200 126 00:08:41,120 --> 00:08:48,399 CL16. XMPP was disabled. We've enabled that 127 00:08:45,519 --> 00:08:52,399 now. That should be a massive uh jump in performance. Okay, we've checked XMPP. 128 00:08:50,720 --> 00:08:55,839 We didn't check power limits. We made this list before I remembered that it 129 00:08:53,760 --> 00:08:58,880 was an AM4 system. That's okay. It's still something you should do if you can 130 00:08:57,200 --> 00:09:02,160 or have to. After you've made your changes, don't forget to hit save and 131 00:09:00,480 --> 00:09:06,560 exit. Probably the first thing I'm going to look at is Connor's startup apps 132 00:09:04,080 --> 00:09:09,839 because uh I'm just getting into Windows. Connor, the next step is 133 00:09:08,800 --> 00:09:13,440 bloatware. >> And I dragged you over here to just make 134 00:09:11,839 --> 00:09:17,440 sure that we can turn off some startup apps because your computer takes forever 135 00:09:15,120 --> 00:09:23,040 to boot. You know this is this is true. >> Yeah. >> What do you not need? Like let like like 136 00:09:21,040 --> 00:09:24,480 >> do you really need Battlelet every single How much Battleet do you play? 137 00:09:24,320 --> 00:09:28,720 Like >> I don't play Battle Net, >> right? You're not even using You're not 138 00:09:27,360 --> 00:09:32,560 using anything from Blizzard anymore. Okay. So that's just getting off. >> Okay. What about EA? You love the EA 139 00:09:32,080 --> 00:09:38,080 app. It's >> I bought it for one game and I'm not playing it. So 140 00:09:35,120 --> 00:09:41,920 >> goodbye Epic Games Launcher. Hell no. >> Goodbye. I don't know what program is. 141 00:09:40,560 --> 00:09:49,040 We're just going to leave it there. >> Okay. >> We just got rid of like at least five, 142 00:09:46,399 --> 00:09:49,920 if not like seven or eight things at startup. 143 00:09:49,600 --> 00:09:53,360 >> Wow. >> I'm not saying this is going to like make your startup be instant. 144 00:09:52,959 --> 00:09:58,800 >> Yeah. >> But it's going to be a little faster. >> Yeah. I I the main reason I haven't done 145 00:09:57,760 --> 00:10:02,560 this is because I thought you had to go into the programs to turn it off. I didn't know you could just do it from 146 00:10:01,519 --> 00:10:08,880 settings. >> I'm learning. go to the startup apps and 147 00:10:05,440 --> 00:10:10,640 just just turn them off. That's crazy. 148 00:10:08,880 --> 00:10:15,040 Now that we've adjusted our startup apps so that a lot less is actually starting 149 00:10:12,880 --> 00:10:22,000 up, what we wanted to do was look at his storage solution. Uh just to make sure 150 00:10:17,680 --> 00:10:25,440 that Yep, there it is. He's got 24.8 151 00:10:22,000 --> 00:10:28,160 gigs left out of a 4655 gig drive. 152 00:10:25,440 --> 00:10:32,240 That's okay. Um but the bar is getting red and I personally like to have at 153 00:10:29,920 --> 00:10:36,959 least about 10% of my storage drive just stay free. I'm going to run Winderstat 154 00:10:34,320 --> 00:10:40,079 just to see what files he's got where and see what kind of space we can free 155 00:10:38,560 --> 00:10:43,760 up. I'm not going to delete anything right now in case he wants to save 156 00:10:41,920 --> 00:10:47,519 stuff, but this way he'll at least have a good idea of where to look and what he 157 00:10:46,320 --> 00:10:53,920 can at least move around cuz he's got tons of other storage drives on here that he can just offload files. Just as 158 00:10:51,279 --> 00:10:57,040 I suspected, he's got 90 gigs worth of videos. Bunch of Valerant and 159 00:10:55,440 --> 00:11:00,880 Counterstrike. Probably some Tarov stuff. Yeah, some Tarov videos here. Um, 160 00:10:59,360 --> 00:11:05,440 these are clips that he might want to keep, so I'm not going to delete them, 161 00:11:03,040 --> 00:11:12,720 but he can at least move them later and free up 90 plus gigs of storage. Uh, and 162 00:11:08,160 --> 00:11:14,240 that should be plenty. As for actual 163 00:11:12,720 --> 00:11:20,959 debloating, um, there's not a ton on here. Yeah, 164 00:11:17,920 --> 00:11:24,399 nothing really stands out here as 165 00:11:20,959 --> 00:11:26,160 particularly bad bloat wear. So, we're 166 00:11:24,399 --> 00:11:28,800 actually going to keep this as is. >> There's your problem right there. fan's 167 00:11:28,320 --> 00:11:33,440 not working. >> The one fan doesn't spin. It ran out of headers and he doesn't have any 168 00:11:31,839 --> 00:11:36,800 Ysplitters. I'm going to fix that for him. >> I'm going to I'm going to give him a 169 00:11:34,880 --> 00:11:39,600 Ysplitter. Also, his none of his RGB works. Uh he doesn't he didn't realize 170 00:11:38,399 --> 00:11:42,320 he needs an IQ link. >> Oh, yeah. >> With IQ. Can we give him an IQ link? 171 00:11:41,839 --> 00:11:46,920 >> Right. Yeah. Yeah. >> We probably have some of those. >> We should give him an IQ test. 172 00:11:50,000 --> 00:11:57,120 >> I haven't finished the entire list as you can see. >> Yeah. But the main thing is it's AM4 and 173 00:11:55,519 --> 00:12:00,880 he's using 32 gigs of RAM and it was running at 2133 MHz. 174 00:11:59,120 --> 00:12:07,040 >> Yeah. >> CDR4 you are going to want to be running 175 00:12:03,839 --> 00:12:07,760 in the sweet spot which is like 50% 176 00:12:07,040 --> 00:12:11,120 higher than that. >> Yeah. He has 3200 mega transfers uh 177 00:12:10,399 --> 00:12:15,760 modules. >> No. >> So it's like perfect. Like he'd go to 36, but 178 00:12:13,680 --> 00:12:18,880 >> but he just didn't enable DOCP >> AXMP or something on this. It's AM4. 179 00:12:17,600 --> 00:12:23,760 It's an MSI board. I don't know what to tell you. So that's disabled right now. 180 00:12:21,120 --> 00:12:27,680 >> Okay. And this is Tarov. Go ahead and try it. It's not super bad, but every 181 00:12:26,320 --> 00:12:32,639 now and then, >> it hitches. >> Did you see that? That was a huge yikes. 182 00:12:31,040 --> 00:12:35,600 >> Right. And so he's talking about how he'll be playing Tarov or whatever and 183 00:12:34,399 --> 00:12:38,720 some guy will come around the corner and his game will hitch and he'll die. >> Yeah. 184 00:12:37,519 --> 00:12:46,160 >> Which 100%. Right. >> Oh, I would die if that happened. >> Totally. And and that's a symptom of um 185 00:12:43,120 --> 00:12:48,079 memory for DDR4 3200, 3600. There's 186 00:12:46,160 --> 00:12:51,760 another one. Perfect. Perfect. >> Oh, I see it now. And you shouldn't be 187 00:12:50,079 --> 00:12:57,680 having those kinds of stutters on a system of this caliber. >> Got a 5800 X3D and a 3080 Ti. 188 00:12:55,600 --> 00:12:59,760 >> Yeah, this is a great rig. >> It should be chewing up this game. 189 00:12:59,279 --> 00:13:04,480 >> Absolutely. >> There's another one. >> So, at this point, I'm going to 190 00:13:02,320 --> 00:13:07,760 reinstall NVIDIA drivers. I noticed that he didn't even have the NVIDIA app on 191 00:13:06,079 --> 00:13:11,360 here. I don't think we need a fresh drive with the games installed. I don't 192 00:13:09,519 --> 00:13:15,600 think I have to receat stuff. Was another bad one. Yeah. Um, and I don't 193 00:13:14,160 --> 00:13:19,519 think we need to check for hardware failures because I, you know, I have to 194 00:13:17,920 --> 00:13:23,839 confirm that it's XMPP. I haven't enabled it and then gamed again. >> Yeah, this is almost certainly that 195 00:13:22,639 --> 00:13:29,120 though. I don't think this is a defective GPU. You're not getting any artifact data. You just have a awful 196 00:13:28,079 --> 00:13:35,120 bottleneck. Yeah, >> I'd say we could even go one step further and turn on PBO boost. 197 00:13:33,120 --> 00:13:39,600 >> Oh, sure. I can turn on PBO. Yep. >> 5800X 3D is not a super power hungry 198 00:13:37,839 --> 00:13:42,639 chip. So, even though we've got a stock cooler on there, I bet we could squeeze 199 00:13:40,959 --> 00:13:47,120 a little bit more out of it. throw a Y splitter to get >> actually might not even turn this one on 200 00:13:46,000 --> 00:13:50,880 >> because what you're going to be doing is you're going to be just >> going straight into that one. 201 00:13:49,279 --> 00:13:54,720 >> Yeah, I don't think this is going to do anything useful. Noctua published that 202 00:13:52,560 --> 00:13:59,519 thing recently where they showed the optimal fan layouts and it really is not 203 00:13:57,680 --> 00:14:02,560 good to just have your intake blowing straight into your exhaust. >> It makes sense. You're just making like 204 00:14:01,760 --> 00:14:06,399 a little wind tunnel. >> Yeah. So, I would maybe even just take it out. 205 00:14:05,120 --> 00:14:11,600 >> Yeah. He's got it reverse. So, this is like intake and then it's exhausting. >> Yeah. probably give it the old 206 00:14:09,680 --> 00:14:13,920 >> I'm going to dust it with a duster and then I'm his cable management is not 207 00:14:12,800 --> 00:14:19,360 great. I'm going to spend 5 10 minutes cleaning up his cables a little bit. >> It's amazing the impact of a small 208 00:14:17,839 --> 00:14:23,279 misconfiguration. Oh yeah. And this is what drives me crazy about the building 209 00:14:21,199 --> 00:14:25,600 PCs is just adult Lego crowd. It's easy for you because you know when you don't 210 00:14:24,959 --> 00:14:30,480 know >> you don't know. >> You don't know. >> You know what the best part is? His his 211 00:14:29,040 --> 00:14:35,040 two friends who built him the computer are fans. 212 00:14:35,040 --> 00:14:41,760 >> Now we're going to update our graphics driver. And Connor uh doesn't have 213 00:14:38,880 --> 00:14:46,480 GeForce Experience or the app. Um but I checked in device manager display 214 00:14:43,600 --> 00:14:50,079 adapters um his 3080 Ti properties. And I can see that his driver date is 215 00:14:47,839 --> 00:14:54,480 actually pretty recent. It's from 2025 May mid May 14th. So that's not too bad. 216 00:14:52,720 --> 00:14:58,800 But we are going to install the NVIDIA app for him. Um just cuz it works fine 217 00:14:57,199 --> 00:15:02,880 and it's a pretty easy way to keep your stuff up to date. Uh and this is super 218 00:15:00,959 --> 00:15:07,199 easy. Just go to NVIDIA's website or just search NVIDIA app. download NVIDIA 219 00:15:05,120 --> 00:15:10,800 app for gamers and creators. But yeah, there's definitely a fresh driver. Um 220 00:15:08,880 --> 00:15:14,320 the newest one's from July 1st. So, we're going to go ahead download install 221 00:15:12,959 --> 00:15:19,440 that. Once that's done, we're going to check and see if there are any Windows updates to install. We'll get those 222 00:15:17,279 --> 00:15:22,320 downloaded and ran. Easy peasy. His new game ready drivers installed. We're 223 00:15:20,880 --> 00:15:30,320 going to click restart later because I want to do all of the Windows updates now. Windows updates. 224 00:15:27,760 --> 00:15:33,519 View optional updates. Uh we don't want to do the Windows 11 stuff. Driver 225 00:15:31,760 --> 00:15:38,079 updates. Anything. Intel Corporation Bluetooth driver. Let's get the Bluetooth driver. And that should be it. 226 00:15:36,480 --> 00:15:42,720 Once all of these updates are finished installing, we'll make sure XMP is 227 00:15:40,480 --> 00:15:46,800 enabled and we'll launch a game and see if any of that stuttering is gone. It 228 00:15:44,880 --> 00:15:52,560 should be. I really hope we don't have to go through any more of our steps. Um, 229 00:15:50,800 --> 00:15:58,399 especially not swapping hardware piece by piece cuz that can can take a lot of 230 00:15:55,519 --> 00:16:03,600 time. All right, Windows is up to date and our memory is running at 3200 megat 231 00:16:01,680 --> 00:16:07,759 transfers per second now, which is much faster and our AM4 platform is really 232 00:16:06,639 --> 00:16:14,399 going to prefer that. So, let's play some games. Let's see if it stutters still. Okay, Tarov is definitely hard to 233 00:16:12,399 --> 00:16:21,680 run. And I'm still getting but I, you know, actually my 1%s are now mostly 234 00:16:17,680 --> 00:16:24,959 hovering above 60. I'm at like 90 80 an 235 00:16:21,680 --> 00:16:27,120 average of 100 something. Um, so I think 236 00:16:24,959 --> 00:16:29,839 it's definitely improved. We're looking pretty good. Don't get me wrong. 237 00:16:28,399 --> 00:16:33,279 Performance could definitely be better. Uh, Tarov doesn't always run great, but 238 00:16:31,680 --> 00:16:36,800 I haven't hitched at all. It's been at least 10 minutes. Um, and on top of 239 00:16:35,279 --> 00:16:40,079 that, I've even gotten a couple kills. >> Nice shot. >> Thankfully, we didn't have to run 240 00:16:38,560 --> 00:16:43,759 through our entire list. It was a pretty simple fix. But just in case you have 241 00:16:41,759 --> 00:16:46,959 to, here's what you'll have to do. An easy but timeconuming trick to figure 242 00:16:45,600 --> 00:16:50,399 out if you've got a software or a hardware problem is to prep a spare 243 00:16:48,720 --> 00:16:53,920 drive with a fresh Windows install, some drivers, and a game or two that you want 244 00:16:51,920 --> 00:16:57,279 to test. Simply swap the drives, boot it up, and if the fresh install behaves the 245 00:16:55,600 --> 00:17:01,040 same, then you've got an answer. And if it doesn't, that's a different answer 246 00:16:58,800 --> 00:17:04,400 entirely. Admittedly, this step is a lot easier for a company like ours with a 247 00:17:02,800 --> 00:17:08,880 ton of spare drives kicking around. But a 256 gig SATA SSD is going to perform 248 00:17:07,120 --> 00:17:13,360 just fine for a task like this and cost what, $20? And as long as you keep it as 249 00:17:11,520 --> 00:17:17,679 your test drive, it's going to last damn near forever. Our last two steps are 250 00:17:15,600 --> 00:17:21,919 really a bunch of substeps. Reseat everything and swap hardware piece by 251 00:17:19,839 --> 00:17:25,760 piece. The first one can be done by basically anybody, even if it's a pain 252 00:17:23,839 --> 00:17:29,520 in the ass. I'm looking at you CPU power cables, but you'd be surprised by how 253 00:17:27,919 --> 00:17:33,600 often the issue is simply a loose connection with your GPU or your memory 254 00:17:31,440 --> 00:17:37,280 modules, especially with a fresh build or a computer you've moved recently. And 255 00:17:35,840 --> 00:17:41,280 finally, if you're all out of ideas, start swapping hardware with an LTT 256 00:17:39,200 --> 00:17:44,799 screwdriver from ltstore.com. I typically sell my old stuff when buying 257 00:17:42,960 --> 00:17:49,120 something new, but keeping some known good memory modules kicking around or 258 00:17:46,640 --> 00:17:52,799 even buying something like a GT1030 just to confirm if your issue is with the GPU 259 00:17:51,120 --> 00:17:57,200 or the motherboard can save you a trip to warranty land. And if you don't have 260 00:17:55,520 --> 00:18:00,720 the spare parts kicking around, local computer shops often do. And if they're 261 00:17:59,200 --> 00:18:03,679 nice, they'll let you test your stuff in their store. It's tough to say what 262 00:18:02,320 --> 00:18:07,760 might be defective, but in our experience, weird random hardware issues 263 00:18:05,760 --> 00:18:13,039 are almost always because of either a bad power supply or bad memory modules. 264 00:18:10,320 --> 00:18:17,440 And if all else fails, cry. But we're not crying today because Connor, I fixed 265 00:18:16,240 --> 00:18:22,400 your computer. >> No way. Well, I'm pretty sure I did. >> I hope so. 266 00:18:20,240 --> 00:18:25,840 >> I hope so, too. Let's wait and see how the boot up time is. It's not like 267 00:18:24,240 --> 00:18:30,400 amazingly better. You were already using an SSD, but you know, we changed those 268 00:18:28,160 --> 00:18:31,919 startup apps and uh whatnot. >> I feel like it's slower than it was 269 00:18:31,600 --> 00:18:37,120 before. >> No, no, no, no, no, no, no, no, no, no, no. Don't say that. 270 00:18:36,320 --> 00:18:39,840 >> It's on. >> Yeah, that was faster. I could not tell 271 00:18:39,520 --> 00:18:45,120 you. >> It was not a lot faster, but it was a little bit faster. I'm going to take 272 00:18:42,559 --> 00:18:49,360 this as a win. Um, okay. So, your main thing that you did wrong was you didn't 273 00:18:47,520 --> 00:18:53,280 have XMP enabled. >> So, your memory, even though you bought 274 00:18:50,799 --> 00:18:59,440 a 3200 mega transfer kit, >> was only running at like default DDR4 275 00:18:55,840 --> 00:19:00,960 speeds, which is 2133. This should not 276 00:18:59,440 --> 00:19:06,000 only give you better performance in games like in your 1%s and your 277 00:19:02,799 --> 00:19:08,160 averages. Um, but it should fix most if 278 00:19:06,000 --> 00:19:12,559 not all of that stuttering that you were seeing. 279 00:19:09,039 --> 00:19:14,880 >> So, launch Tarov, I guess. So, we'll see 280 00:19:12,559 --> 00:19:18,160 how it feels to you. And, uh, what we can also do is, you 281 00:19:16,960 --> 00:19:21,200 know, you'll take it home tonight. >> Y, >> you game on it for a while. >> Yes, sir. 282 00:19:20,240 --> 00:19:26,080 >> And then let me know. >> I mean, it already feels better for this map because this map is notoriously bad. 283 00:19:25,039 --> 00:19:28,880 >> Does it actually? >> Yeah. I mean, it could just be like my 284 00:19:28,320 --> 00:19:33,919 brain. I'll >> No, no, no. It should It should have like at least a 10% performance boost, 285 00:19:32,240 --> 00:19:37,760 honestly. Maybe even more like 20% or something. >> Normally, when I load into a game, 286 00:19:36,480 --> 00:19:40,960 >> it would feel like kind of sluggish already. >> Right at the start, right as everything 287 00:19:39,600 --> 00:19:44,400 loads in and whatnot. Yeah. >> Right as everything's most competitive 288 00:19:42,640 --> 00:19:47,840 cuz everyone else is loading in. It's not the time to lag. >> Like genuinely, it feel Yeah, it feels 289 00:19:47,039 --> 00:19:52,640 better, eh? >> This is odd. >> Like how good it is now. 290 00:19:50,720 --> 00:19:56,320 >> Yeah. Like my standards for games has been pretty low cuz I just like play at 291 00:19:54,160 --> 00:19:59,360 like 60 FPS or something. Hell yeah. >> But you know what? It's not going to 292 00:19:57,360 --> 00:20:03,440 stutter anymore and you're not going to die. And you guys probably aren't 293 00:20:01,520 --> 00:20:07,520 expecting me to segue to our sponsor, >> MicroEnter. Get ready for back to school 294 00:20:05,280 --> 00:20:12,559 with their back to school sale. They've got tons of great deals like this HP 295 00:20:09,600 --> 00:20:17,360 Aero 13-inch laptop with a Ryzen 7884U, 16 gigs of RAM, and a 1 TB SSD. And hey, 296 00:20:16,160 --> 00:20:20,880 for those of you who are looking to upgrade their definitely for school 297 00:20:19,360 --> 00:20:26,720 gaming setup, you can check out this ASUS 5070 OC GPU that's actually 298 00:20:24,240 --> 00:20:31,120 available. and reasonably priced compared to MSRP. Who would have thought 299 00:20:28,640 --> 00:20:36,640 it? It's available in store like at their newly opened Santa Clara location 300 00:20:33,360 --> 00:20:37,760 which is their 29th store in the US. So, 301 00:20:36,640 --> 00:20:43,440 if you're getting ready for back to school or hey, if you just need an amazing deal on some amazing technology, 302 00:20:41,840 --> 00:20:47,280 check out MicroEnter's back to school sale using our link in the video 303 00:20:45,360 --> 00:20:53,200 description. If you like this video, maybe check out the time we tried to fix 304 00:20:49,120 --> 00:20:55,280 my monitor. Uh, we did fix it. It lasted 305 00:20:53,200 --> 00:20:58,720 another 6 months or so and then I took it to the land at Lionus's house where 306 00:20:57,120 --> 00:21:03,360 it bounced around in my car on the trip there and back and it broke. 307 00:21:01,840 --> 00:21:10,080 But I got six months out of it for like an extra 50 bucks or something so I'm 308 00:21:04,960 --> 00:21:13,120 not complaining. Waifu sticker when 309 00:21:10,080 --> 00:21:13,120 I'd pay for it.