Anyone has a MSI X370? Having bizarre issues.

solarasreign

Reputable
Dec 2, 2017
134
2
4,715
So I got this MB last year when Ryzen first came out, MSI was one of the early companies to have MBs with AM4, and I loved it since. I had zero issues with RAM settings, having the latest BIOS cleared everything out.

It wasn't until recently that I checked into my BIOs and saw that my CPU wasn't overclocked to 3.9 (from a based 3.6) and my RAM was a miserable 2133 when it's actually 3200. So I fixed it again and booted back up. Only, my changes weren't registering. Needless to say, I checked to see if I just needed to update the BIOS, apparently I did, so I did just that, and everything went to Hell after that.

My PC failed to post, not even after tweaking with my OC, and reverted back to the old BIOs, it got to a point where even the OS was even corrupted. I was in 'repair boot hell' and the only way out was to reinstalled the OS again. The more I tried to fix this, the bigger the mess became that I was just fucking myself over. So I'm back on a clean slate, fresh OS installed, I was able to OC to my usual settings, and everything was fine for hrs, until I ran cinebench. It did OpenCL fine, but froze on the CPU run. I forced shut it down and tried again, same thing.

I reverted to 'auto' on my OC profile volts, and it seem okay and it just crash, I didn't even logged in until I was blue screened again. I reverted back to my based 3.6, and left the memory at 3200mhz, since it is the based, no OC there, and it worked again. I ran Cinebench and both test went fine. No crash.

Is this MB failing? Are the updated BIOs to blame?

Because it feels like it can no longer hold a proper OC to me, and each time I think about testing my system, it crashes. I wonder if anyone is having this issue with their MSI X370s and can provide feedback.

Currently rocking an EVGA 650w (I have more than 200w of headroom so I know this isn't it) if anyone assumes it's the PSU.
 
Solution
Did you clear CMOS?

Turn off, disconnect from power line and press power button a few seconds to discharge capacitors. Remove CMOS battery and then short CMOS reset pins together for 15-30 seconds. Wait like 30 min's (good time to make a cup of coffee and enjoy watching the cat at play), short the pins again for good measure and then reassemble.

Check it out.

Oh yeah...also...it's usually better to not crank up the memory to 3200 just because the memory has been rated for it by the mfr. Start slowly, increasing it to 2400, 2666, 2933, 3000, 3200. That also means you don't use XMP: you'll change memory multiplier and punch in the timings and DRAM voltage manually in BIOS.

Always remember the limit for overclocking memory is in...
Did you clear CMOS?

Turn off, disconnect from power line and press power button a few seconds to discharge capacitors. Remove CMOS battery and then short CMOS reset pins together for 15-30 seconds. Wait like 30 min's (good time to make a cup of coffee and enjoy watching the cat at play), short the pins again for good measure and then reassemble.

Check it out.

Oh yeah...also...it's usually better to not crank up the memory to 3200 just because the memory has been rated for it by the mfr. Start slowly, increasing it to 2400, 2666, 2933, 3000, 3200. That also means you don't use XMP: you'll change memory multiplier and punch in the timings and DRAM voltage manually in BIOS.

Always remember the limit for overclocking memory is in the CPU where the memory controller is located, not the DIMM's
 
Solution

solarasreign

Reputable
Dec 2, 2017
134
2
4,715

Jesus, I didn't think about that. What does that do exactly. I mean, would I have to update the BIOs all over again? Does it hurt the OS or any of my drives? Or is it a simple reset of the MB?
 

solarasreign

Reputable
Dec 2, 2017
134
2
4,715

That's bizarre. I never had a problem with that before when I first build it. It read the 3200mhz fine. It's the stock settings for it, I can understand that if I wanted to increase it to start slowly, but just to get accurate reading? :/

Also the MB has the trimmings accurate on their drop menu, so manual input isn't necessary.
 


Residual settings left behind in CMOS memory may not work correctly in later BIOS revs, resulting in unpredictable behaviours. It's always good practice to clear CMOS when you update BIOS, just in case.

I know there are 'memory try-it' settings as well as XMP and XMP2 settings, but don't use those. They're just 'best guesses' to get started and assume all sorts of things about CPU and memory. I'd suggest using the timings and voltages that are listed on your memory kit package. THEN: start slowly ramping up the multiplier to find what the limit your CPU's memory controller can handle.
 

solarasreign

Reputable
Dec 2, 2017
134
2
4,715

I'm confused. You want me to clear my CMOS AFTER updating it? Isn't clearing it reset everything in it's configuration? Or will the latest BIOs remain? Cause right now it has the latest BIOs installed on it. Are you saying that it's okay to do it now? Because my PC works now, it's not a brick or in a startup Hell loop, I reinstalled the OS all over again yesterday. I just can't think about OCing without it crashing that my parts are on stock settings.

Good tip on the RAM, I'll take it into consideration.

 


All 'clearing cmos' does is return all settings and customizations to a default values. It does not change the BIOS revision, only 'burning' an update can do that.

Call me crazy, paranoid or a liberal meathead if you want: when I update BIOS i will do that clear CMOS process both before and AFTER updating it. I want to make sure there are no residual settings in the CMOS memory that could affect things in random ways.

Especially if you've never done it after multiple BIOS updates, that's often a fix if you're experiencing random problems. It may not be if you know it's because of some tippy overclock settings, but it's a safe way to be sure.

 

solarasreign

Reputable
Dec 2, 2017
134
2
4,715

I wouldn't say paranoid. You're just making sure xD But thanks for the suggestions. I'll definitely try this later today.