TRIM is needed if my system use SSD.
You can (and should) update them both (RAID ROM and EFI SataDriver) at the same time. This way your Intel RAID Controller will use the latest RAID ROM/EFI SataDriver version regardless of the OS installation mode (UEFI/LEGACY).
According to my knowledge none of the currently available Intel RST RAID ROM/EFI SataDriver modules will let the TRIM command pass through the Intel SATA RAID Contrloller into a RAID1 array. Only Intel SSD RAID0 arrays and SSDs, which are not member of a RAID array, natvely are supported by the TRIM in RAID feature.
How can I update at the same time?
ROM SataDriver are update using AMI non-UEFI MMTOOL v3.26
EFI SataDriver are update using AMI Aptio UEFI MMTool v4.50.0.23.
It was in series. Am I right?
I understood
How can I update at the same time?
ROM SataDriver are update using AMI non-UEFI MMTOOL v3.26
EFI SataDriver are update using AMI Aptio UEFI MMTool v4.50.0.23.
Your actually used Gigabyte mainboard has an AMI UEFI BIOS, where both Intel RAID modules (ROM and SataDriver) can be modified by the AMI Aptio UEFI MMTool v4.50.0.23. So you can (and should) do it at the same time.
I updated to ROM and EFI SATARAID v13502164 using UEFI BIOS Updater. But the problem was not gone
As I said I my system have two RAID1 №1 and №2. If I copy from RAID №1 my system freeze up. If I copy from RAID №2 my system work ok.
OS locate on RAID1 №1.
May be one HDD from RAID1 is dying?
I have old HDD (Seagete Barracuda 7200.12) from old system which was based AMD SB750 where I install new HDD. My old system is used as server.
I have not written, that the update of the BIOS RAID modules will solve your problem with one of your RAID arrays.
That is possible.
By the way: It is not a good idea to install the OS into a RAID1 array. If I were you, I would purchase a good 120 or 250 GB sized SSD and do a fresh install of the OS onto it.