Jump to content
Latest News
  • Apologies for the downtime. We had to update our backend and theme.
  • We will continue pushing updates.
  • Apologies for the downtime. We had to update our backend and theme.
  • We will continue pushing updates.


T|I Advanced Member
  • Content count

  • Joined

  • Last visited

Community Reputation

53 A Truly Elite Reputation


About allstone

  • Rank
    Senior Member
  • Birthday 06/19/86
  1. I have been trying to find a way to control fans on my y510p. As everything else failed up to the Embedded Controller (EC), I have made myself a program to call dust removal function. With a help of this forum members, I have perfected calling and stopping timing which works on my computer. Basically, running Furmark, if I do not run this program, I constantly run into 97C and thermal throttling for my GPU (see Mhz of core and memory): And when I do run this program, it manages to keep temperatures at 88-93C and there is no more throttling in a long run. Usage: run the program and it will enable dust function when you reach GPU/CPU temperature of 90C. Or Start/Stop it with keyboard shortcut Ctrl+Shift+Q or through menu on tray icon. Download: IdeaFan v1.6 (includes OpenHardwareMonitor beta) So far, this has been tested on 2 computers (y510p Win 8.1/Win 8.1Pro/Win10). Both with Lenovo Energy driver v7.x and v8.x. I have tried it for both 2xSLI and 1x GPU, also for CPU stress tests or simply during high CPU usage, i.e. rendering videos. Feel free to use and leave some comments that it can be further improved if possible. Danger! Do not use Furmark to stress your GPU unless you know what you are doing. I have used it here for testing purposes only. Release Notes v1.6 *change* Migrated to OpenHardwareMonitor beta) *fix* Temperatures are shown and working on Windows 10 (tested on build 1511) v1.5 *fix* Supposedly startup error with OHM should be fixed *new* Added another keyboard shortcut just for diversity v1.4 *fix* When fan is running, nothing should disrupt the cycle (not tray menu nor high cpu/gpu usage or temperatures) *change* Startup option changed from startup folder to windows task *change* Updated default settings *change* Removed sleeps, introduced timers/threads *new* Lower cpu usage v1.3 *change* Reverted default settings (to have several versions with all newest changes available) v1.2 *change* Updated default settings (provided by octiceps) v1.1 *new* Options are saved in ini file *new* Automatic dust function control based on temperature (OpenHardwareMonitor 0.6.0 beta included) *new* Startup option fixed *new* Ability to change timeouts in ini file v1.0 Initial Version to run dust function And here are possible improvement requests for the fututre: 1. Make fans start hitting the 9s/0.5-1s cadence right off the bat. Need to make sure that the last time fans are stopped, its within 0.5-1s gap when they are stopped. This is due to the EC somehow remembering where it left off the last time and resuming from there. If you stopped it in the middle of a spin cycle, the next time you run it the fans will be inconsistent inside the first minute before finding their rhythm again. The length of the gap is also determined by last your stopping point. I've gotten it anywhere from basically none (fans spin down and spin up immediately) up to 1s, but it never goes above that. Edit: tested to stop at 0.5-1s gap, but that seems to have no effect on the initial position. Also tried variable timeouts - seems for EC its no different, with variable its unpredictable, constant value may be required afterall. For now its seems the only way to start off the bat for sure is to know internals of EC - or at least get a fan RPM sensor readings which we do not have. 2. When OHW 0.6 is not started, IdeaFan throws errors (need to check for them), only at COLD first start. See http://forum.techinferno.com/lenovo-ibm/7358-ideafan-y510p-6.html#post102492 (should be fixed in 1.5) 3. Introduce easy HotKey settings in INI file (like Ctrl=yes, Alt=yes, Key=q) and let change the hotkey. Also handle hotkey cannot bind error.

Important Information

By using this site, you agree to our Terms of Use.