Corsair Dustin

So, the motherboard included is going to have limitations in place in BIOS in order to ensure surface components don't overheat. I'll have to go back and play with the i160 some more to see if I can reproduce your issues. I'm working on having an overclocking-enabled BIOS for the i180 produced, if there are issues with the i140/i160's motherboard BIOS in terms of letting customers play with the settings and tweak their systems I'll want to make sure those issues are resolved.

The retail ASRock X299 ITX board WILL NOT FIT in the Corsair One chassis. We had to modify a daughterboard to ensure that it would work. To be honest, if you want to go nuts with a Corsair One, your best bet is just to buy the i180 and manually upgrade the CPU to the i9-9980XE. We've actually validated and certified against that CPU. We won't warrant its operation or any damage you may incur by doing the swap, but it can be done and should work fine. We also have a 64GB upgrade kit for the i180 en route. You can technically buy a 16GBx4 SODIMM kit and it should be fine, but the upgrade kit comes with specially selected ICs and heatspreading tape to guarantee stability. As for the i140/i160, I don't know what you really gain from switching motherboards. Maybe another 100 or 200MHz turbo? Maybe? You can achieve similar results by manually undervolting the CPU, which could reduce noise in the process.

That is NOT what I said. This generation Corsair One has limited upgradeability as far as the graphics card is concerned. You can use any full size card that fits the PCIe height/size spec. You CAN'T use the graphics liquid cooling system with it.

Just as a heads up, we do have fan hysteresis coming for Commander Pro, and are working on revising the fan curves.

Unfortunately it's not possible to open the source code for Link as it uses proprietary IP from other vendors.

Bizarre, but glad it solved the problem.

pxv, your unit is unfortunately from the lot affected by the recall. zguy85, were you having issues before the recent updates or has this started as a result of the Fall Creator's Update from Microsoft?

We've had to prioritize other fixes (see the release notes on 4.9.2), but this is on our radar as something that needs to be resolved. I'm on a Ryzen 7 1800X system myself, I'd like to see this issue fixed. ;)

It's still in the works, but slow going. We've been aggressively prioritizing fixing bugs in the software.

It depends on the version. I wouldn't expect it to, but it is possible that you may have to fix some of your settings after the update.

I don't see where it didn't fix the driver. Your Link dashboard looks like it's reporting your Link products and your Device Manager doesn't have an exclamation point on the driver.

Search me, man. But that said, a new version that should fix the driver signing issue is coming today or tomorrow.

Thank you all for your patience, this problem is maddening for us, too.

The plan is to have it out by the end of the month, but if for whatever reason a new version being validated introduces new bugs, I won't release it and it will be delayed. We've had a rash of new products needing software support (Vengeance LED/RGB on Z370 is a big one right now), but I'm very anxious about continually releasing new versions that add products but don't fix outstanding issues.

We do generally recommend 4.9.0.57, but if users are seeing the driver issue, we have instructions on how to roll back to 4.7.0.77.