FFXIV encounters Unexpected Error when loading into Ul'dah on Fresh Reinstall

[Euthymia]

I've run into an interesting issue where a fresh installation of Final Fantasy XIV for Windows (non-Steam) has left me unable to play, for loading into Ul'dah - the Steps of Nald throws an unexpected error message before it can finish, sometimes multiple times, and often followed by the game client then crashing instead of closing gracefully.

The error occurs in both the DX9 and DX11 versions. The stack traces in the error message are always the same for their respective clients and is as follows:

ffxiv.exe+C6E70E
ffxiv.exe+1465BB
ffxiv.exe+1486CD
ffxiv.exe+156518
ffxiv.exe+1496E3
ffxiv.exe+2B509C
ffxiv.exe+2CC064
ffxiv.exe+2D4DBB

ffxiv_dx11.exe+F457AD
ffxiv_dx11.exe+6747C
ffxiv_dx11.exe+65B03
ffxiv_dx11.exe+E97900
ffxiv_dx11.exe+E98FAF
ffxiv_dx11.exe+E9BA65
ffxiv_dx11.exe+3E280C
ffxiv_dx11.exe+161DA2

What's interesting is that this only began after I reinstalled with a fresh copy when troubleshooting something else (which turned out to be a Windows update leaving me without the Media Feature Pack -- AGAIN). It has persisted through successive reinstallation attempts, a configuration reset, a graphics driver update, and a rollback to eliminate the update and new driver both.

I'm at my wit's end, and while I can still play on my laptop to a limited extent, losing access to one of the major city-states (or more, for all I know) is rather crippling. Please get back to me ASAP.

System information output is available here, or I can post it in the thread on request:
[link revoked following ticket resolution]

[Euthymia]

During further troubleshooting I have determined that this is a hardware issue; following the reinstallation, sqpack/ffxiv/080000.win32.dat0 was located on a cluster that is causing the entire ATA interface to drop and reset when attempts to access the full file are made. While this is incredibly dire, it is also a problem that is of little relation to Final Fantasy XIV itself, and so I will declare this ticket resolved.

However, in the event that this isn't already implemented (and may have simply failed to be triggered during this set of errors), I would like to suggest that the most recent file accessed is added to the error dialogue for future debugging purposes.

[Xeon]

Too bad that anybody from Square will never see this post, because it is just peer-to-peer support. They do not visit these forums at all, unfortunately.