Ryzom

I really enjoy this game and have been getting on well with my tryker, however after a week of crashes every 5 mins i decided to make a new character, so i head that matis would be a good choice, went through making my character ok. I come to play and i get an error and my client crashes so that annoyed me, so i went to make a zorai and the same error message, i made a fyros same error, i then went back to my tryker and guess what....

THE SAME GOD DAM ERROR MESSAGE

Here is the error i hope you guys can think of a solution because otherwise ryzom is going bye bye.

A failed assertion occurs
ProcName: client_ryzom_rd.exe
Date: 2004/10/24 18:15:20
File: R:\code\nel\src\3d\driver\direct3d\driver_direct3d.cpp
Line: 2017
Reason: "0"
-------------------------------

Log with no filter:
-------------------------------
2004/10/24 18:15:14 client_ryzom_rd.exe DBG 3676 udp_sock.cpp 174 : LNETL0: Socket 1932 received 9 bytes from peer 213.208.119.198:47851 (213.208.119.198)
2004/10/24 18:15:15 client_ryzom_rd.exe DBG 3676 udp_sock.cpp 174 : LNETL0: Socket 1932 received 9 bytes from peer 213.208.119.198:47851 (213.208.119.198)
2004/10/24 18:15:15 client_ryzom_rd.exe DBG 3676 udp_sock.cpp 174 : LNETL0: Socket 1932 received 9 bytes from peer 213.208.119.198:47851 (213.208.119.198)
2004/10/24 18:15:15 client_ryzom_rd.exe DBG 3676 udp_sock.cpp 174 : LNETL0: Socket 1932 received 9 bytes from peer 213.208.119.198:47851 (213.208.119.198)
2004/10/24 18:15:15 client_ryzom_rd.exe DBG 3676 udp_sock.cpp 174 : LNETL0: Socket 1932 received 9 bytes from peer 213.208.119.198:47851 (213.208.119.198)
2004/10/24 18:15:15 client_ryzom_rd.exe DBG 3676 udp_sock.cpp 174 : LNETL0: Socket 1932 received 9 bytes from peer 213.208.119.198:47851 (213.208.119.198)
2004/10/24 18:15:16 client_ryzom_rd.exe DBG 3676 udp_sock.cpp 174 : LNETL0: Socket 1932 received 9 bytes from peer 213.208.119.198:47851 (213.208.119.198)
2004/10/24 18:15:16 client_ryzom_rd.exe DBG 3676 udp_sock.cpp 174 : LNETL0: Socket 1932 received 9 bytes from peer 213.208.119.198:47851 (213.208.119.198)
2004/10/24 18:15:16 client_ryzom_rd.exe DBG 3676 udp_sock.cpp 174 : LNETL0: Socket 1932 received 9 bytes from peer 213.208.119.198:47851 (213.208.119.198)
2004/10/24 18:15:16 client_ryzom_rd.exe DBG 3676 udp_sock.cpp 174 : LNETL0: Socket 1932 received 9 bytes from peer 213.208.119.198:47851 (213.208.119.198)
2004/10/24 18:15:16 client_ryzom_rd.exe DBG 3676 udp_sock.cpp 174 : LNETL0: Socket 1932 received 9 bytes from peer 213.208.119.198:47851 (213.208.119.198)
2004/10/24 18:15:17 client_ryzom_rd.exe WRN 3676 sound_manager.cpp 686 : Sound 'specie_but_over' not found !
2004/10/24 18:15:17 client_ryzom_rd.exe DBG 3676 udp_sock.cpp 174 : LNETL0: Socket 1932 received 9 bytes from peer 213.208.119.198:47851 (213.208.119.198)
2004/10/24 18:15:17 client_ryzom_rd.exe WRN 3676 sound_manager.cpp 686 : Sound 'specie_but_over' not found !
2004/10/24 18:15:17 client_ryzom_rd.exe DBG 3676 udp_sock.cpp 174 : LNETL0: Socket 1932 received 9 bytes from peer 213.208.119.198:47851 (213.208.119.198)
2004/10/24 18:15:17 client_ryzom_rd.exe WRN 3676 sound_manager.cpp 686 : Sound 'specie_but_over' not found !
2004/10/24 18:15:17 client_ryzom_rd.exe DBG 3676 udp_sock.cpp 174 : LNETL0: Socket 1932 received 9 bytes from peer 213.208.119.198:47851 (213.208.119.198)
2004/10/24 18:15:17 client_ryzom_rd.exe DBG 3676 udp_sock.cpp 174 : LNETL0: Socket 1932 received 9 bytes from peer 213.208.119.198:47851 (213.208.119.198)
2004/10/24 18:15:17 client_ryzom_rd.exe WRN 3676 sound_manager.cpp 686 : Sound 'specie_but_over' not found !
2004/10/24 18:15:17 client_ryzom_rd.exe WRN 3676 sound_manager.cpp 686 : Sound 'specie_but_over' not found !
2004/10/24 18:15:17 client_ryzom_rd.exe WRN 3676 sound_manager.cpp 686 : Sound 'specie_but_over' not found !
2004/10/24 18:15:17 client_ryzom_rd.exe WRN 3676 sound_manager.cpp 686 : Sound 'specie_but_over' not found !
2004/10/24 18:15:17 client_ryzom_rd.exe WRN 3676 sound_manager.cpp 686 : Sound 'specie_but_over' not found !
2004/10/24 18:15:17 client_ryzom_rd.exe WRN 3676 sound_manager.cpp 686 : Sound 'specie_but_over' not found !
2004/10/24 18:15:17 client_ryzom_rd.exe WRN 3676 sound_manager.cpp 686 : Sound 'specie_but_over' not found !
2004/10/24 18:15:17 client_ryzom_rd.exe WRN 3676 sound_manager.cpp 686 : Sound 'specie_but_over' not found !
2004/10/24 18:15:18 client_ryzom_rd.exe DBG 3676 udp_sock.cpp 174 : LNETL0: Socket 1932 received 9 bytes from peer 213.208.119.198:47851 (213.208.119.198)
2004/10/24 18:15:18 client_ryzom_rd.exe DBG 3676 udp_sock.cpp 174 : LNETL0: Socket 1932 received 9 bytes from peer 213.208.119.198:47851 (213.208.119.198)
2004/10/24 18:15:18 client_ryzom_rd.exe DBG 3676 udp_sock.cpp 174 : LNETL0: Socket 1932 received 9 bytes from peer 213.208.119.198:47851 (213.208.119.198)
2004/10/24 18:15:18 client_ryzom_rd.exe DBG 3676 udp_sock.cpp 174 : LNETL0: Socket 1932 received 9 bytes from peer 213.208.119.198:47851 (213.208.119.198)
2004/10/24 18:15:18 client_ryzom_rd.exe WRN 3676 sound_manager.cpp 686 : Sound 'specie_but_over' not found !
2004/10/24 18:15:18 client_ryzom_rd.exe DBG 3676 udp_sock.cpp 174 : LNETL0: Socket 1932 received 9 bytes from peer 213.208.119.198:47851 (213.208.119.198)
2004/10/24 18:15:18 client_ryzom_rd.exe WRN 3676 sound_manager.cpp 686 : Sound 'specie_but_over' not found !
2004/10/24 18:15:18 client_ryzom_rd.exe WRN 3676 sound_manager.cpp 686 : Sound 'specie_but_over' not found !
2004/10/24 18:15:18 client_ryzom_rd.exe WRN 3676 sound_manager.cpp 686 : Sound 'specie_but_over' not found !
2004/10/24 18:15:18 client_ryzom_rd.exe WRN 3676 sound_manager.cpp 686 : Sound 'specie_but_over' not found !
2004/10/24 18:15:18 client_ryzom_rd.exe DBG 3676 udp_sock.cpp 174 : LNETL0: Socket 1932 received 9 bytes from peer 213.208.119.198:47851 (213.208.119.198)
2004/10/24 18:15:19 client_ryzom_rd.exe DBG 3676 udp_sock.cpp 174 : LNETL0: Socket 1932 received 9 bytes from peer 213.208.119.198:47851 (213.208.119.198)
2004/10/24 18:15:19 client_ryzom_rd.exe DBG 3676 udp_sock.cpp 174 : LNETL0: Socket 1932 received 9 bytes from peer 213.208.119.198:47851 (213.208.119.198)
2004/10/24 18:15:19 client_ryzom_rd.exe DBG 3676 udp_sock.cpp 174 : LNETL0: Socket 1932 received 9 bytes from peer 213.208.119.198:47851 (213.208.119.198)
2004/10/24 18:15:19 client_ryzom_rd.exe INF 3676 connection.cpp 921 : impulseCallBack : CONNECTION:SELECT_CHAR '1' sent.
2004/10/24 18:15:19 client_ryzom_rd.exe INF 3676 connection.cpp 944 : impulseCallBack : CONNECTION:ENTER sent
2004/10/24 18:15:19 client_ryzom_rd.exe DBG 3676 udp_sock.cpp 174 : LNETL0: Socket 1932 received 9 bytes from peer 213.208.119.198:47851 (213.208.119.198)
2004/10/24 18:15:19 client_ryzom_rd.exe DBG 3676 udp_sock.cpp 174 : LNETL0: Socket 1932 received 38 bytes from peer 213.208.119.198:47851 (213.208.119.198)
2004/10/24 18:15:19 client_ryzom_rd.exe INF 3676 impulse_decoder.cpp 72 : CLIMPD: received new impulsion 1 (len=179) at level 1 (channel 0)
2004/10/24 18:15:19 client_ryzom_rd.exe INF 3676 impulse_decoder.cpp 72 : CLIMPD: received new impulsion 1 (len=51) at level 1 (channel 0)
2004/10/24 18:15:19 client_ryzom_rd.exe DBG 3676 impulse_decoder.cpp 82 : CLIMPD: at level 1 (channel 0), 2 actions (ReceivedAck=501/lastAck=2/nextSentPacket=502)
2004/10/24 18:15:19 client_ryzom_rd.exe INF 3676 net_manager.cpp 243 : impulseCallBack : Received CONNECTION:USER_CHAR
2004/10/24 18:15:19 client_ryzom_rd.exe DBG 3676 net_manager.cpp 265 : <impulseUserChar> pos : 2204.910105 -6625.838315 0.000000 heading : -3.514657
2004/10/24 18:15:19 client_ryzom_rd.exe INF 3676 net_manager.cpp 286 : impulseCallBack : Received CONNECTION:READY
2004/10/24 18:15:19 client_ryzom_rd.exe INF 3676 connection.cpp 510 : impulseCallBack : received serverReceivedReady
-------------------------------
User Crash Callback:
-------------------------------
UserId: 174698
ShardId: 103
No user entity informations
ViewPosition: 0.00 0.00 0.00
Time in game: 6h 20min 40sec
LocalTime: 2004/10/24 18:15:20
ServerTick: 32407134
ConnectState: Connected
LocalAddress: :1443 (172.16.1.34)
Language: English
ClientVersion: 1.0.1.700
PatchVersion: 00014
Client is online
Memory: 172mb/510mb
Process Virtual Memory: 489mb
NeL Memory: 0b
OS: Microsoft Windows XP Service Pack 2 (Build 2600) (5.1 2600)
Processor: Intel(R) Pentium(R) 4 CPU 2.60GHz / x86 Family 15 Model 2 Stepping 9 / GenuineIntel / 2593MHz / 2 Processors found
CPUID: bfebfbff
HT: YES
CpuMask: 1
NeL3D: Direct3d / ati2dvag.dll / CONNECT 3D RADEON 9600 Series 128M / \\.\DISPLAY1 / driver version : 6.14.10.6458
3DCard: CONNECT 3D RADEON 9600 Series 128M, version 6.4.5.8
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.000032 msec
Average create time: -1.#IND00 msec
Estimated CPU: 0.000206%%
Sound driver:
FMod Driver
3d hw buffers: 29
2d hw buffers: 32
-------------------------------

