WEBVTT - TechStuff Classic: TechStuff Overclocks a CPU

0:00:04.120 --> 0:00:07.160
<v Speaker 1>Get in touch with technology with tech Stuff from how

0:00:07.200 --> 0:00:13.680
<v Speaker 1>stuff Works dot Com. Hey there, and welcome to tech Stuff.

0:00:13.720 --> 0:00:16.680
<v Speaker 1>I'm your host, Jonathan Strickland. I'm an executive producer with

0:00:16.720 --> 0:00:18.680
<v Speaker 1>How Stuff Works in I heart radio and I love

0:00:18.760 --> 0:00:21.880
<v Speaker 1>all things tech. And it's a Friday, which means it's

0:00:21.920 --> 0:00:25.919
<v Speaker 1>time for another classic episode. The episode you're about to

0:00:26.000 --> 0:00:31.240
<v Speaker 1>hear originally aired way back on February twelve, two thousand twelve,

0:00:31.800 --> 0:00:37.280
<v Speaker 1>and it's titled Text Stuff over Clocks a CPU. Now,

0:00:37.920 --> 0:00:39.640
<v Speaker 1>let's go ahead and get this out of the way.

0:00:40.000 --> 0:00:44.720
<v Speaker 1>CPUs have certainly advanced since two thousand twelve, but the

0:00:44.800 --> 0:00:49.280
<v Speaker 1>general principles behind overclocking remained the same. So I hope

0:00:49.280 --> 0:00:52.160
<v Speaker 1>you enjoy this discussion that Chris and I have about

0:00:52.280 --> 0:00:56.880
<v Speaker 1>what overclocking is and how it is accomplished and take

0:00:56.880 --> 0:01:00.520
<v Speaker 1>it away old version of me and old version of

0:01:00.600 --> 0:01:04.440
<v Speaker 1>Chris Paulett. Today, to start off our episode, we have

0:01:04.480 --> 0:01:08.360
<v Speaker 1>a little Facebook feedback you be. This comes from Brian

0:01:08.400 --> 0:01:10.800
<v Speaker 1>who says, I've been listening to you guys since almost

0:01:10.880 --> 0:01:13.199
<v Speaker 1>the beginning. Keep up the great work. I was wondering

0:01:13.240 --> 0:01:15.479
<v Speaker 1>if you could do a podcast about overclocking. You can

0:01:15.520 --> 0:01:17.280
<v Speaker 1>talk about what it is, how it works and the

0:01:17.280 --> 0:01:19.679
<v Speaker 1>pros and cons of it. I've had some experience myself

0:01:19.720 --> 0:01:21.960
<v Speaker 1>and can tell you it's well worth it. Can't wait

0:01:21.959 --> 0:01:24.920
<v Speaker 1>to listen to your next podcast. Well, Brian, this one

0:01:24.959 --> 0:01:27.680
<v Speaker 1>goes out to you. And we've talked a little bit

0:01:27.680 --> 0:01:30.640
<v Speaker 1>about over clocking and past episodes, particularly anything where we

0:01:30.720 --> 0:01:34.240
<v Speaker 1>talked about CPUs and clock cycles. But but let's let's

0:01:34.319 --> 0:01:37.440
<v Speaker 1>kind of go back and talk about what a clock

0:01:37.520 --> 0:01:43.640
<v Speaker 1>cycle is and why it's important and what overclocking actually means. Yes, now,

0:01:43.880 --> 0:01:47.160
<v Speaker 1>this is something we talked about a long time ago.

0:01:47.200 --> 0:01:49.600
<v Speaker 1>A long long time ago, we talked about the Mega

0:01:49.680 --> 0:01:53.320
<v Speaker 1>Hurt Smith and you know, the giga Hurt Smith, about

0:01:53.360 --> 0:01:56.480
<v Speaker 1>the the speed of the processor and what it means

0:01:56.520 --> 0:01:59.600
<v Speaker 1>and how it's really not necessarily all that important. In fact,

0:01:59.640 --> 0:02:03.920
<v Speaker 1>it's kind of funny looking at computers now, um, because

0:02:03.960 --> 0:02:06.520
<v Speaker 1>now that the dual core and quad core processors and

0:02:06.520 --> 0:02:10.240
<v Speaker 1>and let's just say multi core processors, um, some of

0:02:10.280 --> 0:02:13.560
<v Speaker 1>them look like they're going backward because you'll see, you know,

0:02:13.840 --> 0:02:16.200
<v Speaker 1>a two gig or hurts processor and you wait a minute,

0:02:16.240 --> 0:02:18.440
<v Speaker 1>the one I have now is a three point two

0:02:18.560 --> 0:02:21.040
<v Speaker 1>y a three point two gigg hurts. Well, yeah, because

0:02:21.040 --> 0:02:24.040
<v Speaker 1>it's got multiple cours processing, it's able to do this.

0:02:24.120 --> 0:02:27.200
<v Speaker 1>But the clock speed is is basically the rate at

0:02:27.240 --> 0:02:31.760
<v Speaker 1>which a processor is handling instructions. Very good. Yes, um,

0:02:31.800 --> 0:02:36.920
<v Speaker 1>I actually saw a pretty interesting analogy on a Yale website.

0:02:36.960 --> 0:02:40.959
<v Speaker 1>This was written by H. Gilbert, and Gilbert said that

0:02:41.320 --> 0:02:43.799
<v Speaker 1>think of it like a high school. Right, So you're

0:02:43.800 --> 0:02:47.560
<v Speaker 1>in class and then the bell rings, and that signals

0:02:47.560 --> 0:02:50.160
<v Speaker 1>the end of class. So you leave alrighte and the

0:02:50.240 --> 0:02:52.799
<v Speaker 1>second bell rings and you have to go to your

0:02:52.800 --> 0:02:55.880
<v Speaker 1>next class. So those two bells, he says, think of

0:02:55.880 --> 0:02:58.160
<v Speaker 1>that as a clock cycle. The first bells a tick

0:02:58.240 --> 0:03:01.280
<v Speaker 1>and the second bells of talk, and the entire school

0:03:01.760 --> 0:03:04.880
<v Speaker 1>reacts to those bells. It's not like one class gets

0:03:04.880 --> 0:03:07.760
<v Speaker 1>a bell and then three minutes later another class gets

0:03:07.760 --> 0:03:11.080
<v Speaker 1>a bell. It goes across the entire school. So, uh,

0:03:11.360 --> 0:03:13.800
<v Speaker 1>think of a clock cycle on a on a CPU

0:03:13.919 --> 0:03:15.680
<v Speaker 1>is the same sort of thing, except in steps, students,

0:03:15.680 --> 0:03:20.480
<v Speaker 1>we're talking about data ones and zeros, so ones and zeros,

0:03:20.520 --> 0:03:23.240
<v Speaker 1>and and that at every clock cycle, ones and zeros

0:03:23.280 --> 0:03:27.520
<v Speaker 1>are moving around. And essentially every task you want a

0:03:27.560 --> 0:03:31.520
<v Speaker 1>computer to do requires a certain number of cycles. Uh,

0:03:31.560 --> 0:03:35.280
<v Speaker 1>some tasks only require one cycle and some will require

0:03:35.320 --> 0:03:38.400
<v Speaker 1>multiple cycles because the task actually has more steps than

0:03:38.440 --> 0:03:41.520
<v Speaker 1>what you might first imagine. And this changes over time.

0:03:41.600 --> 0:03:45.760
<v Speaker 1>I should add back, you know, several years ago, many

0:03:45.840 --> 0:03:48.840
<v Speaker 1>years ago, a couple of decades now, adding two numbers

0:03:48.880 --> 0:03:54.240
<v Speaker 1>together might take six or eight clock cycles to complete, uh,

