aujagor

Try deleting the CPUID files in iCue's registry, that seemed to work for me. Unfortunately, I ended up RMA'ing my 370 Strix thinking that was the issue before I ended up resolving this, but the latest update seems to be running fine on my C7Hero. Latest iCue, latest BIOS. I fixed the stability issues previously by doing the CPUID fix I mentioned above, but it cost me the RGB controls for my Vengeance Pro ram; this latest update I left everything as is and have been problem free for a week *knocks on wood*

...This occurred to me on both a B350 chipset and an X470...I mean, I can understand the trouble of finding an X79 system, but don't totally follow the relevance of it.

Popped in to see if there were any updates. On my end, renaming the cpuid .dll's seems to have resolved the black-screen crashes on my Rog H7Wifi, but broke iCue's link to my Vengeance Pro RGB RAM. Could certainly be worse, but frustrating nonetheless (I actually bought the RAM thinking it was the reason my last board was black-screening, but obviously wasn't.) If there's any logs we can pull that would help identify the issue and drive to a resolution I would be happy to provide it when I have the time to do so. I would love to be back to 100% functionality again; getting close to time for another teardown to do a water loop and if I need to make any changes that would certainly be the time to do so.

Having a similar issue with my Crosshair Hero VII Wifi. Issue is compounded, I believe, due to being afflicted by the iCue/CPUID crash issue as well: Latest BIOS versions lock out Vengeance Pro RGB control completely. They don't even show up in iCue. Tried rolling back to 0804, as many were stating that version worked for them. Worked for a bit, then back to crash issues (black screening.) Per the black screen threads, renamed the CPUID dll's in iCue, then they went away again. Guessing that the RAM is controlled via CPUID, which would explain it disappearing as soon as I rename those dll's. If I had to choose, of course I'd rather have a stable system than controllable RGB RAM (especially since I have one stick that seems to randomly lag behind the rest, not much, but enough to send my OCD into overdrive.) That being said, if I could get both to work I would be a very happy camper indeed.

Had this issue on a Strix 370-F, and a Crosshair VII Wifi, both with a 2700X. Came from a 4690K and Z197(?) Krait which couldn't care less about iCue. Just to clarify, do we need to change the name of both CPUIDSDK.dll AND CPUIDSDKx64.dll (or something like that...the 64-bit version of the .dll?) I did to be safe, but wasn't sure if it was necessary. When it's not the holidays and I have time to do some more digging I will try to run the tests requested by Corsair and see what happens. Definitely one heck of a buzzkill though. Really had me rethinking my Ryzen build for the last three weeks or so. ...'Course, that being said, if I did end up going Intel, are there Z370/Z390 boards having issues as well? Would kinda defeat the purpose of doing so obviously...