MySQL bug: MariaDB error, cannot access PHPMyAdmin

[SCHOBER-Astrid]

Dear all,

I do so need your help, please!

I have impemented an offline Wordpress installation via Xampp 8.2.12 (+ Apache 2.4.58 + MariaDB 10.4.32 + PHP 8.2.12 (VS16 X86 64bit thread safe) + PEAR + phpMyAdmin 5.2.1).

It worked nicely for 3 months, but now the MySQL has crashed somehow and I cannot access phpMy Admin anymore. The MySQL ErrorLog actually says it's a bug:

...2024-04-16 9:46:44 0 [Note] InnoDB: 0000000000000000000000000000000000000000000000000000000000000000
2024-04-16 9:46:44 0 [Note] InnoDB: 0000000000000000000000000000000000000000000000000000000000000000
2024-04-16 9:46:44 0 [Note] InnoDB: 0000000000000000000000000000000000000000000000000000000000000000
2024-04-16 9:46:44 0 [Note] InnoDB: 000000000000000000000000000000000000000000000000d21fe19709142bc5
2024-04-16 9:46:44 0 [Note] InnoDB: End of page dump
2024-04-16 9:46:44 0 [Note] InnoDB: It is also possible that your operating system has corrupted its own file cache and rebooting your computer removes the error. If the corrupt page is an index page. You can also try to fix the corruption by dumping, dropping, and reimporting the corrupt table. You can use CHECK TABLE to scan your table for corruption. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-04-16 9:46:44 0 [ERROR] [FATAL] InnoDB: Unable to read page [page id: space=33, page number=1] into the buffer pool after 100. The most probable cause of this error may be that the table has been corrupted. See https://mariadb.com/kb/en/library/innodb-recovery-modes/
240416 9:46:44 [ERROR] mysqld got exception 0x80000003 ;
Sorry, we probably made a mistake, and this is a bug.

Your assistance in bug reporting will enable us to fix this for the next release.
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.4.32-MariaDB source revision: c4143f909528e3fab0677a28631d10389354c491
key_buffer_size=16777216
read_buffer_size=262144
max_used_connections=0
max_threads=65537
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 20304 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()
ucrtbase.dll!raise()
ucrtbase.dll!abort()
mysqld.exe!??$_Construct@$00PEBD@?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@AEAAXQEBD_K@Z()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
mysqld.exe!pthread_dummy()
KERNEL32.DLL!BaseThreadInitThunk()
ntdll.dll!RtlUserThreadStart()
The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mariadbd/ contains
information that should help you find out what is causing the crash.
Writing a core file at C:\xampp\mysql\data
Minidump written to C:\xampp\mysql\data\mysqld.dmp

Does anyone have an idea what to do to save the installation?

Best regard, Astrid