WEBVTT - TechStuff Overclocks a CPU

0:00:00.280 --> 0:00:02.840
<v Speaker 1>Brought to you by the reinvented two thousand twelve camera.

0:00:03.160 --> 0:00:08.920
<v Speaker 1>It's ready. Are you get in touch with technology with

0:00:09.000 --> 0:00:17.920
<v Speaker 1>tech Stuff from how stuff dot com. Well, hello there everyone,

0:00:17.960 --> 0:00:20.279
<v Speaker 1>and welcome to tech stuff. My name is Chris Poulette

0:00:20.280 --> 0:00:22.480
<v Speaker 1>and I am an editor how stuff works dot Com.

0:00:22.480 --> 0:00:25.439
<v Speaker 1>Sitting across from me, as always is seen your writer

0:00:25.520 --> 0:00:28.080
<v Speaker 1>Jonathan Strickland. If I am out of my mind, it's

0:00:28.120 --> 0:00:32.199
<v Speaker 1>all right with me, thought Moses Herzog. All right, I

0:00:32.320 --> 0:00:35.280
<v Speaker 1>was a short one today, Yes, And today to start

0:00:35.320 --> 0:00:38.440
<v Speaker 1>off our episode, we have a little Facebook feedback you be.

0:00:39.280 --> 0:00:41.720
<v Speaker 1>This comes from Brian, who says I've been listening to

0:00:41.760 --> 0:00:44.240
<v Speaker 1>you guys since almost the beginning. Keep up the great work.

0:00:44.479 --> 0:00:46.440
<v Speaker 1>I was wondering if you could do a podcast about

0:00:46.440 --> 0:00:48.479
<v Speaker 1>over clocking. You can talk about what it is, how

0:00:48.479 --> 0:00:50.360
<v Speaker 1>it works, in the pros and cons of it. I've

0:00:50.400 --> 0:00:52.680
<v Speaker 1>had some experience myself and can tell you it's well

0:00:52.720 --> 0:00:56.080
<v Speaker 1>worth it. Can't wait to listen to your next podcast. Well, Brian,

0:00:56.400 --> 0:00:59.160
<v Speaker 1>this one goes out to you. Now. We've talked a

0:00:59.200 --> 0:01:02.200
<v Speaker 1>little bit about over clocking in past episodes, particularly Anything

0:01:02.200 --> 0:01:05.480
<v Speaker 1>where we talked about CPUs and clock cycles. But but

0:01:05.600 --> 0:01:08.840
<v Speaker 1>let's let's kind of go back and talk about what

0:01:08.920 --> 0:01:11.800
<v Speaker 1>a clock cycle is and why it's important and what

0:01:12.040 --> 0:01:16.760
<v Speaker 1>overclocking actually means. Yes, now, this is something we talk

0:01:16.800 --> 0:01:20.080
<v Speaker 1>about a long time ago, A long long time ago,

0:01:20.120 --> 0:01:22.960
<v Speaker 1>we talked about the Mega Hurt Smith and you know,

0:01:23.080 --> 0:01:26.120
<v Speaker 1>the giga Hurt Smith, about the the speed of the

0:01:26.160 --> 0:01:29.520
<v Speaker 1>processor and what it means, and how it's really not

0:01:29.600 --> 0:01:32.160
<v Speaker 1>necessarily all that important. In fact, that it's kind of

0:01:32.200 --> 0:01:36.160
<v Speaker 1>funny looking at computers now, um, because now that the

0:01:36.240 --> 0:01:39.680
<v Speaker 1>dual core and quad core processors and and well let's

0:01:39.680 --> 0:01:42.480
<v Speaker 1>just say multi core processors, um, some of them look

0:01:42.520 --> 0:01:45.560
<v Speaker 1>like they're going backward because you'll see, you know, a

0:01:45.880 --> 0:01:48.080
<v Speaker 1>two gigga Hurts processor and you go, wait a minute,

0:01:48.080 --> 0:01:50.600
<v Speaker 1>the one I have now is a three point two Yeah,

0:01:50.600 --> 0:01:52.480
<v Speaker 1>it is a three point two gigga Hurts. Well, yeah,

0:01:52.560 --> 0:01:55.880
<v Speaker 1>because it's got multiple cores processing, it's able to do this.

0:01:55.960 --> 0:01:59.040
<v Speaker 1>But the clock speed is is basically the rate at

0:01:59.080 --> 0:02:03.600
<v Speaker 1>which a process is handling instructions. Very good. Yes, um.

0:02:03.640 --> 0:02:08.760
<v Speaker 1>I actually saw a pretty interesting analogy on a Yale website.

0:02:08.800 --> 0:02:12.799
<v Speaker 1>This was written by H. Gilbert, and Gilbert said that

0:02:13.200 --> 0:02:15.639
<v Speaker 1>think of it like a high school, right, So you're

0:02:15.680 --> 0:02:19.400
<v Speaker 1>in class and then the bell rings, and that signals

0:02:19.440 --> 0:02:22.000
<v Speaker 1>the end of class. So you leave, alright, and the

0:02:22.120 --> 0:02:24.640
<v Speaker 1>second bell rings and you have to go to your

0:02:24.639 --> 0:02:27.720
<v Speaker 1>next class. So those two bells, he says, think of

0:02:27.760 --> 0:02:30.040
<v Speaker 1>that as a clock cycle. The first bells a tick

0:02:30.080 --> 0:02:33.160
<v Speaker 1>and the second bells of talk, and the entire school

0:02:33.600 --> 0:02:36.720
<v Speaker 1>reacts to those bells. It's not like one class gets

0:02:36.760 --> 0:02:39.639
<v Speaker 1>a bell and then three minutes later another class gets

0:02:39.639 --> 0:02:42.960
<v Speaker 1>a bell. It goes across the entire school. So, uh,

0:02:43.200 --> 0:02:45.640
<v Speaker 1>think of a clock cycle on a on a CPU

0:02:45.760 --> 0:02:47.480
<v Speaker 1>is the same sort of thing, except in steps. Students,

0:02:47.520 --> 0:02:52.320
<v Speaker 1>we're talking about data ones and zeros, so ones and zeros,

0:02:52.360 --> 0:02:55.080
<v Speaker 1>and and that at every clock cycle, ones and zeros

0:02:55.120 --> 0:02:59.360
<v Speaker 1>are moving around. And essentially every task you want a

0:02:59.400 --> 0:03:03.320
<v Speaker 1>computer to do requires a certain number of cycles. Uh.

0:03:03.440 --> 0:03:07.120
<v Speaker 1>Some tasks only require one cycle, and some will require

0:03:07.200 --> 0:03:10.240
<v Speaker 1>multiple cycles because the task actually has more steps than

0:03:10.320 --> 0:03:13.360
<v Speaker 1>what you might first imagine. And this changes over time.

0:03:13.440 --> 0:03:17.639
<v Speaker 1>I should add back, you know, several years ago, many

0:03:17.720 --> 0:03:20.720
<v Speaker 1>years ago, a couple of decades now, adding two numbers

0:03:20.720 --> 0:03:26.120
<v Speaker 1>together might take six or eight clock cycles to complete. Uh,

0:03:26.160 --> 0:03:28.959
<v Speaker 1>and today it might take one clock cycle. So it's

0:03:28.960 --> 0:03:31.799
<v Speaker 1>become more efficient. So that's one way that CPUs have

0:03:31.880 --> 0:03:34.000
<v Speaker 1>sped up over time. But another is that we've actually

0:03:34.000 --> 0:03:36.360
<v Speaker 1>managed to fit more clock cycles in per second. And

