this post was submitted on 09 Nov 2025
536 points (98.4% liked)

Technology

76670 readers
2718 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related news or articles.
  3. Be excellent to each other!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
  9. Check for duplicates before posting, duplicates may be removed
  10. Accounts 7 days and younger will have their posts automatically removed.

Approved Bots


founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] HugeNerd@lemmy.ca 3 points 1 day ago (1 children)

Yeah but it's a hardware issue that's beyond my caring to try and troubleshoot. Random blue screens, memtest86 shows an error always at the same address no matter which sodimms I put or swap them around. I guess it runs until software enters that address range and blam! I think it might be power supply related at the board level, not the power brick. I don't feel like changing capacitors at random, for all I know there might be voltage out of spec because a resistor value drifted.

[–] tryp@programming.dev 2 points 1 day ago

If the memory error is in a small address range and you are willing to get super nerdy, you can tell the linux kernel to avoid the bad addresses. Some discussion in https://unix.stackexchange.com/questions/740806/user-friendly-way-to-apply-badram-patterns