0:03:54.280 --> 0:03:57.080
<v Speaker 1>and today it might take one clock cycle. So it's

0:03:57.120 --> 0:03:59.920
<v Speaker 1>become more efficient. So that's one way that CPUs have

0:04:00.040 --> 0:04:02.120
<v Speaker 1>sped up over time. But an others that we've actually

0:04:02.160 --> 0:04:04.520
<v Speaker 1>managed to fit more clock cycles in per second, and

0:04:04.600 --> 0:04:08.160
<v Speaker 1>that's the speed we talk about with processors. That's how

0:04:08.200 --> 0:04:13.000
<v Speaker 1>many clock cycles or pulses if you prefer, go through

0:04:13.080 --> 0:04:17.600
<v Speaker 1>the the that particular element on your computer every second.

0:04:17.880 --> 0:04:21.279
<v Speaker 1>So if you hear about a here's a dinosaur. Let's

0:04:21.279 --> 0:04:23.880
<v Speaker 1>say you hear about a five hundred mega hurts processor,

0:04:24.480 --> 0:04:29.279
<v Speaker 1>that means five hundred million clock cycles per second go

0:04:29.400 --> 0:04:33.960
<v Speaker 1>through that that CPU. All things considered, that's that's pretty fast, right.

0:04:34.040 --> 0:04:35.800
<v Speaker 1>But you know, then we talk about things like a

0:04:35.839 --> 0:04:39.120
<v Speaker 1>two point for gigahertz processor that's two point four billion

0:04:39.320 --> 0:04:42.559
<v Speaker 1>clock cycles per second, much faster, which is even much faster,

0:04:42.920 --> 0:04:48.479
<v Speaker 1>and they get faster than that obviously, But that's so

0:04:48.480 --> 0:04:50.760
<v Speaker 1>so when we're talking about processor speed. We really talking

0:04:50.800 --> 0:04:54.039
<v Speaker 1>about the amount of work a processor can do within

0:04:54.080 --> 0:04:57.080
<v Speaker 1>a certain amount of time, and faster processors can do

0:04:57.160 --> 0:05:00.279
<v Speaker 1>more work in that in that time frame. So the

0:05:00.360 --> 0:05:04.280
<v Speaker 1>five hundred mega Hurts processor can do five hundred million,

0:05:04.839 --> 0:05:09.800
<v Speaker 1>uh can not five million tasks, but can use five

0:05:10.200 --> 0:05:13.440
<v Speaker 1>million clock cycles toward tasks in a second, whereas the

0:05:13.440 --> 0:05:16.000
<v Speaker 1>two point for gigahurts does two point four billion clock

0:05:16.040 --> 0:05:21.719
<v Speaker 1>cycles toward tasks in a second. So yeah, that's that's

0:05:21.839 --> 0:05:26.000
<v Speaker 1>essentially the speed element. Now, UH CPUs are not the

0:05:26.040 --> 0:05:28.240
<v Speaker 1>only thing that work on cycles, by the way, just

0:05:28.400 --> 0:05:30.600
<v Speaker 1>want to make that clear when we do talk about

0:05:30.600 --> 0:05:35.080
<v Speaker 1>clock cycles. Other elements like memory and IO devices also

0:05:35.320 --> 0:05:38.880
<v Speaker 1>operate on cycles. And all of this is controlled ultimately

0:05:38.960 --> 0:05:43.800
<v Speaker 1>by the motherboard. Yes. Now, if you're wondering how a

0:05:44.880 --> 0:05:47.960
<v Speaker 1>you know, how they come out with these chips, UM,

0:05:48.080 --> 0:05:52.680
<v Speaker 1>Well it's it's it's sort of controlled. Um. If you

0:05:52.720 --> 0:05:55.920
<v Speaker 1>think about it. Let's say, let's take Jonathan's five mega

0:05:56.000 --> 0:06:01.599
<v Speaker 1>Hurts processor. UM, the manufacturer has, you know, knows something

0:06:01.640 --> 0:06:05.920
<v Speaker 1>about the range at which this chip can operate. Um,

0:06:05.960 --> 0:06:08.480
<v Speaker 1>it can operate more slowly than that, it can operate

0:06:08.560 --> 0:06:12.359
<v Speaker 1>more quickly than that. But what goes on is in

0:06:12.440 --> 0:06:15.960
<v Speaker 1>the process of building this and testing this chip, they

0:06:16.000 --> 0:06:18.760
<v Speaker 1>know roughly about how much electricity it's going to use

0:06:18.800 --> 0:06:22.799
<v Speaker 1>and about how hot it's gonna get. Um. Many many

0:06:22.960 --> 0:06:27.400
<v Speaker 1>of us UH have an idea of what happens when

0:06:27.600 --> 0:06:32.679
<v Speaker 1>your computer overheats. UM. It will seize up eventually, UM

0:06:32.920 --> 0:06:36.599
<v Speaker 1>and decrease the operating life of the computer overall too

0:06:37.000 --> 0:06:39.440
<v Speaker 1>if it gets too hot too frequently. Yeah. So the

0:06:40.080 --> 0:06:43.040
<v Speaker 1>thing is the the manufacturer of the processor is going

0:06:43.080 --> 0:06:45.839
<v Speaker 1>to go, well, okay, this is this is a good range.

0:06:45.839 --> 0:06:48.880
<v Speaker 1>This is about what it's gonna do. And essentially, yeah,

0:06:48.920 --> 0:06:54.040
<v Speaker 1>and essentially it'll runs as fast as this without going

0:06:54.160 --> 0:06:58.279
<v Speaker 1>nuts and requiring you know, a A to be immersed

0:06:58.279 --> 0:07:01.159
<v Speaker 1>in liquid nitrogen to keep it cold. We'll get to

0:07:01.200 --> 0:07:04.080
<v Speaker 1>that right, right, So this is under normal operating conditions.

0:07:04.120 --> 0:07:06.120
<v Speaker 1>This is about how fast this chip is going to run.

0:07:06.200 --> 0:07:09.200
<v Speaker 1>Let's say it's five hundred mega hurts and and there

0:07:09.240 --> 0:07:15.960
<v Speaker 1>are instructions UM in the computer actually written into ROM

0:07:15.960 --> 0:07:20.080
<v Speaker 1>that will keep it from doing more than that. Yeah. Essentially,

0:07:20.080 --> 0:07:23.000
<v Speaker 1>you've got two elements that determine the speed. You have

0:07:23.040 --> 0:07:28.239
<v Speaker 1>the motherboard which provides a baseline speed, and those tend

0:07:28.280 --> 0:07:32.560
<v Speaker 1>to be around one, three, one sixty six or two

0:07:32.680 --> 0:07:36.640
<v Speaker 1>hundred mega hurts, and then you have a multiplier on

0:07:36.720 --> 0:07:40.720
<v Speaker 1>the CPU itself. Right, So for the five hundred megahurts

0:07:40.720 --> 0:07:43.560
<v Speaker 1>machine we were talking about, the multiplayer might be five,

0:07:43.680 --> 0:07:46.640
<v Speaker 1>and the motherboard provides one hundred mega hurts. So the

0:07:46.680 --> 0:07:49.920
<v Speaker 1>clock inside the CPU is going to run at five

0:07:50.000 --> 0:07:53.800
<v Speaker 1>times the speed of the clock on the motherboard. So

0:07:53.840 --> 0:07:57.200
<v Speaker 1>the motherboard sets the pace, the CPU multiplies that pace,

0:07:57.480 --> 0:08:00.720
<v Speaker 1>and that's where you get your processor clocks need So

0:08:01.000 --> 0:08:04.080
<v Speaker 1>the five multiplayer times the one hundred mega hurts, that's