0:03:36.440 --> 0:03:40.040
<v Speaker 1>that's the speed we talk about with processors. That's how

0:03:40.040 --> 0:03:44.840
<v Speaker 1>many clock cycles or pulses if you prefer, go through

0:03:44.920 --> 0:03:49.400
<v Speaker 1>the the that particular element on your computer every second.

0:03:49.760 --> 0:03:53.119
<v Speaker 1>So if you hear about a here's a dinosaur. Let's

0:03:53.120 --> 0:03:55.760
<v Speaker 1>say you hear about a five hundred mega Hurts processor.

0:03:56.320 --> 0:04:01.160
<v Speaker 1>That means five hundred million clock cycles per second go

0:04:01.240 --> 0:04:05.839
<v Speaker 1>through that that CPU. All things considered, that's that's pretty fast, right.

0:04:05.880 --> 0:04:07.680
<v Speaker 1>But you know, then we talk about things like a

0:04:07.680 --> 0:04:10.440
<v Speaker 1>two point for giga Hurts processor that's two point four

0:04:10.480 --> 0:04:14.440
<v Speaker 1>billion clock cycles per second, which is even much faster,

0:04:14.760 --> 0:04:20.360
<v Speaker 1>and they get faster than that obviously, But that's so

0:04:20.360 --> 0:04:22.880
<v Speaker 1>so when we're talking about processor speed, really talking about

0:04:22.960 --> 0:04:26.039
<v Speaker 1>the amount of work a processor can do within a

0:04:26.040 --> 0:04:29.240
<v Speaker 1>certain amount of time, and faster processors can do more

0:04:29.320 --> 0:04:32.800
<v Speaker 1>work in that in that timeframe. So the five hundred

0:04:32.800 --> 0:04:37.599
<v Speaker 1>mega Hurts processor can do five hundred million uh can

0:04:38.400 --> 0:04:42.560
<v Speaker 1>not five million tasks, but can use five million clock

0:04:42.600 --> 0:04:45.680
<v Speaker 1>cycles toward tasks in a second, whereas the two point

0:04:45.720 --> 0:04:48.280
<v Speaker 1>for giga Hurts does two point for billion clock cycles

0:04:48.320 --> 0:04:54.080
<v Speaker 1>toward tasks in a second. So yeah, that's that's essentially

0:04:54.120 --> 0:04:58.120
<v Speaker 1>the speed element. Now, uh CPUs are not the only

0:04:58.160 --> 0:05:00.479
<v Speaker 1>thing that work on cycles, by the way, US want

0:05:00.480 --> 0:05:03.240
<v Speaker 1>to make that clear when we do talk about clock cycles.

0:05:04.080 --> 0:05:08.600
<v Speaker 1>Other elements like memory and io devices also operate on cycles.

0:05:08.640 --> 0:05:13.320
<v Speaker 1>And all of this is controlled ultimately by the motherboard. Yes. Now,

0:05:13.680 --> 0:05:17.400
<v Speaker 1>if you're wondering how a you know, how they come

0:05:17.440 --> 0:05:22.760
<v Speaker 1>out with these chips, UM, Well it's it's it's sort

0:05:22.760 --> 0:05:25.600
<v Speaker 1>of controlled UM. If you think about it. Let's say,

0:05:25.680 --> 0:05:31.800
<v Speaker 1>let's take Jonathan's five megahertz processor. UM. The manufacturer has

0:05:31.839 --> 0:05:35.720
<v Speaker 1>you know, knows something about the range at which this

0:05:35.800 --> 0:05:39.640
<v Speaker 1>chip can operate. UM. It can operate more slowly than that,

0:05:39.760 --> 0:05:43.080
<v Speaker 1>it can operate more quickly than that. But what goes

0:05:43.160 --> 0:05:46.520
<v Speaker 1>on is in the process of building this and testing

0:05:46.520 --> 0:05:50.160
<v Speaker 1>this chip, they know roughly about how much electricity it's

0:05:50.200 --> 0:05:53.880
<v Speaker 1>going to use and about how hot it's gonna get. UM.

0:05:53.920 --> 0:05:58.520
<v Speaker 1>Many many of us UH have an idea of what

0:05:58.640 --> 0:06:02.200
<v Speaker 1>happens when you're compute it or overheats. UM. It will

0:06:02.360 --> 0:06:07.080
<v Speaker 1>seize up eventually UM and decrease the operating life of

0:06:07.120 --> 0:06:10.880
<v Speaker 1>the computer overall. Too If it gets too hot too frequently. Yeah.

0:06:11.080 --> 0:06:14.719
<v Speaker 1>So the thing is the manufacturer of the processor is

0:06:14.720 --> 0:06:17.000
<v Speaker 1>going to go, well, okay, this is this is a

0:06:17.040 --> 0:06:20.760
<v Speaker 1>good range. This is about what it's gonna do. And essentially, yeah,

0:06:20.760 --> 0:06:25.880
<v Speaker 1>and essentially it'll runs as fast as this without going

0:06:26.000 --> 0:06:30.120
<v Speaker 1>nuts and requiring you know, a a to be immersed

0:06:30.160 --> 0:06:33.000
<v Speaker 1>in liquid nitrogen to keep it cold. We'll get to

0:06:33.080 --> 0:06:35.960
<v Speaker 1>that right, right, So this is under normal operating conditions.

0:06:36.000 --> 0:06:37.960
<v Speaker 1>This is about how fast this chick is going to run.

0:06:38.040 --> 0:06:41.240
<v Speaker 1>Let's say it's five mega hurts and and there are

0:06:41.279 --> 0:06:48.000
<v Speaker 1>instructions um in the computer actually written into ROM that

0:06:48.040 --> 0:06:51.920
<v Speaker 1>will keep it from doing more than that. Yeah. Essentially,

0:06:51.960 --> 0:06:54.880
<v Speaker 1>you've got two elements that determine the speed. You have

0:06:54.920 --> 0:07:00.200
<v Speaker 1>the motherboard which provides a baseline speed, and those to

0:07:00.279 --> 0:07:04.240
<v Speaker 1>be around one hundred thirty three, one sixty six or

0:07:04.279 --> 0:07:08.039
<v Speaker 1>two hundred mega hurts. And then you have a multiplier

0:07:08.400 --> 0:07:12.520
<v Speaker 1>on the CPU itself. So for the five hundred megahurts

0:07:12.600 --> 0:07:15.400
<v Speaker 1>machine we were talking about, the multiplayer might be five

0:07:15.560 --> 0:07:18.480
<v Speaker 1>and the motherboard provides one hundred mega hurts. So the

0:07:18.520 --> 0:07:21.800
<v Speaker 1>clock inside the CPU is going to run at five

0:07:21.840 --> 0:07:25.600
<v Speaker 1>times the speed of the clock on the motherboard. So

0:07:25.680 --> 0:07:29.040
<v Speaker 1>the motherboard sets the pace, the CPU multiplies that pace,

0:07:29.320 --> 0:07:32.600
<v Speaker 1>and that's where you get your processor clock speed. So

0:07:32.840 --> 0:07:35.960
<v Speaker 1>the five multiplayer times the one hundred mega hurts, that's

0:07:35.960 --> 0:07:38.960
<v Speaker 1>where you get your five hundred mega hurts. Now, if

0:07:39.040 --> 0:07:46.000
<v Speaker 1>you had a a multiplayer that was say twenty four

0:07:46.800 --> 0:07:49.080
<v Speaker 1>times one hundred, well that's where you get the two

