Jump to content
Welcome to the virtual battlefield, Guest!

World War II Online is a Massively Multiplayer Online First Person Shooter based in Western Europe between 1939 and 1943. Through land, sea, and air combat using a ultra-realistic game engine, combined with a strategic layer, in the largest game world ever created - We offer the best WWII simulation experience around.

CTD logs 01/12/12


Ogg
 Share

Recommended Posts

GOPHUR is there anything else needed that you'd like in the reports?

flying quite a while tonight nothing until this respawn after a death.

ww2errinfo.dmp

1

4278657537

1326426166

38

1109188752

0

3221225477

6545664

0

GL Vendor: ATI Technologies Inc.|Renderer: ATI Radeon HD 5800 Series|Access violation: Illegal read by 0063E100 at 00000058

$Id: wwiiClientMessages.cpp 3678 2010-05-18 08:10:04Z osmith@CRS $

WW2_Log.txt

first 2 and last 2

[Thu Jan 12 19:28:18.742 2012] t:0 closing code:30100

[Thu Jan 12 19:28:19.261 2012] t:1 closing code:30006

[Thu Jan 12 19:28:19.787 2012] t:2 closing code:30006

Thu Jan 12 19:28:19 2012 network election of 2 addresses: 66.28.224.143:268ms. 209.144.109.143:275ms. Winner: 66.28.224.143

[Thu Jan 12 19:28:20.084 2012] t:3 srvInf

[Thu Jan 12 19:28:20.337 2012] t:3 on:1 h:1109188751 p:27015 aMap

[Thu Jan 12 19:32:02.195 2012] t:3 pAcc

[Thu Jan 12 19:32:13.725 2012] tciRx ro:2 ip:0.0.0.144

[Thu Jan 12 19:32:13.743 2012] t:3 sNot

[Thu Jan 12 19:32:13.743 2012] ! no cell for rvj

[Thu Jan 12 19:32:13.860 2012] tciNoCnx

[Thu Jan 12 19:32:14.40 2012] Netcode2:66.28.224.144 Opening 66.28.224.144...

[Thu Jan 12 19:32:14.040 2012] t:5 on:1 h:1109188752 p:27015 aCell

[Thu Jan 12 19:32:14.040 2012] redired

[Thu Jan 12 19:32:14.148 2012] Netcode2:66.28.224.144 Opened

[Thu Jan 12 19:32:15.677 2012] Netcode2:66.28.224.144 Established

[Thu Jan 12 20:09:08.544 2012] Netcode2:66.28.224.144 Disconnecting

[Thu Jan 12 20:09:08.544 2012] Netcode2:66.28.224.144 Max bps: 0.00 in, 0.00 out

[Thu Jan 12 20:09:08.544 2012] Netcode2:66.28.224.144 Session Statistics:

Actual bytes per second sent 992

Actual bytes per second received 2544

Message bytes per second sent 720

Message bytes per second resent 72

Message bytes per second queued 720

Message bytes per second processed 2191

Message bytes per second ignored 74

Total bytes sent 2382733

Total bytes received 2957717

Total message bytes sent 1556623

Total message bytes resent 1224

Total message bytes queued 1556623

Total message bytes received 2130558

Total message bytes ignored 456

Messages in send buffer, by priority 0,0,0,0

Bytes in send buffer, by priority 0,0,0,0

Messages in resend buffer 1

Bytes in resend buffer 72

Current packetloss 0%

Average packetloss 0%

Elapsed connection time in seconds 2214

and

[Thu Jan 12 22:41:56.392 2012] Netcode2:66.28.224.144 Session Statistics:

Actual bytes per second sent 1088

Actual bytes per second received 2512

Message bytes per second sent 720

Message bytes per second resent 0

Message bytes per second queued 720

Message bytes per second processed 2154

Message bytes per second ignored 0

Total bytes sent 617341

Total bytes received 975445

Total message bytes sent 402149

