mysqld.exe已停止在xampp windows中工作？

Mysqld.exe已停止在xampp窗口中工作。 当XAMPP软件在后台运行时，我启动了我的计算机，MySQL不会启动

2017-11-20 11:05:36 14f4 InnoDB:警告：正在使用 innodb_其他_内存_池_大小不推荐使用。此选项可能是 在将来的版本中与选项一起删除 innodb使用\u sys\u malloc和innodb的内部内存分配器。 2017-11-20 11:05:36 5364[注]InnoDB:InnoDB_empty_free_list_算法已更改为legacy，原因是 较小的缓冲池大小。为了使用回退，增加缓冲池 至少高达20MB

2017-11-20 11:05:36 5364 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-11-20 11:05:36 5364 [Note] InnoDB: The InnoDB memory heap is disabled
2017-11-20 11:05:36 5364 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2017-11-20 11:05:36 5364 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2017-11-20 11:05:36 5364 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-11-20 11:05:36 5364 [Note] InnoDB: Using generic crc32 instructions
2017-11-20 11:05:36 5364 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2017-11-20 11:05:36 5364 [Note] InnoDB: Completed initialization of buffer pool
2017-11-20 11:05:37 5364 [Note] InnoDB: Highest supported file format is Barracuda.
2017-11-20 11:05:37 5364 [Note] InnoDB: The log sequence number 1835037 in ibdata file do not match the log sequence number

11035100176在ib_日志文件中！ 2017-11-20 11:05:37 14f4 InnoDB:文件操作中的操作系统错误号38。 InnoDB：一些操作系统错误号在 InnoDB： InnoDB:操作读取文件D:\win32 packages\build\src\storage\xtradb\os\os0file.cc和第行 3174 2017-11-20 11:05:37 5364[错误]InnoDB:文件（未知）：“读取”返回操作系统错误238。无法继续操作 171120 11:05:37[错误]mysqld获得异常0x8000003； 这可能是因为你碰到了一个bug。也有可能这个二进制文件 或者它所链接的某个库已损坏，构建不当， 或者配置错误。此错误也可能由硬件故障引起

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.25-MariaDB
key_buffer_size=16777216
read_buffer_size=262144
max_used_connections=0
max_threads=1001
thread_count=0
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 787107 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...
mysqld.exe!my_parameter_handler()
mysqld.exe!strxnmov()
mysqld.exe!?element_index@Item@@UAEPAV1@I@Z()
mysqld.exe!?element_index@Item@@UAEPAV1@I@Z()
mysqld.exe!?element_index@Item@@UAEPAV1@I@Z()
mysqld.exe!?element_index@Item@@UAEPAV1@I@Z()
mysqld.exe!?element_index@Item@@UAEPAV1@I@Z()
mysqld.exe!?element_index@Item@@UAEPAV1@I@Z()
mysqld.exe!?element_index@Item@@UAEPAV1@I@Z()
mysqld.exe!?element_index@Item@@UAEPAV1@I@Z()
mysqld.exe!?element_index@Item@@UAEPAV1@I@Z()
mysqld.exe!?fix_length_and_dec@subselect_partial_match_engine@@UAEXPAPAVItem_cache@@@Z()
mysqld.exe!?ha_initialize_handlerton@@YAHPAUst_plugin_int@@@Z()
mysqld.exe!?plugin_init@@YAHPAHPAPADH@Z()
mysqld.exe!?plugin_init@@YAHPAHPAPADH@Z()
mysqld.exe!?init_net_server_extension@@YAXPAVTHD@@@Z()
mysqld.exe!?win_main@@YAHHPAPAD@Z()
mysqld.exe!?mysql_service@@YAHPAX@Z()
mysqld.exe!strxnmov()
kernel32.dll!BaseThreadInitThunk()
ntdll.dll!RtlInitializeExceptionChain()
ntdll.dll!RtlInitializeExceptionChain()
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.

---

最近，当我试图将XAMPP安装到运行Windows 10的计算机上时，我也遇到了这个问题

如果您阅读了该程序给出的警告，您可以看到它返回了许多有关操作系统的错误。给定“D:\win32 packages\build\src\storage\xtradb\os\os0file.cc”，我假设您的计算机有多个磁盘，因此它不是C:drive

您应该尝试将XAMPP与Windows系统一起安装在C:/drive上。这为我解决了这个问题，之前我在我的E:drive上安装了它，但我无法运行mysql，但Apache运行得很好

2LDR：将XAMPP与操作系统一起安装到C:/drive，并返回反馈：）