MP Crash 1.2.4. 1185

[hawk2495]

I've had a series of MP crashes tonight, and have never had such before in any previous version. The happened in two servers. The first was the 159th, and the two following crash logs showed up:

 

# -------------- 20130509-025746 --------------

 

# C0000005 ACCESS_VIOLATION at F8371D94 00:00000000

00000000 00000000 0000:00000000

F8371D94 0023EFA0 0000:00000000 ?simulate@Car@LandVehicle@EagleFM@@UEAAXN@Z()+74

E3D9B15D 0023F0C0 0000:00000000 ?humanNextStep@woCar@@AEAAXAEAN@Z()+21D

E3D4EB91 0023F0F0 0000:00000000 ?CalculateBox@wcaMirageActivity@@MEAAXXZ()+2F1

FAC786B1 0023F180 0000:00000000

FAC78B6B 0023F1D0 0000:00000000

3F44A929 0023F260 0000:00000000

3F44D47D 0023F2C0 0000:00000000

3F463DA4 0023F2F0 0000:00000000

3F463C7B 0023F320 0000:00000000

3F4F42C8 0023F390 0000:00000000

3F4F579E 0023F990 0000:00000000

3F4F83CF 0023FA40 0000:00000000

7793652D 0023FA70 0001:0001552D C:\Windows\system32\KERNEL32.dll BaseThreadInitThunk()+D

77B6C521 0023FAC0 0001:0002B521 C:\Windows\SYSTEM32\ntdll.dll RtlUserThreadStart()+21

 

 

# -------------- 20130509-025838 --------------

 

# C0000005 ACCESS_VIOLATION at FA951D94 00:00000000

00000000 00000000 0000:00000000

FA951D94 0026EF90 0000:00000000 ?simulate@Car@LandVehicle@EagleFM@@UEAAXN@Z()+74

E50CB15D 0026F0B0 0000:00000000 ?humanNextStep@woCar@@AEAAXAEAN@Z()+21D

E507EB91 0026F0E0 0000:00000000 ?CalculateBox@wcaMirageActivity@@MEAAXXZ()+2F1

FAC786B1 0026F170 0000:00000000

FAC78B6B 0026F1C0 0000:00000000

3F3AA929 0026F250 0000:00000000

3F3AD47D 0026F2B0 0000:00000000

3F3C3DA4 0026F2E0 0000:00000000

3F3C3C7B 0026F310 0000:00000000

3F4542C8 0026F380 0000:00000000

3F45579E 0026F980 0000:00000000

3F4583CF 0026FA30 0000:00000000

7793652D 0026FA60 0001:0001552D C:\Windows\system32\KERNEL32.dll BaseThreadInitThunk()+D

77B6C521 0026FAB0 0001:0002B521 C:\Windows\SYSTEM32\ntdll.dll RtlUserThreadStart()+21

 

These wouldn't even let me select an aircraft before the crash.

 

This was from EZ's server, it actually allowed me to select, startup, and taxi a P-51 to runway before crash. Most disappointing.

# -------------- 20130509-030723 --------------

 

# C0000005 ACCESS_VIOLATION at 3F7383C5 00:00000000

00000000 00000000 0000:00000000

3F7383C5 0024EC00 0000:00000000

3F7691D9 0024EC30 0000:00000000

3F732669 0024ED10 0000:00000000

3F766507 0024EE60 0000:00000000

3F7781E5 0024EF00 0000:00000000

3F6F977A 0024F050 0000:00000000

3F6F561E 0024F080 0000:00000000

FAC786B1 0024F110 0000:00000000

FAC78B6B 0024F160 0000:00000000

3F7DA929 0024F1F0 0000:00000000

3F7DD47D 0024F250 0000:00000000

3F7F3DA4 0024F280 0000:00000000

3F7F3C7B 0024F2B0 0000:00000000

3F8842C8 0024F320 0000:00000000

3F88579E 0024F920 0000:00000000

3F8883CF 0024F9D0 0000:00000000

7793652D 0024FA00 0001:0001552D C:\Windows\system32\KERNEL32.dll BaseThreadInitThunk()+D

77B6C521 0024FA50 0001:0002B521 C:\Windows\SYSTEM32\ntdll.dll RtlUserThreadStart()+21

 

Any ideas guys?

[JG14_Smil]

First thing to check is to set connection speed to Lan in MP options. If that is set, and I have a night where I get booted every time (which I don't, after setting speed to Lan), I would delete my network vault and cfg file and redo the MP connection. I've seen this help before so it is something to try.

Edited May 10, 2013 by JG14_Smil

[hawk2495]

I'll give that a try, thanks for the reply smil. Funny thing is, I post this, get back on, and it works magically... Not holding my breath though. I'll have to do some more testing this weekend.