0:08:04.080 --> 0:08:07.120
<v Speaker 1>where you get your five hundred mega hurts. Now if

0:08:07.160 --> 0:08:14.320
<v Speaker 1>you had a a multiplayer that was say twenty four

0:08:14.920 --> 0:08:17.200
<v Speaker 1>times one hundred, well that's where you get the two

0:08:17.240 --> 0:08:21.120
<v Speaker 1>point four giga hurts because you get the two thousand,

0:08:21.240 --> 0:08:24.920
<v Speaker 1>one four hundred, and then that two thousand, four hundred

0:08:24.920 --> 0:08:28.560
<v Speaker 1>mega hurts is the same as two points for gig hurts. Um.

0:08:28.600 --> 0:08:31.680
<v Speaker 1>So the multiplayers tend to be difficult to change with

0:08:31.800 --> 0:08:34.880
<v Speaker 1>most processors, not all, but a lot of processors have

0:08:35.240 --> 0:08:38.280
<v Speaker 1>the manufacturers have locked down that multiplayer in order to

0:08:38.360 --> 0:08:42.400
<v Speaker 1>prevent people from pushing it too hard and causing problems

0:08:42.440 --> 0:08:46.400
<v Speaker 1>down the line. Yeah, because Ultimately, the majority of us

0:08:46.440 --> 0:08:49.120
<v Speaker 1>are going to buy our computers. We're going to set

0:08:49.120 --> 0:08:51.240
<v Speaker 1>it up, do our work on it, play games on it,

0:08:51.360 --> 0:08:52.959
<v Speaker 1>do whatever it is that we're going to do on it.

0:08:53.320 --> 0:08:57.920
<v Speaker 1>And the point is we wanted to last. Most of

0:08:58.000 --> 0:08:59.720
<v Speaker 1>us can't just go buy a new computer. And if

0:08:59.760 --> 0:09:03.760
<v Speaker 1>we don't know what we're doing as far as over clocking, um,

0:09:03.800 --> 0:09:05.840
<v Speaker 1>you know, we're just gonna we want this machine to

0:09:05.920 --> 0:09:07.840
<v Speaker 1>last us a good long time. And if you use

0:09:07.880 --> 0:09:10.560
<v Speaker 1>it under normal circumstances, unless the fan breaks or some

0:09:10.880 --> 0:09:14.600
<v Speaker 1>the cooling mechanism breaks. Even in computers with no fans,

0:09:14.640 --> 0:09:17.320
<v Speaker 1>let's say, uh, you know one of the older Imax

0:09:17.360 --> 0:09:19.400
<v Speaker 1>that they made a point of putting no fan in.

0:09:19.840 --> 0:09:22.440
<v Speaker 1>If you clogged up the air vents with something dust,

0:09:22.960 --> 0:09:26.320
<v Speaker 1>a blanket, it will overheat and the computer will die

0:09:26.559 --> 0:09:29.360
<v Speaker 1>or it will shorten the life of it. Um, so

0:09:29.559 --> 0:09:31.520
<v Speaker 1>be un study an old crash a lot, that kind

0:09:31.520 --> 0:09:34.200
<v Speaker 1>of thing. So to the point of the manufacturer setting

0:09:34.440 --> 0:09:38.440
<v Speaker 1>a clock speed a default clock speed is is basically

0:09:38.480 --> 0:09:41.600
<v Speaker 1>to make it a motherboard, a chip on a motherboard

0:09:41.600 --> 0:09:44.600
<v Speaker 1>that it's gonna last the average computer user a good

0:09:44.640 --> 0:09:48.440
<v Speaker 1>long while years hopefully, I'd say that's the that's the point.

0:09:48.480 --> 0:09:50.679
<v Speaker 1>I'd say that's true in the majority of cases. There

0:09:50.720 --> 0:09:56.040
<v Speaker 1>are a few cases where manufacturers have developed one chip

0:09:56.120 --> 0:10:00.120
<v Speaker 1>to go in a line of computers and have it

0:10:00.160 --> 0:10:05.520
<v Speaker 1>in essentially a a an artificial limit to how fast

0:10:05.559 --> 0:10:08.400
<v Speaker 1>that processor can go per model. So let's say that

0:10:08.440 --> 0:10:12.760
<v Speaker 1>I've got a selection of computers, um, and we're gonna

0:10:12.760 --> 0:10:15.480
<v Speaker 1>say we're gonna call a Model A, B, C, and D,

0:10:16.440 --> 0:10:19.360
<v Speaker 1>and all four of these have the same processor in them,

0:10:19.880 --> 0:10:22.360
<v Speaker 1>but I've put limitations on it so that Model A

0:10:22.640 --> 0:10:26.000
<v Speaker 1>can only go at five hundred mega hurts, and Model

0:10:26.040 --> 0:10:28.880
<v Speaker 1>B as a giga hurts, and and Model C as

0:10:28.960 --> 0:10:31.080
<v Speaker 1>two gig hurts, and Model D is like two point

0:10:31.120 --> 0:10:34.120
<v Speaker 1>four giga hurts, and two point four is really where

0:10:34.160 --> 0:10:36.839
<v Speaker 1>the sweet spot is. But I've put in these artificial

0:10:37.080 --> 0:10:40.120
<v Speaker 1>limitations on the previous ones. The reason for that would

0:10:40.120 --> 0:10:42.680
<v Speaker 1>be I only have to manufacture one chip, and I

0:10:42.720 --> 0:10:46.960
<v Speaker 1>can create devices for multiple markets. Because there's some people

0:10:47.000 --> 0:10:48.800
<v Speaker 1>are gonna be out there who are saying, I need

0:10:48.840 --> 0:10:50.520
<v Speaker 1>a computer, but I don't need it to do the

0:10:51.360 --> 0:10:54.720
<v Speaker 1>latest stuff, or I can't afford to buy a computer

0:10:54.800 --> 0:10:57.640
<v Speaker 1>that has like the top level technology in it. But

0:10:57.679 --> 0:11:00.240
<v Speaker 1>I'm gonna go and get this base model instead, and

0:11:00.240 --> 0:11:01.760
<v Speaker 1>then they're going to be the up people on the

0:11:01.800 --> 0:11:04.880
<v Speaker 1>other side of it, saying I want the fastest machine

0:11:04.920 --> 0:11:07.280
<v Speaker 1>I can possibly get, so they're gonna go for the

0:11:07.280 --> 0:11:09.640
<v Speaker 1>other one. Well, they can create a whole range of

0:11:09.640 --> 0:11:13.160
<v Speaker 1>computers meeting all of these demands using the same chip

0:11:13.320 --> 0:11:15.920
<v Speaker 1>if they put those limitations in place. And in some

0:11:15.960 --> 0:11:19.920
<v Speaker 1>cases you can't really get around the multiplier limitation without

0:11:20.120 --> 0:11:25.040
<v Speaker 1>some really deep knowledge and risking ruining your computer. However,

0:11:25.520 --> 0:11:29.559
<v Speaker 1>what you can do has changed the rate on the

0:11:29.640 --> 0:11:34.120
<v Speaker 1>motherboard itself, and you do that through the BIOS system.

0:11:34.160 --> 0:11:37.360
<v Speaker 1>And before we before we get into technical detail, um,

0:11:37.400 --> 0:11:40.920
<v Speaker 1>overclocking is the process that we're talking about. Now. This

0:11:41.000 --> 0:11:46.439
<v Speaker 1>means that you're increasing the limit at which the chip

0:11:47.120 --> 0:11:51.440
<v Speaker 1>can process instructions. Yeah, it's essentially pushing more clock cycles

0:11:51.440 --> 0:11:55.040
<v Speaker 1>in per second than what the chip was recommended for.

