WEBVTT

00:00:00.160 --> 00:00:06.960
welcome to an episode of lonus tech tips where I share my frustrations with you a

00:00:04.040 --> 00:00:11.880
little bit I have as some of you know I have what I call the Linus Edition RAM

00:00:09.360 --> 00:00:14.639
this is some older ocz memory that was custom done for me you can see there

00:00:13.280 --> 00:00:18.240
isn't even a part number on it or anything like that you've probably never

00:00:16.440 --> 00:00:22.160
seen a black and blue color scheme like this with an XTC heat spreader it was

00:00:20.039 --> 00:00:28.199
really really cool really special uh so I had 24 gigs of it that's 6x4 gigs and

00:00:26.840 --> 00:00:32.520
uh it's like the coolest thing ever I'm super proud of it it's awesome all that

00:00:30.039 --> 00:00:35.320
whatever it's uh broken now so I was running into issues where the computer

00:00:34.079 --> 00:00:40.480
that was running it you can see I only have five of the sticks here one of the sticks is known good and it's in my

00:00:38.760 --> 00:00:43.399
wife's machine right now so she has 4 gigs of memory which I'd love to

00:00:42.079 --> 00:00:48.000
increase so that when I have to Video Edit on her machine it's uh got enough

00:00:46.079 --> 00:00:53.600
memory and all that good stuff so what happened was her machine started blue

00:00:49.360 --> 00:00:55.120
screening randomly and I was only using

00:00:53.600 --> 00:00:59.359
three of the sticks in her machine at the time and so I pulled out memory I

00:00:57.520 --> 00:01:03.039
swapped memory until I found one that that that wasn't causing problems

00:01:00.840 --> 00:01:07.840
anymore and now I am left with the challenge of finding you know it's like

00:01:05.720 --> 00:01:11.240
out of five sticks now I have to find not only the one that I know is dead so

00:01:10.159 --> 00:01:15.080
this is the one that seemed to be causing the problems with her machine so

00:01:13.400 --> 00:01:18.360
what I did was I confirmed this one was dead by using prime95 blend and I'll

00:01:17.000 --> 00:01:24.439
show you guys the settings I'm using later um this is why I hate overclocking

00:01:21.840 --> 00:01:28.759
memory CU memory issues are so hard to diagnose and uh so hard to narrow down

00:01:27.040 --> 00:01:32.399
to what's working or what's not or what's causing the issue unless plus

00:01:30.079 --> 00:01:37.000
your the rest of your system is 100% completely Rock Solid I wouldn't even

00:01:34.159 --> 00:01:42.159
begin to touch memory cuz it's much much more finicky so that one that one's dead

00:01:39.680 --> 00:01:46.320
cuz what happened was I took four sticks and I ran them in Quad channel on this

00:01:44.280 --> 00:01:52.640
motherboard I set it to the settings I know the memory works at so 1600 C9 1.65

00:01:49.680 --> 00:01:58.680
volts uh default timings other than that uh ont command rate and I got errors

00:01:55.520 --> 00:02:01.079
after about 8 hours so I did every stick

00:01:58.680 --> 00:02:04.560
one by one all five of these sticks in dim slot one ran them individually at

00:02:03.200 --> 00:02:09.319
the same settings remember guys it's less stressful for the memory to run in

00:02:07.159 --> 00:02:12.720
individual mode than it is in a multi Channel mode so this is the only one

00:02:11.120 --> 00:02:16.840
that actually failed it failed after about 10 hours of prime 95 blend which

00:02:15.360 --> 00:02:20.480
is very frustrating because it makes the whole process take a long time so then I

00:02:18.680 --> 00:02:25.400
went oh yeah okay great everything must be good now so all I have to do now is

00:02:22.879 --> 00:02:31.640
take the four remaining sticks and run them in Quad Channel and it'll pass so

00:02:29.120 --> 00:02:35.440
after about 10 hours it failed which means that at least one of the sticks in

00:02:33.720 --> 00:02:39.720
here is still bad even though it was able to run on its own it can't run in a

00:02:37.400 --> 00:02:46.480
multi- channel configuration so since then I have taken this one out and I

00:02:42.640 --> 00:02:49.000
tried to run these three and it failed

00:02:46.480 --> 00:02:53.239
then I took this one out and I put this one back in and tried to run these ones

00:02:50.480 --> 00:02:58.879
in triple Channel and as you guys can see like people ask me all the time how

00:02:56.280 --> 00:03:02.879
long should I run my configuration in prime or some other stress test before I

00:03:01.120 --> 00:03:06.400
know it's stable and then I come back to them I say 24 hours or 48 hours they're

00:03:04.840 --> 00:03:11.200
like oh I ran it for 3 hours and it didn't you know fail so it must be must

00:03:08.799 --> 00:03:16.080
be okay then right no no no it isn't because you see here torture test can

00:03:14.000 --> 00:03:21.400
encounter an error 7 hours and 54 minutes in no problem so the settings

00:03:19.120 --> 00:03:27.200
that I'm using here so if your system makes a mathematical error it is not

00:03:24.319 --> 00:03:30.680
stable now that error could cause any number of things to happen it could

00:03:28.519 --> 00:03:35.439
cause a game to crash it could cause a program to kind of lock up for a second

