Unfortunately even if disabling hyper threading or going down to one core stops the crash it is no kind of solution. For many people doing so will reduce the game's performance to the point is is essentially unplayable anyway. A game not being able to handle multi-core CPUs in the year 2014 is simple unacceptable and it will have to get fixed.
Neither I said that it's an acceptable solution, or that it doesn't have to be fixed, it was purely troubleshooting.
But if I must be honest with you, I'm very less mad at them for having problems on a system that could use up to 12 cores, than companies locking their software at 1 or 2 cores telling you to just "deal with it".
I mean, I'm using an hyper threaded esa-core at 4.2 GHz, I might still be able to do it, but when limiting cores on lower frequencies, say, 2.7-3 GHz, you're really doing it wrong, and I've been on that part of the spectrum for a long time.
Again though, if you're having heavy troubles like I did, and could try the Process Affinity, it could really help them pinpoint the problem and fix it sooner. I still don't know if this works only for me and the other guy in this thread before, or for everyone. Knowing this makes a huge difference.
@Varstahl wrote:Neither I said that it's an acceptable solution, or that it doesn't have to be fixed, it was purely troubleshooting.
But if I must be honest with you, I'm very less mad at them for having problems on a system that could use up to 12 cores, than companies locking their software at 1 or 2 cores telling you to just "deal with it".
I mean, I'm using an hyper threaded esa-core at 4.2 GHz, I might still be able to do it, but when limiting cores on lower frequencies, say, 2.7-3 GHz, you're really doing it wrong, and I've been on that part of the spectrum for a long time.
Again though, if you're having heavy troubles like I did, and could try the Process Affinity, it could really help them pinpoint the problem and fix it sooner. I still don't know if this works only for me and the other guy in this thread before, or for everyone. Knowing this makes a huge difference.
Not trying to jump on you. I just want to underline that this is in no way a final fix because I am paranoid about EA taking this as an excuse to ignore the issue...they already marked on earlier thread on this issue as "solved" because of the disabling multi-core thing.
I've tried setting affinity to core 0 without any luck. Incidentally when running game with -safe flag i was able to play for about an hour without any issues. I am not sure whether the flag only lowers settings to bare minimum or does other things as well.
If i didnt know any better i'd say its a problem with my GFX (670 GTX). However i've ran a burn-in test for about 20 minutes and it was stable on 100% power.
Incidentally, I also have a GTX 670. Btw, I ran the test on Core 0 with all options turned on at maximum, including textures on Insane.
If you don't mind me asking, how did you set up the processor affinity? Before pressing the "play" button ingame? And if you did that, did you see in the resource tab of task manager that the core you specified (and only that) was running at 100% capacity, while the other cores where practically idle?
Dump file sended 😕mileyfrustrated:
I've ran the game, then alt-tabbed from the menu to set affinity in task manager, after that i joined a game and started playing. The first core then fluctuated between 95-100% and the others were all <15%
Also now i am positive it is not the gfx. I've kept an eye on my temp/voltage and i've managed to play just fine with my standard 80C for about 20 minutes with everything on ultra. However sometimes the game crashes just after 30 seconds for no good reason.
EDIT: I'd also like to add that i've played beta without any issues, with my settings maxed.
Yep, sounds consistent. On the mission I specified it would crash a lot in a very short time, but I admit that while testing I would start loading that mission, end it safely, quit and retry.
But if it's taking just "longer", like thedarktangent said, I could still be right in the fact that the timing is aggreviated on multiple cores, while on single core is sporadic but still happens.
Edit: after reading your edit, I remembered that on the beta I had this problem too, but it ended once I disabled Origin overlay. And I feel quite stupid in admitting that today after all the tests I actually didn't try it out.
I have the overlay disabled for all the games, doesnt help much.
