Looking through the forums right now, it does seem like some others are having this issue as well.
Yesterday I renewed my subscription for 30 days and started playing, this went fine for a while until I did a main scenario duty for leveling, Castrum Meridianum to be exact. I clicked accept on the duty finder and it started loading me into the dungeon, however after like 5 seconds the game just closed itself without warning or error message. I kept on restarting the game, everytime it worked fine for like 2 minutes until it randomly closed the game again without any warning or error. After I "finished" the duty I went back to the North Shroud because that's where I left off before I joined the dungeon and continued leveling for a while without any "crashes".
I then decided to repair the game over night, because this does take a LONG time for me, downloading with like 6 mb/s. This morning it was done and I decided to log back in. HOWEVER after the repair I cannot log back in to my character without the game closing on itself without any warning/crashing errors, so repairing actually "damaged" the game more???
I've updated everything that was connected to my PC; OS, mouse, SSD, etc. I also deleted the local files in the meantime, However this all didn't work... Hell it felt like the game was closing/crashing faster after this.
At this very moment I am doing a complete reinstall of the game in hopes of fixing the issue. But my hopes aren't very high... And I lost another day of my subscription because of the last resort reinstall of the game, which isn't a big deal imo but it is very frustrating cause there seems to not be a certain fix that works.
PC Specs;
Intel(R) Core(TM) i5-8400 CPU @ 2.80GHz 2.81 GHz
16 GB RAM
NVIDIA GeForce GTX 1050 Ti
EDIT:
I reinstalled the game, it worked fine for a while until I teleported to Limsa Lominsa, now it once again keeps closing the game whenever I try to log into my character :/
EDIT 2:
Apparently there was a second FFXIV installed on my C: drive, normally I download all my games on an external SSD drive but I decided to remove the copy from my external SSD drive and launch the game from the C: drive one, looks like this solved the issue for now.