9 réponses à ce sujet

[Nerag]

 This has been happening ever since I added Retaliation. Happening to anyone else? I've already ran the repair install but the same thing is happening...

[Mesdalla]

That error gives me since the last update of the game, despite the help.ea.com tell him, or have not bothered to say anything.
I think it's for the certificates of authenticity d EEA-Bioware, antivirus-firewall that will block, apeasr let you access it, block it.

So that means you have not bothered the EA-Bioware to update these certificates to other companies and they block it. As EA-Bioware has no technical support, more than in Canada, not s emolestan to see the reasons of other users complaining about their incompetence.

[.458]

For a long time, if there is any downloading or load screen, my windows 7 will immediately complain that ME3 stopped responding if I do ANYTHING other than wait for it to finish. I don't think there is any support for this to function correctly, e.g., to alt tab out, if it doesn't work for you. Seems to work for some people.

[sirjimmus86]

This has been happening to me too for the last few days, although I was able to install and play retaliation for a while before it got to be a problem.

I did hear one suggestion about uninstalling the most recent windows updates, which I did, but that hasn't helped either.

There are lots of people with this problem, from what I can tell they are in Europe mostly, how about you?

[Shepardess]

UK, identical problem to you ^^ retaliation worked fine for a few days - I've been playing since release without any issues until now.

[sirjimmus86]

Still not working, sorry for spamming so many threads but trying to make sure someone who actually has an insight into what might be broke sees it.

[.458]

USA here. Doesn't seem to be a region issue, and I doubt windows update can be held responsible for issues once an update is complete and the system is rebooted. Makes me wonder if they are using some sort of cpu affinity feature that isn't yielding.

[sirjimmus86]

Well I didn't really think there was much to lose by trying it, it didn't work and I've reinstalled the updates now so that was that.

Could you explain what you mean by the cpu affinity feature thing?

[.458]

sirjimmus86 wrote...

Well I didn't really think there was much to lose by trying it, it didn't work and I've reinstalled the updates now so that was that.

Could you explain what you mean by the cpu affinity feature thing?

It's an advanced performance tuning thing which is almost always just handled by the operating system. It is possible that if someone is concerned about multi-cpu or multi-core performance they might attempt to use this.

Normally when there are several cpu cores to work with the operating system decides which core to use. It becomes possible that different tasks may migrate at different times to different cores, depending on the operating system's idea of which core is a lower load at the time. It keeps cpu use balanced and on average the system stays responsive.

A disadvantage of normal behavior is that there is a lot of cache ram involved at multiple levels within cpus themselves, along with cpu registers. If an operation hits a cpu where the cache is already what is needed, it is a cache hit. If an operation uses a core which requires flushing the current cache and registers and reloading, it is a cache miss. Cache miss can be very expensive.

So sometimes the operating system will provide a means to tell it that a given cpu core is to be dedicated to a particular thread or process. When this happens, nobody else can use that cpu core. The system is somewhat less responsive, but the process that has affinity will not suffer the cache misses and will become more efficient.

I wonder about whether there is some affinity thing going on because normally I would not expect simple multitasking things like alt-tab to force instant failure. I have to admit though that what I deal with in terms of cpu affinity is not on windows, and afffinity features/quirks are highly specific to the operating system and often even the hardware. If this isn't a case of some demand for ME3 to hold a cpu when asked to yield, it could just be a flaw of the operating system itself.

Modifié par .458, 16 octobre 2012 - 12:49 .

[nanotm]

well i dont know about it being a cpu affinity thing but certainly everytime it "checks" something like the origin communication it hangs and half the time theres an app crash

so i would of thought its more a system integration issue between me3 and origin most likely caused due to the origin updates each time a new game is released (meaning its looking for more than one game's comms and so your always gettign hit by a wait cycle that never existed when me3 was released) to test this i opened DA2 and me3 through origin and magically tabbing between them was alsmost seamless as was the reduction in load times etc the problem was trying ot have a frame rate above zero at higher settings

edit after more messing about it seems it might actually be down to a port conflict problem caused by ms office and adobe updater

i just removed both from the startup list and then changed em to manual services starts rather than auto /delayed

so annoying but it seems ot have fixed the problem that was started wiht the last patch, hopefully this will be the case for more people as well

Modifié par nanotm, 16 octobre 2012 - 01:51 .