delly Posted October 26, 2013 Share Posted October 26, 2013 So it all worked beautifully after hacking the registry for Win 8.1 support, I spent hours creating custom curves (v2.4.5110), adding profiles, beholding my beautiful creation! Then reboot, play game, BSOD after 2 minutes. WTF. Reboot again and load up Corsair to check fans are responding to my custom curves.. Not budging, temperature hits 70, rpm just sits there at 900rpm! And no its not the wrong group before you start typing. So I read all the support forums, uninstalled every other AI Suite or program that might even be thinking about monitoring fan speeds but to no avail. Create new profile, ah.. now it works again. So then I tried changing the fan group to water temp and then back again to cpu avg temp and it springs into life! So the workaround is everytime I start windows I have to open corsair and for each fan flick the groups around. Looks like a bug to me, incidentally restarting service did not fix. Another thing that might be relevant is I am using the R4 case and its hardware fan controller with 3 settings, this switch has no effect either (apart from preventing the GTX being controllable with CL). One last thing although its not specifically relevant to this issue, the avg core temp will spike by 10deg every few seconds under load (haswell?) resulting in the fans spooling up (when it works :p:) and down constantly, is there anyway you could implement a kind of smoothing algorithm that perhaps allowed configuration of the duration that a temp would need to remain to trigger rpm changes? Its like my machine is schizophreniac! And no I cant use the water temp, it is just too restrictive (and dangerous). Screenshot: I have applied group flick fiddle (GFF) on the second fan (Fan 4) and you can see it is responding (it has roughly the same curve). Last thing please add a way to copy a custom curve it is so painful having to copy them. http://img43.imageshack.us/img43/6518/g1v6.png Link to comment Share on other sites More sharing options...
This topic is now archived and is closed to further replies.