2017-03-09 10:32:36 4232 [Note] CONNECT: Version 1.05.0001 Jan 17 2017 20:44:09 2017-03-09 10:32:37 4232 [Note] InnoDB: Using mutexes to ref count buffer pool pages 2017-03-09 10:32:37 4232 [Note] InnoDB: The InnoDB memory heap is disabled 2017-03-09 10:32:37 4232 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions 2017-03-09 10:32:37 4232 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier 2017-03-09 10:32:37 4232 [Note] InnoDB: Compressed tables use zlib 1.2.3 2017-03-09 10:32:37 4232 [Note] InnoDB: Using generic crc32 instructions 2017-03-09 10:32:37 4232 [Note] InnoDB: Initializing buffer pool, size = 1022.0M 2017-03-09 10:32:37 4232 [Note] InnoDB: Completed initialization of buffer pool 2017-03-09 10:32:37 4232 [Note] InnoDB: Highest supported file format is Barracuda. 2017-03-09 10:32:37 4232 [Note] InnoDB: 128 rollback segment(s) are active. 2017-03-09 10:32:37 4232 [Note] InnoDB: Waiting for purge to start 2017-03-09 10:32:37 4232 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.34-79.1 started; log sequence number 1691932 2017-03-09 10:32:37 4024 [Note] InnoDB: Dumping buffer pool(s) not yet started 2017-03-09 10:32:37 4232 [Note] Plugin 'FEEDBACK' is disabled. 2017-03-09 10:32:37 4232 [Note] Server socket created on IP: '::'. 2017-03-09 10:32:37 4232 [Note] C:\Program Files (x86)\MariaDB 10.1\bin\mysqld.exe: ready for connections. Version: '10.1.21-MariaDB' socket: '' port: 3306 mariadb.org binary distribution 2017-03-09 10:33:14 5508 [Warning] IP address '10.10.10.89' could not be resolved: No such host is known. 170309 10:33:16 [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.21-MariaDB key_buffer_size=134217728 read_buffer_size=131072 max_used_connections=1 max_threads=1001 thread_count=1 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2311202 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x55b3b8c8 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!TDBODBC::OpenDB()[tabodbc.cpp:877] ha_connect.dll!ha_connect::rnd_init()[ha_connect.cc:3747] ha_connect.dll!ha_connect::index_init()[ha_connect.cc:3435] mysqld.exe!QUICK_RANGE_SELECT::reset()[opt_range.cc:11120] mysqld.exe!mysql_update()[sql_update.cc:605] mysqld.exe!mysql_execute_command()[sql_parse.cc:3752] mysqld.exe!mysql_parse()[sql_parse.cc:7319] mysqld.exe!dispatch_command()[sql_parse.cc:1488] mysqld.exe!do_command()[sql_parse.cc:1143] mysqld.exe!threadpool_process_request()[threadpool_common.cc:271] mysqld.exe!io_completion_callback()[threadpool_win.cc:568] kernel32.dll!GetCPInfoExW() ntdll.dll!WinSqmStartSession() ntdll.dll!TpSetTimer() kernel32.dll!BaseThreadInitThunk() ntdll.dll!RtlInitializeExceptionChain() ntdll.dll!RtlInitializeExceptionChain() Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (0x55b49ee0): UPDATE ODBC_EXCEPT SET EMPL='',ITEM='', ORDERNO='',LOCAT=0,JACTDATE=0,COMMEN='' ,PROGRAM='',MADEBY='',ACTTIME='',LOGGEDIN='',NOTES='' WHERE JACTDATE<158654 and EMPL='JEC' Connection ID (thread ID): 2 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.