0:07:49.080 --> 0:07:53.040
<v Speaker 1>point four giga hurts because you get the two thousand,

0:07:53.080 --> 0:07:56.760
<v Speaker 1>one four hundred, and then that two thousand, four hundred

0:07:56.760 --> 0:08:00.400
<v Speaker 1>mega hurts is the same as two point four gig hurts. Um.

0:08:00.440 --> 0:08:03.560
<v Speaker 1>So the multiplayers tend to be difficult to change with

0:08:03.680 --> 0:08:06.720
<v Speaker 1>most processors, not all, but a lot of processors have

0:08:07.080 --> 0:08:10.160
<v Speaker 1>the manufacturers have locked down that multiplayer in order to

0:08:10.200 --> 0:08:14.280
<v Speaker 1>prevent people from pushing it too hard and causing problems

0:08:14.280 --> 0:08:18.280
<v Speaker 1>down the line. Yeah, because ultimately the majority of us

0:08:18.280 --> 0:08:21.280
<v Speaker 1>are going to buy our computers. We're gonna set it up,

0:08:21.400 --> 0:08:23.320
<v Speaker 1>do our work on it, play games on it, do

0:08:23.400 --> 0:08:25.480
<v Speaker 1>whatever it is that we're gonna do on it. And

0:08:26.360 --> 0:08:29.720
<v Speaker 1>the point is we want it to last. Uh, most

0:08:29.720 --> 0:08:31.480
<v Speaker 1>of us can't just go buy a new computer. And

0:08:31.480 --> 0:08:33.040
<v Speaker 1>if we don't know what we're doing as far as

0:08:33.080 --> 0:08:37.160
<v Speaker 1>over clogging, um, you know, we're just gonna we want

0:08:37.160 --> 0:08:39.160
<v Speaker 1>this machine to last us a good long time and

0:08:39.200 --> 0:08:41.680
<v Speaker 1>if you use it under normal circumstances, unless the fan

0:08:41.760 --> 0:08:45.880
<v Speaker 1>breaks or some the cooling mechanism breaks. Even in computers

0:08:45.880 --> 0:08:48.240
<v Speaker 1>with no fans, let's say, uh, you know one of

0:08:48.280 --> 0:08:50.640
<v Speaker 1>the older Imax that they made a point of putting

0:08:50.640 --> 0:08:53.160
<v Speaker 1>no fan in. If you clogged up the air vents

0:08:53.200 --> 0:08:57.280
<v Speaker 1>with something dust, a blanket, it will overheat and the

0:08:57.320 --> 0:09:00.760
<v Speaker 1>computer will die or it will shorten the life of it. Um,

0:09:01.080 --> 0:09:03.360
<v Speaker 1>So be unsteady and old, crash a lot, that kind

0:09:03.400 --> 0:09:06.079
<v Speaker 1>of thing. So to the point of the manufacturer setting

0:09:06.280 --> 0:09:10.320
<v Speaker 1>a clock speed a default clock speed is is basically

0:09:10.360 --> 0:09:13.480
<v Speaker 1>to make it a motherboard, a chip on a motherboard

0:09:13.480 --> 0:09:16.480
<v Speaker 1>that it's gonna last the average computer user a good

0:09:16.480 --> 0:09:20.280
<v Speaker 1>long while years hopefully, I'd say that's the that's the point.

0:09:20.320 --> 0:09:22.559
<v Speaker 1>I'd say that's true in the majority of cases. There

0:09:22.600 --> 0:09:27.880
<v Speaker 1>are a few cases where manufacturers have developed one chip

0:09:28.000 --> 0:09:31.960
<v Speaker 1>to go in a line of computers and have put

0:09:31.960 --> 0:09:37.360
<v Speaker 1>in essentially a a an artificial limit to how fast

0:09:37.440 --> 0:09:40.240
<v Speaker 1>that processor can go per model. So let's say that

0:09:40.280 --> 0:09:44.840
<v Speaker 1>I've got a selection of computers, um, and we're gonna say,

0:09:44.880 --> 0:09:47.360
<v Speaker 1>we're gonna call A, Model A, B, C, and D,

0:09:48.320 --> 0:09:51.200
<v Speaker 1>and all four of these have the same processor in them,

0:09:51.720 --> 0:09:54.240
<v Speaker 1>but I've put limitations on it so that Model A

0:09:54.520 --> 0:09:57.839
<v Speaker 1>can only go at five hundred mega hurts, and Model

0:09:57.880 --> 0:10:00.600
<v Speaker 1>B as a giga hurts, and and UM models see

0:10:00.600 --> 0:10:02.720
<v Speaker 1>as two gig hurts, and Model D is like two

0:10:02.720 --> 0:10:05.640
<v Speaker 1>point four gig hurts, and two point four is really

0:10:05.720 --> 0:10:08.040
<v Speaker 1>where the sweet spot is. But I've put in these

0:10:08.160 --> 0:10:11.720
<v Speaker 1>artificial limitations on the previous ones. The reason for that

0:10:11.720 --> 0:10:14.400
<v Speaker 1>would be I only have to manufacture one chip, and

0:10:14.440 --> 0:10:18.559
<v Speaker 1>I can create devices for multiple markets. Because there's some

0:10:18.600 --> 0:10:20.480
<v Speaker 1>people are gonna be out there who are saying, I

0:10:20.520 --> 0:10:22.280
<v Speaker 1>need a computer, but I don't need it to do

0:10:22.320 --> 0:10:26.160
<v Speaker 1>the latest stuff, or I can't afford to buy a

0:10:26.160 --> 0:10:28.920
<v Speaker 1>computer that has like the top level technology in it,

0:10:29.440 --> 0:10:31.840
<v Speaker 1>but I'm gonna go and get this base model instead,

0:10:32.040 --> 0:10:33.640
<v Speaker 1>And then they're gonna be the up people on the

0:10:33.640 --> 0:10:36.720
<v Speaker 1>other side of it, saying I want the fastest machine

0:10:36.760 --> 0:10:39.120
<v Speaker 1>I can possibly get, so they're gonna go for the

0:10:39.120 --> 0:10:41.480
<v Speaker 1>other one. Well, they can create a whole range of

0:10:41.520 --> 0:10:45.000
<v Speaker 1>computers meeting all of these demands using the same chip

0:10:45.160 --> 0:10:47.760
<v Speaker 1>if they put those limitations in place, and in some

0:10:47.800 --> 0:10:51.679
<v Speaker 1>cases you can't really get around the multiplier limitation without

0:10:51.960 --> 0:10:56.880
<v Speaker 1>some really deep knowledge and risking ruining your computer. However,

0:10:57.360 --> 0:11:01.439
<v Speaker 1>what you can do has changed a rate on the

0:11:01.480 --> 0:11:05.959
<v Speaker 1>motherboard itself, and you do that through the BIOS system.

0:11:06.000 --> 0:11:09.239
<v Speaker 1>And before we before we get into technical detail, um,

0:11:09.240 --> 0:11:12.760
<v Speaker 1>overclocking is the process that we're talking about. Now. This

0:11:12.840 --> 0:11:18.280
<v Speaker 1>means that you're increasing the limit at which the chip

0:11:18.960 --> 0:11:23.280
<v Speaker 1>can process instructions. Yeah, it's essentially pushing more clock cycles

0:11:23.320 --> 0:11:26.920
<v Speaker 1>in per second than what the chip was recommended for.

0:11:27.760 --> 0:11:31.200
<v Speaker 1>And we should say it really is a recommendation because, uh,

