cancel
Showing results for 
Search instead for 
Did you mean: 

AI Suite 3 Version 3.00.10 & 3.00.13 - user test/report thread

MasterC
Community Admin
Community Admin
Please check the product support page for your board and download Ai Suite 3.00.14 or 3.00.13 (if available).


If you have a Ryzen-based system:

Ai Suite 3.00.13 updated for compatibility with Ryzen power plans (no other changes):

https://drive.google.com/file/d/14NC...ew?usp=sharing

_____________________________________________________________
FPS, Racing, and VR Gamer / Tech Enthusiast / ROG Admin
1,177,561 Views
1,154 REPLIES 1,154

Mergatroid wrote:
AI Suite has always been one of my favorite things on my rig. I love the way it would stress your system, and then calibrate the fans for you.

I found out rather harshly yesterday that it doesn't work with the new MS update/patch to fix Intel's huge blunder.

Unfortunately, the new version of AI Suite 3 is not functioning well on my Sabertooth Z87. It doesn't seem to properly control the case fans. I swear it's using 12V regulation instead of PWM because when it stops my fans or slows them down enough, it shuts off the fan LEDs. If the 12V is staying at 12V, it shouldn't be affecting the LEDs at all. I'm using Corsair ML140 fans. The previous version of AI Suite was working great yesterday. I really loved that software. It did its job perfectly, and never caused any issues.

Another problem is, I have the Assistant Fans 1 & 2 installed. The AI Suite will only run them at 100%, or OFF. I cannot adjust the fan ramp at all. It's off until the temp reaches a value, then it's on 100%. I can change the temperature value where it comes on, but it will not vary the RPM at all.

While I was at work today, I thought for sure the PWM/12V mode in BIOS must be set wrong for both the chassis fans and the assistant fans, but I was surprised to find it set correctly when I checked. Is there a setting in the AI Suite that will let me change the mode for the fans? I have looked and cannot find one.

I would also like to mention how disappointed I am that my board fan setup doesn't seem to be supported anymore as it lists the Assistant Fan Locations as "Unknown". I had thought this software would keep a database of all the boards it supports since it's not really a lot of boards.

Hopefully some of these issues will be corrected in the final release. Hopefully soon since I've had to shut my assist fans off, and my chassis fan LEDs are very dim.


I'm sorry to disappoint you, but this board does not have pwm control for chassis fans at all. 4th pin is used just for rpm monitoring. Check in the manual by yourself, it says "CPU FAN PWM" for cpu fan headers, but only "+5V" for all other headers! I was so sad and disappointed myself, I couldn't believe my eyes 😞

And you really should consider swapping those fans for something without magnetic levitation bearing, because those ML fans really require PWM. Otherwise I think they will have shortened lifespan and become loud very soon. I guess you can try using CPU_OPT header or/and fan splitters.

TimeKillerOne wrote:
I'm sorry to disappoint you, but this board does not have pwm control for chassis fans at all. 4th pin is used just for rpm monitoring. Check in the manual by yourself, it says "CPU FAN PWM" for cpu fan headers, but only "+5V" for all other headers! I was so sad and disappointed myself, I couldn't believe my eyes 😞

And you really should consider swapping those fans for something without magnetic levitation bearing, because those ML fans really require PWM. Otherwise I think they will have shortened lifespan and become loud very soon. I guess you can try using CPU_OPT header or/and fan splitters.



" I was so sad and disappointed myself, I couldn't believe my eyes 😞 " I couldn't agree more. This is something I usually specifically look for, I'm surprised I didn't catch it on this board. However, at the time I had goo-goo eyes for the Z87 with the thermal armor, so I may have missed it on that basis (at least, that's my story and I'm sticking to it). Seeing the 4-pin fan headers was likely the last straw for believing they were PWM headers (Shame on you ASUS. Stop mounting 4-pin chassis fan headers if you board doesn't support PWM fans in those positions).

I doubt the fans will have shortened lifespan. They actually work very well and are very quiet. They are levitating just fine. I have changed the lower RPM up to 700, and the lighting has come back up. The fans are operating almost silently. I'm sure the magnetic bearings are doing their job. It's funny that ASUS would chose to make the 4th pin 5V, which I assume makes the PWM input 100% on these fans, and then control everything by 12V regulation. That's very cheap, considering how much the board cost at the time. I hope their newer boards are pure PWM. I don't purchase 3-pin fans anymore, and all my future boards will have full PWM control. My previous board had full PWM control. Lucky all my fans are working fine. I have basically every fan header on this board used in a Corsair Graphite 760T with a 360mm rad up top, so there is no swapping fan headers. All the fans are four-pin PWM. If the chassis fans are levitating correctly, which I think they are considering how quiet they're running, I think they will be OK.