0:11:55.880 --> 0:11:59.360
<v Speaker 1>And we should say it really is a recommendation because uh,

0:11:59.640 --> 0:12:02.160
<v Speaker 1>like so saying most of these chips, I mean almost

0:12:02.200 --> 0:12:06.240
<v Speaker 1>all chips that come out have the capacity to operate

0:12:06.400 --> 0:12:09.400
<v Speaker 1>over what they are rated for. So at two point

0:12:09.440 --> 0:12:13.320
<v Speaker 1>four gigahertz processor can actually work faster than that. In fact,

0:12:13.400 --> 0:12:16.040
<v Speaker 1>usually it's around five to ten percent faster than what

0:12:16.200 --> 0:12:19.360
<v Speaker 1>the rating is for. So if you are still five

0:12:19.400 --> 0:12:24.559
<v Speaker 1>to tempercent faster without running the risk of causing damage

0:12:24.600 --> 0:12:27.319
<v Speaker 1>to your computer, so you might be able to boost

0:12:27.360 --> 0:12:31.560
<v Speaker 1>your computer's performance by or at least the processing speed

0:12:31.600 --> 0:12:34.680
<v Speaker 1>by five or ten percent without having to worry about

0:12:35.080 --> 0:12:38.720
<v Speaker 1>additional concerns. Once you go beyond that, then you have

0:12:38.760 --> 0:12:41.560
<v Speaker 1>to start looking into creative ways of managing your computer

0:12:41.600 --> 0:12:44.000
<v Speaker 1>so that it doesn't you know, just crash on you.

0:12:44.400 --> 0:12:47.079
<v Speaker 1>And even if you do just overclock your computer a

0:12:47.120 --> 0:12:49.040
<v Speaker 1>little bit, there is a chance that stuff will crash

0:12:49.080 --> 0:12:54.160
<v Speaker 1>because sometimes programs just don't work very well with overclocked processors. Um. Yeah,

0:12:54.200 --> 0:12:58.679
<v Speaker 1>So that's the basis. Though. Overclocking means that you're pushing

0:12:58.679 --> 0:13:03.120
<v Speaker 1>through more clock cycles. Second and uh, before we again,

0:13:03.160 --> 0:13:05.240
<v Speaker 1>before we get into too much detail, this is not

0:13:05.280 --> 0:13:08.040
<v Speaker 1>the kind of thing that you want to do casually

0:13:08.200 --> 0:13:11.240
<v Speaker 1>and figure, oh, you know what, let's just go and

0:13:11.240 --> 0:13:14.240
<v Speaker 1>try this. You want to think about how what happens

0:13:14.400 --> 0:13:17.640
<v Speaker 1>if it doesn't work, because if you don't follow the

0:13:17.679 --> 0:13:20.600
<v Speaker 1>instructions carefully. Um. And we're not going to give you

0:13:20.600 --> 0:13:23.000
<v Speaker 1>a lot of instructions because there's a lot of depend

0:13:23.040 --> 0:13:25.760
<v Speaker 1>upon what the processor is so yeah. Yeah, But the

0:13:25.760 --> 0:13:28.440
<v Speaker 1>thing is, if you're not very careful, you could damage

0:13:28.440 --> 0:13:32.280
<v Speaker 1>your computer permanently. And most of the time, if you

0:13:32.320 --> 0:13:35.679
<v Speaker 1>try to overclock your processor, you're violating a warranty. So

0:13:35.720 --> 0:13:38.000
<v Speaker 1>if you if you do damage your computer, you don't

0:13:38.000 --> 0:13:40.280
<v Speaker 1>have any recourse to get it fixed by the manufacturer

0:13:40.320 --> 0:13:42.480
<v Speaker 1>because they're gonna say, hey, you did this thing you

0:13:42.520 --> 0:13:45.400
<v Speaker 1>weren't supposed to do. Therefore, we have no obligation to

0:13:45.440 --> 0:13:49.679
<v Speaker 1>help you out. So so if you do this, make

0:13:49.720 --> 0:13:51.559
<v Speaker 1>sure you you put some thought into it and make

0:13:51.559 --> 0:13:53.920
<v Speaker 1>sure this is something you feel up to and that

0:13:54.040 --> 0:13:56.439
<v Speaker 1>you're you're willing to try before you really give it

0:13:56.480 --> 0:13:58.960
<v Speaker 1>a shot. If you want to. Uh, it could be

0:13:59.080 --> 0:14:01.640
<v Speaker 1>very very profitable for you if you're looking for a

0:14:01.640 --> 0:14:05.280
<v Speaker 1>faster machine and you have the uh, the ability, and

0:14:05.320 --> 0:14:07.800
<v Speaker 1>the you know, the money if you need it. But

0:14:07.840 --> 0:14:09.920
<v Speaker 1>we can get into that now, right right. And the

0:14:09.960 --> 0:14:12.640
<v Speaker 1>reason why you would want to overclock your machine in

0:14:12.679 --> 0:14:15.720
<v Speaker 1>the first place is that it allows you to run

0:14:15.920 --> 0:14:20.320
<v Speaker 1>more advanced programs at a faster rate without having to

0:14:20.400 --> 0:14:23.200
<v Speaker 1>buy a new processor or a new machine. That's that's

0:14:23.200 --> 0:14:26.160
<v Speaker 1>the big attraction for a lot of gamers out there.

0:14:26.200 --> 0:14:28.680
<v Speaker 1>They'll they'll buy a good gaming rig and then they

0:14:28.720 --> 0:14:32.000
<v Speaker 1>over clocked their processors so that they can run games

0:14:32.040 --> 0:14:35.720
<v Speaker 1>at at the highest settings without any slowdown and to

0:14:35.880 --> 0:14:39.200
<v Speaker 1>have you know, the best performance in their game. Uh.

0:14:39.240 --> 0:14:43.160
<v Speaker 1>And also it means that you know, they they're essentially

0:14:43.200 --> 0:14:47.680
<v Speaker 1>getting higher like they're getting the equivalent of a faster processor,

0:14:47.920 --> 0:14:51.080
<v Speaker 1>but they're buying a less expensive one. Right. So if

0:14:51.120 --> 0:14:53.320
<v Speaker 1>there were say a two point eight processor out there,

0:14:53.320 --> 0:14:55.480
<v Speaker 1>in a three point two processor out there, and you

0:14:55.560 --> 0:14:57.600
<v Speaker 1>knew you could overclock your two point eight so that

0:14:57.680 --> 0:15:01.120
<v Speaker 1>would equal or exceed the three point you say, well,

0:15:01.120 --> 0:15:03.160
<v Speaker 1>why would I spend the extra money getting the three

0:15:03.160 --> 0:15:04.840
<v Speaker 1>point two when I could get the two point eight

0:15:04.880 --> 0:15:08.640
<v Speaker 1>and just over clock that puppy. And of course there's

0:15:08.680 --> 0:15:14.160
<v Speaker 1>the maker's reason because they can. Yeah, yes, there's always

0:15:14.160 --> 0:15:16.440
<v Speaker 1>that too. It's just like, hey, I I have the

0:15:16.480 --> 0:15:19.520
<v Speaker 1>ability to fiddle with my computer settings. Gosh darn it,

0:15:19.600 --> 0:15:22.080
<v Speaker 1>that's what I'm gonna do. Chris and I have more

0:15:22.120 --> 0:15:25.160
<v Speaker 1>to say about over clocking a CPU, but first let's

0:15:25.160 --> 0:15:36.320
<v Speaker 1>take a quick break to thank our sponsor. So you

0:15:36.360 --> 0:15:40.520
<v Speaker 1>were talking a moment ago about the BIOS Basic Input

0:15:40.600 --> 0:15:44.800
<v Speaker 1>Output System. Yes, now, this is a part of When