0:11:31.520 --> 0:11:33.559
<v Speaker 1>like Chris was saying, most of these chips, I mean

0:11:33.640 --> 0:11:37.559
<v Speaker 1>almost all chips that come out have the capacity to

0:11:37.640 --> 0:11:40.960
<v Speaker 1>operate over what they are rated for. So at two

0:11:41.040 --> 0:11:44.800
<v Speaker 1>point four gigahertz processor can actually work faster than that.

0:11:44.880 --> 0:11:47.480
<v Speaker 1>In fact, usually it's around five to ten percent faster

0:11:47.600 --> 0:11:50.240
<v Speaker 1>than what the rating is for. So if you are

0:11:50.240 --> 0:11:54.480
<v Speaker 1>still five to tempercent faster without running the risk of

0:11:55.559 --> 0:11:58.439
<v Speaker 1>causing damage to your computer, so you might be able

0:11:58.520 --> 0:12:02.400
<v Speaker 1>to boost your computer performance by or at least the

0:12:02.640 --> 0:12:05.840
<v Speaker 1>processing speed by five or ten percent without having to

0:12:05.880 --> 0:12:10.320
<v Speaker 1>worry about additional concerns. Once you go beyond that, then

0:12:10.360 --> 0:12:12.920
<v Speaker 1>you have to start looking into creative ways of managing

0:12:12.920 --> 0:12:15.480
<v Speaker 1>your computer so that it doesn't you know, just crash

0:12:15.520 --> 0:12:18.520
<v Speaker 1>on you. And even if you do just overclock your

0:12:18.559 --> 0:12:20.400
<v Speaker 1>computer a little bit, there is a chance that stuff

0:12:20.440 --> 0:12:22.880
<v Speaker 1>will crash because sometimes programs just don't work very well

0:12:22.880 --> 0:12:28.640
<v Speaker 1>with overclocked processors. Um. Yeah, So that's the basis. Though.

0:12:28.760 --> 0:12:32.280
<v Speaker 1>Overclocking means that you're pushing through more clock cycles per second.

0:12:33.120 --> 0:12:35.880
<v Speaker 1>And uh, before we again, before we get into too

0:12:35.960 --> 0:12:38.000
<v Speaker 1>much detail, this is not the kind of thing that

0:12:38.040 --> 0:12:41.320
<v Speaker 1>you want to do casually and figure, oh, you know what,

0:12:42.480 --> 0:12:44.480
<v Speaker 1>let's just go and try this. You want to think

0:12:44.559 --> 0:12:48.719
<v Speaker 1>about how what happens if it doesn't work, because if

0:12:48.720 --> 0:12:51.959
<v Speaker 1>you don't follow the instructions carefully. Um. And we're not

0:12:51.960 --> 0:12:54.200
<v Speaker 1>going to give you a lot of instructions because there's

0:12:54.200 --> 0:12:57.079
<v Speaker 1>a lot depend upon what the processor is. So yeah,

0:12:57.360 --> 0:12:59.560
<v Speaker 1>but the thing is, if you're not very careful, you

0:12:59.559 --> 0:13:03.880
<v Speaker 1>could amage your computer permanently. And most of the time,

0:13:03.920 --> 0:13:07.200
<v Speaker 1>if you try to overclock your processor, you're violating a warranty.

0:13:07.400 --> 0:13:09.599
<v Speaker 1>So if you if you do damage your computer, you

0:13:09.640 --> 0:13:11.520
<v Speaker 1>don't have any recourse to get it fixed by the

0:13:11.520 --> 0:13:14.240
<v Speaker 1>manufacturer because they're gonna say, hey, you did this thing

0:13:14.280 --> 0:13:17.119
<v Speaker 1>you weren't supposed to do. Therefore, we have no obligation

0:13:17.160 --> 0:13:21.240
<v Speaker 1>to help you out. So so if you do this,

0:13:21.400 --> 0:13:23.240
<v Speaker 1>make sure you you put some thought into it and

0:13:23.240 --> 0:13:25.640
<v Speaker 1>make sure this is something you feel up to and

0:13:25.679 --> 0:13:28.199
<v Speaker 1>that you're you're willing to try before you really give

0:13:28.240 --> 0:13:30.720
<v Speaker 1>it a shot if you want to. Uh, it could

0:13:30.760 --> 0:13:33.319
<v Speaker 1>be very very profitable for you if you're looking for

0:13:33.360 --> 0:13:37.000
<v Speaker 1>a faster machine and you have the uh, the ability,

0:13:37.040 --> 0:13:39.040
<v Speaker 1>and the you know, the money if you need it.

0:13:39.559 --> 0:13:41.640
<v Speaker 1>But we can get into that now, right right. And

0:13:41.679 --> 0:13:44.440
<v Speaker 1>the reason why you would want to overclock your machine

0:13:44.440 --> 0:13:46.680
<v Speaker 1>in the first place is that it allows you to

0:13:47.360 --> 0:13:52.080
<v Speaker 1>run more advanced programs at a faster rate without having

0:13:52.120 --> 0:13:54.760
<v Speaker 1>to buy a new processor or a new machine. That's

0:13:54.840 --> 0:13:58.000
<v Speaker 1>that's the big attraction for a lot of gamers out there.

0:13:58.080 --> 0:14:00.520
<v Speaker 1>They'll they'll buy a good gaming rig and then they

0:14:00.559 --> 0:14:04.040
<v Speaker 1>overclocked their processors so that they can run games at

0:14:04.120 --> 0:14:07.880
<v Speaker 1>at the highest settings without any slowdown and to have

0:14:08.000 --> 0:14:11.200
<v Speaker 1>you know, the best performance in their game. UH. And

0:14:11.320 --> 0:14:15.439
<v Speaker 1>also it means that you know they they're essentially getting

0:14:16.040 --> 0:14:19.520
<v Speaker 1>higher like they're getting the equivalent of a faster processor,

0:14:19.760 --> 0:14:22.960
<v Speaker 1>but they're buying a less expensive one. Right. So if

0:14:22.960 --> 0:14:25.200
<v Speaker 1>there were say a two point eight processor out there,

0:14:25.200 --> 0:14:27.360
<v Speaker 1>in a three point two processor out there, and you

0:14:27.440 --> 0:14:29.480
<v Speaker 1>knew you could overclock your two point eight so that

0:14:29.560 --> 0:14:32.960
<v Speaker 1>would equal or exceed the three point two, you say, well,

0:14:32.960 --> 0:14:35.000
<v Speaker 1>why would I spend the extra money getting the three

0:14:35.040 --> 0:14:36.720
<v Speaker 1>point two when I could get the two point eight

0:14:36.720 --> 0:14:40.800
<v Speaker 1>and just overclocked that puppy. And of course there's the

0:14:40.880 --> 0:14:46.320
<v Speaker 1>maker's reason because they can. Yeah, yes, there's always that too.

0:14:46.320 --> 0:14:48.960
<v Speaker 1>It's just like, hey, I I have the ability to

0:14:49.040 --> 0:14:51.720
<v Speaker 1>fiddle with my computer settings. Gosh darn it, that's what

0:14:51.760 --> 0:14:55.200
<v Speaker 1>I'm gonna do. So you were talking a moment ago

0:14:55.520 --> 0:15:00.240
<v Speaker 1>about the BIOS, the basic input output system. Yes, now,

0:15:00.280 --> 0:15:03.680
<v Speaker 1>this is a part of when you boot up your computer.

0:15:03.760 --> 0:15:06.440
<v Speaker 1>It goes through the BIO set up, and part of

