“Do it again.”
“But I did it already.”
“But do it again.”
“But I did it already!”
“Please just do it again.”
“OK, but I already… Well, would you look at that!”
Well high clocked DDR5 ram can be unstable, re seating may have fixed that.
OHHH NOOOOO!!!
Just restarted again.
I tried to wait to post until it was stable. At my wits end here.
fred666, it’s rated 5600, of course I know technically XMP is overclocking, and not 100% guaranteed, but it’s supposed to work. Not overclocking above 5600.
2 Likes
I have XMP ram also. The ram is 3200 Mhz. That is what it runs at. Just because it’s XMP doesn’t mean it’s over clocked if it’s running at the speed the ram is. I would have to set the ram speed higher in order for it to be overclocked. XMP just means it is capable. Most motherboards have settings to overclock and also test it’s capabilities and best settings.
That’s why I said “technically.” Even Intel calls XMP overclocking. Just to reach the “rated speed” of the RAM, if the CPU supports that frequency in the IMC.
Different than trying to run higher than rated speeds. But I’ve read XMP can be “finicky” on some systems even at “rated speeds.”
That’s all I meant by “it’s supposed to work.” That maybe my system is finicky. I’m going to try turning off XMP for a while and see what happens.
Funny thing, I don’t find a way to “disable XMP” in ASRock UEFI, just Auto and XMP 3.0 Profile.
But I went into advanced settings and bumped the speed down from 5600 to 5400. It’s been running 24/7 over a week, being used daily, with no restarts.
“About a week” is the longest it’s run before with no restarts, so I’ll continue leaving it on another week or two. But this is promising. (Yeah, I’ve said that before.) I can live with 5400 if it means I can stop diagnosing whether it’s RAM/IMP/Motherboard and have no additional expense.
So the ram speed is the culprit, that is why i told you that ddr5 ram can be unstable.
For high speed DDR5 you need high quality ram modules and they need to be well supported by the motherboard manufacturer, and better tested by that manufacturer to work.
Some motherboards are picky for ram modules, others will work with just about anything so check the manufacturers website for tested modules to be sure
With DDR4 this less of an issue as the speeds are a lot lower
I had a similar issue when testing different RAMs in the past, some sets just don’t work with the motherboard and can cause crashes. The motherboard manual will usually have a qualified vendor list of compatible RAM and this is how I stopped my crashes under it’s product page on the website. Even then other strange RAM issues can come from using two dual packs of the same RAM rather than a 4 pack of the same RAM as multipacks are confirmed the ram modules work with each other and not always guaranteed when buying multiple smaller packs.
I wish I could say this is solved, but it’s not. I reduced RAM speed every time it restarted itself, all the way down to 4800, and it still restarted. Looking into whether voltage or cas latency changes can help.
I am missing evidence about the restarts. journal, coredumps, etc. There must be something. If there is nothing I would bet that it is a hardware issue.
This almost leads me to believe it’s the motherboard. 
what is de brand and type of your motherboard and ram memory?
Did you use a brand and type of memory that is on the QVL of the motherboard manufacturer?
The fact that your problem is getting “better/ less frequent” indicates a possibly incompatibility between motherboard and ram memory
What is the output of inxi -Ga Do you have nvidia drivers installed even though it’s running on the igpu?
I hope this will be my last post in this thread, but wanted to wrap it up.
TL;DR it was the motherboard.
After my last post, I worked with GSkill on RAM replacement under warranty, took about a month to get it, restarts persisted with the new RAM.
Bought a completely different brand/model of motherboard, installed it, and the machine has been running 24/7 for two weeks without restarting itself.
That should be long enough. If in the future it reboots again, I’ll probably give up on this build.
1 Like
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.