Randomly crashing game.. GTX 970

[Shinsei]

well.. something is off in your system. Bob is working, and he is using the same family of drivers (although, a slightly newer release from 10/16 vs 9/19, and there is a slightly newer one out now from 10/22). So, there could be something off in the driver...or it could be something else in your environment. You said you formatted and reloaded Windows... did you run the offline DX9 Runtimes to correct the common issues that crop up from missing/unregistered DLL's that have caused issues with older games since Vista was released? (note you may need to enable .Net3.5 to install the DX9 files) How about MSIE/WMP support libraries--even if you don't use them, the game DOES and they may need updating.

Something is off in your Windows environment--be that it's API's, drivers, third party processes in the background, or flakey hardware. If it were just the game, it would be causing problems across the board... which it clearly is not.

Without being able to say for certain that your system is exactly as it was prior to patching, you have to keep yourself open to the possibility that something may be awry with your system and not just something that suddenly changed in the game's code with the new patch. Although, there was a note with todays patch that there was some specific combination that was causing crashes that they addressed--but I think that was at the server level.

Another thought jsut hit me... what security are you using? It is possible that the executable is getting trapped because a change has been detected. Firewalls are notorious for this problem--have you checked/updated your white-listing to make sure that isn't an issue?

And comparing it to all those other games that use different methods for handling A/V and thus placing different demands on the system aren't necessarily an indication of a problem suddenly cropping up in the game's code. For instance, if you have a marginal hardware environment, it may not show up with games that are not stressing everything at once like this game. It may be an issue with a driver that only crops up with the specific way XIV is handling overlay or mouse cursor--suddenly you have an access error at a specific memory address because a background driver for another device/service got updated and it is causing a problem.

There is just so much that could be causing the problem... need to be open to the possibilities and check them all out, even if it seems stupid to do so. You may be surprised at some of the things that can cause a crash. My game will crash on launch if I sign on too soon after the desktop comes available. I have to give it a moment to make sure all background processes and such are fully loaded first. Sounds odd... but that's just an idiosyncrasy of Windows that has been around for as long as I've used it, dating back to 3.1.

Fresh Windows 8.1 install. No security as of when I replied back saying it's still crashing. Fresh everything. Like I said I never had a issue with the 680GTX. I still feel this is a driver issue.

If you know of a way to access FFXIV logs, other then the combat logs, it may be able to tell me something...

[Syx]

Fresh Windows 8.1 install. No security as of when I replied back saying it's still crashing. Fresh everything. Like I said I never had a issue with the 680GTX. I still feel this is a driver issue.

If you know of a way to access FFXIV logs, other then the combat logs, it may be able to tell me something...

It's not a driver issue. I use a GTX 970 with the 344.48 drivers and the game has been running beautifully.

[Raist]

It's not a driver issue. I use a GTX 970 with the 344.48 drivers and the game has been running beautifully.

Those are the drivers from October... as in the latest ones. So, it may have been a driver issue that just got fixed. As noted earlier, he is using older drivers and the the other user that is also not having the issue (Bob) was also using a release from October as well.

It may not necessarily be the video drivers per se either--it could be audio, mouse, some odd legacy IR device or an HID drive, or even a background service that is causing the access violation that is crashing the game.

[Squa11_Leonhart]

Those are the drivers from October... as in the latest ones. So, it may have been a driver issue that just got fixed. As noted earlier, he is using older drivers and the the other user that is also not having the issue (Bob) was also using a release from October as well.

It may not necessarily be the video drivers per se either--it could be audio, mouse, some odd legacy IR device or an HID drive, or even a background service that is causing the access violation that is crashing the game.

There wasn't any crash issue (in this game) in 344.11 or .16, just the fog corruption.