Page 1 of 1

Problème de connection [Répondu]

Posted: Tue Nov 14, 2006 3:25 pm
by whitecow
Bonjour

Voila g installé le trial tout c'est bien passer mais au moment ou je clic pour crée mon perso une petite fenetre s ouvre et impossible de se connecter, j ai desinstallé reinstallé rien ni fait, j ai ouvert tout les ports possible (donner dans un post).
Merci de votre aide à tous.

Le message d erreur et le suivant :

Code: Select all

Access Violation exception generated at 0x4795EEA, thread attempts to read at 0x14.
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:
-------------------------------
2006/11/14 16:17:21 client_ryzom_rd.exe INF   e64 string_manager_client.cpp 134 : SM: Creating string cache
2006/11/14 16:17:21 client_ryzom_rd.exe DBG   e64 net_manager.cpp 3584 : CNetManager::update : Connection Ready.
2006/11/14 16:17:22 client_ryzom_rd.exe DBG   e64 udp_sock.cpp 174 : LNETL0: Socket 120 received 208 bytes from peer rsfe124.juk.shards.nevrax.com:47852 (213.208.119.40)
2006/11/14 16:17:22 client_ryzom_rd.exe INF   e64 impulse_decoder.cpp 72 : CLIMPD: received new impulsion 2 (len=1595) at level 1 (channel 1)
2006/11/14 16:17:22 client_ryzom_rd.exe DBG   e64 impulse_decoder.cpp 82 : CLIMPD: at level 1 (channel 1), 1 actions (ReceivedAck=2/lastAck=-1/nextSentPacket=4)
2006/11/14 16:17:22 client_ryzom_rd.exe DBG   e64 network_connection.cpp 3062 : CLMPNET[0158DB10]: Received a generic action MP size 190: number 0 part 0 nbblock 4
2006/11/14 16:17:22 client_ryzom_rd.exe DBG   e64 udp_sock.cpp 174 : LNETL0: Socket 120 received 208 bytes from peer rsfe124.juk.shards.nevrax.com:47852 (213.208.119.40)
2006/11/14 16:17:22 client_ryzom_rd.exe INF   e64 impulse_decoder.cpp 72 : CLIMPD: received new impulsion 2 (len=1595) at level 1 (channel 0)
2006/11/14 16:17:22 client_ryzom_rd.exe DBG   e64 impulse_decoder.cpp 82 : CLIMPD: at level 1 (channel 0), 1 actions (ReceivedAck=5/lastAck=2/nextSentPacket=6)
2006/11/14 16:17:22 client_ryzom_rd.exe DBG   e64 network_connection.cpp 3062 : CLMPNET[0158DB10]: Received a generic action MP size 190: number 0 part 1 nbblock 4
2006/11/14 16:17:22 client_ryzom_rd.exe DBG   e64 udp_sock.cpp 174 : LNETL0: Socket 120 received 208 bytes from peer rsfe124.juk.shards.nevrax.com:47852 (213.208.119.40)
2006/11/14 16:17:22 client_ryzom_rd.exe INF   e64 impulse_decoder.cpp 72 : CLIMPD: received new impulsion 2 (len=1595) at level 1 (channel 1)
2006/11/14 16:17:22 client_ryzom_rd.exe DBG   e64 impulse_decoder.cpp 82 : CLIMPD: at level 1 (channel 1), 1 actions (ReceivedAck=7/lastAck=4/nextSentPacket=8)
2006/11/14 16:17:22 client_ryzom_rd.exe DBG   e64 network_connection.cpp 3062 : CLMPNET[0158DB10]: Received a generic action MP size 190: number 0 part 2 nbblock 4
2006/11/14 16:17:22 client_ryzom_rd.exe DBG   e64 udp_sock.cpp 174 : LNETL0: Socket 120 received 178 bytes from peer rsfe124.juk.shards.nevrax.com:47852 (213.208.119.40)
2006/11/14 16:17:22 client_ryzom_rd.exe INF   e64 impulse_decoder.cpp 72 : CLIMPD: received new impulsion 2 (len=1355) at level 1 (channel 0)
2006/11/14 16:17:22 client_ryzom_rd.exe DBG   e64 impulse_decoder.cpp 82 : CLIMPD: at level 1 (channel 0), 1 actions (ReceivedAck=9/lastAck=6/nextSentPacket=10)
2006/11/14 16:17:22 client_ryzom_rd.exe DBG   e64 network_connection.cpp 3062 : CLMPNET[0158DB10]: Received a generic action MP size 160: number 0 part 3 nbblock 4
2006/11/14 16:17:22 client_ryzom_rd.exe DBG   e64 network_connection.cpp 3034 : CLMPNET[035ECBC0]: Received a TOTAL generic action MP size: number 0 nbblock 4
2006/11/14 16:17:22 client_ryzom_rd.exe DBG   e64 network_connection.cpp 3048 : CLMPNET[035ECBC0]: Received a generic action size 730
2006/11/14 16:17:22 client_ryzom_rd.exe INF   e64 net_manager.cpp 345 : impulseCallBack : Received CONNECTION:USER_CHARS
2006/11/14 16:17:22 client_ryzom_rd.exe INF   e64 connection.cpp 857 : impulseCallBack : received userChars list
2006/11/14 16:17:22 client_ryzom_rd.exe DBG   e64 udp_sock.cpp 174 : LNETL0: Socket 120 received 9 bytes from peer rsfe124.juk.shards.nevrax.com:47852 (213.208.119.40)
2006/11/14 16:17:23 client_ryzom_rd.exe DBG   e64 udp_sock.cpp 174 : LNETL0: Socket 120 received 9 bytes from peer rsfe124.juk.shards.nevrax.com:47852 (213.208.119.40)
2006/11/14 16:17:23 client_ryzom_rd.exe DBG   e64 udp_sock.cpp 174 : LNETL0: Socket 120 received 9 bytes from peer rsfe124.juk.shards.nevrax.com:47852 (213.208.119.40)
2006/11/14 16:17:23 client_ryzom_rd.exe DBG   e64 udp_sock.cpp 174 : LNETL0: Socket 120 received 9 bytes from peer rsfe124.juk.shards.nevrax.com:47852 (213.208.119.40)
2006/11/14 16:17:23 client_ryzom_rd.exe DBG   e64 udp_sock.cpp 174 : LNETL0: Socket 120 received 9 bytes from peer rsfe124.juk.shards.nevrax.com:47852 (213.208.119.40)
2006/11/14 16:17:24 client_ryzom_rd.exe DBG   e64 udp_sock.cpp 174 : LNETL0: Socket 120 received 9 bytes from peer rsfe124.juk.shards.nevrax.com:47852 (213.208.119.40)
2006/11/14 16:17:24 client_ryzom_rd.exe DBG   e64 udp_sock.cpp 174 : LNETL0: Socket 120 received 9 bytes from peer rsfe124.juk.shards.nevrax.com:47852 (213.208.119.40)
2006/11/14 16:17:24 client_ryzom_rd.exe DBG   e64 udp_sock.cpp 174 : LNETL0: Socket 120 received 9 bytes from peer rsfe124.juk.shards.nevrax.com:47852 (213.208.119.40)
2006/11/14 16:17:24 client_ryzom_rd.exe DBG   e64 udp_sock.cpp 174 : LNETL0: Socket 120 received 9 bytes from peer rsfe124.juk.shards.nevrax.com:47852 (213.208.119.40)
2006/11/14 16:17:24 client_ryzom_rd.exe DBG   e64 udp_sock.cpp 174 : LNETL0: Socket 120 received 9 bytes from peer rsfe124.juk.shards.nevrax.com:47852 (213.208.119.40)
2006/11/14 16:17:24 client_ryzom_rd.exe DBG   e64 udp_sock.cpp 174 : LNETL0: Socket 120 received 9 bytes from peer rsfe124.juk.shards.nevrax.com:47852 (213.208.119.40)
2006/11/14 16:17:25 client_ryzom_rd.exe DBG   e64 udp_sock.cpp 174 : LNETL0: Socket 120 received 9 bytes from peer rsfe124.juk.shards.nevrax.com:47852 (213.208.119.40)
2006/11/14 16:17:25 client_ryzom_rd.exe DBG   e64 udp_sock.cpp 174 : LNETL0: Socket 120 received 9 bytes from peer rsfe124.juk.shards.nevrax.com:47852 (213.208.119.40)
2006/11/14 16:17:25 client_ryzom_rd.exe DBG   e64 udp_sock.cpp 174 : LNETL0: Socket 120 received 9 bytes from peer rsfe124.juk.shards.nevrax.com:47852 (213.208.119.40)
2006/11/14 16:17:25 client_ryzom_rd.exe DBG   e64 udp_sock.cpp 174 : LNETL0: Socket 120 received 9 bytes from peer rsfe124.juk.shards.nevrax.com:47852 (213.208.119.40)
2006/11/14 16:17:25 client_ryzom_rd.exe WRN   e64 sound_manager.cpp 700 : Sound 'specie_but_over' not found !
2006/11/14 16:17:25 client_ryzom_rd.exe DBG   e64 udp_sock.cpp 174 : LNETL0: Socket 120 received 9 bytes from peer rsfe124.juk.shards.nevrax.com:47852 (213.208.119.40)
2006/11/14 16:17:26 client_ryzom_rd.exe DBG   e64 udp_sock.cpp 174 : LNETL0: Socket 120 received 9 bytes from peer rsfe124.juk.shards.nevrax.com:47852 (213.208.119.40)
2006/11/14 16:17:26 client_ryzom_rd.exe DBG   e64 udp_sock.cpp 174 : LNETL0: Socket 120 received 9 bytes from peer rsfe124.juk.shards.nevrax.com:47852 (213.208.119.40)
2006/11/14 16:17:26 client_ryzom_rd.exe WRN   e64 sound_manager.cpp 700 : Sound 'specie_but_over' not found !
2006/11/14 16:17:26 client_ryzom_rd.exe WRN   e64 sound_manager.cpp 700 : Sound 'specie_but_over' not found !
2006/11/14 16:17:26 client_ryzom_rd.exe WRN   e64 sound_manager.cpp 700 : Sound 'specie_but_over' not found !
2006/11/14 16:17:26 client_ryzom_rd.exe WRN   e64 sound_manager.cpp 700 : Sound 'specie_but_over' not found !
2006/11/14 16:17:26 client_ryzom_rd.exe WRN   e64 sound_manager.cpp 700 : Sound 'specie_but_over' not found !
2006/11/14 16:17:26 client_ryzom_rd.exe DBG   e64 udp_sock.cpp 174 : LNETL0: Socket 120 received 9 bytes from peer rsfe124.juk.shards.nevrax.com:47852 (213.208.119.40)
2006/11/14 16:17:26 client_ryzom_rd.exe DBG   e64 udp_sock.cpp 174 : LNETL0: Socket 120 received 9 bytes from peer rsfe124.juk.shards.nevrax.com:47852 (213.208.119.40)
2006/11/14 16:17:26 client_ryzom_rd.exe DBG   e64 udp_sock.cpp 174 : LNETL0: Socket 120 received 9 bytes from peer rsfe124.juk.shards.nevrax.com:47852 (213.208.119.40)
2006/11/14 16:17:27 client_ryzom_rd.exe DBG   e64 udp_sock.cpp 174 : LNETL0: Socket 120 received 9 bytes from peer rsfe124.juk.shards.nevrax.com:47852 (213.208.119.40)
2006/11/14 16:17:27 client_ryzom_rd.exe DBG   e64 udp_sock.cpp 174 : LNETL0: Socket 120 received 9 bytes from peer rsfe124.juk.shards.nevrax.com:47852 (213.208.119.40)
-------------------------------
User Crash Callback:
-------------------------------
UserId: 350693
HomeId: 0
ShardId: 0
On a Mainland Shard
Application: ryzom_live
No user entity informations
ViewPosition: 0.00 0.00 0.00
Time in game: 19h 7min 19sec
LocalTime: 2006/11/14 16:17:28
ServerTick: 669271547
ConnectState: Connected
LocalAddress: :4588 (192.168.1.2)
Language: Français
ClientVersion: 1.2.0.800
PatchVersion: 606
Client is online
NumServerHOP: 0
NumFarTP: 0
NumReselectPerso: 0
Connection Events: 
Memory: 412MB/958MB
Process Virtual Memory: 384MB
NeL Memory: 0B
OS: Microsoft Windows XP Service Pack 2 (Build 2600) (5.1 2600)
Processor: Intel(R) Core(TM)2 CPU          6300  @ 1.86GHz / x86 Family 6 Model 15 Stepping 6 / GenuineIntel / 1862MHz / 2 Processors found
CPUID: bfebfbff
HT: NO
CpuMask: 1
NeL3D: OpenGL / S3 Graphics / VIA/S3G UniChrome Pro IGP/MMX/SSE / 1.2
3DCard: VIA/S3G UniChrome Pro IGP, version 0.2.8.3
Sound mixer: 
	Playing sources: 0 
	Available tracks: 32 
	Used tracks: 0 
	Muted sources: 0
	Sources waiting for play: 0 
	HighestPri: 0 / 2 
	HighPri:    0 / 4
	MidPri:     0 / 6 
	LowPri:     0 / 8 
	FreeTracks: 32 / 32 
	Average update time: 0.000003 msec
	Average create time: 0.000000 msec
	Estimated CPU: 0.000381%%
