Mysql startet nicht mehr

[katarakt]

Nun hat es mich auch mal erwischt, von einem auf den kommenden Tag ging mit mal MYSQl nicht mehr.
Folgendes steht in der LOG

Code: Select all

 151222  9:52:07 [Note] InnoDB: Using mutexes to ref count buffer pool pages
151222  9:52:07 [Note] InnoDB: The InnoDB memory heap is disabled
151222  9:52:07 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
151222  9:52:07 [Note] InnoDB: Memory barrier is not used
151222  9:52:07 [Note] InnoDB: Compressed tables use zlib 1.2.3
151222  9:52:07 [Note] InnoDB: Not using CPU crc32 instructions
151222  9:52:07 [Note] InnoDB: Initializing buffer pool, size = 16.0M
151222  9:52:07 [Note] InnoDB: Completed initialization of buffer pool
151222  9:52:07 [Note] InnoDB: Highest supported file format is Barracuda.
151222  9:52:07 [Note] InnoDB: Log scan progressed past the checkpoint lsn 67840292
151222  9:52:07 [Note] InnoDB: Database was not shutdown normally!
151222  9:52:07 [Note] InnoDB: Starting crash recovery.
151222  9:52:07 [Note] InnoDB: Reading tablespace information from the .ibd files...
151222  9:52:10 [Note] InnoDB: Restoring possible half-written data pages
151222  9:52:10 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 67848154
151222  9:52:11 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 151222  9:52:11 [ERROR] mysqld got exception 0xc0000005 ;
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.

danke im voraus

[katarakt]

Âch darunte rsteht noch

To report this bug, see http://kb.askmonty.org/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.0.17-MariaDB
key_buffer_size=16777216
read_buffer_size=262144
max_used_connections=0
max_threads=501
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 403207 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went