Client crashes nach Patch ...

Allgemeine Themen und Diskussionen rund um Saga Of Ryzom und die fantastische Welt von Atys.

Moderators: Boar, Orphanus

Post Reply
bshake
Posts: 15
Joined: Tue Sep 21, 2004 2:26 am

Client crashes nach Patch ...

Post by bshake »

hallo Homins,

bei einigen Spielern (unter anderem ich) gibt es beim Ladebildschirm einen üblen Client-Crash. Meinen Dump hat Infinyti schon per Mail bekommen.

Wer hat noch solche Effekte, beim Laden oder im Spiel ?


mfg

biershake
Top
User avatar
diamon
Posts: 18
Joined: Tue Sep 21, 2004 9:00 am

Re: Client crashes nach Patch ...

Post by diamon »

hir ich hab genau das sebe problem:

Access Violation exception generated at 0x77C0F5EA, thread attempts to read at 0x70.
The thread attempted to read from or write to a virtual address for which it does not have the appropriate access.
-------------------------------

Log with no filter:
-------------------------------
2005/01/13 18:29:24 client_ryzom_rd.exe INF 1932 network_connection.cpp 1090 : CNET[01124550]: received SYNC 99012904 1105637308815 - _CurrentReceivedNumber=909 _CurrentServerTick=99014722
2005/01/13 18:29:24 client_ryzom_rd.exe INF 1932 network_connection.cpp 1119 : CNET[01124550]: sent ACK_SYNC, _LastReceivedNumber=909 _LastAckInLongAck=398
2005/01/13 18:29:24 client_ryzom_rd.exe DBG 1932 udp_sock.cpp 174 : LNETL0: Socket 104 received 22 bytes from peer 213.208.119.196:47851 (213.208.119.196)
2005/01/13 18:29:24 client_ryzom_rd.exe INF 1932 network_connection.cpp 1090 : CNET[01124550]: received SYNC 99012904 1105637309015 - _CurrentReceivedNumber=910 _CurrentServerTick=99014724
2005/01/13 18:29:24 client_ryzom_rd.exe INF 1932 network_connection.cpp 1119 : CNET[01124550]: sent ACK_SYNC, _LastReceivedNumber=910 _LastAckInLongAck=399
2005/01/13 18:29:24 client_ryzom_rd.exe DBG 1932 udp_sock.cpp 174 : LNETL0: Socket 104 received 22 bytes from peer 213.208.119.196:47851 (213.208.119.196)
2005/01/13 18:29:24 client_ryzom_rd.exe INF 1932 network_connection.cpp 1090 : CNET[01124550]: received SYNC 99012904 1105637309215 - _CurrentReceivedNumber=911 _CurrentServerTick=99014726
2005/01/13 18:29:24 client_ryzom_rd.exe INF 1932 network_connection.cpp 1119 : CNET[01124550]: sent ACK_SYNC, _LastReceivedNumber=911 _LastAckInLongAck=400
2005/01/13 18:29:24 client_ryzom_rd.exe DBG 1932 udp_sock.cpp 174 : LNETL0: Socket 104 received 22 bytes from peer 213.208.119.196:47851 (213.208.119.196)
2005/01/13 18:29:24 client_ryzom_rd.exe INF 1932 network_connection.cpp 1090 : CNET[01124550]: received SYNC 99012904 1105637309414 - _CurrentReceivedNumber=912 _CurrentServerTick=99014728
2005/01/13 18:29:24 client_ryzom_rd.exe INF 1932 network_connection.cpp 1119 : CNET[01124550]: sent ACK_SYNC, _LastReceivedNumber=912 _LastAckInLongAck=401
2005/01/13 18:29:24 client_ryzom_rd.exe DBG 1932 udp_sock.cpp 174 : LNETL0: Socket 104 received 22 bytes from peer 213.208.119.196:47851 (213.208.119.196)
2005/01/13 18:29:24 client_ryzom_rd.exe INF 1932 network_connection.cpp 1090 : CNET[01124550]: received SYNC 99012904 1105637309614 - _CurrentReceivedNumber=913 _CurrentServerTick=99014730
2005/01/13 18:29:24 client_ryzom_rd.exe INF 1932 network_connection.cpp 1119 : CNET[01124550]: sent ACK_SYNC, _LastReceivedNumber=913 _LastAckInLongAck=402
2005/01/13 18:29:24 client_ryzom_rd.exe DBG 1932 udp_sock.cpp 174 : LNETL0: Socket 104 received 22 bytes from peer 213.208.119.196:47851 (213.208.119.196)
2005/01/13 18:29:24 client_ryzom_rd.exe INF 1932 network_connection.cpp 1090 : CNET[01124550]: received SYNC 99012904 1105637309817 - _CurrentReceivedNumber=914 _CurrentServerTick=99014732
2005/01/13 18:29:24 client_ryzom_rd.exe INF 1932 network_connection.cpp 1119 : CNET[01124550]: sent ACK_SYNC, _LastReceivedNumber=914 _LastAckInLongAck=403
2005/01/13 18:29:24 client_ryzom_rd.exe DBG 1932 udp_sock.cpp 174 : LNETL0: Socket 104 received 22 bytes from peer 213.208.119.196:47851 (213.208.119.196)
2005/01/13 18:29:24 client_ryzom_rd.exe INF 1932 network_connection.cpp 1090 : CNET[01124550]: received SYNC 99012904 1105637310016 - _CurrentReceivedNumber=915 _CurrentServerTick=99014734
2005/01/13 18:29:24 client_ryzom_rd.exe INF 1932 network_connection.cpp 1119 : CNET[01124550]: sent ACK_SYNC, _LastReceivedNumber=915 _LastAckInLongAck=404
2005/01/13 18:29:24 client_ryzom_rd.exe DBG 1932 udp_sock.cpp 174 : LNETL0: Socket 104 received 22 bytes from peer 213.208.119.196:47851 (213.208.119.196)
2005/01/13 18:29:24 client_ryzom_rd.exe INF 1932 network_connection.cpp 1090 : CNET[01124550]: received SYNC 99012904 1105637310214 - _CurrentReceivedNumber=916 _CurrentServerTick=99014736
2005/01/13 18:29:24 client_ryzom_rd.exe INF 1932 network_connection.cpp 1119 : CNET[01124550]: sent ACK_SYNC, _LastReceivedNumber=916 _LastAckInLongAck=405
2005/01/13 18:29:24 client_ryzom_rd.exe DBG 1932 udp_sock.cpp 174 : LNETL0: Socket 104 received 10 bytes from peer 213.208.119.196:47851 (213.208.119.196)
2005/01/13 18:29:24 client_ryzom_rd.exe WRN 1932 network_connection.cpp 1172 : CNET[01124550]: synchronize->probe
2005/01/13 18:29:24 client_ryzom_rd.exe DBG 1932 udp_sock.cpp 174 : LNETL0: Socket 104 received 10 bytes from peer 213.208.119.196:47851 (213.208.119.196)
2005/01/13 18:29:24 client_ryzom_rd.exe DBG 1932 udp_sock.cpp 174 : LNETL0: Socket 104 received 10 bytes from peer 213.208.119.196:47851 (213.208.119.196)
2005/01/13 18:29:24 client_ryzom_rd.exe DBG 1932 udp_sock.cpp 174 : LNETL0: Socket 104 received 10 bytes from peer 213.208.119.196:47851 (213.208.119.196)
2005/01/13 18:29:24 client_ryzom_rd.exe DBG 1932 udp_sock.cpp 174 : LNETL0: Socket 104 received 10 bytes from peer 213.208.119.196:47851 (213.208.119.196)
2005/01/13 18:29:24 client_ryzom_rd.exe DBG 1932 udp_sock.cpp 174 : LNETL0: Socket 104 received 10 bytes from peer 213.208.119.196:47851 (213.208.119.196)
2005/01/13 18:29:24 client_ryzom_rd.exe DBG 1932 udp_sock.cpp 174 : LNETL0: Socket 104 received 10 bytes from peer 213.208.119.196:47851 (213.208.119.196)
2005/01/13 18:29:24 client_ryzom_rd.exe DBG 1932 udp_sock.cpp 174 : LNETL0: Socket 104 received 10 bytes from peer 213.208.119.196:47851 (213.208.119.196)
2005/01/13 18:29:24 client_ryzom_rd.exe DBG 1932 udp_sock.cpp 174 : LNETL0: Socket 104 received 10 bytes from peer 213.208.119.196:47851 (213.208.119.196)
2005/01/13 18:29:24 client_ryzom_rd.exe DBG 1932 udp_sock.cpp 174 : LNETL0: Socket 104 received 10 bytes from peer 213.208.119.196:47851 (213.208.119.196)
2005/01/13 18:29:24 client_ryzom_rd.exe DBG 1932 udp_sock.cpp 174 : LNETL0: Socket 104 received 10 bytes from peer 213.208.119.196:47851 (213.208.119.196)
2005/01/13 18:29:24 client_ryzom_rd.exe DBG 1932 udp_sock.cpp 174 : LNETL0: Socket 104 received 10 bytes from peer 213.208.119.196:47851 (213.208.119.196)
2005/01/13 18:29:24 client_ryzom_rd.exe DBG 1932 udp_sock.cpp 174 : LNETL0: Socket 104 received 10 bytes from peer 213.208.119.196:47851 (213.208.119.196)
2005/01/13 18:29:24 client_ryzom_rd.exe DBG 1932 udp_sock.cpp 174 : LNETL0: Socket 104 received 10 bytes from peer 213.208.119.196:47851 (213.208.119.196)
2005/01/13 18:29:24 client_ryzom_rd.exe DBG 1932 udp_sock.cpp 174 : LNETL0: Socket 104 received 10 bytes from peer 213.208.119.196:47851 (213.208.119.196)
2005/01/13 18:29:24 client_ryzom_rd.exe DBG 1932 udp_sock.cpp 174 : LNETL0: Socket 104 received 10 bytes from peer 213.208.119.196:47851 (213.208.119.196)
2005/01/13 18:29:24 client_ryzom_rd.exe DBG 1932 udp_sock.cpp 174 : LNETL0: Socket 104 received 10 bytes from peer 213.208.119.196:47851 (213.208.119.196)
2005/01/13 18:29:24 client_ryzom_rd.exe DBG 1932 udp_sock.cpp 174 : LNETL0: Socket 104 received 10 bytes from peer 213.208.119.196:47851 (213.208.119.196)
2005/01/13 18:29:24 client_ryzom_rd.exe DBG 1932 udp_sock.cpp 174 : LNETL0: Socket 104 received 10 bytes from peer 213.208.119.196:47851 (213.208.119.196)
2005/01/13 18:29:24 client_ryzom_rd.exe DBG 1932 udp_sock.cpp 174 : LNETL0: Socket 104 received 10 bytes from peer 213.208.119.196:47851 (213.208.119.196)
2005/01/13 18:29:24 client_ryzom_rd.exe DBG 1932 udp_sock.cpp 174 : LNETL0: Socket 104 received 10 bytes from peer 213.208.119.196:47851 (213.208.119.196)
2005/01/13 18:29:24 client_ryzom_rd.exe INF 1932 network_connection.cpp 2148 : CNET[01124550]: sent ACK_PROBE (21 probes)
2005/01/13 18:29:24 client_ryzom_rd.exe DBG 1932 net_manager.cpp 2734 : CNetManager::update : Probe Received.
2005/01/13 18:29:24 client_ryzom_rd.exe DBG 1932 context_sound.cpp 174 : Init the context sound mektoub_resp_%r4
2005/01/13 18:29:24 client_ryzom_rd.exe DBG 1932 context_sound.cpp 174 : Init the context sound ryz_step_%3_%r4
2005/01/13 18:29:24 client_ryzom_rd.exe DBG 1932 context_sound.cpp 174 : Init the context sound mektoub_pack_%r4
2005/01/13 18:29:24 client_ryzom_rd.exe DBG 1932 context_sound.cpp 174 : Init the context sound cuir_%r5
-------------------------------
User Crash Callback:
-------------------------------
UserId: 83456
ShardId: 102
Player Name: ''
UserPosition: 18867.94 -24376.43 -6.35
ViewPosition: 18867.94 -24376.43 -6.35
Time in game: 0h 3min 33sec
LocalTime: 2005/01/13 18:29:37
ServerTick: 99014736
ConnectState: Probe
LocalAddress: :3018 (192.168.0.141)
Language: Deutsch
ClientVersion: 1.2.0.800
PatchVersion: 00042
Client is online
Memory: 7592kB/510mB
Process Virtual Memory: 936mB
NeL Memory: 0B
OS: Microsoft Windows XP Service Pack 1 (Build 2600) (5.1 2600)
Processor: Intel(R) Pentium(R) 4 CPU 2.80GHz / x86 Family 15 Model 2 Stepping 9 / GenuineIntel / 2793MHz / 2 Processors found
CPUID: bfebfbff
HT: YES
CpuMask: 1
NeL3D: Direct3d / ati2dvag.dll / SAPPHIRE RADEON 9600 ATLANTIS / \\.\DISPLAY1 / driver version : 6.14.10.6497
3DCard: SAPPHIRE RADEON 9600 ATLANTIS, version 6.4.9.7
Sound mixer:
Playing sources: 63
Available tracks: 1
Used tracks: 31
Muted sources: 27
Sources waiting for play: 0
HighestPri: 0 / 2
HighPri: 0 / 4
MidPri: 31 / 6
LowPri: 0 / 8
FreeTracks: 1 / 32
Average update time: 0.000223 msec
Average create time: 0.000016 msec
Estimated CPU: 0.002143%%
Sound driver:
FMod Driver
3d hw buffers: 32
2d hw buffers: 32
-------------------------------
Top
mayfish
Posts: 1
Joined: Fri Sep 24, 2004 1:06 pm

