16:51:10 UTC - 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.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.

key_buffer_size=8388608
read_buffer_size=65536
max_used_connections=6
max_threads=151
thread_count=6
connection_count=6
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 58341 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x78b565d6a0
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...
7ff725871270    mysqld.exe!?copy_blob_value@Field_blob@@QEAA_NPEAUst_mem_root@@@Z()
7ff72590dc72    mysqld.exe!?mysql_prepare_blob_values@@YA_NPEAVTHD@@AEAV?$List@VItem@@@@PEAUst_mem_root@@@Z()
7ff72590ff8f    mysqld.exe!?write_record@@YAHPEAVTHD@@PEAUTABLE@@PEAVCOPY_INFO@@2@Z()
7ff72590d623    mysqld.exe!?mysql_insert@Sql_cmd_insert@@AEAA_NPEAVTHD@@PEAUTABLE_LIST@@@Z()
7ff72590c753    mysqld.exe!?execute@Sql_cmd_insert@@UEAA_NPEAVTHD@@@Z()
7ff7257456d5    mysqld.exe!?mysql_execute_command@@YAHPEAVTHD@@_N@Z()
7ff7259164b6    mysqld.exe!?execute@Prepared_statement@@AEAA_NPEAVString@@_N@Z()
7ff7259168c7    mysqld.exe!?execute_loop@Prepared_statement@@QEAA_NPEAVString@@_NPEAE2@Z()
7ff725918898    mysqld.exe!?mysqld_stmt_execute@@YAXPEAVTHD@@KKPEAEK@Z()
7ff725741140    mysqld.exe!?dispatch_command@@YA_NPEAVTHD@@PEBTCOM_DATA@@W4enum_server_command@@@Z()
7ff72574226a    mysqld.exe!?do_command@@YA_NPEAVTHD@@@Z()
7ff7256e9634    mysqld.exe!handle_connection()
7ff7260fad82    mysqld.exe!?reserve@?$vector@EV?$allocator@E@std@@@std@@QEAAX_K@Z()
7ff725e246fb    mysqld.exe!my_thread_once()
7ff7261bb39f    mysqld.exe!my_wildcmp_mb()
7ff7261bb5ea    mysqld.exe!my_wildcmp_mb()
7ffe62c02d92    KERNEL32.DLL!BaseThreadInitThunk()
7ffe65529f64    ntdll.dll!RtlUserThreadStart()

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (78b2df5c80): INSERT INTO SubjectExtras (SubjectID,FieldID,TextValue,IntegerValue,FloatValue,DateValue,BlobValue) VALUES ('1389625','2079','Infant - Toddlers',NULL,NULL,NULL,NULL) ON DUPLICATE KEY UPDATE TextValue=VALUES(TextValue),IntegerValue=VALUES(IntegerValue),FloatValue=VALUES(FloatValue),DateValue=VALUES(DateValue),BlobValue=VALUES(BlobValue)
Connection ID (thread ID): 63
Status: NOT_KILLED

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.
2015-11-10T20:36:43.150158Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2015-11-10T20:36:43.150158Z 0 [Warning] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.