MySQL shutdown unexpectedly

[membershipsecretary]

Hi.
I was learning to use Xampp (with no problems) then got a new laptop and now have problems. It worked initially but now MySQL will not start. I have gone into the error logs and have this message. Any help with sorting this out would be great.

2022-01-30 18:50:36 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2022-01-30 18:50:36 0 [Note] InnoDB: Uses event mutexes
2022-01-30 18:50:36 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2022-01-30 18:50:36 0 [Note] InnoDB: Number of pools: 1
2022-01-30 18:50:36 0 [Note] InnoDB: Using SSE2 crc32 instructions
2022-01-30 18:50:36 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2022-01-30 18:50:36 0 [Note] InnoDB: Completed initialization of buffer pool
2022-01-30 18:50:37 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=300288
2022-01-30 18:50:37 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2022-01-30 18:50:37 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2022-01-30 18:50:37 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2022-01-30 18:50:37 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2022-01-30 18:50:37 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2022-01-30 18:50:37 0 [Note] InnoDB: Waiting for purge to start
2022-01-30 18:50:37 0 [Note] InnoDB: 10.4.22 started; log sequence number 300297; transaction id 170
2022-01-30 18:50:37 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2022-01-30 18:50:37 0 [Note] Plugin 'FEEDBACK' is disabled.
2022-01-30 18:50:37 0 [Note] Server socket created on IP: '::'.
2022-01-30 18:50:37 0 [Note] InnoDB: Buffer pool(s) load completed at 220130 18:50:37
2022-01-30 18:50:37 0x2628 InnoDB: Assertion failure in file D:\winx64-packages\build\src\storage\innobase\os\os0file.cc line 6202
InnoDB: Failing assertion: slot
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
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: https://mariadb.com/kb/en/library/innodb-recovery-modes/
InnoDB: about forcing recovery.
2022-01-30 18:50:37 0x4208 InnoDB: Assertion failure in file D:\winx6220130 18:50:37 [ERROR] mysqld got exception 0x80000003 ;
4-packages\build\src\storage\innobase\os\os0file.ccThis could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.

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.

linServer version: 10.4.22-MariaDB
e key_buffer_size=16777216
6202read_buffer_size=262144

max_used_connections=0