FF XIV crashing on new hardware

[KenaiChoppa]

Hello! I have been playing FF XIV for more than a year now in my PC with 16 GB of ram and never had an issue. Today I swapped the ram for new sticks giving a total of 32 GB.

All was good: i did a couple of dailies (2 dungeons and 1 trial) but when I got to play Front lines the game crashed giving an "Unexpected error" and then giving me a list of

"ffxiv_d1.exe+[numbers and letters"

I managed to reconnect and finish it. I went to Limsa lominsa and nothing happened. Then i entered Rival wings. Everything was good until mid match when the game crashed again giving me an "Unexpected error" (again) but with a different list with

a couple of "amdxx64.dll+[numbers and letters]"
one "Kernel32.dll+[number]"
and "ntdll.dll+[number]"

Could this error be related to the new hardware or the fact that i changed my setup? Anyone have a fix?

thanks,

[Payadopa]

I had a similar problem when 6.0 launched. The only thing that helped remotely was using DirectX 9 till 6.1. Still didn't stop the crashes but they were less frequent.

My PS5 controller still acts up occasionally and using direct chat (typing immediately in the cat box without having to press enter first) causes me to write 112234422 every time I press square, circle etc even with all keybinds disabled. I've pretty much given up at this point.

[Kirika-]

Hello! I have been playing FF XIV for more than a year now in my PC with 16 GB of ram and never had an issue. Today I swapped the ram for new sticks giving a total of 32 GB.

All was good: i did a couple of dailies (2 dungeons and 1 trial) but when I got to play Front lines the game crashed giving an "Unexpected error" and then giving me a list of

"ffxiv_d1.exe+[numbers and letters"

I managed to reconnect and finish it. I went to Limsa lominsa and nothing happened. Then i entered Rival wings. Everything was good until mid match when the game crashed again giving me an "Unexpected error" (again) but with a different list with

a couple of "amdxx64.dll+[numbers and letters]"
one "Kernel32.dll+[number]"
and "ntdll.dll+[number]"

Could this error be related to the new hardware or the fact that i changed my setup? Anyone have a fix?

thanks,

Make sure the RAM is the correct type for the motherboard/CPU combo, as in it is within the right frequency range and is desktop memory (is not ECC memory if you are running a non-ECC compatible CPU).
Check your BIOS to see if the memory profile matches the specs of the RAM sticks you put in, correct any out of spec/range voltages and clocks.
Triple check that the RAM sticks are properly seated in the slot and there is no damaged or dirty pins in the sockets or on the RAM sticks.
While there, it's a good idea to check your CPU to make sure it's properly in it's socket with no damaged, dirty, or bent CPU pins/LGA pins/contact pads, re-paste the thermo compound, and triple check the cooler fit and pressure (the CPU is also the memory controller on modern systems, so a "bad memory" issue can sometimes actually be a CPU issue)
Run a memory test program, to see if the RAM has any defects or errors - https://www.memtest86.com/ - is the "industry standard" for testing RAM.
Run DXDiag - https://support.microsoft.com/en-us/...7-bf92228dfd85 - to scan the DirectX install on the computer, it can find any errors or glitched/missing files. It can also perform some repair to the DirectX install and "setup" the DirectX install for the system's hardware/changed hardware.
Hit up the websites for your CPU and video card, and download the latest drivers for those from them, do not rely on Windows Update to maintain/update drivers for those devices.

I hope one or more above helps fix the issue.

[KenaiChoppa]

Sorry for replying so late, but I have been busy and couldn't test any solution.

In the end the rams were fine, it was the XMP profile that was causing trouble. I lowered and so far I havent had another crash.

Thanks everyone for your replies!

[Mieleoneis]

Greetings adventurer,

Thanks for providing everyone with an update on the situation! I'm happy to hear that you were able to figure out the cause and find a fix for it. As it appears that this issue is now resolved, I'll be moving this thread to the "Closed Concerns" subforums.

Thank you again for visiting the FINAL FANTASY XIV Technical Support Forums!