I'm crashing a lot on esamir in particular. crashing when viewing cert menu, loadout menu, or any other menu accessed through M key. as well And I used to run 90-110FPS for 3-6 hour sessions no problems Good job SOE. I guess summer sales are more important.
Lately, since the last major update and patches, I have unfortunately been experiencing massive problems regarding crashing. At times I can remain in game for 2 hours, other times... 30 minutes before I crash to desktop. Crashing to desktop appears to be random and happens despite location, environment, in or out of battles, population counts etc. It hasn't been this bad since the first couple months of the games release. Could it possibly be due to having Ultra enabled? My computer is perfectly able to handle this setting, maybe this may be the problem for others. I'll go ahead and change back to High setting. I play on the Connery server, so I don't believe the crashing to desktop problem to be exclusive to Briggs. I am running current Nvidia drivers. Please fix the situation soon, Planetside developers! I am not having a very fun experience
Thats not importat. High ultra mediun low. Its crashs every time. I try with GPUphysx and without. Settings on high or medium. Its doesnt matter.
Seems to be the case. I've been crashing and unable to log in to Briggs without sitting on the login screen for several minutes, when I usually get in instantly. The game is very broken.
Just installed the game today, got excited by game play trailers showing it to be pretty stable, completely fine when im in the original spawn point and through the tutorials... but out of spawn i can last 10 minutes max before i randomly crash, no error reports at all just windows telling me the game is not responding when i say random i mean completely random, there is nothing to connect the crashes, it generally stutters for a few seconds before the crash but thats all the warning i get tried deleting files suggested and validating, still crashes after 10 minutes every setting is on minimum, and its not my computer systems fault as i can play pretty much any other game out there, all drivers updated, decent hardware etc. highly frustrating EDIT: i also get stuck on logging in alot on char select screen and the circle just keeps spinning, not sure if this is related EDIT2: im on the woodman server
Yeah, SOE knows that. I hope they work already for a hotfix. I really want to play with friends but i cant play :/. For what i bought a new pc if i can not play
PlanetSide 2 was never entirely stable for me but since the latest GU both the client and the server (Woodman) seem to be crashing constantly. Running Win7 x64 NVIDIA GTX 660 w/ 314.22 driver i5-3570K 16 GB RAM (tested to be error free) on ASRock Z77 Pro3 Client files validated fine. Other applications are not randomly crashing, just PS2. Here's the harvest from this weekend. You'll notice some recurring fault offsets, so maybe that helps, but in game the crashes appear to be random both regarding time in game or actions in game, noticed no pattern or way to reproduce. Code: Faulting application name: PlanetSide2.exe, version: 0.0.0.0, time stamp: 0x519e724b Faulting module name: APEX_Emitter_x86.dll, version: 1.2.0.1, time stamp: 0x518941d4 Exception code: 0xc0000005 Fault offset: 0x000030a3 Faulting process id: 0x1050 Faulting application start time: 0x01ce5a055a69ed0a Faulting application path: E:\PlanetSide 2\PlanetSide2.exe Faulting module path: E:\PlanetSide 2\APEX_Emitter_x86.dll Code: Faulting application name: PlanetSide2.exe, version: 0.0.0.0, time stamp: 0x519e724b Faulting module name: PlanetSide2.exe, version: 0.0.0.0, time stamp: 0x519e724b Exception code: 0xc0000005 Fault offset: 0x018be382 Faulting process id: 0x177c Faulting application start time: 0x01ce5a1e54698eb1 Faulting application path: E:\PlanetSide 2\PlanetSide2.exe Faulting module path: E:\PlanetSide 2\PlanetSide2.exe Code: Faulting application name: PlanetSide2.exe, version: 0.0.0.0, time stamp: 0x519e724b Faulting module name: PlanetSide2.exe, version: 0.0.0.0, time stamp: 0x519e724b Exception code: 0xc0000005 Fault offset: 0x02558cf0 Faulting process id: 0xcac Faulting application start time: 0x01ce5a27cfd8ac2d Faulting application path: E:\PlanetSide 2\PlanetSide2.exe Faulting module path: E:\PlanetSide 2\PlanetSide2.exe Code: Faulting application name: PlanetSide2.exe, version: 0.0.0.0, time stamp: 0x519e724b Faulting module name: PlanetSide2.exe, version: 0.0.0.0, time stamp: 0x519e724b Exception code: 0xc0000005 Fault offset: 0x01639e80 Faulting process id: 0x1338 Faulting application start time: 0x01ce5a45e5582068 Faulting application path: E:\PlanetSide 2\PlanetSide2.exe Faulting module path: E:\PlanetSide 2\PlanetSide2.exe Code: Faulting application name: PlanetSide2.exe, version: 0.0.0.0, time stamp: 0x519e724b Faulting module name: PlanetSide2.exe, version: 0.0.0.0, time stamp: 0x519e724b Exception code: 0xc0000005 Fault offset: 0x018be382 Faulting process id: 0xddc Faulting application start time: 0x01ce5a4f5e66bfb9 Faulting application path: E:\PlanetSide 2\PlanetSide2.exe Faulting module path: E:\PlanetSide 2\PlanetSide2.exe Code: Faulting application name: PlanetSide2.exe, version: 0.0.0.0, time stamp: 0x519e724b Faulting module name: PlanetSide2.exe, version: 0.0.0.0, time stamp: 0x519e724b Exception code: 0xc0000005 Fault offset: 0x02558cf0 Faulting process id: 0xd88 Faulting application start time: 0x01ce5a61e9ae0663 Faulting application path: E:\PlanetSide 2\PlanetSide2.exe Faulting module path: E:\PlanetSide 2\PlanetSide2.exe Code: Faulting application name: PlanetSide2.exe, version: 0.0.0.0, time stamp: 0x519e724b Faulting module name: PlanetSide2.exe, version: 0.0.0.0, time stamp: 0x519e724b Exception code: 0xc0000005 Fault offset: 0x01639e80 Faulting process id: 0xb00 Faulting application start time: 0x01ce5a71bdba5b42 Faulting application path: E:\PlanetSide 2\PlanetSide2.exe Faulting module path: E:\PlanetSide 2\PlanetSide2.exe Code: Faulting application name: PlanetSide2.exe, version: 0.0.0.0, time stamp: 0x519e724b Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x30363838 Faulting process id: 0x171c Faulting application start time: 0x01ce5a7963a8766b Faulting application path: E:\PlanetSide 2\PlanetSide2.exe Faulting module path: unknown Code: Faulting application name: PlanetSide2.exe, version: 0.0.0.0, time stamp: 0x519e724b Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x30363838 Faulting process id: 0x674 Faulting application start time: 0x01ce5ac625a793dd Faulting application path: E:\PlanetSide 2\PlanetSide2.exe Faulting module path: unknown Code: Faulting application name: PlanetSide2.exe, version: 0.0.0.0, time stamp: 0x519e724b Faulting module name: PlanetSide2.exe, version: 0.0.0.0, time stamp: 0x519e724b Exception code: 0xc0000005 Fault offset: 0x018be382 Faulting process id: 0x171c Faulting application start time: 0x01ce5acac4a21a8d Faulting application path: E:\PlanetSide 2\PlanetSide2.exe Faulting module path: E:\PlanetSide 2\PlanetSide2.exe Code: Faulting application name: PlanetSide2.exe, version: 0.0.0.0, time stamp: 0x519e724b Faulting module name: PlanetSide2.exe, version: 0.0.0.0, time stamp: 0x519e724b Exception code: 0xc0000005 Fault offset: 0x02558cf0 Faulting process id: 0xfb8 Faulting application start time: 0x01ce5adfc0a2585a Faulting application path: E:\PlanetSide 2\PlanetSide2.exe Faulting module path: E:\PlanetSide 2\PlanetSide2.exe Code: Faulting application name: PlanetSide2.exe, version: 0.0.0.0, time stamp: 0x519e724b Faulting module name: PlanetSide2.exe, version: 0.0.0.0, time stamp: 0x519e724b Exception code: 0xc0000005 Fault offset: 0x02558cf0 Faulting process id: 0x1154 Faulting application start time: 0x01ce5aee580a8fd8 Faulting application path: E:\PlanetSide 2\PlanetSide2.exe Faulting module path: E:\PlanetSide 2\PlanetSide2.exe Code: Faulting application name: PlanetSide2.exe, version: 0.0.0.0, time stamp: 0x519e724b Faulting module name: PlanetSide2.exe, version: 0.0.0.0, time stamp: 0x519e724b Exception code: 0xc0000005 Fault offset: 0x02558cf0 Faulting process id: 0x10fc Faulting application start time: 0x01ce5b0200603d42 Faulting application path: E:\PlanetSide 2\PlanetSide2.exe Faulting module path: E:\PlanetSide 2\PlanetSide2.exe Code: Faulting application name: PlanetSide2.exe, version: 0.0.0.0, time stamp: 0x519e724b Faulting module name: PlanetSide2.exe, version: 0.0.0.0, time stamp: 0x519e724b Exception code: 0xc0000005 Fault offset: 0x018be382 Faulting process id: 0x1598 Faulting application start time: 0x01ce5b16c92a6df1 Faulting application path: E:\PlanetSide 2\PlanetSide2.exe Faulting module path: E:\PlanetSide 2\PlanetSide2.exe Code: Faulting application name: PlanetSide2.exe, version: 0.0.0.0, time stamp: 0x519e724b Faulting module name: PlanetSide2.exe, version: 0.0.0.0, time stamp: 0x519e724b Exception code: 0xc0000005 Fault offset: 0x007fc22a Faulting process id: 0x1238 Faulting application start time: 0x01ce5b280891bc62 Faulting application path: E:\PlanetSide 2\PlanetSide2.exe Faulting module path: E:\PlanetSide 2\PlanetSide2.exe Code: Faulting application name: PlanetSide2.exe, version: 0.0.0.0, time stamp: 0x519e724b Faulting module name: PlanetSide2.exe, version: 0.0.0.0, time stamp: 0x519e724b Exception code: 0xc0000005 Fault offset: 0x02558cf0 Faulting process id: 0x13bc Faulting application start time: 0x01ce5b29a003f86d Faulting application path: E:\PlanetSide 2\PlanetSide2.exe Faulting module path: E:\PlanetSide 2\PlanetSide2.exe Good luck with the bug hunt.
... what bothers me most is, that there is no response from SOE to this matter at all (at least based on what I saw in recent posts), and suggesting "to delete and validate files" is not enough. Many posts with lots of details like PC configuration, which game settings are used, when the crash happens, etc. which should give SOE a hint where to start looking at, e.g. Nvidia Users with PhysX enabled, or players using Ultra texture settings. Still many other things why the game could crash... Maybe also start an offical survey to find out how many users are really affected by those crashes (not everyone does post here) and / or frequency; and by doing this, collect details about the pc configuration / OS / drivers / etc. For now it just looks like, the users which are affected by those crashes are just left alone...
OMG i now have the falling through the middle of the earth bug that was fixed 5 updates ago when exiting a vehicle. On another note i got the new Razer keyboard, mouse and pad and it all looks great and back lit when the game crashes. Recommend big time, threw the last keyboard upside the wall due to PS2 but must say vast improvement and too expensive to fling. Mods you see why i posted prior to this update my whimsical Oh ****, not another update that you deleted? I rest my case.
Well, my gameplay this weekend was smooth and stable (with the exception of an audio bug which could be on my end... new sound card on the way) - and I will happily complain about crashes with the rest of us! Complete removal of the nVidia 320 drivers and the Physx they installed. Installation of 314.22. Game settings on High (no ultra settings.. maybe SOE knew what they were talking about when they said there were issues?) and Physx ON. I still seem to be CPU bound even though my GPU is running about 98% use and the CPU is maybe 50%.
I was having a similar problem after downloading GU9 last week, was crashing constantly anywhere from 1 minute to 20 minutes after logging in. I would have the very occasional crash before GU9. I downloaded the 320.18 drivers from Nvidia hoping to fix it but no joy, disabled PhysX and haven't had an issue since. My specs: AMD fx-6100 @ 3.3 8gb DDR3 EVGA GTX 660 TI GTX 560 (dedicated to PhysX) Windows 7 64 bit
In theory yes, they could admit it as surely they know about it at least in a form of a hint or something. But if they do imagine what this would mean logistically. The forums will explode, demands reimbursments, will be made etc, it is exactly what a developer fears the most. Bad publicity in two words. Back to the thread, I went back to 314.22 drivers and managed to pull slightly longer game times; 30-45 mins before a crash.
Ok i've tried that fix you suggested and it hasn't helped, game still crashes randomly. Doesn't matter if i'm fighting or just standing still. Guess we'll have to wait until GU 20 until it might be sorted out. On the upside i get much smoother FPS now with my Physx on and Ultra settings before i had it on low to get decent performance.
"Ausnahmecode: c0000005" and "Exception code: 0xc0000005" this is assuming you have done all the suggestions above and not just say you have. these exception codes are memory related. 1. run memtest - error no: go to 2 2. turn memory times to stock settings. if already stock go to 3 3. Are your memory sticks part of the qualified vendor lists of your motherboard no: go to 4 yes go to 5 4. run memory at the CPU specified frequency 1333 Mhz with timings supported by mem stick. if still no work go to 5. 5. run CPU at stock settings with supported memory speed. 6. Overclocking video card, turn down memory clock to stock settings. if already stock ignore 7. - disclaimer - if you do not know what you are doing with step 7 don't attempt go to control panel > system > advanced system settings click on settings in the performance section. - click on advanced > click on change... - click on custom size - initial size 16mb - maximum - set this to what it shows as recommended below. this is recommended if you use 4 GB or more ram as what this does it forces your ram to be used instead of your swap file unless your memory starts to run out. once that happens windows will open up your swapfile to what it needs and you can continue computing When setting the virtual memory to 16mb it will give you warning regarding setting the minimum below 800mb becuase of error reporting unable to record the problem. if you dont want to risk it set the minimum to 800. but this is relation to stop errors and blue screens etc. a further note if your memory is used up and windows starts to open up swapfile space there will be stutter while this is happening. My system is a i7 3770K @4.5Ghz 32Gb 1600Mhz RAM xmp profile ASUS Maximus V Gene 120GB SSD spit for C drive caching and PS2 stored on empty partition 2TB HDD for windows and files which have 20GB cache partition on SSD GTX 570 @900Mhz, 2000Mhz memory, 1075 mV GTX 285 Physx (which i cant use in PS2 cos it still not stable for my liking) a few update ago i was crashing every 5 mins. sometimes id just load up in the warp-gate and as soon as i started running forward i would crash. i was getting the same excpetion codes at the time i was runnign at 4.6Ghz on my CPU with new mem timings and No GPU overclock. when i ran through the above diagnostic i found my mem timings coupled with the overclock were too high. a turned them down and it worked out. and since then i have never had exsessive crashes. I do occasionally get flicker bug and i do even stutter on even rarer occasions but i never crash from these situations. i have even had the message come up saying PS2 has stopped responding and in 2 secs the game recovers it self. but on rare occasion it just stops and i cant recover. maybe once a week. i will say having memsticks which are on the QVL helps enormously with system stability this is an important step in game stability and overall system stability when overclocking. above steps might not help all. but just remember the exception code is coming from your memory this can be anthing from graphics cards, ram, hard disks (if using swapfiles) CPU L1,L2,L3 caches.
Then just run malware bytes or something why the hell would you bother stopping it from loading but not remove it?
If you know where its loading from you can remove it - with out adding more spyware malware BS scanners that add more