0:15:06.480 --> 0:15:09.800
<v Speaker 1>that BIO set up is the motherboard checks the processor,

0:15:10.240 --> 0:15:12.320
<v Speaker 1>sees what kind of processor it is and what the

0:15:12.360 --> 0:15:17.120
<v Speaker 1>recommended settings are, and then goes into that recommended setting

0:15:17.240 --> 0:15:21.120
<v Speaker 1>for the speed that the motherboard provides as later on

0:15:21.280 --> 0:15:26.000
<v Speaker 1>multiplied by the processor. Uh. The thing is, you can

0:15:26.040 --> 0:15:29.840
<v Speaker 1>actually interrupt the BIOS set up system and manually change

0:15:29.880 --> 0:15:33.280
<v Speaker 1>those settings. So let's say that it was set at

0:15:33.440 --> 0:15:36.000
<v Speaker 1>one hundred megahurts. You could up it up to one

0:15:36.080 --> 0:15:38.920
<v Speaker 1>thirty three or one sixty six or two hundred. Although

0:15:39.560 --> 0:15:44.160
<v Speaker 1>you know the more you boost this the the closer

0:15:44.200 --> 0:15:49.240
<v Speaker 1>you ride that dangerous edge of possibly ruining your machine.

0:15:49.520 --> 0:15:51.320
<v Speaker 1>It's like like getting in a car and pushing it

0:15:51.360 --> 0:15:53.640
<v Speaker 1>faster than it was meant to go. It can start

0:15:53.640 --> 0:15:57.600
<v Speaker 1>to shake apart. Most of the instructions I read in

0:15:57.880 --> 0:16:00.640
<v Speaker 1>the process of doing research for this podcast suggested that

0:16:00.680 --> 0:16:05.600
<v Speaker 1>you would tinker with the multiplier and basically, rather than

0:16:05.920 --> 0:16:08.320
<v Speaker 1>going how high can I push this up, let's turn

0:16:08.360 --> 0:16:10.800
<v Speaker 1>it all the way up, what they suggest doing is

0:16:11.320 --> 0:16:14.440
<v Speaker 1>taking it up a couple of notches. Essentially. Again, read

0:16:14.440 --> 0:16:18.680
<v Speaker 1>the instructions carefully for for the the system that you have,

0:16:18.800 --> 0:16:21.040
<v Speaker 1>and then and then the materials that you've got on him.

0:16:21.120 --> 0:16:25.120
<v Speaker 1>But I'm oversimplifying. For the case of explanation, you might

0:16:25.320 --> 0:16:28.160
<v Speaker 1>crank it up a notch or two notches and test

0:16:28.200 --> 0:16:30.000
<v Speaker 1>it see how it runs. Does it look like it's

0:16:30.040 --> 0:16:32.640
<v Speaker 1>doing all right? Does it look like it's behaving oddly

0:16:32.680 --> 0:16:35.680
<v Speaker 1>if the applications all crashing, But you might need to

0:16:35.760 --> 0:16:38.480
<v Speaker 1>crank it back down again. Yeah, And and like I said,

0:16:38.520 --> 0:16:42.720
<v Speaker 1>not all multiplayers are You can't mess with all multipliers.

0:16:42.800 --> 0:16:44.960
<v Speaker 1>It all depends on the processors. Some of the processors

0:16:45.000 --> 0:16:47.760
<v Speaker 1>are locked, so you let you can't do that, in

0:16:47.800 --> 0:16:50.440
<v Speaker 1>which case you your only recourse is to change the

0:16:50.480 --> 0:16:52.640
<v Speaker 1>setting of the motherboard as opposed to the setting on

0:16:52.760 --> 0:16:56.840
<v Speaker 1>the processor. And also some motherboards you cannot do this

0:16:56.960 --> 0:17:00.720
<v Speaker 1>through a software approach. You actually have to use physical approach.

0:17:00.720 --> 0:17:03.200
<v Speaker 1>You have to change these components that are called jumpers,

0:17:03.720 --> 0:17:08.320
<v Speaker 1>which that will uh will limit the motherboard speed. You

0:17:08.320 --> 0:17:10.960
<v Speaker 1>have to you would have to physically replace those, which

0:17:11.000 --> 0:17:14.480
<v Speaker 1>requires opening up your computer case and taking stuff out

0:17:14.520 --> 0:17:17.080
<v Speaker 1>and changing stuff out, and that that can get a

0:17:17.119 --> 0:17:20.560
<v Speaker 1>little intimidating for folks. It's a little bit simpler when

0:17:20.600 --> 0:17:22.920
<v Speaker 1>you just hit a couple of buttons and then change

0:17:22.960 --> 0:17:27.840
<v Speaker 1>some numbers on the screen, but that might be necessary

0:17:27.840 --> 0:17:30.119
<v Speaker 1>depending on the motherboard. A lot of the stuff about

0:17:30.200 --> 0:17:33.960
<v Speaker 1>personal computers depends heavily on the specific hardware you have,

0:17:34.880 --> 0:17:38.160
<v Speaker 1>which is why if you ever think about building a machine,

0:17:38.680 --> 0:17:41.120
<v Speaker 1>you should really do some research and make sure that

0:17:41.200 --> 0:17:44.320
<v Speaker 1>you know what components you're getting before you you jump

0:17:44.400 --> 0:17:48.639
<v Speaker 1>into it, because not every processor is compatible with every motherboard.

0:17:49.000 --> 0:17:50.760
<v Speaker 1>So if you were to just try and create your

0:17:50.800 --> 0:17:53.280
<v Speaker 1>own computer, build your own computer and you just you know,

0:17:53.359 --> 0:17:56.280
<v Speaker 1>you were buying whatever was on sale. You might discover that,

0:17:56.359 --> 0:18:00.399
<v Speaker 1>oh I got this great motherboard and this great sensor,

0:18:00.520 --> 0:18:03.119
<v Speaker 1>but they aren't compatible with each other, so I can't

0:18:03.160 --> 0:18:05.800
<v Speaker 1>actually build a machine out of it. Well, same sort

0:18:05.840 --> 0:18:08.520
<v Speaker 1>of thing with overclocking. You just you know, they're different

0:18:08.560 --> 0:18:13.520
<v Speaker 1>limitations based upon the actual hardware you have. And of course,

0:18:13.640 --> 0:18:17.439
<v Speaker 1>uh it might involve, uh, depending on what you're doing,

0:18:17.640 --> 0:18:20.200
<v Speaker 1>you might have to play around with the amount of

0:18:20.280 --> 0:18:26.159
<v Speaker 1>voltage uh necessary to run. Yeah, well, I hopefully there

0:18:26.200 --> 0:18:29.679
<v Speaker 1>are our listeners when we start talking about the amount

0:18:29.680 --> 0:18:33.960
<v Speaker 1>of electricity we're getting into um or any any measure

0:18:34.000 --> 0:18:36.280
<v Speaker 1>of electricity, they start going, oh, maybe I don't want

0:18:36.320 --> 0:18:39.360
<v Speaker 1>to do this without you know, really doing some research. UM.

0:18:39.400 --> 0:18:42.000
<v Speaker 1>I would very much recommend doing that if you are

0:18:42.040 --> 0:18:46.240
<v Speaker 1>going to do getting into really messing with this UM.

0:18:46.280 --> 0:18:49.520
<v Speaker 1>But yeah, they're it is worth noting though that uh

0:18:49.320 --> 0:18:54.200
<v Speaker 1>uh certain boards are you know, certain processors, I should say,

