*** URGENT*** MySQL unable to start

[90skaashi]

4:18:30 pm [mysql] Error: MySQL shutdown unexpectedly.
4:18:30 pm [mysql] This may be due to a blocked port, missing dependencies,
4:18:30 pm [mysql] improper privileges, a crash, or a shutdown by another method.
4:18:30 pm [mysql] Press the Logs button to view error logs and check
4:18:30 pm [mysql] the Windows Event Viewer for more clues
4:18:30 pm [mysql] If you need more help, copy and post this
4:18:30 pm [mysql] entire log window on the forums

this error message appears when i try to start MySQL on XAMPP

2021-06-03 16:16:38 1028 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.
2021-06-03 16:16:38 4136 [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.

2021-06-03 16:16:38 4136 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2021-06-03 16:16:38 4136 [Note] InnoDB: The InnoDB memory heap is disabled
2021-06-03 16:16:38 4136 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2021-06-03 16:16:38 4136 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2021-06-03 16:16:38 4136 [Note] InnoDB: Compressed tables use zlib 1.2.3
2021-06-03 16:16:38 4136 [Note] InnoDB: Using generic crc32 instructions
2021-06-03 16:16:38 4136 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2021-06-03 16:16:38 4136 [Note] InnoDB: Completed initialization of buffer pool
2021-06-03 16:16:38 4136 [Note] InnoDB: Setting log file C:\xampp\mysql\data\ib_logfile101 size to 5 MB
2021-06-03 16:16:38 4136 [Note] InnoDB: Setting log file C:\xampp\mysql\data\ib_logfile1 size to 5 MB
2021-06-03 16:16:38 1028 InnoDB: Error: Write to file C:\xampp\mysql\data\ib_logfile101 failed at offset 0.
InnoDB: 512 bytes should have been written, only 12028275 were written.
InnoDB: Operating system error number 87.
InnoDB: Check that your OS and file system support files of this size.
InnoDB: Check also that the disk is not full or a disk quota exceeded.
InnoDB: FormatMessage: Error number 87 means 'The parameter is incorrect.

'.
InnoDB: Error number 87 means 'Unknown error'.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
2021-06-03 16:16:38 1028 InnoDB: Operating system error number 87 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 os_file_write_func to file D:\win32-packages\build\src\storage\xtradb\os\os0file.cc and at line 5117
2021-06-03 16:16:38 4136 [ERROR] InnoDB: File C:\xampp\mysql\data\ib_logfile101: 'os_file_write_func' returned OS error 287. Cannot continue operation
210603 16:16:38 [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.21-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 = 787106 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!my_wildcmp_mb_bin()
mysqld.exe!??2Item_change_record@@SAPAXIPAX@Z()
mysqld.exe!?get_trg_event_map@Update_rows_log_event@@UAEEXZ()
mysqld.exe!?get_trg_event_map@Update_rows_log_event@@UAEEXZ()
mysqld.exe!?get_trg_event_map@Update_rows_log_event@@UAEEXZ()
mysqld.exe!?get_trg_event_map@Update_rows_log_event@@UAEEXZ()
mysqld.exe!?get_trg_event_map@Update_rows_log_event@@UAEEXZ()
mysqld.exe!?get_trg_event_map@Update_rows_log_event@@UAEEXZ()
mysqld.exe!?get_trg_event_map@Update_rows_log_event@@UAEEXZ()
mysqld.exe!?get_trg_event_map@Update_rows_log_event@@UAEEXZ()
mysqld.exe!?get_trg_event_map@Update_rows_log_event@@UAEEXZ()
mysqld.exe!?set_required_privilege@Settable_routine_parameter@@UAEX_N@Z()
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!my_wildcmp_mb_bin()
KERNEL32.DLL!BaseThreadInitThunk()
ntdll.dll!RtlGetAppContainerNamedObjectPath()
ntdll.dll!RtlGetAppContainerNamedObjectPath()
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.
2021-06-03 16:18:28 1b38 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.
2021-06-03 16:18:28 6968 [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.

2021-06-03 16:18:28 6968 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2021-06-03 16:18:28 6968 [Note] InnoDB: The InnoDB memory heap is disabled
2021-06-03 16:18:28 6968 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2021-06-03 16:18:28 6968 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2021-06-03 16:18:28 6968 [Note] InnoDB: Compressed tables use zlib 1.2.3
2021-06-03 16:18:28 6968 [Note] InnoDB: Using generic crc32 instructions
2021-06-03 16:18:28 6968 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2021-06-03 16:18:28 6968 [Note] InnoDB: Completed initialization of buffer pool
2021-06-03 16:18:28 6968 [Note] InnoDB: Setting log file C:\xampp\mysql\data\ib_logfile101 size to 5 MB
2021-06-03 16:18:28 6968 [Note] InnoDB: Setting log file C:\xampp\mysql\data\ib_logfile1 size to 5 MB
2021-06-03 16:18:28 1b38 InnoDB: Error: Write to file C:\xampp\mysql\data\ib_logfile101 failed at offset 0.
InnoDB: 512 bytes should have been written, only 12028275 were written.
InnoDB: Operating system error number 87.
InnoDB: Check that your OS and file system support files of this size.
InnoDB: Check also that the disk is not full or a disk quota exceeded.
InnoDB: FormatMessage: Error number 87 means 'The parameter is incorrect.

'.
InnoDB: Error number 87 means 'Unknown error'.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
2021-06-03 16:18:28 1b38 InnoDB: Operating system error number 87 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 os_file_write_func to file D:\win32-packages\build\src\storage\xtradb\os\os0file.cc and at line 5117
2021-06-03 16:18:28 6968 [ERROR] InnoDB: File C:\xampp\mysql\data\ib_logfile101: 'os_file_write_func' returned OS error 287. Cannot continue operation
210603 16:18:28 [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.21-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 = 787106 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!my_wildcmp_mb_bin()
mysqld.exe!??2Item_change_record@@SAPAXIPAX@Z()
mysqld.exe!?get_trg_event_map@Update_rows_log_event@@UAEEXZ()
mysqld.exe!?get_trg_event_map@Update_rows_log_event@@UAEEXZ()
mysqld.exe!?get_trg_event_map@Update_rows_log_event@@UAEEXZ()
mysqld.exe!?get_trg_event_map@Update_rows_log_event@@UAEEXZ()
mysqld.exe!?get_trg_event_map@Update_rows_log_event@@UAEEXZ()
mysqld.exe!?get_trg_event_map@Update_rows_log_event@@UAEEXZ()
mysqld.exe!?get_trg_event_map@Update_rows_log_event@@UAEEXZ()
mysqld.exe!?get_trg_event_map@Update_rows_log_event@@UAEEXZ()
mysqld.exe!?get_trg_event_map@Update_rows_log_event@@UAEEXZ()
mysqld.exe!?set_required_privilege@Settable_routine_parameter@@UAEX_N@Z()
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!my_wildcmp_mb_bin()
KERNEL32.DLL!BaseThreadInitThunk()
ntdll.dll!RtlGetAppContainerNamedObjectPath()
ntdll.dll!RtlGetAppContainerNamedObjectPath()
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.

this is what appears in the log