Upgraded Video card and lost 128GB of ECC RAM

I have already ordered and have sitting in front of me another 32 GB chip. When I upgraded my Video card from a AMD X570 to an AMD 6700XT (best I could get at the time) In order to eject the video card on an Asus WRX80 Sage I did not have the space My finger probably bent or pushed up the DIMM. I pushed the ram up and when I rebooted lost half my RAM. I have 256GB of Nemix 3200 ECC that worked 100% prior to the event. I assume the one I touched is now bad. I have not put it in yet. Advice before I start?

[theemahn@JackTheRipper ~]$ inxi -F
System:
Host: JackTheRipper Kernel: 6.1.9-arch1-1 arch: x86_64 bits: 64
Desktop: KDE Plasma v: 5.26.5 Distro: Ultimate Arch Linux
Machine:
Type: Desktop System: ASUS product: N/A v: N/A serial:
Mobo: ASUSTeK model: Pro WS WRX80E-SAGE SE WIFI v: Rev 1.xx
serial: UEFI: American Megatrends v: 1003
date: 02/18/2022
CPU:
Info: 32-core model: AMD Ryzen Threadripper PRO 5975WX s bits: 64
type: MT MCP cache: L2: 16 MiB
Speed (MHz): avg: 3422 min/max: 1800/7007 cores: 1: 1758 2: 3600 3: 3600
4: 3600 5: 1771 6: 3600 7: 3600 8: 3600 9: 3600 10: 1792 11: 3600 12: 3600
13: 3600 14: 3600 15: 3600 16: 3600 17: 3600 18: 3600 19: 3600 20: 3600
21: 3600 22: 3600 23: 1843 24: 3600 25: 3600 26: 3600 27: 3600 28: 3600
29: 3600 30: 3600 31: 3600 32: 3600 33: 3600 34: 3600 35: 3600 36: 3600
37: 3600 38: 3600 39: 3600 40: 3600 41: 3600 42: 1792 43: 3600 44: 3600
45: 3600 46: 3600 47: 3600 48: 3600 49: 2706 50: 3600 51: 3600 52: 3600
53: 1811 54: 3600 55: 3600 56: 3600 57: 3936 58: 3600 59: 3600 60: 3600
61: 3600 62: 3600 63: 3600 64: 3600
Graphics:
Device-1: AMD Navi 22 [Radeon RX 6700/6700 XT/6750 XT / 6800M]
driver: amdgpu v: kernel
Display: x11 server: X.Org v: 21.1.6 with: Xwayland v: 22.1.7 driver: X:
loaded: amdgpu unloaded: fbdev,modesetting,radeon,vesa dri: radeonsi
gpu: amdgpu resolution: 1: 1920x1080~60Hz 2: 1920x1080~60Hz
API: OpenGL v: 4.6 Mesa 22.3.4 renderer: AMD Radeon RX 6700 XT (navi22
LLVM 15.0.7 DRM 3.49 6.1.9-arch1-1)
Audio:
Device-1: AMD Navi 21/23 HDMI/DP Audio driver: snd_hda_intel
Device-2: AMD Starship/Matisse HD Audio driver: N/A
Device-3: ASUSTek USB Audio type: USB
driver: hid-generic,snd-usb-audio,usbhid
Sound API: ALSA v: k6.1.9-arch1-1 running: yes
Sound Server-1: PulseAudio v: 16.1 running: yes
Network:
Device-1: Emulex OneConnect 10Gb NIC driver: be2net
IF: enp1s0f0 state: up speed: 10000 Mbps duplex: full
mac: 00:00:c9:c8:b8:d6
Device-2: Emulex OneConnect 10Gb NIC driver: be2net
IF: enp1s0f1 state: up speed: 10000 Mbps duplex: full
mac: 00:00:c9:c8:b8:da
RAID:
Device-1: md0 type: mdraid level: raid-0 status: active size: 4.55 TiB
report: N/A
Components: Online: 0: nvme10n1 1: nvme5n1 2: nvme7n1 3: nvme8n1
4: nvme9n1
Device-2: md127 type: mdraid level: raid-0 status: active size: 21.83 TiB
report: N/A
Components: Online: 0: sdc 1: sda
Drives:
Local Storage: total: 50.36 TiB used: 36.02 TiB (71.5%)
ID-1: /dev/nvme0n1 vendor: Sabrent model: Rocket Q4 size: 931.51 GiB
ID-2: /dev/nvme10n1 vendor: Seagate model: FireCuda 530 ZP1000GM30013
size: 931.51 GiB
ID-3: /dev/nvme1n1 vendor: Sabrent model: Rocket 4.0 1TB size: 931.51 GiB
ID-4: /dev/nvme2n1 vendor: Sabrent model: Rocket Q4 size: 931.51 GiB
ID-5: /dev/nvme3n1 vendor: Sabrent model: Rocket Q4 size: 931.51 GiB
ID-6: /dev/nvme4n1 vendor: Sabrent model: Rocket 4.0 1TB size: 931.51 GiB
ID-7: /dev/nvme5n1 vendor: Seagate model: FireCuda 530 ZP1000GM30013
size: 931.51 GiB
ID-8: /dev/nvme6n1 vendor: Sabrent model: Rocket 4.0 1TB size: 931.51 GiB
ID-9: /dev/nvme7n1 vendor: Seagate model: FireCuda 530 ZP1000GM30013
size: 931.51 GiB
ID-10: /dev/nvme8n1 vendor: Seagate model: FireCuda 530 ZP1000GM30013
size: 931.51 GiB
ID-11: /dev/nvme9n1 vendor: Seagate model: FireCuda 530 ZP1000GM30013
size: 931.51 GiB
ID-12: /dev/sda vendor: HP model: MB012000GWDFE size: 10.91 TiB
ID-13: /dev/sdb vendor: Western Digital model: WUH721818ALE6L4
size: 16.37 TiB
ID-14: /dev/sdc vendor: HP model: MB012000GWDFE size: 10.91 TiB
ID-15: /dev/sde type: USB model: USB DISK 3.0 size: 57.77 GiB
ID-16: /dev/sdf type: USB vendor: PNY model: USB 3.0 FD size: 231.32 GiB
ID-17: /dev/sdg type: USB vendor: A-Data model: USB Flash Drive
size: 7.22 GiB
ID-18: /dev/sdh type: USB vendor: Kingston model: XS2000 size: 1.86 TiB
Partition:
ID-1: / size: 915.81 GiB used: 121.09 GiB (13.2%) fs: ext4
dev: /dev/nvme0n1p1
Swap:
Alert: No swap data was found.
Sensors:
System Temperatures: cpu: 68.4 C mobo: 64.0 C gpu: amdgpu temp: 56.0 C
Fan Speeds (RPM): N/A gpu: amdgpu fan: 667
Info:
Processes: 846 Uptime: 3h 30m Memory: 125.61 GiB used: 11.9 GiB (9.5%)
Shell: Bash inxi: 3.3.24
[theemahn@JackTheRipper ~]$

