WEBVTT

00:00:07.560 --> 00:00:15.160
after I got so many great messages on YouTube about the RAM testing video I

00:00:12.920 --> 00:00:18.240
uploaded yesterday see I've got four sticks going here

00:00:18.560 --> 00:00:24.160
now I thought I'd do an update video just to address a lot of the questions

00:00:22.439 --> 00:00:28.679
and concerns and comments that you guys had so as you can see I did finish my

00:00:26.439 --> 00:00:31.920
24-hour test with the three modules I had before which were running in trip

00:00:30.240 --> 00:00:37.200
Channel just want to clarify this someone was a little bit confused about

00:00:34.680 --> 00:00:41.840
uh how you can run triple channel in a quad Channel motherboard so to clarify

00:00:39.800 --> 00:00:45.640
guys any dual Channel motherboard is capable of running single Channel any

00:00:43.840 --> 00:00:50.079
triple Channel motherboard is capable of running dual Channel or single Channel

00:00:48.199 --> 00:00:55.480
and any quad Channel motherboard is capable of running single dual or triple

00:00:52.960 --> 00:00:59.480
or quad channel so the way that you do that is you populate the dim slots in

00:00:57.399 --> 00:01:01.719
the correct order so here you can see we've got

00:01:00.440 --> 00:01:07.600
A1 and B1 right there so if you wanted to run a

00:01:04.199 --> 00:01:09.159
dual Channel you'd go A1 B1 then if you

00:01:07.600 --> 00:01:13.479
wanted to run in triple Channel you'd populate C1 and if you wanted to run in

00:01:11.080 --> 00:01:16.520
Quad Channel you'd populate D1 so there you go that's how you do it right now

00:01:15.159 --> 00:01:20.280
it's running in Quad Channel because I do have four memory sticks in here I

00:01:18.560 --> 00:01:25.079
also had a lot of people commenting on the fact that I wasn't using m test 86

00:01:22.720 --> 00:01:29.520
mest 86 is awesome great memory diagnostic utility it runs before the

00:01:28.159 --> 00:01:35.200
operating system which is really really good it tests all of the memory and it throws up big red errors if it detects

00:01:33.280 --> 00:01:39.799
anything the problem is that the issue I was having was not being detected by

00:01:37.040 --> 00:01:45.159
mest 86 so the reason I was stubbornly using prime 95 is because I don't I'm a

00:01:42.880 --> 00:01:49.600
little bit old school and I'm not using uh Linc s linac or any of the other sort

00:01:47.960 --> 00:01:53.600
of Intel burn chest these are all tools that I haven't really used that much

00:01:51.560 --> 00:01:58.399
plus I knew that I could consistently reproduce the errors on these sticks

00:01:56.360 --> 00:02:01.960
with a prime 95 test after a certain amount of time this is just a test bench

00:02:00.240 --> 00:02:07.399
this is not my main machine so I'm not that concerned with it not being running

00:02:04.360 --> 00:02:10.000
at any given moment so the fact that

00:02:07.399 --> 00:02:14.160
mest 86 wasn't working for me is what prompted me to use prime 95 if mem test

00:02:12.640 --> 00:02:18.560
Works to detect the error that you're getting then that's great however there

00:02:16.120 --> 00:02:23.959
are even times Prime 95 detects nothing m test 86 comes up with errors in like 5

00:02:21.040 --> 00:02:27.599
seconds so you can never really predict which tool is going to be the one that

00:02:25.440 --> 00:02:31.200
is going to find the problem with what you're doing although people in the

00:02:28.959 --> 00:02:36.319
comments are right generally speaking mest 86 is the first one to go for they

00:02:33.800 --> 00:02:40.480
have all kinds of awesome ways to run it so you can just burn the iso to a CD

00:02:38.800 --> 00:02:45.159
which is what I usually do just cuz I'm lazy um or they actually have see I just

00:02:43.720 --> 00:02:49.599
didn't want to empty a USB drive they have a USB drive Creator so you just

00:02:46.879 --> 00:02:55.000
throw a blank USB drive in and it will go ahead and fix all that up for you so

00:02:52.879 --> 00:02:58.680
uh right what other people asked that was really really really good yes this

00:02:56.760 --> 00:03:03.720
is a really good one so people a lot of people asked how did you ru rule out the

00:03:00.280 --> 00:03:06.239
motherboard the CPU the power supply all

00:03:03.720 --> 00:03:11.040
that stuff so this is a very important part of any sort of troubleshooting

00:03:08.760 --> 00:03:15.680
scenario is you got to make sure am I actually isolating the right component

00:03:13.239 --> 00:03:23.200
so I knew it was the RAM because I'd had this motherboard with this CPU with this

00:03:18.799 --> 00:03:27.280
power supply running with this Kingston

00:03:23.200 --> 00:03:31.760
hyperx memory at these speeds

