MariaDB 10.3.10-10.3.13 corrupts table and refuses to start with assertion in row0sel.cc 2986

Zabbix Servers with MariaDB comes up after restart with corrupted Zabbix items table. It always affects the same table. All other tables are good.

Because of the corrupted table, MariaDB Server refuses to start with assertion in row0sel.cc line 2968.

Trying to recover the corrupted tables according to https://mariadb.com/kb/en/library/innodb-recovery-modes/ didn't work for all recovery modes from 1-6.

my.cnf:
-------
[client]
port = 3306
socket = /var/run/mysqld/mysqld.sock
[mysqld_safe]
socket = /var/run/mysqld/mysqld.sock
nice = 0
[mysqld]
pid-file = /var/run/mysqld/mysqld.pid
socket = /var/run/mysqld/mysqld.sock
port = 3306
basedir = /usr
datadir = /var/lib/mysql
tmpdir = /tmp
lc_messages_dir = /usr/share/mysql
lc_messages = en_US
skip-external-locking
max_connections = 100
connect_timeout = 5
wait_timeout = 600
max_allowed_packet = 16M
thread_cache_size = 128
sort_buffer_size = 4M
bulk_insert_buffer_size = 16M
tmp_table_size = 32M
max_heap_table_size = 32M
myisam_recover_options = BACKUP
key_buffer_size = 128M
table_open_cache = 400
myisam_sort_buffer_size = 512M
concurrent_insert = 2
read_buffer_size = 2M
read_rnd_buffer_size = 1M
query_cache_limit = 128K
query_cache_size = 64M
long_query_time = 10
expire_logs_days = 10
max_binlog_size = 100M
default_storage_engine = InnoDB
innodb_log_file_size = 1250M
innodb_log_files_in_group = 4
innodb_log_buffer_size = 1250M
innodb_flush_log_at_trx_commit = 1
innodb_buffer_pool_size = 5G
innodb_buffer_pool_instances = 4
innodb_buffer_pool_chunk_size = 1250M
innodb_file_per_table = 1
innodb_open_files = 400
innodb_io_capacity = 400
innodb_flush_method = O_DIRECT
[galera]
[mysqldump]
quick
quote-names
max_allowed_packet = 16M
[mysql]
[isamchk]
key_buffer = 16M
!include /etc/mysql/mariadb.cnf
!includedir /etc/mysql/conf.d/