Jump to content

try without oc, if there are errors without then bad ram, if there are errors with then up the IMC voltage by a TINY bit (lets say, 1v to 1.05v) 

Ryzen 5 3600 stock | 2x16GB C13 3200MHz (AFR) | GTX 760 (Sold the VII)| ASUS Prime X570-P | 6TB WD Gold (128MB Cache, 2017)

Samsung 850 EVO 240 GB 

138 is a good number.

 

Link to comment
https://linustechtips.com/topic/812391-bad-memory-or-bad-oc/#findComment-10195550
Share on other sites

Link to post
Share on other sites

Just now, Lord Nicoll said:

Generally team group have pretty great memory, so it's less likely  to be bad RAM, however anything can happen in shipping. Try test it without the OC and that'll tell you.

 

Just now, themctipers said:

try without oc, if there are errors without then bad ram, if there are errors with then up the IMC voltage by a TINY bit (lets say, 1v to 1.05v) 

see  you guys in 2 hours then

Link to comment
https://linustechtips.com/topic/812391-bad-memory-or-bad-oc/#findComment-10195577
Share on other sites

Link to post
Share on other sites

1 hour ago, Lord Nicoll said:

Generally team group have pretty great memory, so it's less likely  to be bad RAM, however anything can happen in shipping. Try test it without the OC and that'll tell you.

1 hour ago, themctipers said:

try without oc, if there are errors without then bad ram, if there are errors with then up the IMC voltage by a TINY bit (lets say, 1v to 1.05v) 

1 hour ago, xentropa said:

What frequency did you increase to?

 

Did you adjust the timings?

37 minutes ago, Brooksie359 said:

Might not want to run at 3200 mhz. Try it at normal frequency and see if it runs. Also did you update your bios?

so what should i leave to auto and leave to manual?

this prblem frm bad oc

Link to comment
https://linustechtips.com/topic/812391-bad-memory-or-bad-oc/#findComment-10195969
Share on other sites

Link to post
Share on other sites

Just now, Brooksie359 said:

Well usually I would test at stock settings and go from there. If it works at stock I would slowly increase the frequency on the memory until it doesn't want to work 

you got recommended program to check stability for ram except prime95 and memtest and win diag?

Link to comment
https://linustechtips.com/topic/812391-bad-memory-or-bad-oc/#findComment-10196033
Share on other sites

Link to post
Share on other sites

Just now, Necrodor21 said:

you got recommended program to check stability for ram except prime95 and memtest and win diag?

Cinebench. Usually if I can get through prime95 and Cinebench I won't see any issues or crashes in other programs. Also did you update the bios of your motherboard?

Link to comment
https://linustechtips.com/topic/812391-bad-memory-or-bad-oc/#findComment-10196045
Share on other sites

Link to post
Share on other sites

Just now, Brooksie359 said:

Cinebench. Usually if I can get through prime95 and Cinebench I won't see any issues or crashes in other programs. Also did you update the bios of your motherboard?

latest and sometime my cpu clock wont show the right timing (need to reset bios)

bad bios from asrock k4 x370

Link to comment
https://linustechtips.com/topic/812391-bad-memory-or-bad-oc/#findComment-10196047
Share on other sites

Link to post
Share on other sites

1 minute ago, Necrodor21 said:

latest and sometime my cpu clock wont show the right timing (need to reset bios)

bad bios from asrock k4 x370

Right timing or frequency? Because sometimes the cpu will put itself at stock settings if an overclock didn't work. What you usually have to do is set the frequency to stock and then to the frequency you want for it to actually register. 

Link to comment
https://linustechtips.com/topic/812391-bad-memory-or-bad-oc/#findComment-10196076
Share on other sites

Link to post
Share on other sites

Just now, Brooksie359 said:

Right timing or frequency? Because sometimes the cpu will put itself at stock settings if an overclock didn't work. What you usually have to do is set the frequency to stock and then to the frequency you want for it to actually register. 

actually i cant set multiplier on that mobo

thats the problem

Link to comment
https://linustechtips.com/topic/812391-bad-memory-or-bad-oc/#findComment-10196148
Share on other sites

Link to post
Share on other sites

29 minutes ago, Brooksie359 said:

ok so does it just have you type in the literal frequency? that's what mine does in which case I would set the frequency to 3000 then to whatever frequency overclock you decide to test. 

well in so many test my mobo cant sup 3200

my best clock is 12 12 12 29 at 2933

Link to comment
https://linustechtips.com/topic/812391-bad-memory-or-bad-oc/#findComment-10196440
Share on other sites

Link to post
Share on other sites

57 minutes ago, Necrodor21 said:

well in so many test my mobo cant sup 3200

my best clock is 12 12 12 29 at 2933

honestly the major performance increase is between 2133 and 3000 so you should be good. suck that you didnt get 3200 but still better than 2400 or 2633

Link to comment
https://linustechtips.com/topic/812391-bad-memory-or-bad-oc/#findComment-10196806
Share on other sites

Link to post
Share on other sites

The timings represent the clock cycles for an action

 

Column address strobe (CAS) is the time it takes to address a memory row and to when that electricity flows down to the column decoder.

 

So if CAS latency is 12 at 2400 mhz.  It takes twelve 2400mhz clock cycles to get data.  If you increase to 3200 mhz, you need more clock cycles.  16 will give the same performance.

 

This may be a reason dram oc never scaled so well.  You cant actually make the dram cells discharge their electricity (data) faster by increasing clock speeds.

Link to comment
https://linustechtips.com/topic/812391-bad-memory-or-bad-oc/#findComment-10197911
Share on other sites

Link to post
Share on other sites

2 hours ago, xentropa said:

The timings represent the clock cycles for an action

 

Column address strobe (CAS) is the time it takes to address a memory row and to when that electricity flows down to the column decoder.

 

So if CAS latency is 12 at 2400 mhz.  It takes twelve 2400mhz clock cycles to get data.  If you increase to 3200 mhz, you need more clock cycles.  16 will give the same performance.

 

This may be a reason dram oc never scaled so well.  You cant actually make the dram cells discharge their electricity (data) faster by increasing clock speeds.

yeah but with ryzen is all about increasing infinity fabric bandwidth anyways so it really doesn't matter.

Link to comment
https://linustechtips.com/topic/812391-bad-memory-or-bad-oc/#findComment-10198440
Share on other sites

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×