Sound driver: 
	FMod Driver
	3d hw buffers: 31
	2d hw buffers: 32
-------------------------------

Re: Problème de connection

Posted: Tue Nov 14, 2006 4:09 pm
by faro1
S3G UniChrome Pro IGP <= c'est pas de l'intégré ca ?

A mon avis limite, regarde si tu as les drivers de la chose :)

Faro1

Re: Problème de connection

Posted: Tue Nov 14, 2006 4:19 pm
by whitecow
Salut Faro1

Effectivement c bien de l intégré mais c'est a jour avec le dernier driver (pris sur assus.com ), de plus je ne rencontre aucun prob avec wow, ever2, etc... donc je ne pense pas que sa vient de ma video mais peut etre le prog qui ne l accepte pas.

PS: carete mere derniere generation acceptant le core 2 duo donc je ne pense pas que se soit limite :-) maintenant je me trompe peut etre.

Re: Problème de connection

Posted: Tue Nov 14, 2006 10:25 pm
by hebene
Votre (S3G UniChrome Pro IGP) est une puce intégré a votre chipset et n'est pas supporté par Ryzom.

Re: Problème de connection [Répondu]

Posted: Mon Nov 27, 2006 12:16 pm
by steven3
bonjour j'ai un proble differen de whitecow mon problème:
quand je lance Ryzom il me mais l'interface je mais mon mode passe il me mais la charte et jaccepte. (juste ici il n'y a pe de problème)
et il me mais connexion en cour mais il charge pendant 1h et il me mais rien du tou
aidé moi svp

Re: Problème de connection [Répondu]

Posted: Mon Nov 27, 2006 6:15 pm
by snakke47
Tu as essayé l'ouverture des ports ?