You have corrupted your database, and MYSQL has failed to recover it using its automatic restart/recovery mechanism.
First this may well be caused by closing windows before stopping WAMPServer/MySQL
The answer is in the information that MySQL puts in the error log you supplied.
First, if you have a backup (ha ha) then restore your database from the backup.
Second option
Quote
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
To do this you need to edit the my.ini file,
.. If you are using WAMPServer 64bit, look for this section heading
[wampmysqld]
and change it to
[wampmysqld64]
This fixes a minor bug in the WAMPServer2.5 64bit release.
Now read and understand this and any other MYSQL help you can find
Forcing InnoDB RecoveryTo set the innodb_force_recovery flag you will need to add it and its value after the
(32bit WAMP) [wampmysqld] line
or (64bit WAMP) [wampmysqld64] line
[wampmysqld]
innodb_force_recovery = 1
For example.
No guarantees are give that this will work but before you have to throw your database away is worth a try. As per the MySQL documentation start with innodb_force_recovery = 1 and then move up one at a time until the recovery works. You will have to check the mysql error log each time to see if recovery has worked.
Remove this line when completed dont leave it there.
---------------------------------------------------------------------------------------------
(Windows 10 Pro 64bit) (Wampserver 3.3.4 64bit) Aestan Tray Menu 3.2.5.4
<Apache versions MULTIPE> <PHP versions MULTIPLE> <MySQL Versions MULTIPLE>
<MariaDB versions MULTIPLE> <phpMyAdmin versions MULTIPLE> <MySQL Workbench 8.0.23>Read The Manuals Apache --
MySQL --
PHP --
phpMyAdminGet your Apache/MySQL/mariaDB/PHP ADDONs here from the
WAMPServer alternate Repo-X-X-X-
Backup your databases regularly Here is How dont regret it later! Yes even when developing -X-X-X-