To G.SKILL R&D folks:
At overclock.net forum there is a thread called How do I read/modify/flash SPD/XMP profiles on DDR4 EEPROM?. One guy said that SPD of his TridentZ RGB F4-3200C14Q-32GTZR modules had been corrupted before he found out that the "DRAM SPD Write" BIOS option was set to "Disabled". He has an ASUS Maximus IX Formula motherboard. As you know, this BIOS option prevents SPD EEPROM from being written. This means SPD was corrupted not by G.SKILL RGB control software! And even NOT by software at all, because any attempt to write data to the SPD EEPROM fails. After enabling the "DRAM SPD Write" he had an opportunity to successfully restore SPD with Thaiphoon Burner utility.
My question is: do you guys admit that you made a mistake in the hardware design of the Trident Z RGB series? I'm asking because the problem is much serious as it sounds. You are trying to fix SPD issues with releasing the new versions of your RGB Control software, but they cannot be resolved in that way.
At overclock.net forum there is a thread called How do I read/modify/flash SPD/XMP profiles on DDR4 EEPROM?. One guy said that SPD of his TridentZ RGB F4-3200C14Q-32GTZR modules had been corrupted before he found out that the "DRAM SPD Write" BIOS option was set to "Disabled". He has an ASUS Maximus IX Formula motherboard. As you know, this BIOS option prevents SPD EEPROM from being written. This means SPD was corrupted not by G.SKILL RGB control software! And even NOT by software at all, because any attempt to write data to the SPD EEPROM fails. After enabling the "DRAM SPD Write" he had an opportunity to successfully restore SPD with Thaiphoon Burner utility.
My question is: do you guys admit that you made a mistake in the hardware design of the Trident Z RGB series? I'm asking because the problem is much serious as it sounds. You are trying to fix SPD issues with releasing the new versions of your RGB Control software, but they cannot be resolved in that way.
Comment