EA Staff (Retired)@B0bbyBiraciall, I don't think your problems sound like the Intel issue that (so far) seems to have been successfully worked around in today's patch. It definitely can't cause "Connection to server timed out". There are only two things I know of that can cause that:
1. Your internet connection to the server cuts out for a "long enough" period of time. With the modern internet, this is almost always a problem between the consumer and the ISP, and very often WiFi.
2. If it happens when connecting to a match, it could also be that you took too long loading. The loading we do during the game shouldn't be able to make you time out from a server, even if it takes a crazy long time.
Now, I didn't personally work in any of that code, so I don't know if there are other reasons.
unfortunately after a couple of hours of fun the problem manifests itself again, attached the new crash file.
another one
EA Staff (Retired)@Ruon-21, this is a crash I haven't seen before. Thanks!
There are two addresses to consider:
0x00007FF7BD29FCE0 -- this is the address of the function we wanted to call.
0x40007FF7BD29FCE0 -- this is the address we actually tried to call.
Under 64-bit Windows, memory addresses starting with 0x4 are invalid, so Windows says you got a memory access violation at address 0xFFFFFFFFFFFFFFFF. This is a magic address that the OS reports whenever there is a memory violation you can detect just by looking at the memory address without even trying to look at the memory that the address points to. An analogy would be the post office recognizing that you put a haiku instead of a recipient address on an envelope, so they don't even bother putting it on a truck to find the house.
You'll notice that the only difference between the correct address and the address we tried to call is that the first digit is a 4 instead of a 0. In binary, that's a single bit difference. I don't know any way that the code that fills in this memory could toggle that bit, so it suggests that some other random code is changing that bit behind our back. This sort of bug is really hard to fix without a repro case and/or lots of crash reports.
EA Staff (Retired)@Ruon-21, this is another unique crash I've never seen before. Thanks! I've added it to our bug database.
Suspiciously, in this bug, it looks like RSI is 0x40000290, which is clearly an invalid value and causes the crash. However, 0x00000290 would be a valid value. Just like your last bug, it looks like something changed a 0 to a 4, which is again setting a single bit.
Community Manager