Re: Client crashes nach Patch ...

Post by mayfish »

ja bei mir auch. bei ladebildschirm ca 3/4 hängt sich client auf....
Hab mich schon so auf reitmek gefreut :(
Top
User avatar
diamon
Posts: 18
Joined: Tue Sep 21, 2004 9:00 am

Re: Client crashes nach Patch ...

Post by diamon »

ich war in game :( bin nach pyr geportet und dann tot nix mehr geht
Top
User avatar
radrom
Posts: 10
Joined: Tue Sep 21, 2004 2:26 am

Re: Client crashes nach Patch ...

Post by radrom »

hab das prob hab ich auch, bin max 1 min im game dann crash.
Vor Patch lief es absolut bestens. Und am PC ist nix verändert worden.
Muss also am patch liegen ...

Gruß
Ari
Ari ( Fyros, Juwelier )
Gilde : Die Kamihüter
Top
User avatar
infinyti
Posts: 99
Joined: Tue Sep 21, 2004 10:00 am

Re: Client crashes nach Patch ...

Post by infinyti »

Bitte hier nachlesen und handeln:


http://www.ryzom.com/forum/showthread.php?t=10054


Grüße
Infinyti

CSR-Gamemaster
MDO-Entertainment Deutschland

[color=FFCC66]'Geschmackssache' .. sagte der Affe und biß ins Sofa.[/color]
Top
justus
Posts: 146
Joined: Tue Sep 21, 2004 2:26 am

Re: Client crashes nach Patch ...

Post by justus »

Wollte nach Yrk porten...kurz vor Ende des Ladevorgangs gabs Crash ohne Fehlermeldung.

Konnte mich danach normal wieder einloggen.
------------------------------------------------------------------------------------
Was hängt an der Wand, macht Tik Tak und wenn es herunterfällt ist die Eieruhr kaputt?
------------------------------------------------------------------------------------
Top
User avatar
thoehne
Posts: 123
Joined: Tue Sep 21, 2004 2:26 am

Re: Client crashes nach Patch ...

Post by thoehne »

Also, mir half gestern ein kompletter Recover (mit ryzom_recover.exe) in einer vergleichbaren Situation.

Danach konnte ich wieder ins Spiel.

Vielleicht einfach mal testen...?
Last edited by thoehne on Fri Jan 14, 2005 8:22 am, edited 1 time in total.
Reason: ryzom_recover.exe vergessen...
"Bis wir alle eins sind!"
Explorer 80%, Socializer 66%, Achiever 53%, Killer 0%
Top
Post Reply

Return to “Allgemeines”