Thnx for the suggestion Otomatic,
I've unchecked MSQL and ran MariaDB on port 3306, it sounded hopeful for a second.
So sad it doesn't work and I get a bunch of error reports from the log.
A snipped from the log points out perhaps a bug or even a hardware malfunction:
2017-12-03 20:05:29 11832 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2017-12-03 20:05:29 11832 [Note] InnoDB: Uses event mutexes
2017-12-03 20:05:29 11832 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-12-03 20:05:29 11832 [Note] InnoDB: Number of pools: 1
2017-12-03 20:05:29 11832 [Note] InnoDB: Using generic crc32 instructions
2017-12-03 20:05:29 11832 [Note] InnoDB: Initializing buffer pool, total size = 32M, instances = 1, chunk size = 32M
2017-12-03 20:05:29 11832 [Note] InnoDB: Completed initialization of buffer pool
2017-12-03 20:05:29 11832 [Note] InnoDB: Highest supported file format is Barracuda.
2017-12-03 20:05:29 11832 [Warning] InnoDB: Retry attempts for reading partial data failed.
2017-12-03 20:05:29 11832 [ERROR] InnoDB: Tried to read 512 bytes at offset 0, but was only able to read 0
2017-12-03 20:05:29 11832 [ERROR] InnoDB: File (unknown): 'read' returned OS error 0. Cannot continue operation
171203 20:05:29 [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]
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.2.8-MariaDB
key_buffer_size=67108864
read_buffer_size=262144
max_used_connections=0
max_threads=65537
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 70631 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()[my_init.c:259]
mysqld.exe!raise()[signal.cpp:516]
mysqld.exe!abort()[abort.cpp:71]
mysqld.exe!os_file_handle_error_cond_exit()[os0file.cc:5207]
mysqld.exe!os_file_read_page()[os0file.cc:5089]
mysqld.exe!os_file_read_func()[os0file.cc:5429]
mysqld.exe!fil_io()[fil0fil.cc:5398]
mysqld.exe!log_group_header_read()[log0log.cc:1564]
mysqld.exe!recv_find_max_checkpoint()[log0recv.cc:949]
mysqld.exe!recv_recovery_from_checkpoint_start()[log0recv.cc:3151]
mysqld.exe!innobase_start_or_create_for_mysql()[srv0start.cc:2219]
mysqld.exe!innobase_init()[ha_innodb.cc:4428]
mysqld.exe!ha_initialize_handlerton()[handler.cc:512]
mysqld.exe!plugin_initialize()[sql_plugin.cc:1413]
mysqld.exe!plugin_init()[sql_plugin.cc:1694]
mysqld.exe!init_server_components()[mysqld.cc:5256]
mysqld.exe!win_main()[mysqld.cc:5848]
mysqld.exe!mysql_service()[mysqld.cc:6107]
mysqld.exe!thread_start<void (__cdecl*)(void * __ptr64)>()[thread.cpp:115]
KERNEL32.DLL!BaseThreadInitThunk()
ntdll.dll!RtlUserThreadStart()
The manual page at [
dev.mysql.com] contains
information that should help you find out what is causing the crash.
I should mention that I'm running RAM Disk. Also running Razer Synapse and Logitech Gaming Software, which on a previous test I've stopped all their background services.
I'll try to look into the crash reports myself, but if you or anyone else sees the problem within this report at glance, I would appreciate the heads up. In any case my last resort would be getting my hands dirty with a less streamlined installation of apache/msql/php.
Edited 1 time(s). Last edit at 12/03/2017 08:41PM by isz.