this post was submitted on 21 Jan 2025
10 points (100.0% liked)

Linux Mint

1875 readers
19 users here now

Linux Mint is a free Linux-based operating system designed for use on desktop and laptop computers.

Want to see the latest news from the blog? Set the Firefox homepage to:

linuxmint.com/start/

where is a current or past release. Here's an example using release 21.1 'Vera':

https://linuxmint.com/start/vera/

founded 3 years ago
MODERATORS
 

I have been trying to get mint to install correctly on my system for the last couple days. After much messing around, trying different drives (new flash drive, new nvme) and stuff, I finally ran memtest and I'm getting lots of errors on both sticks, tested individually. It's 2x16 ddr4 3600; I lowered it to 1600 and still get lots of errors, ordered a new pair.

Here's my question - I have win10 on a separate drive. It boots fine and doesn't seem to have an issue with the ram at all. Is Linux more sensitive to memory problems?

you are viewing a single comment's thread
view the rest of the comments
[–] Shadow 2 points 1 week ago* (last edited 1 week ago) (1 children)

I wouldn't expect so. I'd expect bsods and app crashes in Windows.

Are you overclocked? Have you done a bios upgrade and reset it to defaults?

[–] [email protected] 1 points 1 week ago* (last edited 1 week ago) (1 children)

Right, that's what I would expect as well. Bios is updated to current and default reset. Memtest failures were after that - downloaded the full current v11 package from memtest86

Edit and no OC. 5800X, Asus b550m-a (WiFi) board. G.skill ram.

[–] Shadow 2 points 1 week ago (1 children)

And memtest was booted off usb, not run in Linux or anything weird?

That's really odd. I'd definitely expect windows to crash, and it seems odd that it wouldn't if both your sticks are failing when running on their own.

I wonder if you actually have a mobo / CPU issue that windows can handle. Getting new ram seems like the logical next step though.

[–] [email protected] 2 points 4 days ago

New memory fixed it.