0:15:44.840 --> 0:15:46.920
<v Speaker 1>you boot up your computer, it goes through the BIOS

0:15:47.040 --> 0:15:49.720
<v Speaker 1>set up, and part of that BIO set up is

0:15:49.760 --> 0:15:53.760
<v Speaker 1>the motherboard checks the processor, sees what kind of processor

0:15:53.800 --> 0:15:56.560
<v Speaker 1>it is and what the recommended settings are, and then

0:15:57.400 --> 0:16:01.040
<v Speaker 1>goes into that recommended setting. For the speed that the

0:16:01.040 --> 0:16:06.600
<v Speaker 1>motherboard provides is later on multiplied by the processor. Uh.

0:16:07.000 --> 0:16:10.200
<v Speaker 1>The thing is, you can actually interrupt the BIOS set

0:16:10.280 --> 0:16:14.360
<v Speaker 1>up system and manually change those settings. So let's say

0:16:14.360 --> 0:16:17.000
<v Speaker 1>that it was set at one hundred mega hurts, you

0:16:17.000 --> 0:16:19.400
<v Speaker 1>could up it up to one thirty three or one

0:16:19.480 --> 0:16:22.720
<v Speaker 1>sixty six or two hundred. Although you know, the more

0:16:22.920 --> 0:16:27.880
<v Speaker 1>you boost this the the closer you ride that dangerous

0:16:28.000 --> 0:16:32.480
<v Speaker 1>edge of possibly ruining your machine. It's like like getting

0:16:32.480 --> 0:16:34.400
<v Speaker 1>in a car and pushing it faster than it was

0:16:34.480 --> 0:16:37.200
<v Speaker 1>meant to go. It can start to shake apart. Yeah,

0:16:37.320 --> 0:16:40.760
<v Speaker 1>most of the instructions I read in the process of

0:16:40.800 --> 0:16:43.600
<v Speaker 1>doing research for this podcast suggested that you would tinker

0:16:43.640 --> 0:16:49.200
<v Speaker 1>with the multiplier and basically, rather than going how high

0:16:49.240 --> 0:16:51.120
<v Speaker 1>can I push this up? Start it all the way up,

0:16:51.640 --> 0:16:54.400
<v Speaker 1>what they suggest doing is taking it up a couple

0:16:54.400 --> 0:16:58.520
<v Speaker 1>of notches. Essentially, again, read the instructions carefully for for

0:16:58.600 --> 0:17:01.720
<v Speaker 1>the the system that you have, and then and the

0:17:02.040 --> 0:17:05.040
<v Speaker 1>materials that you've got on hand. But I'm oversimplifying. For

0:17:05.040 --> 0:17:08.159
<v Speaker 1>the case of explanation, you might crank it up a

0:17:08.200 --> 0:17:11.359
<v Speaker 1>notch or two notches and test it, see how it runs.

0:17:11.400 --> 0:17:13.119
<v Speaker 1>Does it look like it's doing all right? Does it

0:17:13.160 --> 0:17:16.760
<v Speaker 1>look like it's behaving oddly? If applications all crashing, but

0:17:17.200 --> 0:17:19.520
<v Speaker 1>you might need to crank it back down again. Yeah,

0:17:19.560 --> 0:17:22.800
<v Speaker 1>And and like I said, not all multiplayers are You

0:17:22.840 --> 0:17:26.320
<v Speaker 1>can't mess with all multiplayers. It all depends on the processors.

0:17:26.320 --> 0:17:28.479
<v Speaker 1>Some of the processors are locked, so you that you

0:17:28.560 --> 0:17:31.760
<v Speaker 1>can't do that, in which case you your only recourse

0:17:31.920 --> 0:17:34.159
<v Speaker 1>is to change the setting of the motherboard as opposed

0:17:34.160 --> 0:17:37.520
<v Speaker 1>to the setting on the processor. And also some motherboards

0:17:37.760 --> 0:17:41.800
<v Speaker 1>you cannot do this through a software approach. You actually

0:17:41.840 --> 0:17:43.720
<v Speaker 1>have to use a physical approach. You have to change

0:17:43.720 --> 0:17:48.040
<v Speaker 1>these components that are called jumpers, which that will uh

0:17:48.359 --> 0:17:51.080
<v Speaker 1>will limit the motherboard speed. You have to you would

0:17:51.119 --> 0:17:54.760
<v Speaker 1>have to physically replace those, which requires opening up your

0:17:54.800 --> 0:17:58.120
<v Speaker 1>computer case and taking stuff out and changing stuff out,

0:17:58.160 --> 0:18:00.719
<v Speaker 1>and that that can get a little utimidating for folks.

0:18:00.720 --> 0:18:03.720
<v Speaker 1>It's a little bit simpler when you just hit a

0:18:03.760 --> 0:18:06.280
<v Speaker 1>couple of buttons and then change some numbers on the screen,

0:18:07.200 --> 0:18:11.359
<v Speaker 1>But that might be necessary depending on the motherboard. A

0:18:11.359 --> 0:18:14.440
<v Speaker 1>lot of the stuff about personal computers depends heavily on

0:18:14.480 --> 0:18:18.679
<v Speaker 1>the specific hardware you have, which is why if you

0:18:18.760 --> 0:18:21.719
<v Speaker 1>ever think about building a machine, you should really do

0:18:21.800 --> 0:18:24.880
<v Speaker 1>some research and make sure that you know what components

0:18:24.920 --> 0:18:28.160
<v Speaker 1>you're getting before you you jump into it. Because not

0:18:28.240 --> 0:18:31.560
<v Speaker 1>every processor is compatible with every motherboard. So if you

0:18:31.600 --> 0:18:33.960
<v Speaker 1>were to just try and create your own computer, build

0:18:33.960 --> 0:18:35.760
<v Speaker 1>your own computer, and you just you know, you were

0:18:35.800 --> 0:18:39.480
<v Speaker 1>buying whatever was on sale, you might discover that, oh,

0:18:39.520 --> 0:18:42.800
<v Speaker 1>I got this great motherboard and this great processor, but

0:18:42.880 --> 0:18:45.679
<v Speaker 1>they aren't compatible with each other, so I can't actually

0:18:45.720 --> 0:18:48.000
<v Speaker 1>build a machine out of it. Well, the same sort

0:18:48.040 --> 0:18:50.720
<v Speaker 1>of thing with overclocking. You just you know, they're different

0:18:50.760 --> 0:18:55.680
<v Speaker 1>limitations based upon the actual hardware you have. And of course,

0:18:55.840 --> 0:18:59.879
<v Speaker 1>uh it might involve depending on what you're doing, you

0:19:00.080 --> 0:19:03.440
<v Speaker 1>might have to play around with the amount of voltage

0:19:03.920 --> 0:19:07.440
<v Speaker 1>uh necessary to run the dangerous to Yeah, well, I

0:19:07.760 --> 0:19:10.679
<v Speaker 1>hopefully there are our listeners when we start talking about

0:19:10.880 --> 0:19:15.400
<v Speaker 1>the amount of electricity we're getting into um or any

0:19:15.440 --> 0:19:18.159
<v Speaker 1>any measure of electricity, they start going, oh, maybe I

0:19:18.160 --> 0:19:20.359
<v Speaker 1>don't want to do this without you know, really doing

0:19:20.359 --> 0:19:23.760
<v Speaker 1>some research. Um, I would very much recommend doing that

0:19:23.800 --> 0:19:27.080
<v Speaker 1>if you are going to do getting into really messing

0:19:27.080 --> 0:19:30.200
<v Speaker 1>with this. Um. But yeah, there it is worth noting

0:19:30.240 --> 0:19:34.879
<v Speaker 1>though that uh uh certain boards are you know, certain

