Crashes

[sumoman]

Hey guys as of late my number of crashes has increased hugely. i went from havin maybe 1 every1 couple of hours 2 as of this evenin i had 3 in 1 hour

I would like to now how to decrease crashes in anyway possible
thx guys

[Zerlin]

There can be many sources of the game crashing on your system:

- overheating due to dirty/damaged cooling on powersupply/CPU/GPU/Chipset or system not being ventilated properly
- sound/video/network/system drivers that did not get installed properly for some reason
- non-standard drivers
- timing of RAM not set properly
- RAM slightly damaged
- mismatched RAM
- malware/spyware/viruses
- system/GPU overclocked
- power supply not giving clean power
- loose connections on cables or CPU
- system/GPU BIOS needs upgrading
- DirectX needs to be upgraded to DX9.0c
- motherboard/cards have a component that is malfunctioning
- other apps running that are conflicting with the game somehow

These are most of the things that I can think of off the top of my head. As you can see there are many factors to consider.
The easiest thing to attempt in my opinion is:
- unplug your system from th emains and used some canned air to clean the dust out of your system
- make sure all RAM, cards and cables are seated properly in their connectors
- make sure DX9.0c is installed then remove your video drivers, reboot and install the video drivers again.
- Update your virus checker/spyware remover and thoroughly scan your system.
- Make sure all your Windows Updates are done.
- stop all the other apps running on your system when trying to play Ryzom
- Run the 'check data' option from the launcher to verify that your game files are not corrupt.
- Then run the 'Configure Ryzom' app to disable all the advanced GFX functionality and lower the settings, as well as disabling sound. Slowly enable and raise the GFX settings as you find the game working properly.

If it still crashes at lowest settings then chances are you have a hardware/OS issue that needs more serious investigation.

[thexdane]

this might sound odd but i got an oddball suggestion

check that your email settings are correct, so check that outlook is ok to send email through your server or what ever is your default email client according to windows

[rushin]

i find some gfx driver updates cause unexpected crashes.. i went through a phase of crashing every few hours, rolled back drivers to a previous version and the crashes stopped..

its an easier place to start than ripping apart ur hardware

[micrix]

Hey guys as of late my number of crashes has increased hugely. i went from havin maybe 1 every1 couple of hours 2 as of this evenin i had 3 in 1 hour

I would like to now how to decrease crashes in anyway possible
thx guys

I can not remember my last crash. The client runs fine on my PC. But yesterday i had 4 in a row.

Anybody else ?

[geezas]

Could be some network thing ? Lately I have been getting some weird lag that locks the cleint for a few secs and then everything go's verry fast and it's back to normal. I know of one other who has a similar problem.

[thexdane]

Could be some network thing ? Lately I have been getting some weird lag that locks the cleint for a few secs and then everything go's verry fast and it's back to normal. I know of one other who has a similar problem.

that's called lag, the speed thing is normal to happen after you unlag

[geezas]

that's called lag, the speed thing is normal to happen after you unlag

I was thinking since it happens alot more to me it might be a bigger problem for others, making the client crash or lock up and stay locked and then crashing?

Normaly the 'please wait' thingy pop's up, but this just locks my client and it does not update or respond to anything for 3 to 10 seconds before rolling on on fast forward and doing the 'please wait' for a few nanosecs and I'm back and connected again.

[mmatto]

I was thinking since it happens alot more to me it might be a bigger problem for others, making the client crash or lock up and stay locked and then crashing?

My connection can't usually recover from please wait and ends up in "FS Lost" for some reason. Nothing seems to help but restart. And this have been quite often last days, especially yesterday (6-8 restarts in couple of hours).

[sumoman]

I dont no if this is the same for every1 but this is what i get when i crash with the 3 buttons down the bottom : debug ignore and quit which all result in the screen goin white and having to use windows task manager to close it

