seid dem ich ryzom mit nem amd64 rechner spiel bekomm ich ca. alle halbe std nen access violation meldung. egal ob ich nun irgendwo rum renn und mobs klopp oder ob ich einfach nur irgendwo rum sitze. Vielleicht hat ja jemand von euch ne idee an was es liegen könnte. Windows hab ich neu installiert ryzom auch.
Vorsichts halber setzt ich auch mal die access violation meldung hier mit in den post rein.
Access Violation exception generated at 0x99744B, thread attempts to read at 0x80000.
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/02/01 20:36:36 client_ryzom_rd.exe DBG 2964 impulse_decoder.cpp 82 : CLIMPD: at level 2 (channel 0), 1 actions (ReceivedAck=6309/lastAck=6306/nextSentPacket=6310)
2005/02/01 20:36:36 client_ryzom_rd.exe DBG 2964 client_chat_manager.cpp 579 : <impulseDynString> Received CHAT, put in buffer : waiting association
2005/02/01 20:36:36 client_ryzom_rd.exe INF 2964 string_manager_client.cpp 505 : DynString 2258319845 available : [&SPLM&You invoke an offensive spell on a Lesser Izam.]
2005/02/01 20:36:36 client_ryzom_rd.exe DBG 2964 cdb_synchronised.cpp 167 : Update DB
2005/02/01 20:36:36 client_ryzom_rd.exe WRN 2964 player_cl.cpp 487 : PL:computeAnimSet:246: not a male or a female (gender=3).
2005/02/01 20:36:36 client_ryzom_rd.exe DBG 2964 net_manager.cpp 544 : <impulseChat> Received CHAT : You invoke an offensive spell on a Lesser Izam. with category splm
2005/02/01 20:36:37 client_ryzom_rd.exe DBG 2964 udp_sock.cpp 174 : LNETL0: Socket 132 received 166 bytes from peer 213.208.119.195:47851 (213.208.119.195)
2005/02/01 20:36:37 client_ryzom_rd.exe INF 2964 impulse_decoder.cpp 72 : CLIMPD: received new impulsion 1 (len=315) at level 2 (channel 1)
2005/02/01 20:36:37 client_ryzom_rd.exe DBG 2964 impulse_decoder.cpp 82 : CLIMPD: at level 2 (channel 1), 1 actions (ReceivedAck=6310/lastAck=6307/nextSentPacket=6311)
2005/02/01 20:36:37 client_ryzom_rd.exe DBG 2964 cdb_synchronised.cpp 167 : Update DB
2005/02/01 20:36:37 client_ryzom_rd.exe DBG 2964 udp_sock.cpp 174 : LNETL0: Socket 132 received 134 bytes from peer 213.208.119.195:47851 (213.208.119.195)
2005/02/01 20:36:37 client_ryzom_rd.exe DBG 2964 udp_sock.cpp 174 : LNETL0: Socket 132 received 183 bytes from peer 213.208.119.195:47851 (213.208.119.195)
2005/02/01 20:36:37 client_ryzom_rd.exe INF 2964 impulse_decoder.cpp 72 : CLIMPD: received new impulsion 1 (len=99) at level 2 (channel 3)
2005/02/01 20:36:37 client_ryzom_rd.exe DBG 2964 impulse_decoder.cpp 82 : CLIMPD: at level 2 (channel 3), 1 actions (ReceivedAck=6312/lastAck=6309/nextSentPacket=6313)
2005/02/01 20:36:37 client_ryzom_rd.exe DBG 2964 cdb_synchronised.cpp 167 : Update DB
2005/02/01 20:36:37 client_ryzom_rd.exe DBG 2964 udp_sock.cpp 174 : LNETL0: Socket 132 received 157 bytes from peer 213.208.119.195:47851 (213.208.119.195)
2005/02/01 20:36:37 client_ryzom_rd.exe INF 2964 impulse_decoder.cpp 72 : CLIMPD: received new impulsion 1 (len=99) at level 2 (channel 0)
2005/02/01 20:36:37 client_ryzom_rd.exe DBG 2964 impulse_decoder.cpp 82 : CLIMPD: at level 2 (channel 0), 1 actions (ReceivedAck=6313/lastAck=6310/nextSentPacket=6314)
2005/02/01 20:36:37 client_ryzom_rd.exe DBG 2964 cdb_synchronised.cpp 167 : Update DB
2005/02/01 20:36:37 client_ryzom_rd.exe DBG 2964 string_manager_client.cpp 308 : <CStringManagerClient::getString> sending 'STRING_MANAGER:STRING_RQ' message to server
2005/02/01 20:36:37 client_ryzom_rd.exe DBG 2964 udp_sock.cpp 174 : LNETL0: Socket 132 received 183 bytes from peer 213.208.119.195:47851 (213.208.119.195)
2005/02/01 20:36:37 client_ryzom_rd.exe INF 2964 impulse_decoder.cpp 72 : CLIMPD: received new impulsion 1 (len=99) at level 2 (channel 1)
2005/02/01 20:36:37 client_ryzom_rd.exe DBG 2964 impulse_decoder.cpp 82 : CLIMPD: at level 2 (channel 1), 1 actions (ReceivedAck=6314/lastAck=6311/nextSentPacket=6315)
2005/02/01 20:36:37 client_ryzom_rd.exe DBG 2964 cdb_synchronised.cpp 167 : Update DB
2005/02/01 20:36:38 client_ryzom_rd.exe DBG 2964 udp_sock.cpp 174 : LNETL0: Socket 132 received 179 bytes from peer 213.208.119.195:47851 (213.208.119.195)
2005/02/01 20:36:38 client_ryzom_rd.exe INF 2964 impulse_decoder.cpp 72 : CLIMPD: received new impulsion 1 (len=579) at level 1 (channel 0)
2005/02/01 20:36:38 client_ryzom_rd.exe DBG 2964 impulse_decoder.cpp 82 : CLIMPD: at level 1 (channel 0), 1 actions (ReceivedAck=6315/lastAck=6310/nextSentPacket=6316)
2005/02/01 20:36:38 client_ryzom_rd.exe INF 2964 string_manager_client.cpp 344 : String 222959 available : [Nathaniel$Defensive_Magician$]
2005/02/01 20:36:38 client_ryzom_rd.exe DBG 2964 udp_sock.cpp 174 : LNETL0: Socket 132 received 112 bytes from peer 213.208.119.195:47851 (213.208.119.195)
2005/02/01 20:36:38 client_ryzom_rd.exe INF 2964 impulse_decoder.cpp 72 : CLIMPD: received new impulsion 1 (len=99) at level 2 (channel 3)
2005/02/01 20:36:38 client_ryzom_rd.exe DBG 2964 impulse_decoder.cpp 82 : CLIMPD: at level 2 (channel 3), 1 actions (ReceivedAck=6316/lastAck=6313/nextSentPacket=6317)
2005/02/01 20:36:38 client_ryzom_rd.exe DBG 2964 cdb_synchronised.cpp 167 : Update DB
2005/02/01 20:36:38 client_ryzom_rd.exe DBG 2964 udp_sock.cpp 174 : LNETL0: Socket 132 received 217 bytes from peer 213.208.119.195:47851 (213.208.119.195)
2005/02/01 20:36:38 client_ryzom_rd.exe INF 2964 impulse_decoder.cpp 72 : CLIMPD: received new impulsion 1 (len=83) at level 1 (channel 0)
2005/02/01 20:36:38 client_ryzom_rd.exe INF 2964 impulse_decoder.cpp 72 : CLIMPD: received new impulsion 1 (len=115) at level 1 (channel 0)
2005/02/01 20:36:38 client_ryzom_rd.exe DBG 2964 impulse_decoder.cpp 82 : CLIMPD: at level 1 (channel 0), 2 actions (ReceivedAck=6317/lastAck=6316/nextSentPacket=6318)
2005/02/01 20:36:38 client_ryzom_rd.exe INF 2964 impulse_decoder.cpp 72 : CLIMPD: received new impulsion 1 (len=99) at level 2 (channel 0)
2005/02/01 20:36:38 client_ryzom_rd.exe DBG 2964 impulse_decoder.cpp 82 : CLIMPD: at level 2 (channel 0), 1 actions (ReceivedAck=6317/lastAck=6314/nextSentPacket=6318)
2005/02/01 20:36:38 client_ryzom_rd.exe DBG 2964 client_chat_manager.cpp 579 : <impulseDynString> Received CHAT, put in buffer : waiting association
2005/02/01 20:36:38 client_ryzom_rd.exe INF 2964 string_manager_client.cpp 505 : DynString 2258320071 available : [&SPLM&You succesfully cast your spell.]
2005/02/01 20:36:38 client_ryzom_rd.exe DBG 2964 cdb_synchronised.cpp 167 : Update DB
2005/02/01 20:36:38 client_ryzom_rd.exe DBG 2964 net_manager.cpp 544 : <impulseChat> Received CHAT : You succesfully cast your spell. with category splm
2005/02/01 20:36:38 client_ryzom_rd.exe DBG 2964 udp_sock.cpp 174 : LNETL0: Socket 132 received 120 bytes from peer 213.208.119.195:47851 (213.208.119.195)
2005/02/01 20:36:38 client_ryzom_rd.exe INF 2964 impulse_decoder.cpp 72 : CLIMPD: received new impulsion 1 (len=99) at level 2 (channel 1)
2005/02/01 20:36:38 client_ryzom_rd.exe DBG 2964 impulse_decoder.cpp 82 : CLIMPD: at level 2 (channel 1), 1 actions (ReceivedAck=6318/lastAck=6315/nextSentPacket=6319)
2005/02/01 20:36:38 client_ryzom_rd.exe DBG 2964 cdb_synchronised.cpp 167 : Update DB
2005/02/01 20:36:38 client_ryzom_rd.exe DBG 2964 udp_sock.cpp 174 : LNETL0: Socket 132 received 106 bytes from peer 213.208.119.195:47851 (213.208.119.195)
2005/02/01 20:36:39 client_ryzom_rd.exe DBG 2964 udp_sock.cpp 174 : LNETL0: Socket 132 received 147 bytes from peer 213.208.119.195:47851 (213.208.119.195)
2005/02/01 20:36:39 client_ryzom_rd.exe INF 2964 impulse_decoder.cpp 72 : CLIMPD: received new impulsion 1 (len=99) at level 2 (channel 3)
2005/02/01 20:36:39 client_ryzom_rd.exe DBG 2964 impulse_decoder.cpp 82 : CLIMPD: at level 2 (channel 3), 1 actions (ReceivedAck=6320/lastAck=6317/nextSentPacket=6321)
2005/02/01 20:36:39 client_ryzom_rd.exe DBG 2964 cdb_synchronised.cpp 167 : Update DB
-------------------------------
User Crash Callback:
-------------------------------
UserId: 58442
ShardId: 102
Player Name: 'Deathbreath'
UserPosition: 18947.20 -24413.76 -1.65
ViewPosition: 18947.20 -24413.76 -1.65
Time in game: 0h 21min 22sec
LocalTime: 2005/02/01 20:36:40
ServerTick: 116266036
ConnectState: Connected
LocalAddress: :1275 (192.168.1.2)
Language: English
ClientVersion: 1.2.0.800
PatchVersion: 00048
Client is online
Memory: 63mB/1023mB
Process Virtual Memory: 817mB
NeL Memory: 0B
OS: Microsoft Windows XP Service Pack 2 (Build 2600) (5.1 2600)
Processor: AMD Athlon(tm) 64 Processor 3500+ / x86 Family 15 Model 15 Stepping 0 / AuthenticAMD / 2211MHz / 1 Processors found
CPUID: 78bfbff
HT: NO
CpuMask: 1
NeL3D: OpenGL / NVIDIA Corporation / GeForce 6600 GT/PCI/SSE2/3DNOW! / 1.5.2
3DCard: NVIDIA GeForce 6600 GT, version 6.6.9.3
No sound
-------------------------------
MfG
Deathbreath
AMD64 = Access Violation
Moderator: Boar
Re: AMD64 = Access Violation
Zwei Fragen:bses2001 wrote:seid dem ich ryzom mit nem amd64 rechner spiel bekomm ich ca. alle halbe std nen access violation meldung. egal ob ich nun irgendwo rum renn und mobs klopp oder ob ich einfach nur irgendwo rum sitze. Vielleicht hat ja jemand von euch ne idee an was es liegen könnte. Windows hab ich neu installiert ryzom auch.
Vorsichts halber setzt ich auch mal die access violation meldung hier mit in den post rein.
1. Wie warm wird deine CPU?
2. Wie schaut deine Spannungsversorgung aus? (nein, ich will NICHT hören, dass du Netzteil XY hast - schau bitte direkt nach den Spannungen. Wenn du nicht weisst wie --> Google "Mother Board Monitor" oder ggf. ein Monitoring-Tool deines Mainboard-Herstellers)
Go forth, live, learn, and most important, live together, not alone, for thou will soon discover there being a great danger, a danger thou never seen afore. The existence of Hominkind is at stake. The Kitin are still on the surface, great numbers of them. Who the Kitin are? Your worst nightmare...
(\(\
(^.^)
(")") *This is the cute bunny virus, please copy this into your sig so it can spread.
(\(\
(^.^)
(")") *This is the cute bunny virus, please copy this into your sig so it can spread.
Re: AMD64 = Access Violation
also ich hab Netzteil XY 
nee spaß beiseite
Vcore Voltage: 1,50V
3.3V Voltage: 3,28V
5V Voltage: 5,05V
12V Voltage: 11,96V
CPU Termperatur: 72°C
nee spaß beiseite
Vcore Voltage: 1,50V
3.3V Voltage: 3,28V
5V Voltage: 5,05V
12V Voltage: 11,96V
CPU Termperatur: 72°C
Re: AMD64 = Access Violation
Findest du nicht, dass das ein _WENIG_ hoch ist?bses2001 wrote:CPU Termperatur: 72°C
EDIT: Warum ich das Frage? Einfache Sache. Ähnliche Access Violations hatte ich im Sommer... Da ist mir fast meine CPU abgefackelt mit Temperaturen jenseits der 70 Grad...
Go forth, live, learn, and most important, live together, not alone, for thou will soon discover there being a great danger, a danger thou never seen afore. The existence of Hominkind is at stake. The Kitin are still on the surface, great numbers of them. Who the Kitin are? Your worst nightmare...
(\(\
(^.^)
(")") *This is the cute bunny virus, please copy this into your sig so it can spread.
(\(\
(^.^)
(")") *This is the cute bunny virus, please copy this into your sig so it can spread.
Re: AMD64 = Access Violation
nee eigentlich net mein alter cpu hatte ohne wakü 75°C (wakü konnt ich bei amd64 noch net einbauen lieferprobs)
evtl wars auch en anzeige fehler inzwischen wird mir 34°C angezeigt
evtl wars auch en anzeige fehler inzwischen wird mir 34°C angezeigt
Re: AMD64 = Access Violation
<obsolete>
Go forth, live, learn, and most important, live together, not alone, for thou will soon discover there being a great danger, a danger thou never seen afore. The existence of Hominkind is at stake. The Kitin are still on the surface, great numbers of them. Who the Kitin are? Your worst nightmare...
(\(\
(^.^)
(")") *This is the cute bunny virus, please copy this into your sig so it can spread.
(\(\
(^.^)
(")") *This is the cute bunny virus, please copy this into your sig so it can spread.
Re: AMD64 = Access Violation
wiegesagt inzwischen hab ich cpu temperatur auf 34°C ohne was verändert zuhaben. naja ich trau den mainboardmoitoren sowieso nicht. und er wird wieder abstürzen bin ich mir sicher
Re: AMD64 = Access Violation
Mich würd eher interessieren wie das bei den anderen Leuten mit AMD64 ist - ich denke mal, du wirst nicht der einzige sein...
Re: AMD64 = Access Violation
Lass mal Prime95 (extremer Stresstest für den CPU) durchlafen.
Wenn Dein Rechner nicht durchhält, dann hast den Schuldigen gefunden.
Prime95 info und link
Wenn Dein Rechner nicht durchhält, dann hast den Schuldigen gefunden.
Prime95 info und link
Thelon, Krieger aus Zora
It's nice to be important, but it's more important to be nice.
"Es gibt keinen Grund, warum irgend jemand einen Computer in seinem Haus wollen würde."
Ken Olson, Präsident, Vorsitzender und Gründer von Digital Equipment Corp., 1977
3D-Weltengenerator
(\__/)
(o.0 )
(> < ) This is Bunny. Copy Bunny into your signature to help him on his way to world domination.
It's nice to be important, but it's more important to be nice.
"Es gibt keinen Grund, warum irgend jemand einen Computer in seinem Haus wollen würde."
Ken Olson, Präsident, Vorsitzender und Gründer von Digital Equipment Corp., 1977
3D-Weltengenerator
(\__/)
(o.0 )
(> < ) This is Bunny. Copy Bunny into your signature to help him on his way to world domination.
Re: AMD64 = Access Violation
mein AMD 64 rennt ohne probleme.
Hatte früher auch immer acces violations (alle 5-20 mins) das lag aber an einem wackler im speicher.
Kannst ja mal bissel am speicher timeing fummeln. Ryzom ist sehr RAM-intensiv. Könnte schon sein dass es da *zu* sensibel ist.
Hatte früher auch immer acces violations (alle 5-20 mins) das lag aber an einem wackler im speicher.
Kannst ja mal bissel am speicher timeing fummeln. Ryzom ist sehr RAM-intensiv. Könnte schon sein dass es da *zu* sensibel ist.