WampServer

2019-07-10 21:25:30 4800 [Note] Plugin 'FEDERATED' is disabled.
2019-07-10 21:25:30 4800 [Note] InnoDB: Using atomics to ref count buffer pool pages
2019-07-10 21:25:30 4800 [Note] InnoDB: The InnoDB memory heap is disabled
2019-07-10 21:25:30 4800 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2019-07-10 21:25:30 4800 [Note] InnoDB: Compressed tables use zlib 1.2.3
2019-07-10 21:25:30 4800 [Note] InnoDB: Not using CPU crc32 instructions
2019-07-10 21:25:30 4800 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2019-07-10 21:25:30 4800 [Note] InnoDB: Completed initialization of buffer pool
2019-07-10 21:25:30 4800 [Note] InnoDB: Highest supported file format is Barracuda.
2019-07-10 21:25:30 4800 [Note] InnoDB: Log scan progressed past the checkpoint lsn 2715219834
2019-07-10 21:25:30 4800 [Note] InnoDB: Database was not shutdown normally!
2019-07-10 21:25:30 4800 [Note] InnoDB: Starting crash recovery.
2019-07-10 21:25:30 4800 [Note] InnoDB: Reading tablespace information from the .ibd files...
2019-07-10 21:25:31 4800 [Note] InnoDB: Restoring possible half-written data pages
2019-07-10 21:25:31 4800 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 2715223661
2019-07-10 21:25:32 4800 [Note] InnoDB: 128 rollback segment(s) are active.
2019-07-10 21:25:32 4800 [Note] InnoDB: Waiting for purge to start
2019-07-10 21:25:32 4800 [Note] InnoDB: 5.6.17 started; log sequence number 2715223661
2019-07-10 21:25:32 4800 [Note] InnoDB: !!! innodb_force_recovery is set to 1 !!!
2019-07-10 21:25:32 4800 [Note] Server hostname (bind-address): '*'; port: 3306
2019-07-10 21:25:32 4800 [Note] IPv6 is available.
2019-07-10 21:25:32 4800 [Note] - '::' resolves to '::';
2019-07-10 21:25:32 4800 [Note] Server socket created on IP: '::'.
2019-07-10 21:25:32 4800 [Note] Event Scheduler: Loaded 0 events
2019-07-10 21:25:32 4800 [Note] wampmysqld64: ready for connections.
Version: '5.6.17' socket: '' port: 3306 MySQL Community Server (GPL)
2019-07-10 21:25:32 570 InnoDB: Assertion failure in thread 1392 in file trx0purge.cc line 699
InnoDB: Failing assertion: purge_sys->iter.trx_no <= purge_sys->rseg->last_trx_no
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to [bugs.mysql.com].
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: [dev.mysql.com]
InnoDB: about forcing recovery.

Hi

Your database crashed, maybe the PC crashed. It is attempting recovery but looks likeit failed. There are processes to attempt recovery described in the manual.

The links to help you and give you more details of the issue and the possible solutions are all in the report you show us.

The MySQL manual can be fould, well look at my signature below and links to all the manuals can be found there

Or look in the WAMPManager menu for links to the individual manuals.

Although the simplest method of recovery would be to restore your last backup! I assume of course that you took regular backups of your databases

---------------------------------------------------------------------------------------------
(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 -- phpMyAdmin
Get 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-