Windows 10 Enterprise - MYSQL shutdown unexpectedly

Problems with the Windows version of XAMPP, questions, comments, and anything related.

Windows 10 Enterprise - MYSQL shutdown unexpectedly

Postby Ka Tech » 08. August 2015 09:36

I've installed Windows 10 Enterprise 64bit on my machine (clean install not upgrade) and attempting to install Apache, PHP and MySQL on my machine to use for local web development. In short I keep running into an error "MySQL shutdown unexpectedly". I've attempted to install using XAMPP as well as WAMP on my machine and still run into the identical error. That is Apache connects and works on both XAMPP and WAMP however I get a MySQL error identical on both XAMPP and WAMP.

So far from all the research I've done please find a synopsis of my situation and the solutions I've tried on XAMPP. I'm thinking this is to do with Windows 10. Also as a side note I'm using bootcamp on my MacBook 12 inch so not sure if this adding to the problem but I would not have thought so.

1.Apache running on port 80:433 for XAMPP
XAMP I get:
8:50:59 AM [mysql] Error: MySQL shutdown unexpectedly.
8:50:59 AM [mysql] This may be due to a blocked port, missing dependencies,
8:50:59 AM [mysql] improper privileges, a crash, or a shutdown by another method.
8:50:59 AM [mysql] Press the Logs button to view error logs and check
8:50:59 AM [mysql] the Windows Event Viewer for more clues
8:50:59 AM [mysql] If you need more help, copy and post this
8:50:59 AM [mysql] entire log window on the forums

2.Turned off windows firewall, same errors

3.I've checked for skype but it is actually not installed on my machine.Also checked control panel -> view local services, skype is not there nor running Tried netstat-b in the command prompt and I can't see anything with port 80. Also tried netstat -aon | findstr :80, only TCP 192.168.0.10:49556 23.205.116.42:80 ESTABLISHED 1884. Note: If the port was an issue Apache should not be working

4.I checked the control panel -> view local services there is no World Wide Web Publishing Service.

5.Tried deleting ib_logfile1, ib_logfile and ibdata1. As well as appending my.ini with innodb_force_recovery = 1. I get a slightly different error which I put below.

6.I also tried innodb_flush_method=normal. I get errors which I have provided a log below.

I'm pretty much out of options and about to give into the fact that MySQL may not work on my windows 10 machine. But before I do any help would be appreciated.

Error Logs:
2015-08-08 08:31:08 7024 [Note] Plugin 'FEDERATED' is disabled.
2015-08-08 08:31:08 18ec 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.
2015-08-08 08:31:08 7024 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-08-08 08:31:08 7024 [Note] InnoDB: The InnoDB memory heap is disabled
2015-08-08 08:31:08 7024 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-08-08 08:31:08 7024 [Note] InnoDB: Memory barrier is not used
2015-08-08 08:31:08 7024 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-08-08 08:31:08 7024 [Note] InnoDB: Not using CPU crc32 instructions
2015-08-08 08:31:08 7024 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-08-08 08:31:08 7024 [Note] InnoDB: Completed initialization of buffer pool
2015-08-08 08:31:08 7024 [Note] InnoDB: Highest supported file format is Barracuda.
2015-08-08 08:31:08 18ec InnoDB: Operating system error number 87 in a file operation.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
2015-08-08 08:31:08 7024 [ERROR] InnoDB: File C:\wamp\mysql\data\ib_logfile0: 'aio read' returned

Error Log @ innodb_force_recovery = 1
2015-08-08 09:32:05 3804 [Note] Plugin 'FEDERATED' is disabled.
2015-08-08 09:32:05 1bf8 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.
2015-08-08 09:32:05 3804 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-08-08 09:32:05 3804 [Note] InnoDB: The InnoDB memory heap is disabled
2015-08-08 09:32:05 3804 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-08-08 09:32:05 3804 [Note] InnoDB: Memory barrier is not used
2015-08-08 09:32:05 3804 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-08-08 09:32:05 3804 [Note] InnoDB: Not using CPU crc32 instructions
2015-08-08 09:32:05 3804 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-08-08 09:32:05 3804 [Note] InnoDB: Completed initialization of buffer pool
2015-08-08 09:32:05 3804 [Note] InnoDB: The first specified data file C:\xampp\mysql\data\ibdata1 did not exist: a new database to be created!
2015-08-08 09:32:05 3804 [Note] InnoDB: Setting file C:\xampp\mysql\data\ibdata1 size to 10 MB
2015-08-08 09:32:05 3804 [Note] InnoDB: Database physically writes the file full: wait...
2015-08-08 09:32:05 3804 [Note] InnoDB: Setting log file C:\xampp\mysql\data\ib_logfile101 size to 5 MB
2015-08-08 09:32:05 3804 [Note] InnoDB: Setting log file C:\xampp\mysql\data\ib_logfile1 size to 5 MB
2015-08-08 09:32:05 1bf8 InnoDB: Operating system error number 87 in a file operation.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
2015-08-08 09:32:05 3804 [ERROR] InnoDB: File C:\xampp\mysql\data\ib_logfile101: 'aio write' returned OS error 187. Cannot continue operation