0:18:54.480 --> 0:18:59.720
<v Speaker 1>come with the the ability to overclock sort of sanctioned

0:19:00.080 --> 0:19:03.080
<v Speaker 1>they're built in. Intel has several chips that you can

0:19:03.840 --> 0:19:07.440
<v Speaker 1>uh go into a specific screen and change the settings

0:19:07.640 --> 0:19:12.320
<v Speaker 1>if you want to overclock your processor. Extreme Edition Yeah.

0:19:12.400 --> 0:19:14.080
<v Speaker 1>So that way, you know, you can do like the

0:19:14.119 --> 0:19:18.040
<v Speaker 1>turbo stuff, or you can actually knock up the processor speed.

0:19:18.400 --> 0:19:20.880
<v Speaker 1>You can change the multiplier a little bit, that kind

0:19:20.920 --> 0:19:23.639
<v Speaker 1>of stuff. And uh you know again this is you

0:19:23.720 --> 0:19:25.880
<v Speaker 1>might ask, well, why isn't it like that just out

0:19:25.920 --> 0:19:27.800
<v Speaker 1>of the box. Well, for one thing, not everyone needs

0:19:27.800 --> 0:19:31.359
<v Speaker 1>that kind of performance. And for another, uh, here's the

0:19:31.359 --> 0:19:34.000
<v Speaker 1>thing about processors. We've talked about heat a bit and

0:19:34.040 --> 0:19:36.199
<v Speaker 1>about generating heat, and too much heat can be a

0:19:36.200 --> 0:19:40.920
<v Speaker 1>bad thing. When you have electricity running through a circuit,

0:19:41.359 --> 0:19:44.439
<v Speaker 1>it generates heat as a byproduct. Yes, some energy is

0:19:44.480 --> 0:19:46.600
<v Speaker 1>lost due to heat. Yeah, waste. It wastes some of

0:19:46.640 --> 0:19:51.640
<v Speaker 1>its energy as heat. Yeah. So the more electricity you're

0:19:51.640 --> 0:19:55.760
<v Speaker 1>pushing through the more the more uh work you're making

0:19:55.800 --> 0:19:58.440
<v Speaker 1>your system do, the more heat it's going to generate.

0:19:58.920 --> 0:20:01.879
<v Speaker 1>And before along, that heat might get to a point

0:20:01.920 --> 0:20:06.400
<v Speaker 1>that's causing damage or or causing malfunctions within the machine itself.

0:20:06.680 --> 0:20:08.760
<v Speaker 1>So you have to figure out a way of dispersing

0:20:08.800 --> 0:20:12.280
<v Speaker 1>that heat um to handle that, or else your device

0:20:12.320 --> 0:20:14.040
<v Speaker 1>isn't gonna work for very long. You might have the

0:20:14.080 --> 0:20:17.119
<v Speaker 1>world's fastest computer, but only for a few minutes before

0:20:17.119 --> 0:20:22.160
<v Speaker 1>it just uh yeah, well, of course, there have been

0:20:22.240 --> 0:20:25.399
<v Speaker 1>computers with no fans, there have been computers with multiple fans.

0:20:25.400 --> 0:20:27.639
<v Speaker 1>It all sort of depends on on the guts on

0:20:27.760 --> 0:20:30.720
<v Speaker 1>the you know, the stuff that's inside the box um.

0:20:30.840 --> 0:20:34.639
<v Speaker 1>And if you go to different overclocking communities you can

0:20:34.760 --> 0:20:39.600
<v Speaker 1>learn about the parts and bits that people uh seem

0:20:39.640 --> 0:20:41.200
<v Speaker 1>to feel are the best. Now, I saw a couple

0:20:41.200 --> 0:20:44.640
<v Speaker 1>of fans listed as being excellent for overclockers because they're

0:20:44.640 --> 0:20:47.720
<v Speaker 1>reliable and they push a lot of air um. But

0:20:47.920 --> 0:20:50.120
<v Speaker 1>depending on what you're doing, that may not be enough.

0:20:50.320 --> 0:20:52.720
<v Speaker 1>You might have to go to, say a water cooling system,

0:20:52.800 --> 0:20:56.400
<v Speaker 1>which you know, water is a much more efficient dispersal

0:20:56.720 --> 0:21:00.800
<v Speaker 1>of heat than than air is dispersal. I'm making up

0:21:00.800 --> 0:21:04.320
<v Speaker 1>words now or misusing them at any rate. So anyway,

0:21:04.480 --> 0:21:07.240
<v Speaker 1>water is much better at taking care of heat than

0:21:07.359 --> 0:21:10.560
<v Speaker 1>than air is, and so a water based cooling system

0:21:10.720 --> 0:21:14.080
<v Speaker 1>can be very useful for people who are overclocking their

0:21:14.160 --> 0:21:16.520
<v Speaker 1>their machines and they want to really push it to

0:21:16.560 --> 0:21:20.280
<v Speaker 1>the limit. Yeah, I was joking about the liquid nitrogen earlier,

0:21:20.320 --> 0:21:22.600
<v Speaker 1>but there are people who have some very elaborate liquid

0:21:22.720 --> 0:21:27.040
<v Speaker 1>cooled computer systems, and depending on how much you're you're pushing,

0:21:27.119 --> 0:21:29.439
<v Speaker 1>especially if you have something like the again, like the

0:21:29.480 --> 0:21:32.280
<v Speaker 1>Intel chips are the A M. D. S Black Edition

0:21:32.320 --> 0:21:35.040
<v Speaker 1>chips where you can you've got the opportunity to really

0:21:35.080 --> 0:21:38.520
<v Speaker 1>tinker with it, um you might do that. They are

0:21:38.560 --> 0:21:43.399
<v Speaker 1>actually an overclocking competitions. Liquid nitrogen has been used to

0:21:43.480 --> 0:21:48.080
<v Speaker 1>cool uh CPUs. Yeah, I'm just it's not the kind

0:21:48.080 --> 0:21:50.960
<v Speaker 1>of thing that the general public because he's not gonna have.

0:21:51.160 --> 0:21:53.240
<v Speaker 1>You'm not going to have a steady supply of liquid

0:21:53.359 --> 0:21:56.399
<v Speaker 1>nitrogen to run through your machine constantly so that you

0:21:56.440 --> 0:21:59.359
<v Speaker 1>can you can keep it going. But any how have

0:21:59.440 --> 0:22:03.760
<v Speaker 1>you seen my nitrogen? It's not the stage. Why do

0:22:03.880 --> 0:22:08.280
<v Speaker 1>you need to know the uh uh? Where is my

0:22:08.400 --> 0:22:11.359
<v Speaker 1>super suit? The uh? Yeah? But if you if you,

0:22:12.240 --> 0:22:14.720
<v Speaker 1>if you don't have a station have liquid nitrogen, then

0:22:14.760 --> 0:22:16.800
<v Speaker 1>you know what are cooling or some other method is

0:22:16.800 --> 0:22:21.040
<v Speaker 1>probably the best for you. But during these competitions that

0:22:21.200 --> 0:22:25.760
<v Speaker 1>the purpose of the competitions isn't to build the fastest computer.

0:22:25.880 --> 0:22:28.480
<v Speaker 1>It's to to try and push the limits of overclocking

0:22:28.480 --> 0:22:30.760
<v Speaker 1>as far as you can go. It's not that you're

0:22:30.800 --> 0:22:34.640
<v Speaker 1>going to have a practical machine after you're done, right,

0:22:34.680 --> 0:22:37.879
<v Speaker 1>It's just this is an example of a a an

