Ever since I bought FFXIV it has done nothing but crash. The times in between crashes are very sporadic, ranging from 1 hour to 5 minutes to 3 hours. The game crashes to desktop every time, and no BSOD. As of right NOW this is what the event log says.
Faulting application name: ffxiv.exe, version: 1.0.0.0, time stamp: 0x5306d9ee
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x19f62800
Faulting process id: 0x2ec
Faulting application start time: 0x01cf3264c116cf6a
Faulting application path: C:\Program Files (x86)\SquareEnix\FINAL FANTASY XIV - A Realm Reborn\game\ffxiv.exe
Faulting module path: unknown
Report Id: cc2e99a8-9e5a-11e3-b25b-ac220b504d72
What is discerning to me is that before, the event log said: Faulting module name: nvd3dum.dll I don't know what changed but it is very suspicious. I don't know if these other errors that came up on the log have anything to do with the game but...
Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected.
The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID
{22279AF5-03AE-4CAF-989D-2530918B2F1C}
and APPID
{0773CCD6-59A2-4D26-B235-19247767E645}
to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC). This security permission can be modified using the Component Services administrative tool
My computer specs are:
ASUS M5A99FX PRO R2.0
GeForce GTX 760
AMD FX(tm)-6100 Six-Core Processor
8.00 GB RAM
Driver Version 334.89
Windows 7 Pro 64 bit
And since I have no idea what the issue could possibly be I'm going to throw out everything I've tried to troubleshoot. I have toggled in and out of windowed and full screen in game, (seemed to help some people...) Ran Windows Memory Diagnostic twice but the computer froze both times at 2/2 99% Overall Completion I have yet to try memtest. I have uninstalled and reinstalled the game 5-8 times. Did a clean reinstall of my drivers, updated sound driver on MB. Ran CCleaner to fix registry errors, the game did come up as an issue but.....it didn't fix the problem. I bought this game on the 7th of Feb and it has been crashing since day 1. Now another thing I have to mention is that I have a HD from my old computer hooked up to this one, not reformatted so it still has the old computer OS on it and all the files, don't know if that is an issue but I'm just throwing it out there. I have not disconnected the HD from the computer yet because I don't know if its really a problem that I need to tear my computer out of my desk for. I have taken out memory sticks to test if they were faulty, but the same error keeps popping and the game keeps crashing. I installed Hardware Monitor and the GPU core stays at 60 degrees C when the game is in play and all the temperatures are good. My brother went into BIOS and did some tinkering in there...not sure what he did but it didn't help either. I keep hoping its just a simple issue that hasn't been discovered yet. This is the only game that I play with desktop crashes, I've played Rust, Skyrim, Elder scrolls beta no problems...I'm pretty sure I've done other troubleshooting but I don't remember them all >..< I'm getting pretty desperate here. ;-;
Faulting module name: unknown
Printable View
-
02-26-2014, 09:50 AMIlonaWFaulting module name: unknown
-
02-26-2014, 11:28 AMGunnerAU
The Nvd3dum.dll file is a graphics card related driver dll. Have you conisdered the possibility there's a hardware issue with your card, or even your motherboard?
Also, have you tried using older versions of your graphic drivers? On my gaming laptop (before the motherboard got fried...) I had some issues with the more recent NVidia Drivers slowing down and crashing games, but when I rolled back games like XCom and Tomb Raider went from choppy mess with crashes to smooth game play.
I'm no techpert though, so take my comment with a pinch of ram. -
02-26-2014, 11:41 AMaerolol
lol there's even a SQL query on the error =O
-
02-26-2014, 12:03 PMIlonaWSQL?? :< I don't know much about computers so i don't know what that means :(Quote:
Originally Posted by aerolol
-
02-26-2014, 12:04 PMIlonaWAs far as Nvd3dum goes, the event log says now "unknown" :<Quote:
Originally Posted by GunnerAU
-
02-26-2014, 12:07 PMDSNQuote:
Originally Posted by aerolol
Its actually WQL the query language for WMI -
02-28-2014, 12:29 PMIlonaW
For anyone who also gets this error, the problem was fixed by installing the first beta driver for my video card.