Recent content by Indra4523

I have unsupportedcl 16 gskill trident z running 3200mhz on 1600x and m b350 mortar mobo. Most of the cl 16 3200 are not samsung b die. So you may have some trouble with it. But like I said I finally got mine running with alot of tweaking also the latest bios updates helle alot with compatibility

Hey I just experienced a dip in mhz on all cores from 3899 to 3725 for a fraction of a second I looked at the prime 95 and this happen just as one test passed and another began around the 2 hour mark. Nothing else fluctuated like vcore or temps or cpu usage. Is that still a sign of instability...

Yeah I was going to try 4ghz my temps are pretty good I think most of the time during load they are at 60c with an occasional spike to 64 is the max. I'm pretty impressed with cryorig. I think I am going to try and dial in my 3.9 ghz oc so I know my setting and then go for 4.0.

Hey seanie sorry I have not replied back until now. I have been busy. I have got my nb set to 1.1 now with vcore at 1.3625 and a frequency of 3900. Llc of mode 1 I have done a hand full of p95 passes of 60 to 90 min. I'm in the process of doing a 2 hour run. At least now that I have the time. So...

Is msi llc mode 1 highest setting or minimum setting.

Hey seanie thanks for the reply. My temps were all good I never went above 65 c actual temp. As far as any nb tweaks I haven't tried any yet. When I get home I'll try those setting and let you know. I'm also on bios 1.4 it's the latest one as of 2 weeks ago. Also I did bump up my v core to 1.385...

I agree I also have the msi b350m mortar just clocked to 3.950 2 hours stable prime 95 at 1.375 v. I say if your the slightest bit interested in overclocking get a b350 and have fun. Just go slow. Seanie. I have not been able to get my ram to 3200mhz.

Hello all 1600x B350m mortar 3200mhz ram set to 2933 I can't get it to boot to 32 Cryorig h5 ultimate tower cooler I'm very happy with the system. I clocked it stable at 3.85ghz with 1.275 v prime 95 for 90 min. When I pushed to 3.9 it required quite a big bump in vcore 1.33. It ran stable...