0:22:38.000 --> 0:22:41.760
<v Speaker 1>artist if you will an engineer really knowing the limitations

0:22:41.800 --> 0:22:43.480
<v Speaker 1>and how to play with them and how to push

0:22:43.520 --> 0:22:47.360
<v Speaker 1>things to a super speed. So at ce S two

0:22:47.400 --> 0:22:51.960
<v Speaker 1>thousand eleven there was an overclocking competition where they had

0:22:52.080 --> 0:22:55.159
<v Speaker 1>several different phases and they were overclocking things, not just

0:22:55.280 --> 0:22:59.239
<v Speaker 1>CPUs but also graphics processing cards, because you can do

0:22:59.280 --> 0:23:02.600
<v Speaker 1>this with various components, not just CPUs. It's just that's

0:23:02.600 --> 0:23:04.400
<v Speaker 1>what we tend to think about when we talked about

0:23:04.400 --> 0:23:07.720
<v Speaker 1>over clocking. But in this competition, they took an I

0:23:07.960 --> 0:23:14.119
<v Speaker 1>seven x Intel chip, which normally runs at three point

0:23:14.200 --> 0:23:17.600
<v Speaker 1>three three giga hurts with a turbo speed capable of

0:23:17.680 --> 0:23:22.680
<v Speaker 1>three point six giga hurts. That's pretty darn fast. They

0:23:22.720 --> 0:23:26.439
<v Speaker 1>over clocked it to five point nine three five giga hurts,

0:23:27.080 --> 0:23:31.280
<v Speaker 1>so nearly six giga hurts of of clock speed. Um.

0:23:31.320 --> 0:23:36.440
<v Speaker 1>And that was using some pretty phenomenal cooling mechanisms. Uh,

0:23:36.760 --> 0:23:38.959
<v Speaker 1>not something that the average consumer is going to have

0:23:39.080 --> 0:23:44.080
<v Speaker 1>at his or her fingertips. Not the average consumer. Maybe

0:23:44.160 --> 0:23:48.000
<v Speaker 1>maybe if your last name is do find Schmirtz, you

0:23:48.119 --> 0:23:51.160
<v Speaker 1>might have something. Well, yeah, but that's all coming from

0:23:51.160 --> 0:23:57.879
<v Speaker 1>the alimony. Um, it's my coldinator. Um. Yeah, And and

0:23:57.920 --> 0:24:00.560
<v Speaker 1>it does require that when you over clocked your processor,

0:24:00.560 --> 0:24:03.119
<v Speaker 1>it does require that you tweak some other settings on

0:24:03.200 --> 0:24:07.040
<v Speaker 1>your computer, including the ram UM. So keep in mind

0:24:07.080 --> 0:24:09.800
<v Speaker 1>that this is not a a if you're just sort

0:24:09.800 --> 0:24:12.800
<v Speaker 1>of I thinking of tinkering with it just for the

0:24:12.840 --> 0:24:15.560
<v Speaker 1>fun of it. UM. Keep in mind that once you

0:24:15.600 --> 0:24:18.080
<v Speaker 1>start messing with one part of it, you might have

0:24:18.119 --> 0:24:23.920
<v Speaker 1>to tune some other factors relating to your your computer's operations.

0:24:23.920 --> 0:24:26.919
<v Speaker 1>So uh, make sure you do a bit of reading

0:24:27.000 --> 0:24:31.040
<v Speaker 1>about the processor you're using, UM and the other equipment,

0:24:31.080 --> 0:24:33.520
<v Speaker 1>the ram the type of ram UM. You might even

0:24:33.560 --> 0:24:36.200
<v Speaker 1>check out your GPU. If you're feeling bold, you might

0:24:36.240 --> 0:24:39.080
<v Speaker 1>even try to overclock your GPU again. This will also

0:24:39.720 --> 0:24:42.640
<v Speaker 1>increase the amount of heat. UM, so you this might

0:24:42.680 --> 0:24:46.320
<v Speaker 1>be a good time to uh move your computer to

0:24:46.440 --> 0:24:50.400
<v Speaker 1>a small bard in Norway where it is u where

0:24:50.480 --> 0:24:54.359
<v Speaker 1>I'm told it's rather chilly. Um, But the people at

0:24:54.359 --> 0:24:56.640
<v Speaker 1>the seed vault are be going no move it down there.

0:24:56.640 --> 0:25:00.560
<v Speaker 1>You're making the seeds warm up. But so, yeah, that's

0:25:00.640 --> 0:25:02.400
<v Speaker 1>quite a bit of there's quite a bit of tinkering

0:25:02.400 --> 0:25:04.520
<v Speaker 1>that could be involved with this that you know. It's

0:25:04.560 --> 0:25:06.199
<v Speaker 1>not just a oh well, I'm just going to turn

0:25:06.280 --> 0:25:07.959
<v Speaker 1>this one up to eleven and we're good. Yeah, there

0:25:07.960 --> 0:25:10.199
<v Speaker 1>are a lot of resources out on the net that

0:25:10.320 --> 0:25:12.560
<v Speaker 1>will help you out if you want to try this.

0:25:12.760 --> 0:25:16.879
<v Speaker 1>And really, the nice thing is there's so many that

0:25:16.920 --> 0:25:19.280
<v Speaker 1>are out there that you've got a good chance. If

0:25:19.280 --> 0:25:23.080
<v Speaker 1>you just plug in whatever processor you have and the

0:25:23.119 --> 0:25:26.840
<v Speaker 1>word overclocking into a decent search engine, you will probably

0:25:26.880 --> 0:25:30.560
<v Speaker 1>get some returns from people who have gone through this

0:25:30.600 --> 0:25:32.840
<v Speaker 1>process and they can tell you what worked for them

0:25:32.960 --> 0:25:36.080
<v Speaker 1>or what you know, what things to avoid. Um And

0:25:36.119 --> 0:25:37.760
<v Speaker 1>like I said, there are a lot of communities out

0:25:37.760 --> 0:25:41.040
<v Speaker 1>there on the net that have just full discussions, like

0:25:41.080 --> 0:25:44.119
<v Speaker 1>full message boards just dedicated to overclocking and the different

0:25:44.160 --> 0:25:46.760
<v Speaker 1>techniques that they used. And uh, you know, some of

0:25:46.800 --> 0:25:48.920
<v Speaker 1>these might be a little technical and might require a

0:25:48.960 --> 0:25:52.520
<v Speaker 1>little bit of backtracking so that you can really understand

0:25:52.760 --> 0:25:58.359
<v Speaker 1>the the subtle, the subtleties of what it is they're saying.

0:25:58.600 --> 0:26:03.080
<v Speaker 1>But but it's totally doable. I mean, in most cases,

0:26:03.119 --> 0:26:06.000
<v Speaker 1>it's doable without you ever having to crack open your computer,

0:26:06.119 --> 0:26:07.960
<v Speaker 1>which is the best part, right you know, because you

0:26:08.440 --> 0:26:10.160
<v Speaker 1>every time you have to open your computer and take

0:26:10.160 --> 0:26:14.880
<v Speaker 1>stuff out, that eliminates a significant percentage of the people

0:26:14.920 --> 0:26:17.240
<v Speaker 1>who would have tried it otherwise just because it's either

0:26:17.440 --> 0:26:21.440
<v Speaker 1>too much of a hassle or they find it too intimidating. UM.

0:26:21.680 --> 0:26:24.359
<v Speaker 1>Two things though to to make sure. One that you

0:26:24.440 --> 0:26:29.680
<v Speaker 1>don't make assumptions on similarities. That was one thing that