Total message bytes resent 0

Total message bytes queued 402149

Total message bytes received 762430

Total message bytes ignored 0

Messages in send buffer, by priority 0,0,0,0

Bytes in send buffer, by priority 0,0,0,0

Messages in resend buffer 1

Bytes in resend buffer 72

Current packetloss 0%

Average packetloss 0%

Elapsed connection time in seconds 588

[Thu Jan 12 22:41:56.508 2012] spe

[Thu Jan 12 22:41:56.508 2012] t:25 sending pEx with result: 23

[Thu Jan 12 22:41:56.579 2012] t:25 closing code:30014

[Thu Jan 12 22:41:56.579 2012] t:25 got ENOTCONN:10057

[Thu Jan 12 22:41:56.579 2012] t:25 closing code:30122

[Thu Jan 12 22:41:56.840 2012] pmr

[Thu Jan 12 22:41:56.860 2012] t:26 closing code:30122

[Thu Jan 12 22:41:56.860 2012] spe

[Thu Jan 12 22:41:56.860 2012] pEx/no cell

[Thu Jan 12 22:42:07.602 2012] t:3 pAcc

[Thu Jan 12 22:42:07.904 2012] tciRx ro:2 ip:0.0.0.144

[Thu Jan 12 22:42:08.310 2012] t:3 sNot

[Thu Jan 12 22:42:08.310 2012] rvj

[Thu Jan 12 22:42:08.424 2012] tciNoCnx

[Thu Jan 12 22:42:08.600 2012] Netcode2:66.28.224.144 Opening 66.28.224.144...

[Thu Jan 12 22:42:08.600 2012] t:27 on:1 h:1109188752 p:27015 aCell

[Thu Jan 12 22:42:08.600 2012] ! cell active

[Thu Jan 12 22:42:08.600 2012] redired

[Thu Jan 12 22:42:08.706 2012] Netcode2:66.28.224.144 Opened

[Thu Jan 12 22:42:46.430 2012] Netcode2:66.28.224.144 Established

Date and time: 1/12/2012 22:42:46

Program compile time: Dec 12 2011 10:19:10

File version: 1.34.7

GL Vendor: ATI Technologies Inc.

Renderer: ATI Radeon HD 5800 Series

Access violation: Illegal read by 0063E100 at 00000058

Link to comment
Share on other sites

This is the important part:

Access violation: Illegal read by 0063E100 at 00000058

And we already collect that automatically. It's number four on the list with 400 examples since the release of 1.34.7.

Looks like youget all 4 of our major crashes. Many of these are memory related with terrain.

I show you having 3 crashes on the 15th and 4 on the 14th.

I assume you fly a lot which is producing these memory errors. Can I ask how much ram you have and what your swap file usage is looking like when your flying?

This should be fixed in the beta. I can make a PC open test client if you are interested in taking the time to fly around a bit and see if you still get the crash.

Link to comment
Share on other sites

This is the important part:

Access violation: Illegal read by 0063E100 at 00000058

I assume you fly a lot which is producing these memory errors. Can I ask how much ram you have and what your swap file usage is looking like when your flying?

This should be fixed in the beta. I can make a PC open test client if you are interested in taking the time to fly around a bit and see if you still get the crash.

Patriot Viper 6GB (3 x 2GB) 240-Pin DDR3 SDRAM DDR3 1333

Not sure what swap file usage even is......I can build em but don't know cowdung abut what makes em tick.

I am pretty much a stick jockey.

I'll be happy to help any way I can. I'm not home much though. I'll be home Friday night if you'd like to build something for me to try and break. Also let me know what to look at while playing and I'll give that information next time I break it.

Thanks

Link to comment
Share on other sites

Ogg there's a beta listed in the stickies. If you get the chance could you do a few sorties on that ans see if you still have the crash. Granted won;t be many targets but it would be helpful to know if someone who gets this crash repeatably still gets it on beta.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...