DirectX 11 crash issue

[RinKaenbyou]

You mentioned a bug.... Soooooooo coding... Game issue. Needs fixed as no other game really runs into this.

Thank you come again.

Oh, how convenient that you ignored everything else Puss_Kat said in their message. Hate to break it to ya but the issue doesn't exist on non-faulty hardware as they clearly stated so it's a computer hardware issue. Your computer needs fixing as no one with stable/non-faulty hardware runs into this issue. Thank you come again.

[Irruchi]

Oh, how convenient that you ignored everything else Puss_Kat said in their message. Hate to break it to ya but the issue doesn't exist on non-faulty hardware as they clearly stated so it's a computer hardware issue. Your computer needs fixing as no one with stable/non-faulty hardware runs into this issue. Thank you come again.

Sorry the most people aren't running optimal hardware even if it waaaaay overshoots the recommended.
But you guys in camp faulty hardware sayers, miss the fact that how all others titles and even software and diagnostics don't have faults, yet this one game which is software runs into the same issue for many people.

Huh.... How interesting... Maybe I should toss out my PC and buy another 20+ systems till I somehow have the special gem of a system you guys supposedly talk about.
There's even some people who fixed the issue for weeks without the error only for it to show it's ugly messages again.
So obviously their hardware must have obviously in your eyes gone and took a dump and now they need a new system?

You guys have some interesting mental gymnastics going on to come to these conclusions that somehow it's a problem with the hardware and software can never cause system instability ever......

[RinKaenbyou]

Sorry the most people aren't running optimal hardware even if it waaaaay overshoots the recommended.
But you guys in camp faulty hardware sayers, miss the fact that how all others titles and even software and diagnostics don't have faults, yet this one game which is software runs into the same issue for many people.

Huh.... How interesting... Maybe I should toss out my PC and buy another 20+ systems till I somehow have the special gem of a system you guys supposedly talk about.
There's even some people who fixed the issue for weeks without the error only for it to show it's ugly messages again.
So obviously their hardware must have obviously in your eyes gone and took a dump and now they need a new system?

You guys have some interesting mental gymnastics going on to come to these conclusions that somehow it's a problem with the hardware and software can never cause system instability ever......

This has nothing to do with "optimal hardware" though. You are completely missing the point here. There is a piece of hardware or multiple pieces INSIDE your computer that is faulty. That is the problem here. Nothing more, nothing less. You need to figure out and find what the faulty piece of hardware INSIDE your computer is and replace it. That's all you need to do and then your issues will go away. Why is that so hard for you to grasp? Genuine question here because you really seem to not understand this at all.
And you also seem to completely be unable to grasp the fact that it is entirely possible for a single program, regardless of what it is, to cause hardware faults to manifest.

Again, this has nothing to do with optimal hardware or a godly computer. It is simply a piece of hardware in your current setup that is faulty. GPU, Motherboard, CPU, a combo....you just need to find what it is that is faulty. How hard is that for you to understand? Also, just because these other people found "fixes" doesn't anything because most of them are temporary unless they've actually replaced a part they thought was the cause but then had the issue crop up again which means the part they replaced either wasn't the cause or was just one piece of hardware causing the issue.

You have some interesting mental gymnastics to believe that DX11 software can cause system instability by itself because spoiler alert: IT CAN'T! It is a 100% proven fact that DX11 software CANNOT cause system instablity unless the hardware in your computer is faulty!

[Irruchi]

This has nothing to do with "optimal hardware" though. You are completely missing the point here. There is a piece of hardware or multiple pieces INSIDE your computer that is faulty. That is the problem here. Nothing more, nothing less. You need to figure out and find what the faulty piece of hardware INSIDE your computer is and replace it. That's all you need to do and then your issues will go away. Why is that so hard for you to grasp? Genuine question here because you really seem to not understand this at all.
And you also seem to completely be unable to grasp the fact that it is entirely possible for a single program, regardless of what it is, to cause hardware faults to manifest.

Again, this has nothing to do with optimal hardware or a godly computer. It is simply a piece of hardware in your current setup that is faulty. GPU, Motherboard, CPU, a combo....you just need to find what it is that is faulty. How hard is that for you to understand? Also, just because these other people found "fixes" doesn't anything because most of them are temporary unless they've actually replaced a part they thought was the cause but then had the issue crop up again which means the part they replaced either wasn't the cause or was just one piece of hardware causing the issue.

You have some interesting mental gymnastics to believe that DX11 software can cause system instability by itself because spoiler alert: IT CAN'T! It is a 100% proven fact that DX11 software CANNOT cause system instablity unless the hardware in your computer is faulty!