00:03:27.280 --> 00:03:33.640
so600 uh C9 ont command rate all of that

00:03:31.760 --> 00:03:38.000
good stuff so that's how I ruled out the motherboard that's how I ruled out the

00:03:35.319 --> 00:03:42.360
CPU and the power supply you got to rule out things like heat I'm running on an

00:03:39.599 --> 00:03:47.680
open test platform with air flow directly over the fan or the RAM itself

00:03:45.480 --> 00:03:51.519
so we can pretty much rule out heat how do you rule out your RAM settings well

00:03:49.400 --> 00:03:56.840
because this memory was running at these settings in the past so that's how I

00:03:54.000 --> 00:04:00.480
know that it should be fine assuming nothing's gone wrong with it in the

00:03:58.319 --> 00:04:06.200
meantime so these are my two dead this one errors in Prime 95 this one

00:04:03.079 --> 00:04:08.360
errors in a multi- channel configuration

00:04:06.200 --> 00:04:12.200
eventually aha that's another one I had a lot of people commenting lonus you

00:04:10.439 --> 00:04:16.959
idiot why didn't you just run one stick at a time guys if you'd watch the video

00:04:14.480 --> 00:04:22.400
you'd know I had already run all of the sticks individually this stick the one

00:04:20.000 --> 00:04:26.840
right there on the left passes on its own but as soon as you put it in a

00:04:24.520 --> 00:04:31.240
multi- channel configuration it the entire thing fails whereas all of these

00:04:29.360 --> 00:04:36.320
sticks all together in a multi Channel config are not failing so that's how I

00:04:34.320 --> 00:04:41.639
know that this guy right here with the duct tape is dead that one on the left

00:04:39.000 --> 00:04:45.960
is borderline which is not good enough it's for all intents and purposes dead

00:04:44.039 --> 00:04:50.280
but it's much harder to catch compared to one that's just outright dead doesn't

00:04:47.759 --> 00:04:54.960
post or causes blue screens right away so I think that pretty much covers

00:04:53.120 --> 00:05:00.479
it thank you for checking out this sort of updated video on diagnosing memory I

00:04:58.759 --> 00:05:03.360
hope this clar clears up some of the questions you guys had don't forget to

00:05:02.120 --> 00:05:07.720
subscribe to lineus Tech tips for unboxings reviews and other computer

00:05:07.960 --> 00:05:15.240
videos I love this camera using the fs700 today I was using the XA 10 last

00:05:13.080 --> 00:05:19.160
time the mic's terrible though I don't have my lapel mic I'm using the shotgun

00:05:17.280 --> 00:05:24.240
mic that's on the top so before you complain about the audio just I know

00:05:21.240 --> 00:05:26.800
it's the wrong mic it's bad oh well

00:05:24.240 --> 00:05:26.800
you'll get over

00:05:27.319 --> 00:05:34.280
it I'm sorry one more thing in spite of my warnings to the contrary I did have a

00:05:32.479 --> 00:05:38.600
couple people saying oh my R is stable enough it worked in games and just cuz

00:05:36.440 --> 00:05:41.960
it fails in Prime 95 after an hour doesn't mean it's not yes it does it

00:05:40.000 --> 00:05:45.160
means it's not stable it isn't stable it's not good enough uh if it ever

00:05:43.919 --> 00:05:50.520
crashes when your computer's doing something critical it can completely corrupt your entire OS and make it non-

00:05:48.360 --> 00:05:57.479
bootable the odds of that happening I don't know you roll that die uh last

00:05:53.919 --> 00:05:59.240
thing is it has to be stable in every in

00:05:57.479 --> 00:06:03.560
every stress test it has to be stable in Prime stable in m test stable in Linux a

00:06:01.440 --> 00:06:07.280
stable system is stable and doesn't make mistakes when I'm done this Prime 95

00:06:05.680 --> 00:06:10.759
test just for good measure because remember that fourth stick has been in

00:06:08.840 --> 00:06:15.400
my wife's machine so I for all I know it's dead too so I'm going to run the

00:06:12.599 --> 00:06:19.280
whole thing through m test 86 again once I'm done here in order to reassure

00:06:17.599 --> 00:06:23.479
myself that all of this is working completely 100% before I redeploy it in

00:06:21.840 --> 00:06:27.759
a system and another thing I forgot I had

00:06:25.960 --> 00:06:30.360
a lot of people saying lius you have so much memory why don't you just throw it

00:06:28.960 --> 00:06:34.880
away and buy new memory memory is so cheap what are you crazy throw away

00:06:32.199 --> 00:06:39.840
Hardware jeez way to be money bags no you don't

00:06:38.280 --> 00:06:46.039
throw away Hardware you test it you see if it works

00:06:42.360 --> 00:06:46.039
if it works you keep it if it doesn't

00:06:48.560 --> 00:06:53.360
work then you throw it away