Access Violation exception generated at 0xA40051, thread attempts to read at 0x7ED72408.
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/05/04 18:25:29 client_ryzom_rd.exe DBG 2832 udp_sock.cpp 174 : LNETL0: Socket 212 received 9 bytes from peer 213.208.119.147:47851 (213.208.119.147)
2005/05/04 18:25:29 client_ryzom_rd.exe DBG 2832 udp_sock.cpp 174 : LNETL0: Socket 212 received 9 bytes from peer 213.208.119.147:47851 (213.208.119.147)
2005/05/04 18:25:29 client_ryzom_rd.exe DBG 2832 udp_sock.cpp 174 : LNETL0: Socket 212 received 9 bytes from peer 213.208.119.147:47851 (213.208.119.147)
2005/05/04 18:25:29 client_ryzom_rd.exe DBG 2832 udp_sock.cpp 174 : LNETL0: Socket 212 received 9 bytes from peer 213.208.119.147:47851 (213.208.119.147)
2005/05/04 18:25:30 client_ryzom_rd.exe DBG 2832 udp_sock.cpp 174 : LNETL0: Socket 212 received 9 bytes from peer 213.208.119.147:47851 (213.208.119.147)
2005/05/04 18:25:30 client_ryzom_rd.exe DBG 2832 udp_sock.cpp 174 : LNETL0: Socket 212 received 9 bytes from peer 213.208.119.147:47851 (213.208.119.147)
2005/05/04 18:25:30 client_ryzom_rd.exe DBG 2832 udp_sock.cpp 174 : LNETL0: Socket 212 received 9 bytes from peer 213.208.119.147:47851 (213.208.119.147)
2005/05/04 18:25:30 client_ryzom_rd.exe DBG 2832 udp_sock.cpp 174 : LNETL0: Socket 212 received 9 bytes from peer 213.208.119.147:47851 (213.208.119.147)
2005/05/04 18:25:30 client_ryzom_rd.exe DBG 2832 udp_sock.cpp 174 : LNETL0: Socket 212 received 9 bytes from peer 213.208.119.147:47851 (213.208.119.147)
2005/05/04 18:25:31 client_ryzom_rd.exe DBG 2832 udp_sock.cpp 174 : LNETL0: Socket 212 received 9 bytes from peer 213.208.119.147:47851 (213.208.119.147)
2005/05/04 18:25:31 client_ryzom_rd.exe DBG 2832 udp_sock.cpp 174 : LNETL0: Socket 212 received 9 bytes from peer 213.208.119.147:47851 (213.208.119.147)
2005/05/04 18:25:31 client_ryzom_rd.exe DBG 2832 udp_sock.cpp 174 : LNETL0: Socket 212 received 9 bytes from peer 213.208.119.147:47851 (213.208.119.147)
2005/05/04 18:25:31 client_ryzom_rd.exe DBG 2832 udp_sock.cpp 174 : LNETL0: Socket 212 received 9 bytes from peer 213.208.119.147:47851 (213.208.119.147)
2005/05/04 18:25:31 client_ryzom_rd.exe DBG 2832 udp_sock.cpp 174 : LNETL0: Socket 212 received 9 bytes from peer 213.208.119.147:47851 (213.208.119.147)
2005/05/04 18:25:32 client_ryzom_rd.exe DBG 2832 udp_sock.cpp 174 : LNETL0: Socket 212 received 9 bytes from peer 213.208.119.147:47851 (213.208.119.147)
2005/05/04 18:25:32 client_ryzom_rd.exe DBG 2832 udp_sock.cpp 174 : LNETL0: Socket 212 received 9 bytes from peer 213.208.119.147:47851 (213.208.119.147)
2005/05/04 18:25:32 client_ryzom_rd.exe DBG 2832 udp_sock.cpp 174 : LNETL0: Socket 212 received 9 bytes from peer 213.208.119.147:47851 (213.208.119.147)
2005/05/04 18:25:32 client_ryzom_rd.exe DBG 2832 udp_sock.cpp 174 : LNETL0: Socket 212 received 9 bytes from peer 213.208.119.147:47851 (213.208.119.147)
2005/05/04 18:25:32 client_ryzom_rd.exe DBG 2832 udp_sock.cpp 174 : LNETL0: Socket 212 received 9 bytes from peer 213.208.119.147:47851 (213.208.119.147)
2005/05/04 18:25:33 client_ryzom_rd.exe DBG 2832 udp_sock.cpp 174 : LNETL0: Socket 212 received 9 bytes from peer 213.208.119.147:47851 (213.208.119.147)
2005/05/04 18:25:33 client_ryzom_rd.exe DBG 2832 udp_sock.cpp 174 : LNETL0: Socket 212 received 9 bytes from peer 213.208.119.147:47851 (213.208.119.147)
2005/05/04 18:25:33 client_ryzom_rd.exe DBG 2832 udp_sock.cpp 174 : LNETL0: Socket 212 received 9 bytes from peer 213.208.119.147:47851 (213.208.119.147)
2005/05/04 18:25:33 client_ryzom_rd.exe DBG 2832 udp_sock.cpp 174 : LNETL0: Socket 212 received 9 bytes from peer 213.208.119.147:47851 (213.208.119.147)
2005/05/04 18:25:33 client_ryzom_rd.exe DBG 2832 udp_sock.cpp 174 : LNETL0: Socket 212 received 9 bytes from peer 213.208.119.147:47851 (213.208.119.147)
2005/05/04 18:25:34 client_ryzom_rd.exe DBG 2832 udp_sock.cpp 174 : LNETL0: Socket 212 received 9 bytes from peer 213.208.119.147:47851 (213.208.119.147)
2005/05/04 18:25:34 client_ryzom_rd.exe DBG 2832 udp_sock.cpp 174 : LNETL0: Socket 212 received 9 bytes from peer 213.208.119.147:47851 (213.208.119.147)
2005/05/04 18:25:34 client_ryzom_rd.exe DBG 2832 udp_sock.cpp 174 : LNETL0: Socket 212 received 9 bytes from peer 213.208.119.147:47851 (213.208.119.147)
2005/05/04 18:25:34 client_ryzom_rd.exe DBG 2832 udp_sock.cpp 174 : LNETL0: Socket 212 received 9 bytes from peer 213.208.119.147:47851 (213.208.119.147)
2005/05/04 18:25:34 client_ryzom_rd.exe DBG 2832 udp_sock.cpp 174 : LNETL0: Socket 212 received 9 bytes from peer 213.208.119.147:47851 (213.208.119.147)
2005/05/04 18:25:35 client_ryzom_rd.exe DBG 2832 udp_sock.cpp 174 : LNETL0: Socket 212 received 9 bytes from peer 213.208.119.147:47851 (213.208.119.147)
2005/05/04 18:25:35 client_ryzom_rd.exe DBG 2832 udp_sock.cpp 174 : LNETL0: Socket 212 received 9 bytes from peer 213.208.119.147:47851 (213.208.119.147)
2005/05/04 18:25:35 client_ryzom_rd.exe DBG 2832 udp_sock.cpp 174 : LNETL0: Socket 212 received 9 bytes from peer 213.208.119.147:47851 (213.208.119.147)
2005/05/04 18:25:35 client_ryzom_rd.exe DBG 2832 udp_sock.cpp 174 : LNETL0: Socket 212 received 9 bytes from peer 213.208.119.147:47851 (213.208.119.147)
2005/05/04 18:25:35 client_ryzom_rd.exe DBG 2832 udp_sock.cpp 174 : LNETL0: Socket 212 received 9 bytes from peer 213.208.119.147:47851 (213.208.119.147)
2005/05/04 18:25:36 client_ryzom_rd.exe DBG 2832 udp_sock.cpp 174 : LNETL0: Socket 212 received 9 bytes from peer 213.208.119.147:47851 (213.208.119.147)
2005/05/04 18:25:36 client_ryzom_rd.exe DBG 2832 udp_sock.cpp 174 : LNETL0: Socket 212 received 9 bytes from peer 213.208.119.147:47851 (213.208.119.147)
2005/05/04 18:25:36 client_ryzom_rd.exe DBG 2832 udp_sock.cpp 174 : LNETL0: Socket 212 received 9 bytes from peer 213.208.119.147:47851 (213.208.119.147)
2005/05/04 18:25:36 client_ryzom_rd.exe DBG 2832 udp_sock.cpp 174 : LNETL0: Socket 212 received 9 bytes from peer 213.208.119.147:47851 (213.208.119.147)
2005/05/04 18:25:36 client_ryzom_rd.exe DBG 2832 udp_sock.cpp 174 : LNETL0: Socket 212 received 9 bytes from peer 213.208.119.147:47851 (213.208.119.147)
2005/05/04 18:25:37 client_ryzom_rd.exe DBG 2832 udp_sock.cpp 174 : LNETL0: Socket 212 received 9 bytes from peer 213.208.119.147:47851 (213.208.119.147)
2005/05/04 18:25:37 client_ryzom_rd.exe DBG 2832 udp_sock.cpp 174 : LNETL0: Socket 212 received 9 bytes from peer 213.208.119.147:47851 (213.208.119.147)
2005/05/04 18:25:37 client_ryzom_rd.exe DBG 2832 udp_sock.cpp 174 : LNETL0: Socket 212 received 9 bytes from peer 213.208.119.147:47851 (213.208.119.147)
2005/05/04 18:25:37 client_ryzom_rd.exe DBG 2832 udp_sock.cpp 174 : LNETL0: Socket 212 received 9 bytes from peer 213.208.119.147:47851 (213.208.119.147)
2005/05/04 18:25:37 client_ryzom_rd.exe DBG 2832 udp_sock.cpp 174 : LNETL0: Socket 212 received 9 bytes from peer 213.208.119.147:47851 (213.208.119.147)
2005/05/04 18:25:38 client_ryzom_rd.exe DBG 2832 udp_sock.cpp 174 : LNETL0: Socket 212 received 9 bytes from peer 213.208.119.147:47851 (213.208.119.147)
2005/05/04 18:25:38 client_ryzom_rd.exe DBG 2832 udp_sock.cpp 174 : LNETL0: Socket 212 received 9 bytes from peer 213.208.119.147:47851 (213.208.119.147)
2005/05/04 18:25:38 client_ryzom_rd.exe DBG 2832 udp_sock.cpp 174 : LNETL0: Socket 212 received 9 bytes from peer 213.208.119.147:47851 (213.208.119.147)
2005/05/04 18:25:38 client_ryzom_rd.exe DBG 2832 udp_sock.cpp 174 : LNETL0: Socket 212 received 9 bytes from peer 213.208.119.147:47851 (213.208.119.147)
2005/05/04 18:25:38 client_ryzom_rd.exe DBG 2832 udp_sock.cpp 174 : LNETL0: Socket 212 received 9 bytes from peer 213.208.119.147:47851 (213.208.119.147)
2005/05/04 18:25:39 client_ryzom_rd.exe DBG 2832 udp_sock.cpp 174 : LNETL0: Socket 212 received 9 bytes from peer 213.208.119.147:47851 (213.208.119.147)
2005/05/04 18:25:39 client_ryzom_rd.exe DBG 2832 udp_sock.cpp 174 : LNETL0: Socket 212 received 9 bytes from peer 213.208.119.147:47851 (213.208.119.147)
-------------------------------
User Crash Callback:
-------------------------------
UserId: 55486
ShardId: 103
No user entity informations
ViewPosition: 0.00 0.00 0.00
Time in game: 9h 47min 13sec
LocalTime: 2005/05/04 18:25:40
ServerTick: 193843972
ConnectState: Connected
LocalAddress: :1485 (81.76.202.248)
Language: English
ClientVersion: 1.2.0.800
PatchVersion: 00064
Client is online
Memory: 167mB/511mB
Process Virtual Memory: 327mB
NeL Memory: 0B
OS: Microsoft Windows XP Service Pack 2 (Build 2600) (5.1 2600)
Processor: AMD Athlon(tm) XP 2100+ / x86 Family 6 Model 6 Stepping 2 / AuthenticAMD / 1740MHz / 1 Processors found
CPUID: 383fbff
HT: NO
CpuMask: 1
NeL3D: OpenGL / NVIDIA Corporation / GeForce4 MX 420/AGP/SSE/3DNOW! / 1.5.1
3DCard: NVIDIA GeForce4 MX 420, version 6.1.7.6
No sound
-------------------------------