Fatal DirectX Error Again (Not resolved)

Hey all, for some reason my last thread got sent to the resolved section. This issue had been good for about 24 hours and just recently started again. Haven't changed anything. Here are the logs from my event viewer. Any help would be appreciated.

Edit: As a note, I have the application allowed through my firewall and antivirus.

1)Application ffxiv.exe has been blocked from accessing Graphics hardware.

2)Faulting application name: ffxiv.exe, version: 1.0.0.0, time stamp: 0x537031fd
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0xbf6803cc
Faulting process id: 0x110c
Faulting application start time: 0x01cf73bd0bf4361b
Faulting application path: F:\Steam\steamapps\common\FINAL FANTASY XIV - A Realm Reborn\game\ffxiv.exe
Faulting module path: unknown
Report Id: 42acd390-dfc3-11e3-826c-f46d04561eb6
Faulting package full name:

Glancing at your other thread, it sounds like a driver for an input device is not playing nice. Common culprits are certain models of Logitech keyboards or mice, and touch screens. More frequent for people who upgraded from Win 8.0 to 8.1 versus a clean 8.1 install. Check for updated drivers for your input devices if you haven't already. Some have had success by setting the WUDF service to automatic instead of the default manual (triggered) startup in the services snap-in (services.msc from run/search box, right click "Windows Driver Foundation - User-mode Driver Framework" to access it's properties page to change the startup type, apply the change, then reboot).

As for 8.1 not being supported as mentioned earlier, it wasn't officially supported in much the same way as Windows XP. It may run just fine, it may have issues. SE never really completed testing/debugging for the new environment--the website says differently now, but for a long time the official line was that 8.1 was not really supported. It is now, but it isn't... moreso because they don't really know what's wrong with it when it breaks, because the issue typically is due to an issue with a third party vendor's driver not behaving with 8.1's new API's (more specifically, the new DirectX9 emulation layer--note that Win8.0's D3D9.DLL was a 6.2 release, and in Win8.1 it is 6.3). Some have managed to correct some issues with the emulation by running the off-line installer for DirectX9 . By default, you download a small stub for on-line install. In the notes at the download page, there is a link to a 95MB download that unpacks installers that copy all the DLL's and register them--usually one of these is missed by the online installer and causes an error because of a broken association to one of the D3D9 support dll's.

Simply put, there were a lot of glitches when 8.1/IE11 was released last fall, some of which have yet to be fully vetted by Microsoft and other vendors--it isn't JUST SE having trouble with it. It's a more common problem than a lot of people realize, and simply is not quite fully supported across the board just yet. Win 8.0 and MSIE10 were still having support issues when Win8.1 and MSIE 11 hit the market, and the developers of both software and hardware are having a hard time slapping the band-aids on fast enough to keep things working.