The following command-line options can be used to make AIDA64 more stable when a hardware incompatibility issue occurs:

/SAFE

Using this option the most common hardware incompatibility issues can be avoided by disabling low-level PCI, SMBus and sensor scanning. In network audit this option should be used in all cases to make sure AIDA64 does not cause system instability.

/SAFEST

Using this option all common hardware incompatibility issues can be avoided. When this option is used, AIDA64 will not load its kernel drivers, and so all low-level hardware access features get disabled.

/NT4ZIPFIX

Using this option an Iomega Zip drive related issue ("Subject aida64.exe - Drive Not Ready / Body: The drive is not ready for use; it's door may be open") can be avoided. This problem may occur only on Windows NT 4.0 systems.