My Assistant fans are sill not functioning though. At first, they seemed to work but would only come on 100%. Then the Fan Xpert 2 software greyed them out and produced an error saying I needed some ASUS add-in hardware to get those fans working (ASUS FAN EXTENSION CARD is required to enable these items). Now, one is greyed out, but the other is working 0% 100% (but I have shut it off). So, weird, one fan is getting the error, and one seems to work but has to be shut off because it will only work at 100%. However, the BIOS seems to be able to control them. At least, when I boot up the PC the assist fans are on, but they are not loud at all (can't hear them), but I can see the one by the CPU spinning. Then the AI Suite loads, and they ramp up full speed (at least the one does if I turn it on, the other is stuck at that error). The software says "Unknown" for the position of those fans.

I think tomorrow I'm going to check out Speed Fan and see if it's working better on this board than the last time I used it. I hope it can identify the assistant fans. If not, I will let the BIOS run them.

mrbillishere wrote:
I can confirm that for my motherboard, the X99 Deluxe II that, after the January 2018 patch, it cannot run the older version of AI Suite 3 that came with the motherboard. The application was broken due to the fact that aisuite3.exe and aaHMSvc.exe were both throwing a kernel exception when I ran the AI Suite III program from my start menu. The errors are present in the Windows Application Event Log every time you try to run AI Suite 3.

After a complete uninstall and cleanup of the older app's footprint, I tried installing the new v3.00.10 version of the software. The installation works, and I see that AISuite3.exe is running in the background, however it is not possible to bring up the UI for it and nothing is present in the system tray. In other words, it doesn't work.

This is a bummer because this mobo is brand new and basically I have about a week to be able to send it back to the retailer I bought it from.

I also have another X99 system that is built on a Sabertooth X99 with thermal radar 2.0. I'll give this new software a try but I'm not expecting it to work any better.




Try Restarting Windows without Signature Drivers Enabled, This Will Get the Software to work Under Normal Windows. To Do This Go to Action Center at Bottom Right Corner, and Click on All Settings. New Window Opens Choose Update & Security, From There Chose on the Left hand Side of the Window Recovery Select the Word on the Left hand side and in the Main Window you'll see a Button Restart. Click this a Blue Screen with some text will appear, Click restart. Now This Part is Important. Read The Option Restart With Digital Signature Drivers Disabled Read What Number This Falls Under I think 7 but you will Press that Number to access it then once you login back to desktop Install the AI suite and once it asks you to restart do so the Windows will now reboot with normal security Privileges this is only to get his Beta installed and Working.Good Luck

mrbillishere wrote:
I can confirm that for my motherboard, the X99 Deluxe II that, after the January 2018 patch, it cannot run the older version of AI Suite 3 that came with the motherboard. The application was broken due to the fact that aisuite3.exe and aaHMSvc.exe were both throwing a kernel exception when I ran the AI Suite III program from my start menu. The errors are present in the Windows Application Event Log every time you try to run AI Suite 3.

After a complete uninstall and cleanup of the older app's footprint, I tried installing the new v3.00.10 version of the software. The installation works, and I see that AISuite3.exe is running in the background, however it is not possible to bring up the UI for it and nothing is present in the system tray. In other words, it doesn't work.

This is a bummer because this mobo is brand new and basically I have about a week to be able to send it back to the retailer I bought it from.

I also have another X99 system that is built on a Sabertooth X99 with thermal radar 2.0. I'll give this new software a try but I'm not expecting it to work any better.


Normally I like ASUS. I have been using their products for a long, long time. But in this case, if I was in your shoes, I would seriously consider jumping ship and sending that board back. My board is four generations old (Haswell Sabertooth Z87), and I'm very unhappy that my PC now feels like it's crippled. I was using AI Suite because it worked, and for my board it worked really well. Now it doesn't control the case fans as well as it used to. It seemed to clibrate their speeds better in the older version. I have manually fixed that, but it would be nice if it worked as well as it used to. It doesn't control the assistant fans at all. I have had to shut them off. However, the BIOS still seems to run them at a reasonable speed if I prevent AI Suite from loading. Because of this, I am thinking of abandoning AI Suite and trying Speedfan. It failed to work on this board once before, but maybe they have updated it enough that it might work properly now.

I can't imagine how you must feel, having a brand new board but the same feeling I get from knowing things are not working properly. If I was you I likely would already have started the procedure for sending it back. Get a board with apps that you know work.

Personally, I feel Intel should be compensating us for all the problems they have caused. If one of those class action suits crosses my path, I am sure going to join in. My system has gone from being the best, most awesome working reliable system I have ever owned to something I would almost describe as a little "clunky", all because of these patches used to make up for Intel's mistakes.

Time to start thinking Ryzen for my next build.

Installed 300.10 over original install, then 300.13 then DIP5 1.05.13 then 14, all still stable. Going on over a month now.
Microsoft Windows 10 Professional (x64) Build 16299.309 (1709/RS3)
Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz
ASUS PRIME H270-PLUS Intel H270 (Kaby Lake)
BIOS Version: 0808
Crucial Technology 1200.5 MHz (DDR4-2400 / PC4-19200) BLS8G4D240FSB.16FA 4x8 = 32GB
EVGA GTX 1050 Ti SC ACX 2.0
SSD INTEL SSDPEKKW512G7

Yesterday I upgraded BIOS on my X299-Deluxe to latest build 1201 and now AISuite 3.00.13/1.05.14 won't load with "remote procedure call failed" error.

AMP_US
Level 9
I'm going to try some of the suggestions in this thread, but ATM, the Beta is still broken on my M7F running W10. FanExpert is 100% not functional.

enosrasun
Level 7
ok ,managed to get the installer working.

1 dowload the installer on .zip .rar format
2 right click -> properties -> hit unblock on bottom
3 hit apply
4 run asussetup az administrator

Yoda1
Level 8
Working ok so far on a Apex IX.
Your ass is grass, smoke it I will!

AlexB121
Level 7
Anyone know when the stable version is coming ?