0:26:29.680 --> 0:26:32.000
<v Speaker 1>that I read that if your computer, if you're reading

0:26:32.400 --> 0:26:35.080
<v Speaker 1>information Reform about overclock and you're getting ready, you're you're

0:26:35.280 --> 0:26:39.160
<v Speaker 1>gotten the bug. You're seriously thinking about this now, and

0:26:39.200 --> 0:26:41.800
<v Speaker 1>that you're reading a post by someone who's done it,

0:26:42.040 --> 0:26:44.639
<v Speaker 1>who's who's got a chip that's a little that's just

0:26:44.720 --> 0:26:47.600
<v Speaker 1>a little different than yours. Don't go by that information.

0:26:47.640 --> 0:26:50.359
<v Speaker 1>They said that, Um, from from what I have read

0:26:50.520 --> 0:26:52.920
<v Speaker 1>from people who have written instructions on so you want

0:26:52.960 --> 0:26:55.720
<v Speaker 1>to overclock your computer, well here's what you should do.

0:26:55.880 --> 0:26:57.800
<v Speaker 1>That was one of the things that I read several

0:26:57.840 --> 0:27:01.280
<v Speaker 1>times was if you've got something that's very similar to

0:27:01.520 --> 0:27:05.120
<v Speaker 1>what you've got to the instructions from, don't don't go

0:27:05.320 --> 0:27:08.760
<v Speaker 1>by strict similarities. Make sure that you are going by

0:27:08.920 --> 0:27:13.359
<v Speaker 1>someone who knows instructions based on the specific stuff that

0:27:13.400 --> 0:27:16.919
<v Speaker 1>you're using. Because similarities aren't good enough. When you're messing

0:27:16.960 --> 0:27:20.000
<v Speaker 1>with this, you could seriously damage your computer. And uh,

0:27:20.280 --> 0:27:23.800
<v Speaker 1>that's the other part. Make sure that you're really willing

0:27:24.000 --> 0:27:27.159
<v Speaker 1>to give this a try, knowing that you might really

0:27:27.400 --> 0:27:30.320
<v Speaker 1>muck things up for the insides of your machine. Yeah,

0:27:30.320 --> 0:27:33.080
<v Speaker 1>if you're careful, you probably don't really need to worry

0:27:33.160 --> 0:27:34.520
<v Speaker 1>so much. But it's good to have in the back

0:27:34.560 --> 0:27:37.719
<v Speaker 1>of your mind because otherwise, you know, if you you know,

0:27:37.840 --> 0:27:39.720
<v Speaker 1>if you do the typical what we like to think

0:27:39.720 --> 0:27:42.879
<v Speaker 1>of as the typical American thing, we're more equals better, right,

0:27:43.040 --> 0:27:45.600
<v Speaker 1>you might be let's craig it up to eleven and

0:27:45.640 --> 0:27:49.160
<v Speaker 1>the next thing you know, your machine doesn't do anything anymore.

0:27:49.200 --> 0:27:52.679
<v Speaker 1>It's not it's not doing anything faster than any machine

0:27:52.720 --> 0:27:56.359
<v Speaker 1>you've ever had. My computer does nothing at the speed

0:27:56.359 --> 0:28:00.520
<v Speaker 1>of light. It works great as a doorstop. Yeah. No,

0:28:00.640 --> 0:28:02.880
<v Speaker 1>I'm sure that there will be somebody out there who's

0:28:02.920 --> 0:28:06.240
<v Speaker 1>listening listening to this podcast who has had experience overclocking,

0:28:06.240 --> 0:28:08.320
<v Speaker 1>and they're going to write in and say, no, Jonathan

0:28:08.359 --> 0:28:11.720
<v Speaker 1>and Chris, it's easy to overclock, maybe for some people,

0:28:12.200 --> 0:28:16.119
<v Speaker 1>but for some systems and for some systems, but um,

0:28:16.359 --> 0:28:18.840
<v Speaker 1>you can't. You can't. You can't at play that universally

0:28:18.880 --> 0:28:22.679
<v Speaker 1>across everybody. And uh, and it's it is possible that

0:28:22.800 --> 0:28:26.680
<v Speaker 1>if you're not careful, you could damage your computer. And

0:28:26.800 --> 0:28:29.320
<v Speaker 1>if you don't have a need for overclocking, if you're

0:28:29.320 --> 0:28:35.960
<v Speaker 1>not playing lots of of of high resource demanding games

0:28:36.640 --> 0:28:39.200
<v Speaker 1>or or other applications that just require a lot of

0:28:39.200 --> 0:28:43.400
<v Speaker 1>processing power. Um. I mean, it could be a fun

0:28:43.440 --> 0:28:45.520
<v Speaker 1>experiment if it's something that you just want to try

0:28:45.520 --> 0:28:47.120
<v Speaker 1>and get your hand in, and especially if you have

0:28:47.200 --> 0:28:49.200
<v Speaker 1>like an old machine lying around that you don't really

0:28:49.240 --> 0:28:51.320
<v Speaker 1>care about and you just want to have the experience

0:28:51.360 --> 0:28:53.960
<v Speaker 1>of overclocking something, that's fine. But if you don't really

0:28:53.960 --> 0:28:55.680
<v Speaker 1>have a need for it at all, I really don't

0:28:55.720 --> 0:28:58.760
<v Speaker 1>see any reason to do it, because ultimately, if you

0:28:58.800 --> 0:29:02.120
<v Speaker 1>are overclocking your machine to really push its limits, that

0:29:02.320 --> 0:29:04.560
<v Speaker 1>is it is not just a time investment, but it

0:29:04.640 --> 0:29:06.959
<v Speaker 1>is a money investment too, because you will have to

0:29:07.000 --> 0:29:09.800
<v Speaker 1>find some way to address that heat problem. It's not

0:29:10.040 --> 0:29:12.520
<v Speaker 1>you know, because your computer when it was built, was

0:29:12.560 --> 0:29:15.000
<v Speaker 1>built with a certain amount of heat in mind and

0:29:15.080 --> 0:29:17.720
<v Speaker 1>nothing beyond that, and you're gonna be generating a lot

0:29:17.760 --> 0:29:19.960
<v Speaker 1>more heat than what that computer was designed to handle.

0:29:20.480 --> 0:29:22.400
<v Speaker 1>On the other hand, if your office is in the breeder,

0:29:23.080 --> 0:29:25.720
<v Speaker 1>that may not be such a problem. Yeah, some days

0:29:25.720 --> 0:29:28.600
<v Speaker 1>I wonder if we are so that wraps up this

0:29:28.680 --> 0:29:32.760
<v Speaker 1>discussion about overclocking and apparently the HVAC system and how

0:29:32.800 --> 0:29:35.720
<v Speaker 1>stuff works dot com. If you guys have any requests

0:29:35.760 --> 0:29:37.400
<v Speaker 1>for topics that you would like us to cover, let

0:29:37.480 --> 0:29:40.000
<v Speaker 1>us know on Facebook or Twitter. Are handled. There is

0:29:40.040 --> 0:29:43.280
<v Speaker 1>text stuff h s W or send us an email.

0:29:43.400 --> 0:29:47.239
<v Speaker 1>Our address is tech stuff at Discovery dot com and

0:29:47.320 --> 0:29:49.600
<v Speaker 1>Chris and I will talk to you again really soon.

0:29:53.800 --> 0:29:56.400
<v Speaker 1>Brought to you by the reinvented two thousand twelve camera.

0:29:56.720 --> 0:29:57.920
<v Speaker 1>It's ready, are you