2017-03-21 15:18:44 8656 [Note] CONNECT: Version 1.05.0003 Mar 11 2017 20:10:03
170324  9:29:03 [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.

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.22-MariaDB
key_buffer_size=65536
read_buffer_size=262144
max_used_connections=9
max_threads=1001
thread_count=3
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 513494 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x20dc9e88
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...
ha_connect.dll!MAPFAM::ReadBuffer()[filamap.cpp:365]
ha_connect.dll!TDBCSV::ReadBuffer()[tabfmt.cpp:906]
ha_connect.dll!TDBMUL::ReadDB()[tabmul.cpp:520]
ha_connect.dll!CntReadNext()[connect.cc:464]
ha_connect.dll!ha_connect::rnd_next()[ha_connect.cc:3885]
mysqld.exe!handler::ha_rnd_next()[handler.cc:2578]
mysqld.exe!rr_sequential()[records.cc:470]
mysqld.exe!sub_select()[sql_select.cc:18332]
mysqld.exe!do_select()[sql_select.cc:17968]
mysqld.exe!JOIN::exec_inner()[sql_select.cc:3221]
mysqld.exe!JOIN::exec()[sql_select.cc:2512]
mysqld.exe!mysql_select()[sql_select.cc:3447]
mysqld.exe!handle_select()[sql_select.cc:372]
mysqld.exe!mysql_execute_command()[sql_parse.cc:3442]
mysqld.exe!mysql_parse()[sql_parse.cc:7348]
mysqld.exe!dispatch_command()[sql_parse.cc:1492]
mysqld.exe!do_command()[sql_parse.cc:1109]
mysqld.exe!threadpool_process_request()[threadpool_common.cc:271]
mysqld.exe!io_completion_callback()[threadpool_win.cc:568]
kernel32.dll!BaseFormatTimeOut()
ntdll.dll!RtlEqualDomainName()
ntdll.dll!TpIsTimerSet()
kernel32.dll!BaseThreadInitThunk()
ntdll.dll!RtlUserThreadStart()

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x1ee74030): CREATE TABLE test.Alarms_Back_Multiple  AS    SELECT    *  FROM    dispoin.t_CONNECT_CSV_Zipped_DISPOIN_Server
Connection ID (thread ID): 86
Status: NOT_KILLED

Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=off

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.
2017-03-24  9:34:53 9768 [ERROR] mysqld.exe: Table '.\mysql\plugin' is marked as crashed and should be repaired
2017-03-24  9:34:53 9768 [Warning] Checking table:   '.\mysql\plugin'
2017-03-24  9:34:53 9768 [ERROR] mysql.plugin: 1 client is using or hasn't closed the table properly
2017-03-24  9:34:53 9768 [Note] CONNECT: Version 1.05.0003 Mar 11 2017 20:10:03
2017-03-24  9:34:53 9768 [Note] mysqld.exe: Aria engine: starting recovery
transactions to roll back: 1 0 (0.0 seconds); tables to flush: 1 0 (0.0 seconds); 
2017-03-24  9:34:53 9768 [Note] mysqld.exe: Aria engine: recovery done
2017-03-24 09:34:53 2628 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.
2017-03-24  9:34:53 9768 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-03-24  9:34:53 9768 [Note] InnoDB: The InnoDB memory heap is disabled
2017-03-24  9:34:53 9768 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2017-03-24  9:34:53 9768 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2017-03-24  9:34:53 9768 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-03-24  9:34:53 9768 [Note] InnoDB: Using generic crc32 instructions
2017-03-24  9:34:53 9768 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2017-03-24  9:34:53 9768 [Note] InnoDB: Completed initialization of buffer pool
2017-03-24  9:34:53 9768 [Note] InnoDB: Highest supported file format is Barracuda.
2017-03-24  9:34:53 9768 [Note] InnoDB: The log sequence numbers 1616918 and 1616918 in ibdata files do not match the log sequence number 7747465438 in the ib_logfiles!
2017-03-24  9:34:53 9768 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer...
2017-03-24  9:34:54 9768 [Note] InnoDB: 128 rollback segment(s) are active.
2017-03-24  9:34:54 9768 [Note] InnoDB: Waiting for purge to start
2017-03-24  9:34:54 9768 [Note] InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.35-80.0 started; log sequence number 7747465438
2017-03-24  9:34:54 5924 [Note] InnoDB: Dumping buffer pool(s) not yet started
2017-03-24  9:34:54 9768 [Note] Plugin 'FEEDBACK' is disabled.
2017-03-24  9:34:54 9768 [Note] Server socket created on IP: '::'.
2017-03-24  9:34:54 9768 [Note] C:\Program Files\MariaDB 10.1\bin\mysqld.exe: ready for connections.
Version: '10.1.22-MariaDB'  socket: ''  port: 3305  mariadb.org binary distribution
170324  9:39:29 [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.

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.22-MariaDB
key_buffer_size=65536
read_buffer_size=262144
max_used_connections=4
max_threads=1001
thread_count=2
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 513494 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x1e0cd708
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...
ha_connect.dll!MAPFAM::ReadBuffer()[filamap.cpp:365]
ha_connect.dll!TDBCSV::ReadBuffer()[tabfmt.cpp:906]
ha_connect.dll!TDBMUL::ReadDB()[tabmul.cpp:520]
ha_connect.dll!CntReadNext()[connect.cc:464]
ha_connect.dll!ha_connect::rnd_next()[ha_connect.cc:3885]
mysqld.exe!handler::ha_rnd_next()[handler.cc:2578]
mysqld.exe!rr_sequential()[records.cc:470]
mysqld.exe!sub_select()[sql_select.cc:18332]
mysqld.exe!do_select()[sql_select.cc:17968]
mysqld.exe!JOIN::exec_inner()[sql_select.cc:3221]
mysqld.exe!JOIN::exec()[sql_select.cc:2512]
mysqld.exe!mysql_select()[sql_select.cc:3447]
mysqld.exe!handle_select()[sql_select.cc:372]
mysqld.exe!mysql_execute_command()[sql_parse.cc:3442]
mysqld.exe!mysql_parse()[sql_parse.cc:7348]
mysqld.exe!dispatch_command()[sql_parse.cc:1492]
mysqld.exe!do_command()[sql_parse.cc:1109]
mysqld.exe!threadpool_process_request()[threadpool_common.cc:271]
mysqld.exe!io_completion_callback()[threadpool_win.cc:568]
kernel32.dll!BaseFormatTimeOut()
ntdll.dll!RtlEqualDomainName()
ntdll.dll!TpIsTimerSet()
kernel32.dll!BaseThreadInitThunk()
ntdll.dll!RtlUserThreadStart()

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x1e4fef60): CREATE TABLE test.Alarms_Back_Multiple  AS    SELECT    *  FROM    dispoin.t_CONNECT_CSV_Zipped_DISPOIN_Server
Connection ID (thread ID): 4
Status: NOT_KILLED

Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=off

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.
2017-03-24  9:54:49 5104 [Note] CONNECT: Version 1.05.0003 Mar 11 2017 20:10:03
2017-03-24  9:54:49 5104 [Note] mysqld.exe: Aria engine: starting recovery
transactions to roll back: 1 0 (0.0 seconds); tables to flush: 1 0 (0.0 seconds); 
2017-03-24  9:54:49 5104 [Note] mysqld.exe: Aria engine: recovery done
2017-03-24 09:54:49 13f0 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.
2017-03-24  9:54:49 5104 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-03-24  9:54:49 5104 [Note] InnoDB: The InnoDB memory heap is disabled
2017-03-24  9:54:49 5104 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2017-03-24  9:54:49 5104 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2017-03-24  9:54:49 5104 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-03-24  9:54:49 5104 [Note] InnoDB: Using generic crc32 instructions
2017-03-24  9:54:49 5104 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2017-03-24  9:54:49 5104 [Note] InnoDB: Completed initialization of buffer pool
2017-03-24  9:54:49 5104 [Note] InnoDB: Highest supported file format is Barracuda.
2017-03-24  9:54:49 5104 [Note] InnoDB: The log sequence numbers 1616918 and 1616918 in ibdata files do not match the log sequence number 7747465448 in the ib_logfiles!
2017-03-24  9:54:50 5104 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer...
2017-03-24  9:54:50 5104 [Note] InnoDB: 128 rollback segment(s) are active.
2017-03-24  9:54:50 5104 [Note] InnoDB: Waiting for purge to start
2017-03-24  9:54:50 5104 [Note] InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.35-80.0 started; log sequence number 7747465448
2017-03-24  9:54:50 1072 [Note] InnoDB: Dumping buffer pool(s) not yet started
2017-03-24  9:54:50 5104 [Note] Plugin 'FEEDBACK' is disabled.
2017-03-24  9:54:50 5104 [Note] Server socket created on IP: '::'.
2017-03-24  9:54:50 5104 [Note] C:\Program Files\MariaDB 10.1\bin\mysqld.exe: ready for connections.
Version: '10.1.22-MariaDB'  socket: ''  port: 3305  mariadb.org binary distribution
170324  9:58:02 [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.

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.22-MariaDB
key_buffer_size=65536
read_buffer_size=262144
max_used_connections=3
max_threads=1001
thread_count=2
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 513494 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x1e164d58
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...
ha_connect.dll!MAPFAM::ReadBuffer()[filamap.cpp:365]
ha_connect.dll!TDBCSV::ReadBuffer()[tabfmt.cpp:906]
ha_connect.dll!TDBMUL::ReadDB()[tabmul.cpp:520]
ha_connect.dll!CntReadNext()[connect.cc:464]
ha_connect.dll!ha_connect::rnd_next()[ha_connect.cc:3885]
mysqld.exe!handler::ha_rnd_next()[handler.cc:2578]
mysqld.exe!rr_sequential()[records.cc:470]
mysqld.exe!sub_select()[sql_select.cc:18332]
mysqld.exe!do_select()[sql_select.cc:17968]
mysqld.exe!JOIN::exec_inner()[sql_select.cc:3221]
mysqld.exe!JOIN::exec()[sql_select.cc:2512]
mysqld.exe!mysql_select()[sql_select.cc:3447]
mysqld.exe!handle_select()[sql_select.cc:372]
mysqld.exe!execute_sqlcom_select()[sql_parse.cc:5920]
mysqld.exe!mysql_execute_command()[sql_parse.cc:2979]
mysqld.exe!mysql_parse()[sql_parse.cc:7348]
mysqld.exe!dispatch_command()[sql_parse.cc:1492]
mysqld.exe!do_command()[sql_parse.cc:1109]
mysqld.exe!threadpool_process_request()[threadpool_common.cc:271]
mysqld.exe!io_completion_callback()[threadpool_win.cc:568]
kernel32.dll!BaseFormatTimeOut()
ntdll.dll!RtlEqualDomainName()
ntdll.dll!TpIsTimerSet()
kernel32.dll!BaseThreadInitThunk()
ntdll.dll!RtlUserThreadStart()

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x1e1735c0): SELECT  *FROM  dispoin.t_CONNECT_CSV_Zipped_DISPOIN_Server
Connection ID (thread ID): 3
Status: NOT_KILLED

Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=off

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.