Newsletter Archives

  • Problems with February Security Updates KB3134814 and KB3135782 and AISuite

    Just got this from reader FN:

    I installed KB3134814 (cumulative IE 11 security update) and KB3135782 (security update foe Adobe Flash) yesterday on my Windows 8.1 64 bit OS. Upon the required restart for installing the updates, a BIOS utility app triggered an “Access violation at address 00413FDO in module AISuite3.exe). This was a situation I have not previously encountered and the other BIOS utilities would not load successfully. As a little background, AISuite3.exe contains a number of configuration utilities to change BIOS settings for OC the CPU, fan setting optimization, etc. and is generally useful for monitoring MB temperatures and CPU utilization. I have installed version 1.00.56 of the Asustek AISuite3 software which I confirmed is the latest release.

    After a few hours of sleuthing, I traced the access violation error to a specific app which is AIcharger plus.exe within the suite that loads from the startup menu. The purpose of AIcharger plus is to enable the battery charging of portable devices, such as smartphones, from USB ports on the motherboard. This program (I believe version 51) caused all sorts of headaches for people when they were trying to upgrade their system from Win 8 to Win 8.1, namely the upgrade would fail to install because of compatibility issues. The only solution was to remove AIcharger at the time if you wanted to perform the upgrade. So there is a history of this app bot playing nice with Win 8.1. After tracing the problem to the source, I “disabled” AIchargerplus in the start menu and the problem is successfully removed as a workaround. All the other BIOS utilities in the AISuite3 began launching and working properly again without any discernible issues. I have yet to make up my mind as to whether I will uninstall the problem app or just go with triage in the startup menu. I do not use my USB ports to charge devices anyway.I am certain that one of the KBs mentioned triggered the issue because they were the only two that I installed and the error first occurred upon the required installation reboot. I am just passing this experience along for purposes of intel for your DEFCON rating for February Windows security patches. I am running an Asus Z87-Pro motherboard with a Core i7 4770K CPU on my desktop system. The AISuite3 is also used with a number of other Asus motherboards and so it is not inconceivable that others may encounter this problem.

    If I had to hazard a best guess, I would suspect KB3134814 to be the install that triggered the issue.