SoylentNews

Arthur T Knackerbracket [soylentnews.org] writes:

--- --- --- --- Entire Story Below - Must Be Edited --- --- --- --- --- --- ---

Arthur T Knackerbracket has processed the following story [tomshardware.com]:

Gigabyte has released new firmware and an updated version of the Gigabyte Control Center (GCC) software for the company's Intel motherboards to solve a peculiar bug that corrupts the SPD (serial presence detect) on DDR5 [tomshardware.com] memory modules. Fortunately, the issue only affects the information on the SPD and will not damage the integrity of the memory modules.

There were some user reports on the Baidu Tieba community in China about persistent memory issues with Gigabyte motherboards based on Intel's 600- and 700-series chipsets. After a month of usage, one user [baidu.com] stated how his Z790 Aorus Elite AX motherboard stopped detecting one of the DDR5 memory modules. When he finally got it to recognize the memory module, it was showing as having a capacity of 384GB, which was hilarious and scary at the same time. Later, one of the memory kit's XMP profiles disappeared, and then the DDR5-6000 profile had its timings replaced to 1-36-104-194. According to the user, he had replaced the "faulty" memory times, but the outcome was the same. The problem was erratic. Sometimes, it would present itself after a month, sometimes after a week, or after a couple of days.

Another Gigabyte motherboard owner [baidu.com] reported similar behaviors on his system. He constantly suffered from system crashes and noted that after one of the incidents, his memory lost the AMD EXPO profile. In another episode, the motherboard corrupted the DDR5-6800 XMP profile with ludicrous timings, such as 34-153-0-0.

The Chinese netizens had labeled the problem as the notorious "burning memory issue" because, at first, many thought that Gigabyte motherboards were burning up and killing the DDR5 memory modules since the system got to a point where it wouldn't boot properly. It may sound like an overreaction at the time, but luckily, the issue only botches the memory timings and not the DRAM voltage. If it did, the result would have been different. As per Gigabyte, the memory should be fine. It's just that the SPD is messed up, and obviously, the wrong parameters prevent the system from posting correctly.

Gigabyte acknowledged the problem via the company's official Aorus Bilibili account [bilibili.com] and provided insight into the burning issue. In its statement, Gigabyte pushes the blame on memory vendors, claiming that some brands don't correctly implement "SPD Write Protection." If you've never heard of "SPD Write Protection," it's a feature that impedes access to the SPD data.

According to Gigabyte, without a correct "SPD Write Protection" implementation, there is a faint chance that the SPD information may be incorrect when using the DDR5 memory with GCC. However, Gigabyte doesn't explain why the motherboard or the GCC software would write anything to the SPD. Luckily, nothing is damaged, and you need to refresh the SPD firmware to return the memory to normal. Gigabyte advises its Intel 600- and 700-series motherboard owners to update their motherboard's firmware and GGC to the latest versions to prevent the issue.

The description for the latest F6 firmware for the Z790 Aaorus Tachyon [gigabyte.com] or the FN firmware for the Z690 Aorus Elite AX [gigabyte.com] reads, "enable SPD write protect, help fixing DDR5 compatibility issue due to some module did not introduce JEDEC SPD write protection properly."

If you own an Intel 600- or 700-series motherboard from Gigabyte, don't forget to bring your firmware and GCC to the latest versions to avoid headaches.

Original Submission