WEBVTT 00:00:00.240 --> 00:00:07.759 So, I actually did a dedicated video on core unlocking quite some time ago on my 00:00:04.520 --> 00:00:10.480 NCIXCOM channel, but ASUS has actually 00:00:07.759 --> 00:00:15.440 recently updated their core unlocker utility to make it even simpler. So, 00:00:13.440 --> 00:00:21.520 Core Unlocking is basically taking processors such as the 00:00:17.240 --> 00:00:22.880 X3720, which AMD has um what they've 00:00:21.520 --> 00:00:30.240 done is they've actually Okay, I'm going to drop the camera here for a minute so that I can break the seal on the CPU box 00:00:27.199 --> 00:00:32.559 here. What AMD has actually done is they 00:00:30.240 --> 00:00:38.480 have physically disabled well not physically but through kind of a a 00:00:34.559 --> 00:00:42.320 software trick they have disabled the uh 00:00:38.480 --> 00:00:44.320 one of the cores in the CPU. So they've 00:00:42.320 --> 00:00:50.079 actually got dual cores that are also unlock or locked quad cores as well as 00:00:47.280 --> 00:00:53.600 the triple cores. So the 720 today basically okay here I'm going to sort of 00:00:51.840 --> 00:01:00.320 stop rambling. The point of this video is to show you in real time how quickly 00:00:56.800 --> 00:01:02.000 you can unlock the core of a CP of a CPU 00:01:00.320 --> 00:01:09.360 in order to get better performance out of it. So today I'm going to be using the M4A889 GTD Pro USB 3 from ASUS using 00:01:07.360 --> 00:01:14.000 their core unlocker. So ASUS has simplified the whole process down to one 00:01:12.080 --> 00:01:18.320 button, a switch that you hit on the motherboard that will automatically 00:01:15.920 --> 00:01:23.840 unlock any available extra cores for you. So here's my uh my retail 720. Just 00:01:22.080 --> 00:01:28.640 going to install it in the socket here. So, lift up the lever. All right. 00:01:26.400 --> 00:01:33.360 Where's my little triangle? I think it's going to be in that corner. Yep, there 00:01:30.000 --> 00:01:35.280 we go. Okay. So, install that. Now, I'm 00:01:33.360 --> 00:01:39.439 just doing a quick demo here, so I'm not going to bother Oh, my batter is dying. 00:01:38.159 --> 00:01:43.680 That's going to make this a far less effective demonstration in real time. 00:01:42.000 --> 00:01:48.320 Hopefully, it lasts long enough for me to get some thermal compound on here and 00:01:46.079 --> 00:01:51.920 boot this thing up. So, I'm just going to apply a little bit of thermal 00:01:49.439 --> 00:01:56.000 compound on the CPU and then I'm just going to throw a heat sink on top of it 00:01:53.840 --> 00:02:01.360 rather than actually hook it up properly because um I don't have a whole lot of 00:01:58.719 --> 00:02:05.439 time here. So, here we go. Just going to plug in the fan. Okay, so the Coron 00:02:02.960 --> 00:02:10.479 locker has been simplified right down to a and we're back. Hate it when the uh 00:02:08.640 --> 00:02:15.680 battery dies on my camera, but what can you do? Okay, so I was just showing the 00:02:12.879 --> 00:02:19.680 core unlocking button that ASUS has added to their motherboard. Well, 00:02:17.760 --> 00:02:22.879 motherboards, some of them. So, you can see there's a little arrow here that 00:02:21.200 --> 00:02:27.760 points to where the core unlocker button is. You press that button, the light 00:02:24.560 --> 00:02:31.760 goes red, and then in theory, there are 00:02:27.760 --> 00:02:33.680 four cores on this triple core CPU. 00:02:31.760 --> 00:02:39.760 Now there's a lot of uh misconceptions about uh you know there being dangers 00:02:36.840 --> 00:02:43.519 involved in unlocking cores like your system's going to be unstable and that 00:02:41.760 --> 00:02:49.360 may be true but you got to understand that AMD unlocks cores for any number of 00:02:46.800 --> 00:02:53.760 different reasons. Some of them are unlocks them locks them seals them off 00:02:51.920 --> 00:02:59.760 for any number of different reasons. So press F1 to go into setup. Okay. F10 00:02:57.680 --> 00:03:04.000 enter. And so those reasons could be anything ranging from the core being 00:03:01.599 --> 00:03:09.360 actually physically defective to maybe it not meeting their target power 00:03:05.920 --> 00:03:11.680 envelope to maybe it being stable but 00:03:09.360 --> 00:03:16.159 you know only uh only within not quite within their tolerances because almost 00:03:13.519 --> 00:03:21.680 all CPUs will actually run faster than what they're spec by at least a little 00:03:18.080 --> 00:03:23.599 bit. Okay. So as long as you run the 00:03:21.680 --> 00:03:28.080 proper stability test. Oh, there you go. Four cores are activated. That was easy. 00:03:25.760 --> 00:03:33.040 As long as you run the necessary stability tests on your CPU, which means 00:03:30.400 --> 00:03:39.519 just, you know, Prime 95 for 24 to 48 hours, if the CPU doesn't make a math 00:03:35.440 --> 00:03:42.760 error, then it's stable. And this one 00:03:39.519 --> 00:03:46.239 appears to be not 00:03:42.760 --> 00:03:49.040 stable. That's too bad. I mean, there 00:03:46.239 --> 00:03:58.560 you go. I just pulled sort of any random any random retail CPU. And uh this one 00:03:53.440 --> 00:04:00.400 happens to not be stable with the core 00:03:58.560 --> 00:04:04.319 unlocker. I'm going to give it sort of one more try. I'm going to load the 00:04:02.000 --> 00:04:09.280 defaults in the setup here and I'm going to 00:04:05.400 --> 00:04:11.120 cuz h that's kind of disappointing. I've 00:04:09.280 --> 00:04:16.639 actually had pretty good success myself unlocking CPUs and I had hoped that this 00:04:14.560 --> 00:04:21.440 just sort of random one would work for me here. So far, no success. But that's 00:04:19.919 --> 00:04:27.759 the whole point of doing this kind of thing on camera so that everyone can 00:04:24.000 --> 00:04:31.880 learn and have new experiences. Maybe 00:04:27.759 --> 00:04:31.880 I'll have some of my V8 juice. 00:04:32.960 --> 00:04:41.040 Hopefully we don't get a blue screen this time. Blue screens are bad. Okay. 00:04:37.360 --> 00:04:41.040 No, let's just start Windows 00:04:43.000 --> 00:04:52.360 normally. H I wonder if it's to do with AHCI mode. 00:04:49.240 --> 00:04:55.440 Could be something like 00:04:52.360 --> 00:04:57.919 that. Well, I guess you're along for the 00:04:55.440 --> 00:05:01.440 ride now. I'm not about to stop the video now. If 00:05:01.880 --> 00:05:08.240 you're interested, you can keep watching. And if you're not, then you 00:05:05.680 --> 00:05:12.960 can always not watch anymore. So, I'm going to go into the onboard devices 00:05:10.320 --> 00:05:17.479 configuration. I'm going to set the serial serial port. No, I'm going to set 00:05:16.479 --> 00:05:23.240 the onboard. No. 00:05:20.600 --> 00:05:29.639 Hey, where are my uh where are my SATA 00:05:26.199 --> 00:05:31.479 ports? North bridge configuration. 00:05:29.639 --> 00:05:35.960 No. No. This is stupid. 00:05:39.840 --> 00:05:42.840 H. 00:05:45.280 --> 00:05:54.560 Well, I might have to give up at some point here. Can't figure out how to 00:05:51.000 --> 00:05:58.080 set RAID on this motherboard. Normally, 00:05:54.560 --> 00:06:02.080 it's here, but I don't see it here. So, 00:05:58.080 --> 00:06:05.479 I I actually don't have any uh any ideas 00:06:02.080 --> 00:06:05.479 beyond that. 00:06:15.840 --> 00:06:24.199 Oh, wonder if that's a problem. I'm going to do 00:06:19.000 --> 00:06:24.199 this. Probably not, but you never know. 00:06:34.319 --> 00:06:42.800 Maybe I'll just show you the test bench some more. So, there's that little light that 00:06:39.280 --> 00:06:42.800 says in theory everything should be 00:06:43.400 --> 00:06:50.919 working. I didn't turn on turbo key, so it's not the uh it's not the automated 00:06:48.560 --> 00:06:56.199 overclocking that's causing any problems here. Okay, we'll try that one more 00:06:53.199 --> 00:06:56.199 time. 00:06:59.759 --> 00:07:07.280 Oh, wouldn't it be funny if that had been 00:07:03.720 --> 00:07:09.039 it? How about that? So, there you go. We 00:07:07.280 --> 00:07:14.080 figured out how to get the system booted up. Well, we I guess I Well, you were 00:07:11.599 --> 00:07:18.240 here, too. Okay. No, we we figured out how to get the system booted up. I have 00:07:15.759 --> 00:07:22.160 Catalyst Control Center installed, which is completely unnecessary when you're 00:07:19.840 --> 00:07:28.000 running a NVIDIA video card. So, I'm just going to go ahead and exit that. 00:07:23.280 --> 00:07:30.400 So, let's uh let's fire up CPUZ to see 00:07:28.000 --> 00:07:34.720 whether we have four cores running or not. So, I'm just going to go ahead and 00:07:32.479 --> 00:07:39.199 do that. And it looks like we have four cores, four threads. They're running at 00:07:37.039 --> 00:07:43.520 stock speed of 2.8 GHz. So, we'll go into the task manager here. So, yeah, 00:07:41.360 --> 00:07:48.160 you can see that task manager has 1 2 3 four CPUs. And then we Okay, this is 00:07:46.319 --> 00:07:54.879 what I was saying before. You will need to run Prime 95 and I recommend small 00:07:51.160 --> 00:07:56.879 FFTs for I'd say a minimum of 24 hours 00:07:54.879 --> 00:08:02.240 and then I'd run it anywhere from 24 to 48 hours to ensure that your triple core 00:07:58.960 --> 00:08:04.759 CPU is stable with four cores enabled. 00:08:02.240 --> 00:08:09.759 And then you can actually even sometimes overclock triple cores unlocked to quad 00:08:07.520 --> 00:08:14.800 core and get even even more performance out of them. But there you go. That was 00:08:11.440 --> 00:08:17.440 my core unlocking uh tutorial and we 00:08:14.800 --> 00:08:22.280 figured out what the problem was and thank you for checking it out.