You hook them up to the internet and it doesn't fix itself. That's weird. Can you get me some log files at pieter@thisdomain?
To get the log files:
- folder: C:\ProgramData\Intel\Intel Extreme Tuning Utility
- delete all
- open XTU, when you get the error zip the folder and mail it to me
It might just be easier to have one thread with all the (extreme) tools The Stilt has made for AMD.
THE LIST OF SOFTWARE
APU Fuse Interpreter ("AFI"), latest version: R1.02
BullDozer Conditioner ("BDC), latest version: R1.0.3B
Devastator PowerTune ("DPT"), latest version: R1.00 (unzip with 7-zip)
Trinity Control Interface K2 ("TCI K²"), latest version: V1.1
THE DETAILS
1) APU Fuse Interpreter
R1.02 - R1.01 - R1.00
Original post: http://forum.hwbot.org/showthread.php?t=86930
2) BullDozer Conditioner
V1.03B - V1.02B - V1.01B - V1.00B
Original post: http://forum.hwbot.org/showthread.php?t=78490
3) Devastator PowerTune
R1.00 (unzip with 7-zip)
Original post: http://forum.hwbot.org/showpost.php?p=269267&postcount=48
4) Trinity Control Interface K2
V1.1 - V1.0
Original post: http://forum.hwbot.org/showthread.php?t=59243
Not that I'm aware of. XTU installs the XTU Service (surprise!), and then requires the services other OC tools require as well. For example MEI driver.
Would it be interesting to add "actual CPU frequency" to the application, add a validation functionality, and create a benchmark category for this? Link the hash to an actual OC result, correlate, and get some interesting findings?
Or would none of those findings be any interesting?
The benchmark is "working", Ian. We get about 900 submissions per week. There is a problem with V4.2.0.8, Windows 7, and X79 mainly.
I have forwarded Intel the issue, logs, and requests for quick solution.