![MySQL 服务器崩溃,错误代码:0xe06d7363](https://linux22.com/image/761013/MySQL%20%E6%9C%8D%E5%8A%A1%E5%99%A8%E5%B4%A9%E6%BA%83%EF%BC%8C%E9%94%99%E8%AF%AF%E4%BB%A3%E7%A0%81%EF%BC%9A0xe06d7363.png)
Mysql 服务器频繁崩溃,出现以下异常,但无法找到崩溃的确切原因,如能提供任何建议或帮助我将不胜感激!
MySQL版本为5.7.17和Windows Server 2012 R2标准
04:31:03 UTC - mysqld got exception 0xe06d7363 ; 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=304087040 read_buffer_size=65536 max_used_connections=610 max_threads=1600 thread_count=498 connection_count=498 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 828410 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... 7ffd7254908c KERNELBASE.dll!RaiseException() 7ff77ee1f407 mysqld.exe!my_wildcmp_mb() 7ff77ee574c1 mysqld.exe!my_wildcmp_mb() 7ff77ec26365 mysqld.exe!?reserve@?$vector@EV?$allocator@E@std@@@std@@QEAAX_K@Z() 7ff77ec257a0 mysqld.exe!?reserve@?$vector@EV?$allocator@E@std@@@std@@QEAAX_K@Z() 7ff77ec2ac08 mysqld.exe!?reserve@?$vector@EV?$allocator@E@std@@@std@@QEAAX_K@Z() 7ff77ec2a923 mysqld.exe!?reserve@?$vector@EV?$allocator@E@std@@@std@@QEAAX_K@Z() 7ff77ecccb4c mysqld.exe!?reserve@?$vector@EV?$allocator@E@std@@@std@@QEAAX_K@Z() 7ff77eccd7f2 mysqld.exe!?reserve@?$vector@EV?$allocator@E@std@@@std@@QEAAX_K@Z() 7ffd735c13d2 KERNEL32.DLL!BaseThreadInitThunk() 7ffd752254f4 ntdll.dll!RtlUserThreadStart() The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains