2018-09-17 18:06:43 21e4 InnoDB: Operating system error number 38 in a file operation. InnoDB

2018-09-17 18:06:43 8676 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2018-09-17 18:06:43 8676 [Note] InnoDB: The InnoDB memory heap is disabled
2018-09-17 18:06:43 8676 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2018-09-17 18:06:43 8676 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2018-09-17 18:06:43 8676 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-09-17 18:06:43 8676 [Note] InnoDB: Using generic crc32 instructions
2018-09-17 18:06:43 8676 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2018-09-17 18:06:43 8676 [Note] InnoDB: Completed initialization of buffer pool
2018-09-17 18:06:43 8676 [Note] InnoDB: Highest supported file format is Barracuda.
2018-09-17 18:06:43 8676 [Note] InnoDB: The log sequence number 1835037 in ibdata file do not match the log sequence number 175039819 in the ib_logfiles!
2018-09-17 18:06:43 21e4 InnoDB: Operating system error number 38 in a file operation.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
InnoDB: Operation read to file d:\win32-packages\build\src\storage\xtradb\os\os0file.cc and at line 3235
2018-09-17 18:06:43 8676 [ERROR] InnoDB: File (unknown): 'read' returned OS error 238. Cannot continue operation
180917 18:06:43 [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 https://mariadb.com/kb/en/reporting-bugs

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.34-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 = 787136 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!parse_user()
mysqld.exe!parse_user()
mysqld.exe!parse_user()
mysqld.exe!parse_user()
mysqld.exe!parse_user()
mysqld.exe!parse_user()
mysqld.exe!parse_user()
mysqld.exe!parse_user()
mysqld.exe!parse_user()
mysqld.exe!parse_user()
mysqld.exe!?ha_initialize_handlerton@@YAHPAUst_plugin_int@@@Z()
mysqld.exe!?plugin_init@@YAHPAHPAPADH@Z()
mysqld.exe!?plugin_init@@YAHPAHPAPADH@Z()
mysqld.exe!?init_net_server_extension@@YAXPAVTHD@@@Z()
mysqld.exe!?win_main@@YAHHPAPAD@Z()
mysqld.exe!?mysql_service@@YAHPAX@Z()
mysqld.exe!strxnmov()
KERNEL32.DLL!BaseThreadInitThunk()
ntdll.dll!RtlUnicodeStringToInteger()
ntdll.dll!RtlUnicodeStringToInteger()
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.