Software pulling and using that api still can though. and like I said, if I already came up empty handed for any faults in any of my hardware.... I have every right to point to software.

[RinKaenbyou]

Software pulling and using that api still can though. and like I said, if I already came up empty handed for any faults in any of my hardware.... I have every right to point to software.

Except it can't. Software using DX11 cannot UNDER ANY CIRCUMSTANCES cause system instability without existing hardware faults. The API thing you keep bringing up doesn't matter. It still cannot do what you claim it is doing without existing system instability!
There is no room for argument on this because it's a simple, undeniable FACT! The sooner you get that through your thick skull, the better. You have absolutely no right to point to software in this case because it's NOT the software. It's YOUR hardware. And just cause you couldn't find any faults doesn't mean your PC is clean. It just means whatever tests you did couldn't find the hardware faults which is entirely possible because it could very well be something whatever tests you did outright cannot find and thus is something you'll have to open up your PC to check the hardware by swapping stuff out and all that fun.

[Irruchi]

Except it can't. Software using DX11 cannot UNDER ANY CIRCUMSTANCES cause system instability without existing hardware faults. The API thing you keep bringing up doesn't matter. It still cannot do what you claim it is doing without existing system instability!
There is no room for argument on this because it's a simple, undeniable FACT! The sooner you get that through your thick skull, the better. You have absolutely no right to point to software in this case because it's NOT the software. It's YOUR hardware. And just cause you couldn't find any faults doesn't mean your PC is clean. It just means whatever tests you did couldn't find the hardware faults which is entirely possible because it could very well be something whatever tests you did outright cannot find and thus is something you'll have to open up your PC to check the hardware by swapping stuff out and all that fun.

In fact.
There is also another type of software fault
which is often overlooked

AMD Radeon™ Software may crash or become unresponsive while playing some DirectX® 11 games such as PlayerUnknown’s Battlegrounds™ with multiple displays connected in extended mode.

Not hardware fault but driver fault which Drivers are software. But that may solve it for some of the more extreme failures that cause the reinstalls.
So in essence I was looking in the wrong place thanks to the "faulty" hardware claims.

[Puss_Kat]

Drivers were brought up multiple times and the PUB crash is specific to PUB.

[Macbrush]

I am just very sorry to say that it doesn't matter whether it's the developer's fault, they should've at least acknowledged it, and investigate, then if it turned out not their fault, and nothing they could've done, they could just say so. But instead, the issue is completely ignored.

[Amarande]

Soooo ... my own perspective on what's likely going on here, maybe it might jog SE to check into that instead:

I don't think it's the graphics drivers.
I don't think it's your hardware.
I don't think it's FFXIV per se.
Honestly, I think it's actually the launcher, combined with imperfect Internet connections, and XIV's notorious lack of any kind of client data integrity checks.

Personally, I've seen the DX errors on two occasions.

Once was during the latter weeks of Eureka: Pagos being current content, and if memory serves, the errors only happened in Pagos. It spontaneously went away when 4.45 dropped and Eureka: Pyros came out.

Once is currently. The game itself works perfectly, but I've been noticing DX errors if I click Exit Game.

Different PCs (the one I used during Eureka had nVidia, and the one I have now has AMD), and I know my current PC has been put through its hardware paces (I also play Chess extensively, including once generating a set of 6 piece Syzygy tablebases - which literally have to be bit-perfect, so it's extremely unlikely there can be any problems with the RAM or CPU, while just in case I've put the GPU through a torture test with FurMark without incident).

Now keep in mind that FFXIV verifies its client data integrity extremely poorly under normal circumstances, and a chronic issue seen by many players has been the "unable to complete version check" one during patches, as well (remember the heartbreak that was Shirogane launch due to so many people losing out right at the door because version check failed and they had to stop and reinstall the game, after which the houses were all gone - and then SE decided to pull the ultimate hold my beer by adding in the FC restriction and timer shenanigans with 4.2 so most of those that missed out on Shiro missed out on houses throughout Stormblood?).

My guess: People's FFXIV installations are slightly corrupted as a result of Internet blips (I don't think we need to list the weight of evidence that SE barely thinks about the state of the Internet in the West at all), and the failure of the game to check its data robustly, and that is what ultimately results in the DX errors.

It would handily explain the Eureka experience at least: Eureka was updated in 4.45 to account for Pyros, so presumably my Pagos related data from the previous patch was corrupted, then it got overwritten by a good copy from the update.