← sources

Home server keeps crashing from one flipped RAM bit. Can I trust a memmap workaround, or do I need new RAM?

source: reddit (reddit:homelab)published 2026-11-09 06:15ingested 2026-11-10 02:41

retained text

I bought a used PC a while back and it's now my little home server (Minecraft + TeamSpeak on Ubuntu, kernel 7.0). It's been crashing on and off since day one, always the same way, and after about two weeks of digging I'm pretty sure it's one flaky RAM bit. I can't get to the box physically right now, so for now I'm keeping it alive in software, and I'd like to know if that's sane or if I'm just delaying the inevitable.

Hardware: MSI B365M PRO-VDH (BIOS 1.10 from 2019), i5-9600K so no ECC. 4x8GB from two different kits, two per channel: DIMM0 on both channels is Crucial Ballistix BLS8G4D240FSB (dual rank), DIMM1 is Corsair Vengeance CMK16GX4M2A2400C14 (single rank). No XMP, 2133 at 1.2V.

Symptoms: the java server segfaulted 5 or 6 times in two weeks in unrelated places (JIT threads, chunk loading etc) and the kernel panicked once. In every crash dump the bad pointer was the right value with bit 45 flipped, e.g. 0x0000774a... read as 0x0000574a..., and the panic was a timer callback jumping to 0xffffdfffbbc39890 instead of 0xffffffffbbc39890. 5 min of memtester found nothing, and my own light-load tester found nothing in ~1.8 TB of reads. stressapptest (`-M 20000 -s 21600 -W -m 6`, ~26 GB/s) got 8 miscompares in 6 hours, all bit 45, both directions (3 1->0, 5 0->1), re-read also wrong. Decoding the addresses with the memory controller's channel hash (MCHBAR 0x5024 = 0x120c3200) puts all 8 on channel B, all inside a ~470 MB window (0x41be3b900 to 0x4386fb500) out of the 20 GB tested, all at offset 0 of the cache line. Rank interleave is on (MAD_INTRA = 0x110) so I can't map it to a specific stick from software.

What I've set up so far:

- offlined 0x418000000-0x43fffffff (640 MB, the bad window plus margin) with memory hotplug, and added `memmap=640M$0x418000000` for next boot. Rerunning the 6h stressapptest tonight to see if it's clean with that hole.
- kernel.panic=10, panic_on_oops=1, soft/hard lockup -> panic, so a kernel crash at least reboots the box
- the minecraft start script restarts the server when the JVM dies
- tried both hardware watchdogs, iTCO and the NCT6797D Super I/O one. neither actually resets the board. BIOS locks TCO_EN to its SMI handler and the Super I/O WDT output doesn't seem to be wired to reset, which is annoying since a hard hang would just sit there.

Questions for people who run stuff 24/7:

1. would you trust a memmap hole like this long term on a box you don't babysit, or do these faults tend to spread?
2. any other way to get a reliable hardware reset on a consumer board like this when both onboard watchdogs are useless? (external USB watchdog, smart plug, something else?)
3. when I do get physical access, would you bother reseating/rearranging (each kit on its own channel, cleaning contacts, a bit more DRAM voltage, dropping to 1866) or just buy a matched 2x16 kit and be done with it? I'd like to keep 32 GB.

Also posted the more RAM-tuning side of this on r/overclocking if anyone wants the extra detail: https://www.reddit.com/r/overclocking/comments/1xrh590/used_pc_i_bought_keeps_crashing_traced_it_to_one/

thanks


---

**UPDATE (day 2): what I tried and what happened**

1. Cleaned the contacts and rearranged so each channel has one matched kit:
   - Before: A1 Crucial, A2 Corsair, B1 Crucial, B2 Corsair (mixed kits on both channels)
   - After: A1+A2 = Crucial Ballistix BLS8G4D240FSB x2, B1+B2 = Corsair CMK16GX4M2A2400C14 x2
   - The Crucial that used to sit in B1 moved to channel A.

   Result: stressapptest (28.5 GB, -W) found an error after 23 min. Still channel B, still bit 45 (this time 0->1), still the first 8 bytes of a cache line, and the physical address (0x43a4878c0) fell in the SAME ~600 MB range as all the earlier errors. So the moved Crucial is clean, and cleaning didn't help.

2. BIOS: DRAM voltage 1.20 V -> 1.35 V (sensor reads ~1.344 V), Memory Fast Boot disabled (forces full retraining), still JEDEC 2133, XMP off.

   Result: error after 2.5 min. Channel B, bit 45 (1->0), same physical range (0x41af3d480). Voltage made no difference.

Full error list so far (16 events):

- 6 crashes in production (4 JVM SIGSEGVs, 1 JVM crash with a probable bit 37 flip, 1 kernel panic). Every one I could decode was bit 45 of a 64-bit word.
- 10 stressapptest miscompares: all bit 45, all channel B, both directions (1->0 and 0->1), all at offset 0 of a 64-byte cache line, all within physical 0x41a000000-0x43b000000. The reread always returned the same wrong value, so the bad value was really stored in RAM.
- A light-load tester over 22 GiB (1.8 TB verified) found nothing. It only shows under heavy memory traffic.

Conclusion so far: it's not contacts, not mixed kits, not voltage. The fault stays at a fixed physical address range on channel B no matter how the sticks are arranged, and it always hits the same data line (DQ45). My guess is a weak chip or cells on the Corsair in B2 (the only stick that never moved) or that slot.

Current workaround: I took that range plus a margin out of use with the kernel parameter `memmap=896M$0x410000000` (and offlined the memory blocks at runtime). That's ~2.8% of RAM. The server is back up. On the software side the JVM also runs with a pointer layout that avoids bit 45, auto-restarts after a crash, and the kernel reboots on panic.

document fetched 2026-11-10 00:35 · canonical https://reddit.com/r/homelab/comments/1xrk84b/home_server_keeps_crashing_from_one_flipped_ram