Endeavouros freezes sometimes and leads to force restart

Perhaps check it. I recommend using the RAM’s built-in profile in the BIOS for now. It should be something like:

• EXPO Profile #0: DDR5-6000 CL36-38-38 @1.35V

1 Like

Ya that does look low. I wouldn’t be using SPD but rather XMP profile at 1.35 Volts.

EXPO is just AMD’s version of Intel’s XMP.

I didn’t know that. :wink:

Edit: I guess this is because it’s an AM5 board which i haven’t had myself.

1 Like

Yeah I was a late comer to that detail myself at one point :sweat_smile:

For a long time, I believed memory profiles were universally called “XMP”. It was only when I stumbled across “EXPO” I discovered it was an Intel thing.

1 Like

I just checked the bios and it seems that’s the one that’s currently selected:

Also, looking in the H/W monitor tab, the voltage is showing around 1.35V:

1 Like

So to confirm, it was found like that, no change was made I take it?

It was worth checking in any case. Have you approached the UEFI/BIOS update @ricklinux suggested?

Yes, no change was made, so I’m not sure why is the inxi command showing 1.1V :thinking:

Regarding the BIOS update, I was also considering that, but I wanted to leave it as a last resort since I’ve never done it before and I’m afraid of bricking my machine.

Any other thing we could explore before trying that?

I think it’s ok. inxi can’t always pull precise details, particularly on memory frequency, and voltage it would seem (run without sudo and you’ll get a different result again). So it was worth double checking in the BIOS itself.

With respect to other things you could try before a BIOS update:

  • You could create a new user account, and from a clean slate, try to re-produce the same issue. If you can’t reproduce the issue, it might be a specific configuration or corruption issue in your regular user account.
  • You could also try recreating the issue in the Live ISO environment. If you can reproduce it there, I’d say that’s telling of a hardware issue. I’d be hesitant to place much weight on not being able to reproduce the issue there though, as so many variables have changed.
  • The EndeavourOS live ISO has a memory testing utility. It’s an option from the boot menu. You could try running that for a day or so.
  • Lastly, what brand/model power supply (PSU) do you have? It’s one detail inxi can’t provide, but can sometimes point to a power issue. Your specs so far haven’t given me all that much reason to be concerned about this though.

With respect to the UEFI/BIOS update, I’d suggest it’s still worth considering in any case. Those updates are important for the stability and security of your system. Understandably, caution and care needs to be taken when performing an update. You must allow it to fully complete, or you do risk bricking the system.

Thanks for the suggestions, I’ll try them and let you guys know.

Regarding your question about the PSU, this is the one I have:

1 Like

That PSU is ranked as “Tier A • High-end”, according to the PSU Tier List, and your power draw still sits within the safe range (approx 620W). So I wouldn’t consider that a likely cause.

1 Like

You are overclocking the ram speed, try to use stock speeds for the modules used.
DDR5 memory can get unstable on higher speeds, especially if you overclock.

Sure, let me try that as well

Most RAM is technically overclocked relative to the JEDEC standard spec (DDR5-4800).

The Kingston KF560C36BBE-16 @mdan is using is officially rated for DDR5-6000, so it’s not overclocked beyond the RAM’s official capability.

That said, there’s no harm in trying the default JEDEC profile, or the lower 5600MHz profile. I’d be careful stepping outside of those predefined profiles though.

1 Like

As suggested, it seems that updating the bios to the latest version (3.20) did it :smiley:

To test it I left the PC up for over 48 hours and I haven’t had the freezing issue so far; before, I couldn’t leave it idle for more than a few hours, otherwise, I would come back to an unresponsive system.

Thanks everyone for all the help!

1 Like

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.