I want you to be very aware, I write software for multi cores. Today, I am way beyond what I am about to show you. I do not care if you have a Million cores.

I have studied it (A ripper makes that look like a joke):

I just want my 256GB of ram back. Before I start suggestions.

I almost forgot to tell you I write software to boot from RAM:

Yes ,I am the real deal. Want me to tell you things you do not know yet? I am TheeMahn. Hardware, is all I asked. Funny I have built 1000’s of computers, 0 wilth ECC, err 1.

I ran Memtest on it and it acted like the first 4 memory banks were open. I may have to learn ECC. Memory is a lifetime. I believe was $1288.00 for memory. $132 more and I am fine with that as long as it works. I am willing to take the loss. I honestly feel it was my fault. I can make them send me a full bank of RAM. 8 Sticks. I am trying to avoid that. Pulling a Thread ripper Pro is no joke, At that point they should be paying me.

I think you mean one RAM stick is bad, right? To test which one, remove all, then install one stick in the designated slot (the manual shows which one). If that works (boots), add a 2nd stick. Swap out the first stick with the 3rd. As long as each combo boots, continue swapping RAM sticks alternately. When all sticks boot (or you’ve found the offending stick), add 2 more sticks to the working pair. Again, see the manual for which slots you’ll need to populate. Again, if the new combo doesn’t work, swap out one of the latest additions for another stick and try again. Eventually, you’ll find a working quad-group. Then add the remaining sticks, doubling up the total (4->8). By now, you should have an idea which stick(s is/are faulty. Replace, reboot, be happy :slight_smile:

2 Likes

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