For example, if we want the Vendor ID String (see below), we should code something like that: The idea of the CPUID instruction is that you can call it with different values in EAX, and it will return different information about the processor. This avoids problems with CPUs that do support CPUID but don't support the ID bit in EFLAGS and is likely to be faster for CPUs that do support CPUID (and slower for CPUs that don't). Note 2: You can simply attempt to execute the CPUID instruction and see if you get an invalid opcode exception. The are also CPUs that support CPUID if and only if it has to be enabled first (Cyrix M1). Note 1: There are some old CPUs where CPUID is supported but the ID bit in EFLAGS is not (NexGen). Helps if you have a temperature gun to check various components, as well.Pushfd Save EFLAGS pushfd Store EFLAGS xor dword, 0x00200000 Invert the ID bit in stored EFLAGS popfd Load stored EFLAGS (with ID bit inverted) pushfd Store EFLAGS again (ID bit may or may not be inverted) pop eax eax = modified EFLAGS (ID bit may or may not be inverted) xor eax, eax = whichever bits were changed popfd Restore original EFLAGS and eax, 0x00200000 eax = zero if ID bit can't be changed, else non-zero ret Same thing goes for temperature gradients. Ideally, the lower you can keep your temps, the better. The TJunction for the i7-7700k is 100c, so keep it below that, and you should be good. Some good programs for monitoring temps are HWInfo, and HWMonitor. Usually the Intel burn test, or OCCT are recommended. Used to cause some over-voltage issues on Intel chips. That way you can be fairly confident when gaming that your computer isn't going to reach unreasonable temperatures, or suddenly interrupt a gaming session.Īs per tests though, a lot of people aren't terribly fond of P95 here. That's one reason to run a stress test out of the box, as it's a worst case scenario for CPU utilization. Instead of doing all these load tests and stuff.Įh, it's always nice to know where your computer sits thermally. Or is the best thing to just use it like you normally would.
If that doesn't work or you're still having other issues then you probably still have a monitoring software interfering with the AIO/Link communications, find what it is and disable it.Īnything else such as this that I would need to do with a new rig? You can test if this worked by setting the fan speed in Link to 100%, if it doesn't fluctuate you are set and can change the curve to whatever. The problem is bad coding in Link that fights for AIO control with other programs. That should fix the fan issue for some Corsair AIOs (H80i GT/v2, H110i GTX/H115i, H100i GTX and others made by Asetek). For others: Disable any monitoring of Corsair AIO sensors. For HWinfo: manually disable all monitoring of the AIO sensors/components.
For AIDA64: First make sure you have the newest update installed, then, go to Preferences>Stability and make sure the "Corsair Link sensor support" box is checked and make sure the "Asetek LC sensor support" box is UNchecked. Are you getting weird fan behavior, speed fluctuations, and/or other issues with Link?Īre you running AIDA64, HWinfo, CAM, or HWmonitor? (ASUS suite & other monitoring software often have the same issue.)Ĭorsair Link has problems with some monitoring software so you may have to change some settings to get them to work smoothly.