Error Log @ innodb_flush_method=normal
2015-08-08 18:57:00 2100 [Note] Plugin 'FEDERATED' is disabled.
2015-08-08 18:57:00 1b50 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.
2015-08-08 18:57:00 2100 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-08-08 18:57:00 2100 [Note] InnoDB: The InnoDB memory heap is disabled
2015-08-08 18:57:00 2100 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-08-08 18:57:00 2100 [Note] InnoDB: Memory barrier is not used
2015-08-08 18:57:00 2100 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-08-08 18:57:00 2100 [Note] InnoDB: Not using CPU crc32 instructions
2015-08-08 18:57:00 2100 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-08-08 18:57:00 2100 [Note] InnoDB: Completed initialization of buffer pool
2015-08-08 18:57:00 2100 [Note] InnoDB: The first specified data file C:\xampp\mysql\data\ibdata1 did not exist: a new database to be created!
2015-08-08 18:57:00 2100 [Note] InnoDB: Setting file C:\xampp\mysql\data\ibdata1 size to 10 MB
2015-08-08 18:57:00 2100 [Note] InnoDB: Database physically writes the file full: wait...
2015-08-08 18:57:00 2100 [Note] InnoDB: Setting log file C:\xampp\mysql\data\ib_logfile101 size to 5 MB
2015-08-08 18:57:01 2100 [Note] InnoDB: Setting log file C:\xampp\mysql\data\ib_logfile1 size to 5 MB
2015-08-08 18:57:01 1b50 InnoDB: Operating system error number 87 in a file operation.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
2015-08-08 18:57:01 2100 [ERROR] InnoDB: File C:\xampp\mysql\data\ib_logfile101: 'aio write' returned OS error 187. Cannot continue operation
Ka Tech
 
Posts: 1
Joined: 08. August 2015 09:25
Operating System: Windows 10

Re: Windows 10 Enterprise - MYSQL shutdown unexpectedly

Postby Debugged » 08. August 2015 12:12

Error 87 from https://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html means "The parameter is incorrect".

Not sure what that means exactly but could this be due to an OS path being wrong?

I have just started using XAMPP and am testing the portable version from here: http://sourceforge.net/projects/xampp/files/XAMPP%20Windows/5.6.8/ -> xampp-portable-win32-5.6.8-0-VC11.7z

Download that, extract it to D:\ , assuming you have an OS partition C:\ and a Data partition D:\, then BEFORE running xampp-control.exe in D:\xampp right-click -> properties -> compatibility tab -> at the bottom Change settings for all users -> at the bottom again Privilege Level and tick Run this program as an admin -> Apply -> Ok.

Then start xampp-control.exe in D:\xampp and see if you can run Apache and MySQL like that.

Again, I am not sure what the parameter error means but at least you could give it a shot like that.

Then, before installing Win10 what OS did you run? Win 7? By any chance did you perhaps make an OS system image? I create OS images regularly with Macrium Reflect Free and like that can test out software to my heart's content, if something messes up I simply restore a clean OS state and have nothing to worry about. Sooo in case you have a clean Win 7 image, restore that to your OS partition C:\ and try with the installer version 5.6.11 from the main index/download site of the XAMPP website if it does not work with the portable version from inside a folder on your current Win 10 installation.

Please NOTE I am no superhero with regards to that error, merely trying to help, so perhaps if it works out of a folder you can narrow down that you might have to edit a "parameter" on the OS (Win 10), since it is giving you an OS error.

Hope this helps in any way.
Forgive me if all this has nothing to do with this particular error.
100% pure perseverance, nothing else!
Debugged
 
Posts: 21
Joined: 07. August 2015 23:26
Operating System: Win 7 Ultimate 64 SP1


Return to XAMPP for Windows

Who is online

Users browsing this forum: No registered users and 34 guests