Official download of the current CTR 2.0 RC5 on igor’sLAB (download link)
- Download the CTR and unpack the ZIP archive in a directory of your choice
- Then download the Cinebench R20 archive https://igorslab.de/installer/CinebenchR20.zip and extract the contents of the archive to the “CB20” folder (this folder is located in the CTR folder).
- Runs the Cinebench R20, please accept the license agreement, closes the Cinebench R20.
- The CTR is now ready for use.
Official download of the current CTR 2.0 RC5 with CB20 on igor’sLAB (download, 320 MB)
- Download the CTR and unpack the ZIP archive in a directory of your choice
- Runs the Cinebench R20 from SubDir, please accept the license agreement, closes the Cinebench R20.
- The CTR is now ready for use.
The Cleaner reliably deletes old CTR configuration data from the registry. Important in case of conflicts and error messages!
Possible errors during installation or execution
1.I can not find the download link
Look up there ^ 😉
2. Frequency and temperature are not displayed in monitoring
Either another monitoring application prevents the communication between CTR and CPU or the BIOS is incompatible. If necessary, another BIOS with the latest AGESA should be installed.
3. CMD_REJECTED_PREREQUISITE or FAILED
Either another monitoring application prevents the communication between CTR and CPU or the BIOS is incompatible. If necessary, another BIOS with the latest AGESA should be installed.
4. CTR does not start
Always run CTR as administrator via Windows UNC: Right click, Run as administrator.
Possibly the configuration of CTR is corrupted and has to be reset. To do this, the following directories must be deleted: %LOCALAPPDATA%/A, %LOCALAPPDATA%/Nemesis_UI
v2 This can also be done with the CTR-Cleaner, see download link above.
If applicable, see also points 6. and 7.
5. CTR does not start with Windows
The task scheduling aka Task Scheduler in Windows has a bug in the current version. It may help to delete the CTR 2.0 task in the Task Scheduler and let CTR create it again automatically.
6. CTR is detected as malware by Windows Smartscreen or Windows Defender
This is a false alarm. Other anti-virus tools, such as VIRUSTOTAL, classify CTR as harmless.
If necessary, an exception for the CTR directory must be defined in Windows Defender or alternatively all contained files must be unblocked manually via “Unblock” in the file properties.
7. FACEIT Client Anti-Cheat or Valorant “Vanguard” blocks inpoutx64.dll
Should no longer occur with 2.0 RC4.This is the monitoring library, which must be manually defined as an exception.
Credits by Yuri Bubliy (@1usmus)
Behind absolutely every project, besides the developer and author of the idea, there are also people who have contributed. I would like to thank everyone who participated in the testing, gave technical advice, or found important information that could improve the CTR. In particular, I would like to express a special thanks:
@A_z_z_y (Vadym Kosmin), Martin Malik, @CodeZ1LLa (Oleg Kasumov), @lDevilDriverl (Oleksii Baidala), Sami Makinen (AMD), Danny Ordway (ACI), @Spaik (Alexey Savitski), @datspike (Alexey Elesin), Keaton Blomquist, @tsa, @cluster_edge, @Anem (Anton Emashov), @PavelG, @CapFrameX, @irusanov, @stormpand.
Also ddf CTR contains third party modules:
- Ryzen Master SDK from AMD – the main monitoring module.
- LibreHardwareMonitorLib – Monitoring of CPU svi2 and SOC svi2.
- Cinebench R20 from Maxon – the most popular benchmark.
- Prime95 by George Woltman – the best comprehensive stress test CPU.
- Reverse engineering version of Shamino’s CCX working tool – as a basis for accessing the SMU.
1,679 Antworten
Kommentar
Lade neue Kommentare
Urgestein
Urgestein
Mitglied
Urgestein
1
Urgestein
1
Veteran
Mitglied
1
Mitglied
Urgestein
Moderator
1
Neuling
Urgestein
1
Veteran
Urgestein
Alle Kommentare lesen unter igor´sLAB Community →