WEBVTT 00:00:00.080 --> 00:00:08.720 okay come here come here okay so this is our mining GPU that we're using 00:00:05.359 --> 00:00:11.519 for gaming in spite of its complete lack 00:00:08.720 --> 00:00:16.320 of any video outputs but you've seen this before 00:00:13.360 --> 00:00:19.760 and the last time we left you guys we weren't recommending these things even 00:00:18.480 --> 00:00:26.000 though they're like 75 bucks for the equivalent of a gtx 00:00:22.800 --> 00:00:29.199 1060 because the only drivers we had for 00:00:26.000 --> 00:00:31.679 them were modified by some chinese 00:00:29.199 --> 00:00:37.440 driver modification team and we had no way of knowing exactly what was inside 00:00:33.920 --> 00:00:40.559 them but today all of that changes first 00:00:37.440 --> 00:00:43.920 and foremost we are going to manually 00:00:40.559 --> 00:00:46.800 modify NVIDIA's drivers ourselves making 00:00:43.920 --> 00:00:50.559 this completely safe to use second while we're at it we're going to 00:00:48.559 --> 00:00:54.879 kill NVIDIA's telemetry that they build into their drivers and third 00:00:53.199 --> 00:00:58.719 we are going to run this in sli 00:00:56.879 --> 00:01:03.600 with one of these which is like what 00:01:00.800 --> 00:01:07.600 what running a real gaming GPU with a mining one in sli they're not even the 00:01:05.760 --> 00:01:13.360 same part number oh and while we're at it the 1060 doesn't even support sli 00:01:11.600 --> 00:01:16.240 but we're gonna do it you know what else we're gonna do tell 00:01:14.880 --> 00:01:20.159 you about our sponsor glasswire with glasswire you can 00:01:18.400 --> 00:01:24.159 instantly see your current and past network activity you can detect malware 00:01:22.240 --> 00:01:28.880 and block badly behaving apps on your pc or Android device and you can get it for 00:01:26.560 --> 00:01:35.659 25 off at the link in the video description with offer code Linus 00:01:38.640 --> 00:01:44.240 okay so here's the situation right now we're not quite starting from scratch 00:01:42.400 --> 00:01:48.960 but pretty close so we've already disabled driver signing and you can see 00:01:46.159 --> 00:01:53.200 how to do that in our previous video here where we use the the modified 00:01:50.960 --> 00:01:57.520 chinese driver but other than that we're looking at a pretty bone stock 00:01:54.960 --> 00:02:03.119 configuration here so our p106 mining GPU is installed in our system but the 00:02:00.479 --> 00:02:06.960 drivers for it are not loaded in any way we're in a in a completely blank state 00:02:04.880 --> 00:02:11.440 and we're running entirely off of the onboard graphics that are built into our 00:02:09.280 --> 00:02:14.959 CPU here so Anthony's back hi 00:02:18.239 --> 00:02:24.720 uh before we go any further i want to lay out what our ideal scenario would be 00:02:22.480 --> 00:02:29.520 here because in our last video we weren't just relying on a driver of 00:02:27.360 --> 00:02:34.879 unknown origins it was also a little bit on the older side so in a perfect world 00:02:32.160 --> 00:02:39.760 we would want our p106 mining card here to behave exactly like a gtx 1060 00:02:37.840 --> 00:02:44.080 because hardware wise they're the same thing so that means gaming support 00:02:41.920 --> 00:02:48.879 compute support and even end bank video encoding support and all of that while 00:02:46.480 --> 00:02:53.040 being able to run the very latest drivers however we've run into some 00:02:51.360 --> 00:02:56.879 challenges and we are going to have to make a few compromises here so 00:02:55.599 --> 00:03:00.959 what do we got well first of all we won't be able to run on 00:02:59.280 --> 00:03:05.040 the latest driver at least not right now the way it works right now it we're just 00:03:02.560 --> 00:03:07.680 getting a code 43 error every time so 00:03:05.760 --> 00:03:12.400 either NVIDIA has changed something or they've hatched it or whatever either 00:03:09.599 --> 00:03:16.319 way we're stuck with 416.34 aside from that as far as i know it's not possible 00:03:14.480 --> 00:03:20.159 to get mvx to work so so you're stuck with quick sync which 00:03:18.400 --> 00:03:26.560 fortunately you're gonna have to have because you're running your onboard graphics anyway in order to even get a 00:03:23.360 --> 00:03:28.400 display output from this thing or x264 00:03:26.560 --> 00:03:34.480 so with that out of the way Anthony is going to start by downloading our own 00:03:31.519 --> 00:03:39.519 fresh version of that 416 series driver and then taking the chinese one and the 00:03:37.440 --> 00:03:43.920 NVIDIA one and comparing what the difference is between them so that we 00:03:41.599 --> 00:03:48.720 can replicate the modifications that the chinese team has made that allows the 00:03:46.159 --> 00:03:53.519 driver to be installed without copying over anything that could be 00:03:50.959 --> 00:03:57.360 nefariously hidden inside it so i'm using notepad plus plus and the reason 00:03:55.280 --> 00:04:00.319 for that is it's free it's pretty great actually it's got a huge number of 00:03:58.640 --> 00:04:04.879 features including this compare feature which we can access via this plugins 00:04:02.720 --> 00:04:08.319 section here we just type in compare and i've already installed it so it's in 00:04:06.239 --> 00:04:12.560 here but yeah once you have that just go to you load up your first file go to 00:04:10.480 --> 00:04:16.880 plugins compare set as first to compare i've already done that now i will load 00:04:14.799 --> 00:04:20.079 up the other one which is this chinese driver 00:04:17.919 --> 00:04:23.600 plugins compare compare so here we have a full listing of 00:04:22.479 --> 00:04:28.000 everything that is different between these two drivers so as we can see these 00:04:26.080 --> 00:04:33.120 lines here have been modified so where it used to say section 110 it now says 00:04:30.720 --> 00:04:39.120 section 108 which is actually the same if you look at these device ids 1c06 is 00:04:36.160 --> 00:04:44.320 actually the gtx 1060 one c07 is our p106 they have different sections in the 00:04:41.840 --> 00:04:47.919 vanilla driver but in the chinese driver they do not that is the primary thing 00:04:46.160 --> 00:04:52.400 we're going to be changing here okay now the final one of these sections here 00:04:50.639 --> 00:04:55.840 you'll notice that it actually says that it's 109 instead of 110. it's dropped 00:04:54.320 --> 00:05:00.320 down a number the same is true over here so we'll just follow here so it'll be 00:04:58.080 --> 00:05:05.759 107 for each basically what we're doing is we're copying the same config from 00:05:02.639 --> 00:05:08.240 our 1c06 which is our gtx 1060. so we 00:05:05.759 --> 00:05:13.199 want section 107 for all of these things now what we're doing here is basically 00:05:11.039 --> 00:05:17.280 just tricking the driver into thinking it's compatible we're not actually 00:05:14.639 --> 00:05:21.280 changing any of the functional files of the driver installation is that 00:05:19.440 --> 00:05:25.520 correct that's right and if we go down through the rest of the comparison here 00:05:22.880 --> 00:05:29.759 there is nothing different really so then it's possible that our chinese 00:05:27.120 --> 00:05:34.000 driver was totally clean yeah possible but i mean we don't know about the exes 00:05:32.080 --> 00:05:37.280 the inf is perfectly fine we can make some additional changes while we're here 00:05:35.360 --> 00:05:42.880 though telemetry isn't it convenient that they just listed under nv telemetry 00:05:39.759 --> 00:05:45.520 yeah for those not familiar telemetry is 00:05:42.880 --> 00:05:49.919 a feature of a software or driver that reports back on your usage to the 00:05:48.560 --> 00:05:55.039 manufacturer and a lot of the time this is stuff that 00:05:52.160 --> 00:05:59.360 you can opt out of but a lot of the time it's just baked right in so there you go 00:05:57.120 --> 00:06:03.120 we passed our compatibility check yep let's go ahead and install it of course 00:06:01.039 --> 00:06:05.600 we do not want GeForce experience also don't care about 3d vision because we 00:06:04.319 --> 00:06:11.520 don't actually have anything that we can connect it to and hopefully we will get 00:06:08.720 --> 00:06:16.960 the same exact thing we got the other day but we did it for ourselves on a 00:06:13.919 --> 00:06:20.319 fresh driver hey there we go all right 00:06:16.960 --> 00:06:22.560 so that's it if nothing else we now can 00:06:20.319 --> 00:06:25.759 say confidently that if you pick up one of these mining cards and use this 00:06:24.479 --> 00:06:29.039 method on this particular driver you will be 00:06:28.160 --> 00:06:32.240 able to play games 00:06:32.560 --> 00:06:38.639 yeah that monitor doesn't really have a shield on its 00:06:36.720 --> 00:06:42.639 yeah the biggest criticism we had last time is that we didn't actually show the 00:06:41.120 --> 00:06:48.560 Intel integrated and how poorly that performed oh really 00:06:45.120 --> 00:06:51.280 yeah oh uh it would be worse than this 00:06:48.560 --> 00:06:54.800 a lot worse yeah this is deus ex mankind divided running at 1080p 00:06:53.759 --> 00:07:00.800 at greater than eight frames per second so 00:06:59.360 --> 00:07:04.880 it's working now the thing is even though we're 00:07:02.880 --> 00:07:08.560 having trouble moving on to the latest drivers which would give us support for 00:07:06.720 --> 00:07:11.520 things like oh i mean i guess freesync doesn't matter because you'd be you 00:07:10.000 --> 00:07:15.840 could actually have freesync running off of Intel's onboard graphics yeah oh you 00:07:14.240 --> 00:07:20.639 could never mind depending on whether or not your onboard graphics supports freesync okay but still there are good 00:07:19.120 --> 00:07:24.479 reasons to be running the latest drivers now we're not saying it's impossible 00:07:23.039 --> 00:07:28.880 we're just saying that when we applied this same method to 00:07:27.199 --> 00:07:33.919 the latest drivers even checking line by line 00:07:31.440 --> 00:07:37.919 we weren't successful so it might just be down to people who are a little bit 00:07:36.560 --> 00:07:42.560 better versed in their driver modification wizardry to figure out what 00:07:40.639 --> 00:07:46.240 the additional things that NVIDIA has changed whether just 00:07:44.720 --> 00:07:50.880 through the course of changing things to make them better or to specifically 00:07:47.840 --> 00:07:52.160 block this in order to make that work 00:07:50.880 --> 00:07:56.800 either way at the very least using a slightly older 00:07:54.400 --> 00:08:00.080 driver we have a working gaming system 00:07:58.479 --> 00:08:04.879 on the cheap but that's not where we stopped today for 00:08:03.280 --> 00:08:09.120 our next trick we're gonna run this thing in sli now 00:08:07.520 --> 00:08:13.599 we're still gonna have to deal with that same driver compatibility limitation 00:08:11.280 --> 00:08:20.240 because one of the cards in our system is one of these p106 mining cards but 00:08:17.039 --> 00:08:23.199 what it at least demonstrates is that 00:08:20.240 --> 00:08:27.520 from a proof of concept standpoint this can work so you might think that this 00:08:25.599 --> 00:08:32.240 process is as simple as throwing a real gtx 1060 into the system and then again 00:08:30.639 --> 00:08:37.440 forcing our driver to install remember it's an unsigned driver now so you gotta 00:08:34.800 --> 00:08:41.200 do that process manually but as we're about to discover 00:08:39.599 --> 00:08:45.680 it did not it did not 00:08:43.200 --> 00:08:50.640 oh hi mark whatever the point is there's no sli option in here whatsoever so 00:08:48.959 --> 00:08:55.519 now what some kind of weird thing off the tech powerup form yeah what are we 00:08:52.480 --> 00:08:57.360 doing so it's a program called different 00:08:55.519 --> 00:09:00.640 sli auto it's currently in the downloads folder but you guys will have to 00:08:59.040 --> 00:09:05.360 download and extract that for yourselves and we don't actually want to run the 00:09:02.160 --> 00:09:06.560 program okay that would be too easy yes 00:09:05.360 --> 00:09:11.120 it used to work but it doesn't anymore so 00:09:09.200 --> 00:09:16.240 so you'll want to go to see Windows system 32 driver store and now we want 00:09:13.760 --> 00:09:19.519 to sort it by date we want to copy the uh 00:09:17.800 --> 00:09:25.120 nvldmkm it's the driver itself i might not see this here 00:09:23.600 --> 00:09:29.360 yeah i couldn't find it earlier either okay so just in a sea of envy paste it 00:09:27.360 --> 00:09:33.600 into the different sli auto folder now you want to open up a hex editor i 00:09:30.800 --> 00:09:37.839 downloaded hxd it's free should be there on the desktop okay oh you got it you 00:09:35.839 --> 00:09:44.320 want to search for this for the string of uh values seven five zero five zero f 00:09:41.839 --> 00:09:47.360 b a oh i already had it there okay cool there it is so we want to change that so 00:09:46.399 --> 00:09:52.360 you'll want to go to the beginning of that and type in yeah c74324000 00:09:56.720 --> 00:10:03.279 the hard part's over okay so we want to go back to the folder you 00:10:01.360 --> 00:10:07.760 got that driver from we want to take the folder name itself copy that and this is 00:10:05.760 --> 00:10:11.760 probably also already auto populated but if you go back to the different sli auto 00:10:09.360 --> 00:10:15.839 folder yep right click install.cmd go to edit see where it says the nb disk inf 00:10:14.240 --> 00:10:19.680 that kind of stuff there you want to replace that in every 00:10:17.760 --> 00:10:23.279 every every instance so you can use the replace function in notepad for that 00:10:21.760 --> 00:10:29.120 yeah all right so then we want to restart into safe mode 00:10:25.440 --> 00:10:31.760 oh lordy okay so networking yeah sure 00:10:29.120 --> 00:10:36.320 all right next you're going to want to go into that folder again different sli 00:10:34.160 --> 00:10:39.440 auto and run install.cmd as administrator i guess it's the same 00:10:37.600 --> 00:10:44.640 thing in safe mode anyway you know what let's just do it okay boom reboot now 00:10:42.399 --> 00:10:50.640 for changes to take effect yep so what have we done here sign the driver really 00:10:48.079 --> 00:10:55.519 supposedly it doesn't actually work oh okay um that's something that we can do 00:10:52.800 --> 00:10:59.600 though um something that requires a lot more busting around that 00:10:57.760 --> 00:11:04.959 we don't really want to do right now it does that copies the modified driver that we 00:11:03.200 --> 00:11:08.959 change the bits around in to the proper locations in Windows yep 00:11:08.000 --> 00:11:14.959 and well that's really about it and then just to clarify for the viewers 00:11:12.399 --> 00:11:19.440 out there changing those hex values have we done anything unsafe to our system 00:11:17.440 --> 00:11:22.880 have we potentially compromised it not compromised no but who told us to change 00:11:21.519 --> 00:11:29.680 those values well it's actually a guy on the tech powerup 00:11:25.600 --> 00:11:31.519 forums okay by the name of um 00:11:29.680 --> 00:11:34.800 pretentious yeah there we go that's the name yeah he's got a little script that 00:11:33.040 --> 00:11:39.360 he runs that takes about an hour or two to find where exactly the string that we 00:11:36.880 --> 00:11:43.839 found yeah is in each driver release and he just updates it on the forum it's 00:11:41.519 --> 00:11:48.320 pretty great basically what it does yeah is it disables the check for sli as far 00:11:46.079 --> 00:11:52.079 as motherboard compatibility and you know enter GPU compatibility so to be 00:11:50.880 --> 00:11:58.800 clear you guys aren't going to be running an rtx 2080 ti and 00:11:55.360 --> 00:12:01.680 a gtx 1030 and sli at least not 00:11:58.800 --> 00:12:06.560 to any positive effect but over here in a case where we have two 00:12:04.000 --> 00:12:09.760 gpus that we know are identical other than NVIDIA 00:12:08.160 --> 00:12:13.760 deciding they're not our expectation is that we would 00:12:11.839 --> 00:12:17.839 actually be able to achieve an improvement in performance 00:12:15.519 --> 00:12:20.480 so here it is the sli option is there in the driver we're going to go ahead and 00:12:19.360 --> 00:12:26.120 enable it and bippidy 00:12:27.440 --> 00:12:36.079 oh keyboard light just went off as it turns out that sli mod will not work 00:12:32.560 --> 00:12:37.279 with the p106 unfortunately whatever 00:12:36.079 --> 00:12:42.880 maybe it's the fact that it doesn't have outputs maybe it's the fact that they have two different v BIOS's that are you 00:12:41.360 --> 00:12:46.639 know for whatever reason right now it does not work if we could force the card 00:12:45.040 --> 00:12:53.360 to take a different b bias that might work but i haven't been able to get that to work either i mean we can still run 00:12:50.800 --> 00:12:55.519 gtx 1060 is an sli i guess that's still fun 00:12:54.079 --> 00:13:00.720 all right so what we've done here is we've manually installed our driver again 00:12:57.920 --> 00:13:05.279 moved our HDMI cable over to this GPU and we're going to go ahead and enable 00:13:03.120 --> 00:13:10.639 our other device which got automatically disabled somewhere along the way it's 00:13:06.800 --> 00:13:10.639 kind of like a precautionary measure hey 00:13:10.800 --> 00:13:17.600 sli enabled on the gtx 1060. 00:13:14.480 --> 00:13:19.040 where's my deus ex at now beaches i'm 00:13:17.600 --> 00:13:22.560 actually not sure what the scaling would be like here 00:13:21.279 --> 00:13:27.519 now the thing here is that there's nothing particularly amazing about 00:13:25.200 --> 00:13:31.120 running graphics cards in a multi-GPU configuration without a bridge running 00:13:29.440 --> 00:13:36.000 between them in fact AMD has been doing it this way for several generations now 00:13:33.200 --> 00:13:40.560 NVIDIA though has stuck to their guns saying that the available bandwidth over 00:13:38.000 --> 00:13:44.720 the pci express slots is not enough to handle the intercard communication and 00:13:42.399 --> 00:13:50.000 has even gone as far as to upgrade the original sli link to the new envy link 00:13:48.079 --> 00:13:56.720 standard that you'll see on their rtx cards with that said even though we won't be 00:13:53.519 --> 00:13:59.120 able to speak to necessarily 00:13:56.720 --> 00:14:03.680 you know micro stuttering and how this solution affects something like that we 00:14:01.120 --> 00:14:07.600 can see if we could at least get an FPS improvement with this configuration and 00:14:05.440 --> 00:14:11.120 we'll know pretty shortly here yeah the benchmark only takes 90 seconds 00:14:09.920 --> 00:14:16.399 hey wow that's a pretty nice little improvement 00:14:15.040 --> 00:14:21.279 there isn't it yeah so 00:14:18.240 --> 00:14:24.399 once again our experimenting with NVIDIA 00:14:21.279 --> 00:14:27.199 graphics cards video does come with some 00:14:24.399 --> 00:14:31.920 caveats this isn't necessarily a configuration we'd recommend sli is in 00:14:30.000 --> 00:14:36.800 most cases not as good an option as simply getting 00:14:34.079 --> 00:14:42.000 a single higher powered graphics card so i don't even necessarily disagree with 00:14:39.120 --> 00:14:46.639 NVIDIA disabling sli by default on their lower end cards it's just something that 00:14:44.079 --> 00:14:51.120 was kind of fun to do and interesting to show you guys 00:14:48.000 --> 00:14:54.639 just how simple it is for manufacturers 00:14:51.120 --> 00:14:56.800 to lock down and or enable functionality 00:14:54.639 --> 00:15:00.560 at least from a sort of hex editor perspective now the qc that would 00:14:58.959 --> 00:15:04.160 actually go into ensuring that this would be an adequate solution for their 00:15:02.800 --> 00:15:07.440 users that's a completely separate story and 00:15:06.240 --> 00:15:14.079 maybe part of the reason that manufacturers won't allow functionality 00:15:10.160 --> 00:15:15.920 that they otherwise could but uh 00:15:14.079 --> 00:15:20.399 i'll let you guys be the judge of exactly why it is that this is locked 00:15:18.639 --> 00:15:23.120 out you guys can leave a comment down below you know what else you can do down 00:15:22.000 --> 00:15:28.720 below check out our sponsor freshbooks is the super simple to use 00:15:26.959 --> 00:15:33.199 small business accounting solution for freelancers and the self-employed it's a 00:15:31.279 --> 00:15:37.120 simple way to be more productive more organized and to get paid faster you can 00:15:35.760 --> 00:15:40.959 create and send professional looking invoices in less than 30 seconds you can 00:15:39.360 --> 00:15:44.639 set up online payments with just a couple of clicks to get paid up to four 00:15:42.639 --> 00:15:48.079 days faster you can see when your client has seen your invoice to put an end to 00:15:46.320 --> 00:15:52.959 the guests and games and if you have any trouble you can reach out to freshbooks's award-winning customer 00:15:51.120 --> 00:15:59.040 support where you won't get any phone trees or escalations nothing like that 00:15:55.759 --> 00:16:01.040 just answers so visit freshbooks.com 00:15:59.040 --> 00:16:05.199 tech tips and enter Linus tech tips in the how did you hear about us section to 00:16:02.560 --> 00:16:08.639 get your 30-day free trial so thanks for watching guys if you disliked this video 00:16:07.040 --> 00:16:12.000 you can hit that button but if you liked it hit like get subscribed or maybe 00:16:10.720 --> 00:16:16.959 consider checking out where to buy the stuff we featured at the link in the video description also down there is our 00:16:15.600 --> 00:16:23.839 merch store which has cool shirts like this one and not yours and our community forum 00:16:20.399 --> 00:16:23.839 which you should totally join