As you can see in the XAMPP control's panel, MySQL can't be started if its port is already in used, can you check if the 3306 port is in used in your system? You can click on the "Netstat" button on the top right corner of the manager.

If the port is free, could you please share with us the content of the MySQL log? You can also use our support tool that collects the MySQL information.

NOTE: The tool will inform you about the information that will be shared with us and you can decide wether to share it or not. Please review it and ask us any doubt you have if you do not agree with sharing some of the information.

Also doesnt allow me to upload the ZIP file containing the reports from the xampp tool, that also needs to change so I can upload it

We updated our support tool to upload the files to an accessible place for the Bitnami Engineers so you won't need to upload the .zip file here. To use the latest improvements, you will need to download the latest version of the tool that I shared above. It should give you a code that you will need to share with us.

In case you run into any issue with the tool, you can also upload here the MySQL log that you'll find inside the MySQL folder, that way, we will know the exact issue of the server.

I've been checking your log files and I noticed that the error messages you received on Sept 12th, 2017 don't appear right now.

2017-09-12 09:13:12 7468 [Note] InnoDB: Page size: 16384, Possible space_id count:0^M
InnoDB: Error: could not open single-table tablespace file .\carsforsaleblack\cfs_links.ibd^M
InnoDB: We do not continue the crash recovery, because the table may become^M
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.^M
InnoDB: To fix the problem and start mysqld:^M

On Oct 21st, 2017, MySQL started throwing the following error message:

This 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.
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.
key_buffer_size=16777216
read_buffer_size=262144
max_used_connections=3
max_threads=151
thread_count=2
connection_count=2
It is possible that mysqld could use up to.
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 133778 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x21b4d008
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...
32c7c0 mysqld.exe!my_thread_name()
5679ed mysqld.exe!my_mb_ctype_mb()
47d2f6 mysqld.exe!?my_aes_create_key@@YAXPBEIPAEW4my_aes_opmode@@@Z()
396177 mysqld.exe!?my_aes_create_key@@YAXPBEIPAEW4my_aes_opmode@@@Z()
480383 mysqld.exe!?my_aes_create_key@@YAXPBEIPAEW4my_aes_opmode@@@Z()
3c4d19 mysqld.exe!?my_aes_create_key@@YAXPBEIPAEW4my_aes_opmode@@@Z()
3c7488 mysqld.exe!?my_aes_create_key@@YAXPBEIPAEW4my_aes_opmode@@@Z()
3c7528 mysqld.exe!?my_aes_create_key@@YAXPBEIPAEW4my_aes_opmode@@@Z()
3c7853 mysqld.exe!?my_aes_create_key@@YAXPBEIPAEW4my_aes_opmode@@@Z()
355b5f mysqld.exe!?my_aes_create_key@@YAXPBEIPAEW4my_aes_opmode@@@Z()
da5d0 mysqld.exe!?ha_commit_low@@YAHPAVTHD@@_N1@Z()

It seems that there is an issue in the server (maybe one of the libraries got corrupted). You can check the MySQL's crashing page in order to know more about the different issues of the server:

I see that post of mine was started in OCT 2018. I have now installed XAMPP into another folder and 3 months later it happens again and am wondering this is not very stable, I also see lots of forum regarding the same thing with no fixe anywhere.

I'm sorry to hear that you are running into problems again with MySQL. As you can see in the MySQL log, it failed with the following error message

2018-03-31 09:32:21 140 [Note] d:\xampp3 latest win7\mysql\bin\mysqld.exe: ready for connections.^M
Version: '5.6.21' socket: '' port: 3306 MySQL Community Server (GPL)^M
2018-03-31 09:32:21 1374 InnoDB: Assertion failure in thread 4980 in file trx0purge.cc line 699^M
InnoDB: Failing assertion: purge_sys->iter.trx_no <= purge_sys->rseg->last_trx_no^M
InnoDB: We intentionally generate a memory trap.^M
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.^M
InnoDB: If you get repeated assertion failures or crashes, even^M
InnoDB: immediately after the mysqld startup, there may be^M
InnoDB: corruption in the InnoDB tablespace. Please refer to^M
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html^M
InnoDB: about forcing recovery.^M
22:32:21 UTC - mysqld got exception 0x80000003 ;
This 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.
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.

This database version is quite old, it was released in 2014 and probably have some bugs and issues so I suggest you ask in the official forums of MySQL to get more information about how to avoid that.