00:03:33.480 --> 00:03:39.920
it could cause your entire operating system to corrupt you don't know what an

00:03:37.200 --> 00:03:44.439
error will do until you have an error and it does something so that's why I do

00:03:42.400 --> 00:03:48.319
not tolerate any errors in my machines and people who are like yeah yeah I

00:03:45.760 --> 00:03:52.159
overclock my CPU to whatever and it's pretty stable it's game stable no no

00:03:50.159 --> 00:03:56.400
game stable is not stable stable is stable so to show you guys the settings

00:03:53.920 --> 00:04:00.680
I'm using I'm using the blend preset and then I'm going custom and then I'm

00:03:58.319 --> 00:04:05.280
adjusting the memory to you to something near to what so I'd go with something

00:04:02.799 --> 00:04:08.959
like that i' go you know let's use 112 gab if we're going to have 12 gigs

00:04:07.840 --> 00:04:14.599
of memory in there so what I'm going to do now that I know I'm hoping it's only

00:04:12.840 --> 00:04:17.880
one more stick that's dead because they used to run in these settings just fine

00:04:16.440 --> 00:04:22.320
so this one remember I know this one's dead this one's going on the wall with

00:04:19.680 --> 00:04:26.560
the other legendary stuff so what I'm going to do now is I'm going to shut the

00:04:23.520 --> 00:04:28.919
system down like it takes days to

00:04:26.560 --> 00:04:31.720
diagnose a dead memory stick especially with these multi Channel configurations

00:04:30.600 --> 00:04:38.120
we have now where you can have up to eight sticks of memory in a desktop machine I mean it's ridiculous so now

00:04:35.680 --> 00:04:42.280
I've tested this this and this and I've tested this this and this and I'm still

00:04:40.520 --> 00:04:45.320
getting errors so now what I'm going to do is I'm going to put this guy back in

00:04:44.039 --> 00:04:48.680
and I'm going to take out one of these guys and we're going to see how that how

00:04:47.320 --> 00:04:53.000
that goes for us it's always important when you're testing this kind of stuff like if I put them in all the wrong

00:04:51.560 --> 00:04:58.000
slots then they might all be running in single Channel mode so you want to populate the uh the dim slots in the

00:04:56.000 --> 00:05:03.919
right order so there's there you go see they're all they're all labeled there so

00:05:00.080 --> 00:05:06.840
I need to make sure I'm populating A1 B1

00:05:03.919 --> 00:05:09.560
and where's yeah there we go and C1 in order to get this working so the

00:05:08.039 --> 00:05:14.360
system's shut down just going to go ahead and ground myself on the power

00:05:11.919 --> 00:05:18.280
supply here turn the power supply off just because you never know when the

00:05:16.560 --> 00:05:21.840
system's going to you know go ahead and just turn itself on when you're in the

00:05:19.800 --> 00:05:27.120
middle of working on it because it happens let me tell you that was a scary

00:05:24.240 --> 00:05:30.720
one I just like I plugged in a uh I plugged in a PCI Express card and the

00:05:29.000 --> 00:05:36.600
system powered on before I'd even finished getting it into the slot I was

00:05:32.759 --> 00:05:38.919
like oh yay dead card dead board they

00:05:36.600 --> 00:05:44.120
didn't die they were okay actually okay so there you go so now I'm going to see

00:05:41.840 --> 00:05:48.120
if maybe my stick B is dead it's important to label stuff I mean I can I

00:05:45.800 --> 00:05:51.199
can remember but I you know especially when all the memory looks the same it's

00:05:49.479 --> 00:05:55.960
important to make sure you actually do label things so anyway there we go so

00:05:54.520 --> 00:06:01.800
then we're going to power it back up and it's going to need another oops I need to turn my power supply back on sorry

00:06:00.440 --> 00:06:04.680
power it back up and hopefully it doesn't take another 8 hours to find the

00:06:03.520 --> 00:06:11.000
error again but I've already been working on this for days and it's been very frustrating so there you go guys

00:06:08.599 --> 00:06:15.599
how to diagnose memory problems takes a while mest 86 is

00:06:13.520 --> 00:06:19.560
another one but it used to be I mean just like prime it used to be a lot

00:06:17.240 --> 00:06:24.360
faster back when it didn't have to go through you know 12 16 24 48 gigs of

00:06:22.479 --> 00:06:32.199
memory in order to find out if there was any kind of problem and

00:06:28.280 --> 00:06:33.319
uh yeah memory yay don't forget to

00:06:32.199 --> 00:06:38.080
subscribe flyless Tech hips for unboxings reviews and other computer videos and I hope this has been helpful

00:06:36.919 --> 00:06:42.720
remember guys if you're having a stability issue with your system the

00:06:40.360 --> 00:06:47.919
things to check memory make sure your memory is 100% stable power supply if

00:06:45.880 --> 00:06:51.479
memory isn't the problem it's probably your power supply and then you move on

00:06:49.520 --> 00:06:55.240
to your motherboard and then you move on to it's probably a software issue unless

00:06:53.800 --> 00:07:02.840
your you know your video card driver is crashing or something very specific and you can go okay yeah that's probably the

00:06:57.960 --> 00:07:02.840
video card thanks guys take care