Err, y have tried openGL graphic mode ?
advanced feature disabled ? (not only reducing quality)
updated soundboard drivers ?
eax disabled ?
delete the "log.log" and "clients.log" file in ryzom install folder ?
no overheating ? (how mins before crash after cold reboot)
directx9c seems mean with some gboard also
dont forget to defrag your hdd : ryzom's patch and log files generate a lots of frag....
try playing in windowed not fullscreen mode

also advanced "bugtrack" :
no programs running in background ? (especially spywares!!!!)
beware of programs who generate popups (like msn)
remove your wallpaper-changing software also
what is your mainboard chipset ? try renew driver of them
sure no overheating ? removing dust inside the computer help a lot
what about ACPI and power saving ? is there any harddrive going in "sleep" state during play ?
of course you're not overclocking any hardware parts....

Same here, I love this game but i will be forced to leave if it keeps on crashing, i tried everything

hey guys me again, ive got everything working if ur using an ATI card an update was releases bout 4 days ago to the catalyt drivers. go check i think thats fixed my probs good luck

Chances are that you just needed to do a clean install of your video drivers all along. I have been using all versions of Cats since 4.5 with no problems when installed properly (upgrade DX9c, removing old drivers, rebooting and then running new driver installer). Version 4.5 of Cats was the only one that I can remember that has actually been problematic with SoR.