Bug #89940 Error: MySQL shutdown unexpectedly.
Submitted: 7 Mar 2018 6:50 Modified: 7 Mar 2018 8:02
Reporter: Frederik Smith Email Updates:
Status: Unsupported Impact on me:
None 
Category:MySQL Server Severity:S3 (Non-critical)
Version:10.1.30-MariaDB OS:Microsoft Windows (Win10)
Assigned to: CPU Architecture:Other (x64)
Tags: error, shutdown, win10

[7 Mar 2018 6:50] Frederik Smith
Description:
Installation via XAMPP, says:
07:36:20  [mysql] 	Error: MySQL shutdown unexpectedly.
07:36:20  [mysql] 	This may be due to a blocked port, missing dependencies, 
07:36:20  [mysql] 	improper privileges, a crash, or a shutdown by another method.
07:36:20  [mysql] 	Press the Logs button to view error logs and check
07:36:20  [mysql] 	the Windows Event Viewer for more clues
07:36:20  [mysql] 	If you need more help, copy and post this
07:36:20  [mysql] 	entire log window on the forums

MYSQL_ERROR.TXT FILE:
2018-03-07 07:36:13 11d8 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.
2018-03-07  7:36:13 4568 [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.

2018-03-07  7:36:13 4568 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2018-03-07  7:36:13 4568 [Note] InnoDB: The InnoDB memory heap is disabled
2018-03-07  7:36:13 4568 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2018-03-07  7:36:13 4568 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2018-03-07  7:36:13 4568 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-03-07  7:36:13 4568 [Note] InnoDB: Using generic crc32 instructions
2018-03-07  7:36:13 4568 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2018-03-07  7:36:13 4568 [Note] InnoDB: Completed initialization of buffer pool
2018-03-07  7:36:13 4568 [Note] InnoDB: Highest supported file format is Barracuda.
2018-03-07 07:36:13 11d8  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 read to file D:\win32-packages\build\src\storage\xtradb\os\os0file.cc and at line 3199
2018-03-07  7:36:13 4568 [ERROR] InnoDB: File (unknown): 'read' returned OS error 287. Cannot continue operation
180307  7:36:13 [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.30-MariaDB
key_buffer_size=25165824
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 = 795321 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!?compare_ulonglong@@YAHPB_K0@Z()
mysqld.exe!?compare_ulonglong@@YAHPB_K0@Z()
mysqld.exe!?compare_ulonglong@@YAHPB_K0@Z()
mysqld.exe!no_key()
mysqld.exe!no_key()
mysqld.exe!no_key()
mysqld.exe!?compare_ulonglong@@YAHPB_K0@Z()
mysqld.exe!?str_result@Item@@UAEPAVString@@PAV2@@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!strxnmov()
KERNEL32.DLL!BaseThreadInitThunk()
ntdll.dll!RtlSubscribeWnfStateChangeNotification()
ntdll.dll!RtlSubscribeWnfStateChangeNotification()
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.

DistributedCOM FROM EVENTVIEWER:
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{6B3B8D23-FA8D-40B9-8DBD-B950333E2C52}
 and APPID 
{4839DDB7-58C2-48F5-8283-E1D1807D0D7D}
 to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

How to repeat:
Happens everytime mysqld is started.

Suggested fix:
"This security permission can be modified using the Component Services administrative tool."
[7 Mar 2018 7:09] Frederik Smith
Solution found via: https://community.apachefriends.org/f/viewtopic.php?f=16&t=72437
[7 Mar 2018 8:02] MySQL Verification Team
Thank you for the bug report. Please file the bug report on MariaDB bug system. Thanks.