Запустить MySQL под Windows

Есть типовой и гарантированно рабочий пакет с MySQL(MariaDB 10.1.38)+Apache (на основе XAMMP). Он успешно работает на 5 серверах. Но на одном из сервере (Windows 2012) MySQL не запускается. Старая версия MySQL на том же сервере тоже перестала запускаться. Протокол ниже. Права на файлы полные. Порты свободны. Замена папки с файлами БД на дефолтную результата не дала.

Требуется:
1. Запустить MySQL 
2. Объяснить причину проблемы

К серверу предоставляется RDP доступ. Срок выполнения работы — 2 часа. 

Предложение только для специалистов более чем с 20 позитивными отзывами. Возможны как безопасная сделка, так и перевод напрямую. 



2020-08-12 17:53:12 960 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2020-08-12 17:53:12 2400 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.

2020-08-12 17:53:12 2400 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2020-08-12 17:53:12 2400 [Note] InnoDB: The InnoDB memory heap is disabled
2020-08-12 17:53:12 2400 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2020-08-12 17:53:12 2400 [Note] InnoDB: mm_lfence() and mm_sfence() are used for memory barrier
2020-08-12 17:53:12 2400 [Note] InnoDB: Compressed tables use zlib 1.2.11
2020-08-12 17:53:12 2400 [Note] InnoDB: Using generic crc32 instructions
2020-08-12 17:53:12 2400 [Note] InnoDB: Initializing buffer pool, size = 32.0M
2020-08-12 17:53:12 2400 [Note] InnoDB: Completed initialization of buffer pool
2020-08-12 17:53:12 960 InnoDB: Operating system error number 6 in a file operation.
InnoDB: Some operating system error numbers are described at
InnoDB: dev.mysql.com/doc/refman/...
InnoDB: Operation close to file d:winx64-packagesbuildsrcstoragextradbosos0file.cc and at line 2493
2020-08-12 17:53:12 2400 [ERROR] InnoDB: File (unknown): 'close' returned OS error 206. Cannot continue operation
200812 17:53:12 [ERROR] mysqld got exception 0x80000003 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.

To report this bug, see mariadb.com/kb/en/reporti...

We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.

Server version: 10.1.38-MariaDB
key_buffer_size=16777216
read_buffer_size=262144
max_used_connections=0
max_threads=1001
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 787931 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
mysqld.exe!my_parameter_handler()
mysqld.exe!strxnmov()
mysqld.exe!strxnmov()
mysqld.exe!my_xml_set_user_data()
mysqld.exe!my_xml_set_user_data()
mysqld.exe!my_xml_set_user_data()
mysqld.exe!my_xml_set_user_data()
mysqld.exe!my_xml_set_user_data()
mysqld.exe!parse_user()
mysqld.exe!?ha_initialize_handlerton@@YAHPEAUst_plugin_int@@@Z()
mysqld.exe!?plugin_init@@YAHPEAHPEAPEADH@Z()
mysqld.exe!?plugin_init@@YAHPEAHPEAPEADH@Z()
mysqld.exe!?init_net_server_extension@@YAXPEAVTHD@@@Z()
mysqld.exe!?win_main@@YAHHPEAPEAD@Z()
mysqld.exe!?mysql_service@@YAHPEAX@Z()
mysqld.exe!strxnmov()
KERNEL32.DLL!BaseThreadInitThunk()
ntdll.dll!RtlUserThreadStart()
The manual page at dev.mysql.com/doc/mysql/e... contains
information that should help you find out what is causing the crash.