0:19:34.920 --> 0:19:39.639
<v Speaker 1>processors I should say, come with the the ability to

0:19:39.720 --> 0:19:43.920
<v Speaker 1>overclock sort of sanctioned. Yeah, they're built in. Intel has

0:19:43.920 --> 0:19:47.720
<v Speaker 1>several chips that you can uh go into a specific

0:19:47.800 --> 0:19:51.200
<v Speaker 1>screen and change the settings if you want to overclock

0:19:51.280 --> 0:19:55.479
<v Speaker 1>your processor, like the Extreme edition. Yeah, so that way, seriously,

0:19:55.640 --> 0:19:57.560
<v Speaker 1>you can do like the turbo stuff, or you can

0:19:57.600 --> 0:20:01.240
<v Speaker 1>actually knock up the processors bed you can change the

0:20:01.320 --> 0:20:04.440
<v Speaker 1>multiplier a little bit, that kind of stuff. And uh,

0:20:04.480 --> 0:20:06.720
<v Speaker 1>you know again this is you might ask, well, why

0:20:06.760 --> 0:20:08.679
<v Speaker 1>isn't it like that just out of the box. Well,

0:20:08.800 --> 0:20:11.639
<v Speaker 1>for one thing, not everyone needs that kind of performance.

0:20:11.680 --> 0:20:15.200
<v Speaker 1>And for another, uh, here's the thing about processors. We've

0:20:15.200 --> 0:20:17.280
<v Speaker 1>talked about heat a bit and about generating heat, and

0:20:17.480 --> 0:20:19.800
<v Speaker 1>too much heat can be a bad thing. When you

0:20:19.840 --> 0:20:24.560
<v Speaker 1>have electricity running through a circuit, it generates heat as

0:20:24.560 --> 0:20:28.119
<v Speaker 1>a byproduct. Some energy is lost due to heat waste.

0:20:28.160 --> 0:20:31.440
<v Speaker 1>It waste some of its energy as heat. Yeah, so

0:20:31.840 --> 0:20:36.120
<v Speaker 1>the more electricity you're pushing through. The more the more

0:20:36.400 --> 0:20:39.680
<v Speaker 1>uh work you're making your system do, the more heat

0:20:39.720 --> 0:20:43.200
<v Speaker 1>it's going to generate. And before long that heat might

0:20:43.280 --> 0:20:46.720
<v Speaker 1>get to a point that's causing damage or or causing

0:20:46.760 --> 0:20:49.720
<v Speaker 1>malfunctions within the machine itself. So you have to figure

0:20:49.720 --> 0:20:52.720
<v Speaker 1>out a way of dispersing that heat UM to handle that,

0:20:53.280 --> 0:20:55.680
<v Speaker 1>or else your device isn't gonna work for very long.

0:20:55.720 --> 0:20:58.280
<v Speaker 1>You might have the world's fastest computer, but only for

0:20:58.320 --> 0:21:03.440
<v Speaker 1>a few minutes before it just of yeah, well, of course,

0:21:03.920 --> 0:21:06.119
<v Speaker 1>there have been computers with no fans. There have been

0:21:06.160 --> 0:21:08.840
<v Speaker 1>computers with multiple fans. It all sort of depends on

0:21:08.840 --> 0:21:11.160
<v Speaker 1>on the guts on the you know, the stuff that's

0:21:11.160 --> 0:21:14.800
<v Speaker 1>inside the box um. And if you go to different

0:21:14.840 --> 0:21:19.600
<v Speaker 1>overclocking communities, you can learn about the parts and bits

0:21:19.640 --> 0:21:22.800
<v Speaker 1>that people uh seem to feel are the best. Now

0:21:22.840 --> 0:21:25.440
<v Speaker 1>I saw a couple of fans listed as being excellent

0:21:25.480 --> 0:21:28.320
<v Speaker 1>for overclockers because they're reliable and they push a lot

0:21:28.320 --> 0:21:31.399
<v Speaker 1>of air UM. But depending on what you're doing, that

0:21:31.480 --> 0:21:33.280
<v Speaker 1>may not be enough. You might have to go to

0:21:33.359 --> 0:21:36.399
<v Speaker 1>say a water cooling system, which uh you know, water

0:21:36.560 --> 0:21:40.280
<v Speaker 1>is a much more efficient dispersal of heat than than air,

0:21:40.400 --> 0:21:44.840
<v Speaker 1>is it dispersal. I'm making up words now or misusing

0:21:44.880 --> 0:21:47.520
<v Speaker 1>them at any rate. So anyway, water is much better

0:21:47.560 --> 0:21:50.480
<v Speaker 1>at taking care of heat than than air is, and

0:21:50.520 --> 0:21:54.639
<v Speaker 1>so a water based cooling system can be very useful

0:21:54.680 --> 0:21:57.320
<v Speaker 1>for people who are overclocking their their machines and they

0:21:57.359 --> 0:22:00.159
<v Speaker 1>want to really push it to the limit. Yeah, I

0:22:00.240 --> 0:22:02.879
<v Speaker 1>was joking about the liquid nitrogen earlier, but there are

0:22:02.880 --> 0:22:07.000
<v Speaker 1>people who have some very elaborate liquid cooled computer systems.

0:22:07.040 --> 0:22:09.840
<v Speaker 1>And depending on how much you're you're pushing, especially if

0:22:09.840 --> 0:22:12.320
<v Speaker 1>you have something like the again like the Intel chips

0:22:12.320 --> 0:22:14.960
<v Speaker 1>are the A M. D S Black Edition chips where

0:22:15.000 --> 0:22:18.920
<v Speaker 1>you can you've got the opportunity to really tinker with it. Um,

0:22:19.080 --> 0:22:23.680
<v Speaker 1>you might do that. There are actually an over clucking competitions.

0:22:23.800 --> 0:22:28.920
<v Speaker 1>Liquid nitrogen has been used to cool uh CPUs. Yeah,

0:22:28.920 --> 0:22:30.959
<v Speaker 1>I'm just it's not the kind of thing that the

0:22:31.040 --> 0:22:33.879
<v Speaker 1>general public because it's all gonna have. You'm not gonna

0:22:33.920 --> 0:22:36.720
<v Speaker 1>have a steady supply of liquid nitrogen to run through

0:22:36.760 --> 0:22:39.679
<v Speaker 1>your machine constantly so that you can you can keep

0:22:39.720 --> 0:22:42.080
<v Speaker 1>it going. But in any how have you seen my

0:22:42.119 --> 0:22:46.240
<v Speaker 1>liquid nitrogen? It's not under the stage. Why do you

0:22:46.320 --> 0:22:51.280
<v Speaker 1>need to know the uh uh where is my super suit.

0:22:51.760 --> 0:22:54.720
<v Speaker 1>The uh yeah, but if you if you, if you

0:22:54.760 --> 0:22:57.040
<v Speaker 1>don't have a stay supply of liquid nitrogen, then you

0:22:57.040 --> 0:22:59.400
<v Speaker 1>know what are cooling or some other method is probably

0:23:00.240 --> 0:23:03.480
<v Speaker 1>the best for you. But during these competitions that the

0:23:03.520 --> 0:23:07.960
<v Speaker 1>purpose of the competitions isn't to build the fastest computer.

0:23:08.080 --> 0:23:10.679
<v Speaker 1>It's to to try and push the limits of overclocking

0:23:10.680 --> 0:23:12.960
<v Speaker 1>as far as you can go. It's not that you're

0:23:13.000 --> 0:23:16.840
<v Speaker 1>going to have a practical machine after you're done, right,

0:23:16.840 --> 0:23:20.520
<v Speaker 1>It's just this is an example of a a an artist,

