Issue with RAM in B2 port Failure detected in memory module connected to B2 slot.
Issue with RAM in B2 port Failure detected in memory module connected to B2 slot.
Hello, Your first build is done. The setup includes a 13700k Gigabyte Z790 UD AX v1.1 with BIOS F8, Corsair Vengeance RGB 2x16GB DDR5, DeepCool LT720, and Asus TUF 4070 Ti motherboard. I assembled the PC two weeks ago without issues until sudden slowdowns occurred—especially when shutting down games, which caused extreme lag even for the mouse. Force restarts were needed, but no BSOD appeared. Then, during startup, the B2 slot RAM stopped working despite the RGB staying on. I replaced the faulty RAM with a similar kit from Amazon and waited over 24 hours before it failed again after a system freeze and reboot. Could you assist?
The problem might lie with the mount. It could be useful to check that as well: https://wccftech.com/gigabyte-addresses-...-firmware/
Are you certain these issues often happen? Most RAM problems seem linked to the motherboard, especially dirty slots, which is common when working with older systems. It’s likely a faulty board—recommend replacing it since CPU pads are usually the weakest part. Before that, try cleaning the CPU pads; isopropyl alcohol works best, though a wet cloth will suffice. You’ll just need to let it dry a bit longer. I’ve noticed similar problems with dirty CPU pads on my i7 950. When testing with an X58A UDR3, only the outer slot was functional, while others barely detected anything. CPU detection came through, but Task Manager showed only 1GB usable because I used 1GB sticks. The issue became apparent once I reached 2900MHz DDR3 and added more sticks. Swapping to an i7 930 resolved the problem, and all RAM slots worked again. I also saw signs of other slots failing even at normal speeds, though I didn’t pay much attention at first. Regarding dirty sockets, I’ve seen it happen before—especially with certain models like the 970 Extreme3. The RAM would only partially detect until the BIOS settings changed, which led to a D4 error. After cleaning and powering down everything, the problem disappeared.
Thanks for the late notice. The mobile was repaired and most issues are resolved. Thanks to everyone!