InnoDB: Assertion failure in thread 3608 in file btr0pcur.c line 440

[earvinnill]

Hi. I'm having trouble with the existing database server in our company. It is built with a pc server only and it has millions of data.

Problem:
Cannot use any CRUD / Backup / Duplicate Table. After I executed one of those, suddenly it loses mysql connection.

System Used:
Xampp
MYSQL

MYSQL ERROR LOG:
180306 17:19:12 InnoDB: Assertion failure in thread 3608 in file btr0pcur.c line 440
InnoDB: Failing assertion: page_is_comp(next_page) == page_is_comp(page)
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://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: http://dev.mysql.com/doc/refman/5.5/...-recovery.html
InnoDB: about forcing recovery.
InnoDB: Thread 5812 stopped in file ibuf0ibuf.c line 4419
---

What I tried to fix:
Backup
mysqldump
repair table
transfer data of xampp to another setup of pc. same error.

Does anyone know how to handle this error? It is live data and the process owner of the system needs the data.

[earvinnill]

Tried also inno_db_recovery, the mysqld.exe stops working after i execute a dump

[topshot]

Are you running a newer version of 5.5?

See this bug to see if it helps.

Could also be a hardware issue - bad drive or RAM or not enough RAM.

Otherwise, submit a bug report as the log instructed you in the first place.

[earvinnill]

Are you running a newer version of 5.5?

See this bug to see if it helps.

Could also be a hardware issue - bad drive or RAM or not enough RAM.

Otherwise, submit a bug report as the log instructed you in the first place.

it seems that bug post is still open due to the status is still no feedback up to now.