Strange crashes. Anyone else?

[WindyGamer]

Played all day yesterday, and days before. No problem.

Today, crashed at 1:30 with a popup box. Then again after a few minutes with no box. Just Client gone. Standing around in Limsa.

Now played MSQ Roulette for an hour and did some gear upgrades. All no problems. Then at exactly 16:30 local time client disappeared. I was opening inventory. But I'd done that a bunch of times before in the past few minutes too. Logged back in no problem.

Times seem odd like they are on some exact time. Win10 with all updates. Just updated my graphics driver a few hours ago after the first two crashes. RTX 2060

Anybody else seen strange crashes?

[Valkyrie_Lenneth]

Nope, no issues here.

[MrKusakabe]

My crashes happen when I have the LoL launcher running in the background. It's not even a crash - The game literally closes within 0.3 seconds smoothly, no error mesage, no Windows error sound, nothing written into logs, no harddisk access, RAM immediately available. The crash is so smooth it's actually better and more swift than shutting down the game via the menu.
I figured out later the LoL client has changed to be running on the GPU and since I close it and/or reboot, all is fine. Could imagine some other GPU-related task might cause problems (e.g. hardware-accelerated Flash/HTML5 players like Youtube's) or software aging that causes them.


On a freshly rebooted system, I never had any of these random crashes.

[WindyGamer]

Yep. Nope. Don't play League of Legends. No other GPU related software has run since the system was rebooted. And like I said, I had just played in Praetorium for an hour or more before the crash. I'll keep watching. Thanks for the input.

[Lauront]

If you mean Direct X crashes, they are ubiquitous... a lot of players, myself included, have been getting them. You can try these steps, as they may (or may not) help.

[WindyGamer]

If you mean Direct X crashes, they are ubiquitous... a lot of players, myself included, have been getting them. You can try these steps, as they may (or may not) help.

Wheew. Every time I see that kind of list I imagine a truck to fetch a large pile of rocks. Nope. Not going there. My system is very stable, not flakey. Latest Windows 10, Latest Nvidia drivers, yada yada.

But I did notice something else. Recently I purchased and installed Witcher III - Yeah. I know. Right? And it comes with a "Launcher" called the GoG or something. Anyway. I very carefully went to GoG's settings and unchecked "Start with Windows" or some such. However, it appears to have ignored that and GoG was running at the times that I had the crashes. And it's not running today, because it does not "ReStart" itself once you say "Exit GoG". At least that, right?

So. I'm wondering if these game launchers have it in for each other. I would not expect the game "Launchers" to actually use DirectX11, but maybe they do.
I would not normally expect that these launchers are "Jealous" in some way and are saying to themselves - "You are playing way to much of that other game, and not me, so I'll randomly clobber that nice game you've been playing...." anyway. That's the conspiratist [or is that Conspiratorialist?] in me I guess. But what with all the other "Real" conspiracies going around: Why not?

But after shutting that GoG thing down, I have played all day hard - gathering Moogle Tomes - and no FFXIV client crashes. So that's a data point. And it lines up with a previous comment that a LoL [League of Legends I presume] Launcher was causing problems for someone.

Say. Do these Launchers look for programs that are "adding features" [not using the Exp banned word here] games, and deciding that other games are baddies and clobbering them? Naw. That's second order conspiracy theory, certainly. But we do have two data points on that line.

[Kirika-]

So. I'm wondering if these game launchers have it in for each other. I would not expect the game "Launchers" to actually use DirectX11, but maybe they do.
I would not normally expect that these launchers are "Jealous" in some way and are saying to themselves - "You are playing way to much of that other game, and not me, so I'll randomly clobber that nice game you've been playing...." anyway. That's the conspiratist [or is that Conspiratorialist?] in me I guess. But what with all the other "Real" conspiracies going around: Why not?

But after shutting that GoG thing down, I have played all day hard - gathering Moogle Tomes - and no FFXIV client crashes. So that's a data point. And it lines up with a previous comment that a LoL [League of Legends I presume] Launcher was causing problems for someone.

Say. Do these Launchers look for programs that are "adding features" [not using the Exp banned word here] games, and deciding that other games are baddies and clobbering them? Naw. That's second order conspiracy theory, certainly. But we do have two data points on that line.

It is more likely the other launchers use different versions of DirectX or ActiveX (yes, most launchers are Internet Explorer based) during their idle stages to load the banners, links, pre-launch, and media.
While your video card is happy to be running a DirectX11 game, it doesn't like to be interrupted to also run other DirectX versions or media-overlays at the same time, even those that are in another window in the background or minimized.

Less stuff running in the background = better for gaming

So exit/shut-off/do-not-run-on-Windows-startup all your launchers and only start the one up for the game you are going to play.

[Antonio_Xul]

Yesterday in the morning, I was suffering from severe lag, whether I was hunting or doing instances. It was bad, so I quit for the day. Today everything was good to go.

[Lauront]

It could be that they're interfering but even when I shut down GOG in the past it made little difference... part of the problem is that the game lumps a number of different issues under the Direct X heading, and so you need to go into your event log to get a better idea of what it was.

[Izar_Chillen]

Event viewer is a good way to check what might be causing errors and or crashed if its not immediately obvious. Its easy to get to grips with if you have never used it before.

So for example, if its a 3rd party driver issue, there will be highlights about a critical error and give a code which you can use to identify a process that is crashing. This way you can at least (if a driver issue) remove the offending driver and revert to an older build or clean the bad driver ( display driver uninstaller if a GPU driver issue) and reinstall it.

https://www.bleepingcomputer.com/for...-event-viewer/