Constantly crashing

[Kennitus]

Well for you at this point I don't know if it's coming from SE or your PC, because I know some people that had never crashed at all and one of them is playing on a gaming laptop GTX 560 M. Some says it's the server too... dunno but good luck.

[Kennitus]

Intel core i5 at least must be the solution.

[Kennitus]

I know some people that had never crashed at all and one of them is playing on a gaming laptop GTX 560 M.

He plays on highest laptop settings... never crashed at Coerthas neither at Mor Dhona. Gotta know if its SE coding errors or computer specs at the end.
Is SE even reading this thread?

[Kennitus]

Bump. Well it's start crashing at Coerthas. This really need to be fixed!

[Kennitus]

Another bump.
I'll tell you what result it'll give when I'll upgrade, in two three weeks, my Pentuim Dual-Core CPU E5300 / 2.60GHz to an Intel Haswell Processor Core i7-4770K / 3.50 GHz Quad-Core Socket-LGA1150 8 Mo

[Eagle7D8]

I am having major crash issues on PS3. It just kicks me to the XMB randomly while zoning. Not sure if it's the same cause as the PC people but SE needs to fix it.

[Ubermann]

Constant crashing indeed, this has been around for a long time now.... Address this, please!

[Nashie]

First day playing and crashing every 5 minutes. Luckly being in IT im able to track problems down pretty quick.

I havent gone through the settings yet to adjust it, but I can tell its a graphics card heat issue with a couple other games have. HWmonitor shows I go from 120 degrees outside game to near 200 in game. Overclocked GTX670. Most games for me run around 160 degrees. Gonna start playing with settings and if I find anything Ill post, after I turn my fan up

[Ubermann]

First day playing and crashing every 5 minutes. Luckly being in IT im able to track problems down pretty quick.

I can tell its a graphics card heat issue.

Misdiagnosis.

Its not a heat issue. I'm playing with the same rig that I used at launch, a rig that did not encounter this problem until after the patch mentioned in this thread's OP. A rig which ONLY encounters this problem while FATE grinding, often the second a FATE ends, ONLY in zones with a lot of players, with crashes occurring when many of those players aren't even being rendered.

I have a GTX 550 Ti, play on the the lowest settings available in the game (Medium for laptop), and have all effects for other players turned off. My PC isn't amazing, but it can handle plenty of other far more demanding games than this without issue.

So no, its not a heat issue; its bad coding and programming on SE's end, just like the R6025 runtime error is. Its also inexcusable that both errors have persisted for so long.

[Marishi-Ten]

Misdiagnosis.

Its not a heat issue. I'm playing with the same rig that I used at launch, a rig that did not encounter this problem until after the patch mentioned in this thread's OP. A rig which ONLY encounters this problem while FATE grinding, often the second a FATE ends, ONLY in zones with a lot of players, with crashes occurring when many of those players aren't even being rendered.

I have a GTX 550 Ti, play on the the lowest settings available in the game (Medium for laptop), and have all effects for other players turned off. My PC isn't amazing, but it can handle plenty of other far more demanding games than this without issue.

So no, its not a heat issue; its bad coding and programming on SE's end, just like the R6025 runtime error is. Its also inexcusable that both errors have persisted for so long.

I don't think it's a programming issue on the server end. If it was, we all would have the same issue. Just reading through this thread, there are at least 3 separate issues going on:

1.) Heat. Heat drives down voltage. As voltage drops, efficiency drops. As efficiency drops, the GPU ramps up to balance supply/demand. Rendering becomes unstable. Instead of looping forever, the card forces a panic and windows kills the program.

2.) Drivers. When updating drivers, you never really get rid of the old driver (unless you scrub it in safe mode). The bits and pieces of the old driver could cause a panic and force close the program in an attempt to resolve the render loop.

3.) Hardware Issue. Maybe the card is just bad/going bad. Semi conductors go bad all the time. Crappy solder job from the tool at the plant, a bad dye, impurities on the etching of the board, a blown or inefficient capacitor. All these can cause all sorts of havoc.

I wouldn't rule anything out. Heat can and will cause exactly what some users are seeing. Without testing and consolidation of information, there isn't a way to tell if there is a common link.