-
I'm Running this Game with an AMD Phenom II X6 processor, with Ati HD 6850 graphics card and having the same problem. Sounds to me it's more of a software problem more so than hardware. Espcecially since it's not native to a specific type of processor, Mother board, OS, or Graphics card. The problem seems to be persistent no matter what machine your running.
I had even downgraded from windows 8 to windows 7 64 bit and did every possible form of troubleshooting. Problem still occured. I just hope there will be a patch whether it be from SE, microsoft, ati, or amd, etc.
-
-
PS3 Crash
I have only had one crash* with my PS3 previously, up until yesterday when I had 2 with in a couple hours. 1 on the way to the level 38 dungeon in Central Thanalan and the other in the dungeon Cutter's Cry.
*The previous one was right after they initiated the 30 minute afk timer.
-
I'm canceling my sub to FFXIV because of this and going back to that 'leading competitor' temporarily. I'll be eagerly watching until this gets fixed (if it ever does). Good luck, peeps.
-
I've encountered lots of problems while overclocking my AMD Phenom II Black Edition or my 550GTX TI. Both give the same results: Game crashes since the last phase of the open Beta at random occasions. During early Beta 3, I could oc my system just as I wished even while the game was running.
Since the day that brought the "benchmark tool", this was completly impossible. I had to make my settings prior to starting the tool, if something didn't work well I had to reboot. Seems like that tool and the release client save hardware settings throughout changes, even with restarting the client.
The final result for me is:
- VGA card overclocked a) random fragmentation in dungeons b) blue screens on any place on a random time span (can bei 5 minutes or 5 hours in between)
- CPU overclock just blue screens on the same random time span as with VGA card.
Why did this work perfectly during beta and is now piece of crap? I could easily run my CPU with a multiplier of 20 instead of basic 16 (which means 0,8GHz more) and ~22% more in VGA card, now it even gives BSoD on the lowest increase (0,5 multiplier for example).
-
I just got a BSOD while not even actively using the computer the game was running on. I was sitting idle in a zone while queued for the duty finder, so I was checking stuff on my laptop.
I managed to quickly jot down some information on the BSOD, which pointed to a file named nvlddmkm.sys. Additional crash report as follows:
Problem signature
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.4
Locale ID: 1033
Files that help describe the problem
100713-9796-01.dmp
sysdata.xml
WERInternalMetadata.xml
View a temporary copy of these files
Warning: If a virus or other security threat caused the problem, opening a copy of the files could harm your computer.
Extra information about the problem
BCCode: 1000007e
BCP1: FFFFFFFFC0000005
BCP2: FFFFF8800662B896
BCP3: FFFFF8800836B1E8
BCP4: FFFFF8800836AA40
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1
After Googling nvlddmkm.sys, one suggestion is to disable Aero in Windows 7. Silly as that sounds I'll try anything at this point.
-
Hello guys, I was having these problems everytime I was playing with a video drive. At the time I was using the GeForce 327.23 Driver and then I tryed to downgrade and used the GeForce 320.49 Driver but still got the crashes. After play without drive for the weekend I tryed a Beta Driver the GeForce 331.40 Driver - (BETA) the that it was made to BF4 Beta it looks like. Not having any problems so far and playing for 4 days without any problem. Hope this help some of you.
o3o/
-
going to have to test out both the above.
disabling aero and using the new beta driver..
-
tried both beta 331.40 driver and disabling aero.. still crashed.
-
Same issue here. I'm getting BSOD while in dungeons (as a healer this is really bad for the group) and even by idling in town i sometimes get it.
Tried various nvidia drivers and still the same issue, tweaked in-game display settings and nothing. Surfed around Google and no fixes found.
An SE mod said something in this thread "we are looking on this issue", so any enlightenment about a possible fix for this? or are we bound to deal with this during our game experience?
So far nothing else has been said/done about this problem.
Thanks.