Consistent, replicate-able DX Error with Gathering Log

[aisthesis]

It just happened to me on PS5, so it is not a windows only issue. It happened twice in a row while gathering items in Azys Lla for the Skysung Pickaxe. After finding this thread, I tried the steps mentioned by OP and it crashed:
1. Open Gathering Log.
2. Navigate to Skysteel Tool page. Selected and displayed oddly specific items. I don't have the Diadem step unlocked yet, so I believe it's simply the Skysteel Tool page.
3. Close Gathering Log.
4. Reopen Gathering Log and game freezes and crashes.

Submitted error report via PS5 interface in every instance of the error/crash.

[EiraValkyrie]

We now have multiple systems encountering this same exact crash. It happens regardless of playing on PC or Console, so installation path is irrelevant. It also still crashes even if you use DirectX 9.0c, so the crash isn't related to that. One reason for the crash may be the way game tries to remember which item you had selected, and when you reopen the log, that item index doesn't exist in the regular 1-80 gathering log points (since it's on second page), so it tries to select a position that doesn't exist, therefore: crash.

Can we please get an update on what's happening, admins? It really feels like walking on eggshells when playing now, if I accidentally open gathering log at wrong point, game crashes. It makes gathering incredibly difficult.

Please give us a status report.

[Sythalin]

Good morning and thank you for posting on the Final Fantasy XIV Technical Support Forums.

We would like to recommend the following steps:

1) Remove game and all content
2) Restart PC
3) Install and run a registry cleaner
4) Restart PC
5) Reinstall the game
6) Restart PC
7) Launch game to see if issue is resolved

Thank you for visiting the Final Fantasy XIV Technical Support Forums.

This is the most ridiculous "troubleshooting" that I've ever read and is exactly as EiraValkyrie said - a goose chase.

It's simple. The game worked fine for everyone prior to patch 5.55. After that, multiple people across multiple platforms are crashing in the exact same place that is consistently reproducible. If you do not have an internal report of a cause, or that it needs further testing to find the source, that's cool. People will understand as long as there's some feedback and acknowledgement. Responding with the equivalent of "turn it off then back on again" is only going to piss people off.

[MiniTofu]

This is the most ridiculous "troubleshooting" that I've ever read and is exactly as EiraValkyrie said - a goose chase.

It's simple. The game worked fine for everyone prior to patch 5.55. After that, multiple people across multiple platforms are crashing in the exact same place that is consistently reproducible. If you do not have an internal report of a cause, or that it needs further testing to find the source, that's cool. People will understand as long as there's some feedback and acknowledgement. Responding with the equivalent of "turn it off then back on again" is only going to piss people off.

I agree! Really a generic response and waste of people's time that is not even the fault of the hardware. It's the game issue and it is happening on cross-platform.

[whereabouts]

I have exactly the same problem "gather log"