Randomly crashing game.. GTX 970

[Shinsei]

Like I said, if it was anything else or the card that was causing the issue, all my other games, including CS:GO, LoL, and Shadow of Mordor would crash, it's not the display driver crashing, the game just crashes with "Final Fantasy a Realm Reborn has stopped responding"

EDIT: Continued to happen after reinstalling windows (formatted)

[Raist]

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.

[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...

[Raist]

Isn't Windows Firewall on by default on a fresh install? It blocks all kinds of stuff at first. Just saying... might be right under your nose and don't even know it.

You can get a handy utility called TinyWall that makes it pretty easy to tweak/maintain Windows Firewall. (link is to cnet page about it). Note it isn't a firewall itself, just a utility to manage the Windows Firewall rules. Could try turning of Defender too I guess... or create exceptions for XIV executables via the Tools menu maybe.

Your Windows/directx logs may help shed more light on what could be going on under the hood otherwise. You can run eventvwr.msc to get to the Windows logs. Think the dxerror.log is only generated when problems are found, so not seeing anything that looks like it on my system. May be in the root of your system drive, the Windows folder, or even under a sub-folder there labeled simply "log" or "logs".

[Squa11_Leonhart]

Like I said, if it was anything else or the card that was causing the issue, all my other games, including CS:GO, LoL, and Shadow of Mordor would crash

I'm sorry, but you have a near-basic understanding of the way silicon processors operate :\.

LoL and CSGO do not put even half the loading on the gpu that FF14 does, and FF14 utilises all the components of the system far heavier than any of the titles you just listed.

[Shinsei]

I'm sorry, but you have a near-basic understanding of the way silicon processors operate :\.

LoL and CSGO do not put even half the loading on the gpu that FF14 does, and FF14 utilises all the components of the system far heavier than any of the titles you just listed.

Your assumption is wrong sir, I'm actually a level 2 tech for a pretty big company. It's not my PC, it's something to do with the driver. The way it's acting shows it to be that. I'm not here to argue.. I'm just trying to figure out why the hell this is happening to ONLY this game.

Edit: Anyway.. It doesn't matter anymore... It will eventually be fixed.

Edit 2: Is there a way to turn debug logging on?

[Shinsei]

Isn't Windows Firewall on by default on a fresh install? It blocks all kinds of stuff at first. Just saying... might be right under your nose and don't even know it.

You can get a handy utility called TinyWall that makes it pretty easy to tweak/maintain Windows Firewall. (link is to cnet page about it). Note it isn't a firewall itself, just a utility to manage the Windows Firewall rules. Could try turning of Defender too I guess... or create exceptions for XIV executables via the Tools menu maybe.

Your Windows/directx logs may help shed more light on what could be going on under the hood otherwise. You can run eventvwr.msc to get to the Windows logs. Think the dxerror.log is only generated when problems are found, so not seeing anything that looks like it on my system. May be in the root of your system drive, the Windows folder, or even under a sub-folder there labeled simply "log" or "logs".

Thanks, I looked nothing out of the ordinary. Windows Firewall has FFXIV allowed.

[Squa11_Leonhart]

Your assumption is wrong sir, I'm actually a level 2 tech for a pretty big company. It's not my PC, it's something to do with the driver. The way it's acting shows it to be that. I'm not here to argue.. I'm just trying to figure out why the hell this is happening to ONLY this game.

Edit: Anyway.. It doesn't matter anymore... It will eventually be fixed.

It will not be fixed by drivers, as YOU and only you are being affected by this. Francesca and other 900 series owners are not getting such crashes in this game.

You do not have certification in computer/electrical engineering, so i would like if you would not assume you know anything about silicon processors just because you are a level 2 tech. Level 2 is just barely above help desk, and are certainly NOT qualified for handling intricate hardware failure.

Please do not take this as a an attack, It is not intended as one, but i find it quite frustrating when people who don't actually know computer processors on a physical level, claim that something or another is and can only be a driver issue; Particularly when they are the only one getting the issue where others with similar hardware combinations do not.

It more often then not comes down to a software side issue.

Edit 2: Is there a way to turn debug logging on?

You can turn on/off application crash dumps using the reg keys in this link

http://www.mediafire.com/download/x4.../localdump.zip

This is my personal mediafire account and i certify that is all these reg files do

the dumps are then created at c:\Users\{UserAccount}\AppData\Local\CrashDumps\

The error you are getting is more then likely an access violation caused by client side DLL modules being loaded into every process, but not managing their own memory properly. You never posted your full system information screen, so that leaves us in the dark as to what is getting hooked/injected at runtime.

[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.