0:23:20.560 --> 0:23:24.080
<v Speaker 1>if you will, an engineer really knowing the limitations and

0:23:24.119 --> 0:23:26.080
<v Speaker 1>how to play with them and how to push things

0:23:26.320 --> 0:23:29.959
<v Speaker 1>to a super speed. So at ce S two thousand

0:23:30.000 --> 0:23:34.680
<v Speaker 1>eleven there was an overclocking competition where they had several

0:23:34.760 --> 0:23:38.480
<v Speaker 1>different phases and they were overclocking things not just CPUs

0:23:38.480 --> 0:23:41.600
<v Speaker 1>but also graphics processing cards because you can do this

0:23:41.640 --> 0:23:44.879
<v Speaker 1>with various components, not just CPUs. It's just that's what

0:23:45.000 --> 0:23:47.159
<v Speaker 1>we tend to think about when we talk about overclocking.

0:23:47.720 --> 0:23:51.040
<v Speaker 1>But in this competition, they took an I seven nine

0:23:51.520 --> 0:23:56.320
<v Speaker 1>nine X Intel chip, which normally runs at three point

0:23:56.400 --> 0:23:59.800
<v Speaker 1>three three giga hurts with a turbo speed capable of

0:24:00.160 --> 0:24:05.440
<v Speaker 1>points six giga hurts. That's pretty darn fast. They overclocked

0:24:05.480 --> 0:24:09.399
<v Speaker 1>it to five point nine three five giga hurts, so

0:24:09.600 --> 0:24:13.720
<v Speaker 1>nearly six giga hurts of of clock speed. UM, and

0:24:14.040 --> 0:24:19.040
<v Speaker 1>that was using some pretty phenomenal cooling mechanisms. Uh, not

0:24:19.240 --> 0:24:21.440
<v Speaker 1>something that the average consumer is going to have at

0:24:21.520 --> 0:24:26.600
<v Speaker 1>his or her fingertips. Not the average consumer. Maybe maybe

0:24:26.600 --> 0:24:30.440
<v Speaker 1>if your last name is do find Schmirtz, you might

0:24:30.480 --> 0:24:33.439
<v Speaker 1>have something. Well, yeah, but that's all coming from the

0:24:34.040 --> 0:24:40.480
<v Speaker 1>alimony my coldinator. Hither guys, it's Jonathan FROMT the Future.

0:24:40.600 --> 0:24:43.480
<v Speaker 1>I'm just gonna have us take another quick break to

0:24:43.600 --> 0:24:53.560
<v Speaker 1>thank our sponsor. When you overclock your process or, it

0:24:53.600 --> 0:24:56.639
<v Speaker 1>does require that you tweak some other settings on your computer,

0:24:56.680 --> 0:25:00.400
<v Speaker 1>including the ram UM. So keep in mind that this

0:25:00.480 --> 0:25:04.000
<v Speaker 1>is not a a if you're just sort of I

0:25:04.119 --> 0:25:06.960
<v Speaker 1>thinking of tinkering with it just for the fun of it. UM.

0:25:07.119 --> 0:25:09.600
<v Speaker 1>Keep in mind that once you start messing with one

0:25:09.680 --> 0:25:12.120
<v Speaker 1>part of it, you might have to tune some other

0:25:12.240 --> 0:25:18.120
<v Speaker 1>factors relating to your your computer's operations. So uh, make

0:25:18.160 --> 0:25:21.480
<v Speaker 1>sure you do a bit of reading about the processor

0:25:21.560 --> 0:25:24.520
<v Speaker 1>you're using, UM and the other equipment, the ram the

0:25:24.560 --> 0:25:27.520
<v Speaker 1>type of ram UM. You might even check out your GPU.

0:25:27.680 --> 0:25:30.200
<v Speaker 1>If you're feeling bold, you might even try to overclock

0:25:30.240 --> 0:25:34.600
<v Speaker 1>your GPU again. This will also increase the amount of heat. Um.

0:25:34.640 --> 0:25:37.360
<v Speaker 1>So you this might be a good time to uh

0:25:38.160 --> 0:25:42.400
<v Speaker 1>move your computer to a small bard in Norway where

0:25:42.440 --> 0:25:45.840
<v Speaker 1>it is where I'm told it's rather chilly. Um. But

0:25:46.720 --> 0:25:48.640
<v Speaker 1>the people of the seed vault are be coming. No

0:25:48.800 --> 0:25:52.560
<v Speaker 1>move it down there, making the seeds warm up. But

0:25:52.640 --> 0:25:54.600
<v Speaker 1>so yeah, it's quite a bit of there's quite a

0:25:54.600 --> 0:25:56.760
<v Speaker 1>bit of tinkering that could be involved with this that

0:25:57.040 --> 0:25:58.720
<v Speaker 1>you know. It's not just a oh well, I'm just

0:25:58.760 --> 0:26:01.000
<v Speaker 1>gonna turn this one up to eleven. Yeah, there are

0:26:01.000 --> 0:26:03.480
<v Speaker 1>a lot of resources out on the net that will

0:26:03.560 --> 0:26:05.880
<v Speaker 1>help you out if you want to try this. And

0:26:06.440 --> 0:26:10.040
<v Speaker 1>really the nice thing is there's so many that are

0:26:10.040 --> 0:26:12.320
<v Speaker 1>out there that you've got a good chance. If you

0:26:12.400 --> 0:26:16.320
<v Speaker 1>just plug in whatever processor you have and the word

0:26:16.440 --> 0:26:20.040
<v Speaker 1>overclocking into a decent search engine, you will probably get

0:26:20.080 --> 0:26:24.000
<v Speaker 1>some returns from people who have gone through this process

0:26:24.040 --> 0:26:25.960
<v Speaker 1>and they can tell you what worked for them or

0:26:26.000 --> 0:26:29.159
<v Speaker 1>what you know, what things to avoid um. And like

0:26:29.200 --> 0:26:30.880
<v Speaker 1>I said, there are a lot of communities out there

0:26:30.880 --> 0:26:34.240
<v Speaker 1>on the net that have just full discussions, like full

0:26:34.280 --> 0:26:37.520
<v Speaker 1>message boards just dedicated to overclocking and the different techniques

0:26:37.560 --> 0:26:39.880
<v Speaker 1>that they used, and uh, you know, some of these

0:26:39.960 --> 0:26:42.120
<v Speaker 1>might be a little technical and might require a little

0:26:42.119 --> 0:26:47.880
<v Speaker 1>bit of backtracking so that you can really understand the

0:26:46.880 --> 0:26:51.280
<v Speaker 1>the subtle, the subtleties of what it is they're saying.

0:26:51.520 --> 0:26:56.040
<v Speaker 1>But but it's totally doable. I mean, in most cases,

0:26:56.080 --> 0:26:58.960
<v Speaker 1>it's doable without you ever having to crack open your computer,

0:26:59.080 --> 0:27:00.919
<v Speaker 1>which is the best part, right, you know, because you

0:27:01.400 --> 0:27:03.080
<v Speaker 1>every time you have to open your computer and take

0:27:03.119 --> 0:27:07.840
<v Speaker 1>stuff out, that eliminates a significant percentage of the people

0:27:07.840 --> 0:27:10.200
<v Speaker 1>who would have tried it otherwise just because it's either

0:27:10.359 --> 0:27:13.120
<v Speaker 1>too much of a hassle or they find it too intimidating.

0:27:14.119 --> 0:27:17.159
<v Speaker 1>Um two things though, to to make sure one that

0:27:17.240 --> 0:27:22.440
<v Speaker 1>you don't make assumptions on similarities. That was one thing

0:27:22.480 --> 0:27:24.680
<v Speaker 1>that that I read that if your computer, if you're

