F5F Stay Refreshed Hardware Desktop Investigating possible issues with Corsair Vengeance DDR5, checking storage limits, and failed software updates

Investigating possible issues with Corsair Vengeance DDR5, checking storage limits, and failed software updates

Investigating possible issues with Corsair Vengeance DDR5, checking storage limits, and failed software updates

F
fireroster
Member
150
01-10-2021, 08:58 PM
#1
You're experiencing some unusual behavior with your DDR5-6000 kit from Corsair CMH32GX5M2D6000Z36. Only 31.1 GB appears usable, while hardware is reserved at 873 MB. It seems the iGPU might be affecting this. The RAM identification issues—two sticks labeled "unknown"—suggest a possible problem with the memory module or driver configuration. Memtest86 successfully identified both sticks after a restart, but firmware updates are failing with messages like "update failed" instead of "latest version." It looks like Corsair may not have the latest firmware available online, and the situation could be related to missing or outdated software. Keep running tests and monitor progress.
F
fireroster
01-10-2021, 08:58 PM #1

You're experiencing some unusual behavior with your DDR5-6000 kit from Corsair CMH32GX5M2D6000Z36. Only 31.1 GB appears usable, while hardware is reserved at 873 MB. It seems the iGPU might be affecting this. The RAM identification issues—two sticks labeled "unknown"—suggest a possible problem with the memory module or driver configuration. Memtest86 successfully identified both sticks after a restart, but firmware updates are failing with messages like "update failed" instead of "latest version." It looks like Corsair may not have the latest firmware available online, and the situation could be related to missing or outdated software. Keep running tests and monitor progress.

C
CyberSubZero
Member
50
01-11-2021, 03:03 AM
#2
Memtest86 v10 shows no issues after four runs... perhaps overthinking it?
C
CyberSubZero
01-11-2021, 03:03 AM #2

Memtest86 v10 shows no issues after four runs... perhaps overthinking it?

R
Rodri_Mendes
Member
223
01-11-2021, 07:39 AM
#3
Hello, I've also been using Corsair Vengeance DDR5-6000 for a while now. Like you, I wasn't able to perform any firmware updates since I received the same notification. A few days ago, I got a message indicating iCue updates (v5). When opening the app, I noticed my RAM had available firmware updates too. I installed them after stopping Armory Crate AURA (I have an ASUS MOBO). After that, one of the RAM sticks stopped syncing properly. After restarting and checking, I realized the 4th slot on my board lacked SPD information (CPU-Z showed "Unknown"). I'm worried the firmware update might have helped one stick but not the other. I recommend waiting before proceeding, even if updates arrive. If I could get that RAM to display SPD details once, I'd be able to target the update for that specific stick. Unfortunately, it's not working as expected. P.S.: I haven't upgraded iCue to v5 yet—I think it was removed from the market due to SPD write issues (I found a discussion about it).
R
Rodri_Mendes
01-11-2021, 07:39 AM #3

Hello, I've also been using Corsair Vengeance DDR5-6000 for a while now. Like you, I wasn't able to perform any firmware updates since I received the same notification. A few days ago, I got a message indicating iCue updates (v5). When opening the app, I noticed my RAM had available firmware updates too. I installed them after stopping Armory Crate AURA (I have an ASUS MOBO). After that, one of the RAM sticks stopped syncing properly. After restarting and checking, I realized the 4th slot on my board lacked SPD information (CPU-Z showed "Unknown"). I'm worried the firmware update might have helped one stick but not the other. I recommend waiting before proceeding, even if updates arrive. If I could get that RAM to display SPD details once, I'd be able to target the update for that specific stick. Unfortunately, it's not working as expected. P.S.: I haven't upgraded iCue to v5 yet—I think it was removed from the market due to SPD write issues (I found a discussion about it).