0:27:24.680 --> 0:27:28.040
<v Speaker 1>reading information reform about overclocking, you're getting ready, you're you're

0:27:28.240 --> 0:27:32.120
<v Speaker 1>gotten the bug. You're seriously thinking about this now, and

0:27:32.160 --> 0:27:34.719
<v Speaker 1>that you're reading a post by someone who's done it,

0:27:35.000 --> 0:27:37.600
<v Speaker 1>who's who's got a chip that's a little that's just

0:27:37.680 --> 0:27:40.560
<v Speaker 1>a little different than yours. Don't go by that information.

0:27:40.600 --> 0:27:43.320
<v Speaker 1>They said that um from from what I have read

0:27:43.440 --> 0:27:45.880
<v Speaker 1>from people who have written instructions on so you want

0:27:45.920 --> 0:27:48.680
<v Speaker 1>to overclock your computer, well, here's what you should do.

0:27:48.840 --> 0:27:50.760
<v Speaker 1>That was one of the things that I read several

0:27:50.800 --> 0:27:54.240
<v Speaker 1>times was if you've got something that's very similar to

0:27:54.480 --> 0:27:58.040
<v Speaker 1>what you've got to the instructions from, don't don't go

0:27:58.280 --> 0:28:01.719
<v Speaker 1>by strict similarities. Make sure that you are going by

0:28:01.840 --> 0:28:06.320
<v Speaker 1>someone who knows instructions based on the specific stuff that

0:28:06.320 --> 0:28:09.879
<v Speaker 1>you're using, because similarities aren't good enough. When you're messing

0:28:09.880 --> 0:28:12.960
<v Speaker 1>with this, you could seriously damage your computer. And uh,

0:28:13.200 --> 0:28:16.760
<v Speaker 1>that's the other part. Make sure that you're really willing

0:28:16.920 --> 0:28:20.119
<v Speaker 1>to give this a try, knowing that you might really

0:28:20.320 --> 0:28:23.240
<v Speaker 1>muck things up for the insides of your machine. Yeah,

0:28:23.240 --> 0:28:26.080
<v Speaker 1>if you're careful, you probably don't really need to worry

0:28:26.119 --> 0:28:27.440
<v Speaker 1>so much. But it's good to have in the back

0:28:27.480 --> 0:28:30.679
<v Speaker 1>of your mind because otherwise, you know, if you you know,

0:28:30.800 --> 0:28:32.640
<v Speaker 1>if you do the typical what we like to think

0:28:32.680 --> 0:28:35.880
<v Speaker 1>of as the typical American thing, we're more equals better, right,

0:28:36.000 --> 0:28:38.560
<v Speaker 1>you might be Let's Craig get up to eleven and

0:28:38.600 --> 0:28:42.080
<v Speaker 1>the next thing you know, your machine doesn't do anything anymore.

0:28:42.160 --> 0:28:45.640
<v Speaker 1>It's not it's not doing anything faster than any machine

0:28:45.640 --> 0:28:49.280
<v Speaker 1>you've ever had. My computer does nothing at the speed

0:28:49.320 --> 0:28:54.160
<v Speaker 1>of light. It works great as a doorstop. No, I'm

0:28:54.200 --> 0:28:56.200
<v Speaker 1>sure that there will be somebody out there who's listening

0:28:56.360 --> 0:28:59.240
<v Speaker 1>listening to this podcast who has had experience overclocking, and

0:28:59.240 --> 0:29:01.640
<v Speaker 1>they're going to write in and say no, Jonathan and Chris,

0:29:01.680 --> 0:29:05.680
<v Speaker 1>it's easy to overclock maybe for some people, but for

0:29:05.760 --> 0:29:09.720
<v Speaker 1>some systems and for some systems, but um, you can't.

0:29:09.760 --> 0:29:13.720
<v Speaker 1>You can't. You can't apply that universally across everybody. And uh,

0:29:13.800 --> 0:29:16.840
<v Speaker 1>and it's it is possible that if you're not careful,

0:29:17.120 --> 0:29:20.640
<v Speaker 1>you could damage your computer. And if you don't have

0:29:20.680 --> 0:29:24.000
<v Speaker 1>a need for overclocking, if you're not playing lots of

0:29:24.000 --> 0:29:30.360
<v Speaker 1>of of high like resource demanding games or or other

0:29:30.400 --> 0:29:35.080
<v Speaker 1>applications that just require a lot of processing power. Um.

0:29:35.120 --> 0:29:37.360
<v Speaker 1>I mean, it could be a fun experiment if it's

0:29:37.360 --> 0:29:38.920
<v Speaker 1>something that you just want to try and get your

0:29:38.920 --> 0:29:40.600
<v Speaker 1>hand in, and especially if you have like an old

0:29:40.640 --> 0:29:42.760
<v Speaker 1>machine lying around that you don't really care about and

0:29:42.760 --> 0:29:45.320
<v Speaker 1>you just want to have the experience of overclocking something,

0:29:45.360 --> 0:29:47.360
<v Speaker 1>that's fine. But if you don't really have a need

0:29:47.400 --> 0:29:49.800
<v Speaker 1>for it at all, I really don't see any reason

0:29:49.840 --> 0:29:52.680
<v Speaker 1>to do it because Ultimately, if you are overclocking your

0:29:52.720 --> 0:29:56.080
<v Speaker 1>machine to really push its limits, that is, it is

0:29:56.120 --> 0:29:58.000
<v Speaker 1>not just a time investment, but it is a money

0:29:58.000 --> 0:30:00.640
<v Speaker 1>investment too, because you will have to find some way

0:30:00.640 --> 0:30:05.200
<v Speaker 1>to address that heat problem. And that concludes this classic

0:30:05.280 --> 0:30:07.680
<v Speaker 1>episode of tech Stuff. I hope you guys got to

0:30:07.760 --> 0:30:10.720
<v Speaker 1>learn a little bit about clock cycles and over clocking,

0:30:11.120 --> 0:30:15.000
<v Speaker 1>and like I said, things change. CPUs and GPUs are

0:30:15.120 --> 0:30:18.000
<v Speaker 1>much different. I mean, they work on the same general principle,

0:30:18.080 --> 0:30:20.640
<v Speaker 1>but they're much more powerful than they were in two

0:30:20.640 --> 0:30:24.400
<v Speaker 1>thousand twelve. And thank goodness, because otherwise I would never

0:30:24.440 --> 0:30:27.040
<v Speaker 1>be able to play pub g at all. Anyway, I

0:30:27.080 --> 0:30:29.160
<v Speaker 1>hope you enjoyed this classic episode. If you have any

0:30:29.200 --> 0:30:32.360
<v Speaker 1>suggestions for future episodes of tech Stuff, send me a message.

0:30:32.400 --> 0:30:35.600
<v Speaker 1>The email is tech Stuff at how stuff works dot com.

0:30:35.760 --> 0:30:38.760
<v Speaker 1>Drop over to tech stuff podcast dot com. That's our

0:30:38.760 --> 0:30:40.840
<v Speaker 1>website where we have other ways to contact us plus

0:30:40.920 --> 0:30:43.640
<v Speaker 1>information about the show. There's also a link to our

0:30:43.760 --> 0:30:46.880
<v Speaker 1>store over at t public dot com slash tech Stuff.

0:30:47.120 --> 0:30:49.520
<v Speaker 1>Every purchase you make goes to help the show, and

0:30:49.560 --> 0:30:51.920
<v Speaker 1>we greatly appreciate it. And I'll talk to you again

0:30:52.560 --> 0:31:00.240
<v Speaker 1>really soon for more on this and Fathlands of other

0:31:00.320 --> 0:31:11.840
<v Speaker 1>topics is that how stuff works? Dot com m