Runes of Magic US / AU

When you are crashing, are you completely sure that you are crashing? From the sounds of it, I don't think that you are actually crashing, I think you are disconnecting instead (getting booted to login). If that's the case, try running a traceroute to the servers. You can do this by going into the command prompt on the computer and typing into it: tracert 206.253.173..50

I'm not entirely sure about this week as I've been busy with finals, but I know that last week and a couple weeks ago, people were having issues with disconnecting.

I had a problem with Windows 10 constantly crashing, averaging about every 20 minutes. Couldn't find the problem, went back to Windows 8 w/o any problems.

Also, try setting your 'virtual memory' to custom and set the maximum setting to all available memory (set minimum to 10000). This also helped alot (with Windows .

Virtual memory setting is 'file explorer', right click on 'this PC', properties, advance system settings, advanced tab, performance, advanced tab, virtual memory-change. Set to custom size, mine is set to 10,000 min, 1,779,747 max.

Good luck.

Crashing is a very common, long standing issue with this game for a large amount of the players. Known and complained about for years. Zero progress has been made on addressing this. I just checked, and I have over 2000 crash reports in my client folder for the last year and a half. In my experience it is 100% certain that if you zone via snoop from varanas central, to Tergothen Bay and back, you will crash. Also a smallish number of logout/change toon/login cycles without closing the client if your toons are in different zones will reliably crash. Most long term players restart their client before doing important things like siege wars or big runs, why? because otherwise, they will crash randomly during such events. This is learned behavior that most people do not think twice about now adays.

There are a few things you can do, like the ones mentioned above, or like using Datum Memory Booster (or other similar tools, which apparently you have tried) to flush some memory from the game. These "work" for some people (but I challenge any such people to take the above trip).

If you are new, you are likely actually playing the game... which means moving around between zones, which means crashing. Welcome to RoM.


I have actually spent some time debugging this problem, and I believe that a majority of the crashes are in redux_runtime.dll and are highly related to 3d texture storage/processing or corruption. This appears to be 3rd party code that the game is using, and has not been touched (in my client) since 2010. Turning the textures all the way down (to the point where it looks horrible) will likely extend the time you can play without crash, but whats the point?

Quoted from "dekar411"

Quoted from "Zerienga"

When you are crashing, are you completely sure that you are crashing? From the sounds of it, I don't think that you are actually crashing, I think you are disconnecting instead (getting booted to login). If that's the case, try running a traceroute to the servers. You can do this by going into the command prompt on the computer and typing into it: tracert 206.253.173..50

I'm not entirely sure about this week as I've been busy with finals, but I know that last week and a couple weeks ago, people were having issues with disconnecting.

It is not a server or connection issue. Screen goes black and a "Send report" popup is shown. There would not be crash reports otherwise

I tried your command but does not reach:

Source code

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37

Tracing route to 206.253.173.50 over a maximum of 30 hops 1 <1 ms <1 ms <1 ms COMTREND [192.168.1.1] 2 65 ms 29 ms 30 ms 1.128.17.95.dynamic.jazztel.es [95.17.128.1] 3 28 ms 29 ms 28 ms 10.255.164.254 4 48 ms 47 ms 46 ms 45.217.106.212.static.jazztel.es [212.106.217.45 ] 5 45 ms 47 ms 46 ms 46.217.106.212.static.jazztel.es [212.106.217.46 ] 6 66 ms 70 ms 70 ms ae54.edge5.Paris1.Level3.net [212.73.200.73] 7 70 ms 69 ms 71 ms ae5.par22.ip4.gtt.net [141.136.103.181] 8 172 ms 173 ms 171 ms xe-7-2-2.mia12.ip4.gtt.net [141.136.111.45] 9 173 ms 173 ms 173 ms te3-4.ibr4.vaultnetworks.com [173.205.52.186] 10 174 ms 173 ms 173 ms vl944.te1-1.car4.vaultnetworks.com [206.253.168. 158] 11 172 ms 174 ms 173 ms 206.253.171.6 12 * * * Request timed out. 13 * * * Request timed out. 14 * * * Request timed out. 15 * * * Request timed out. 16 * * * Request timed out. 17 * * * Request timed out. 18 * * * Request timed out. 19 * * * Request timed out. 20 * * * Request timed out. 21 * * * Request timed out. 22 * * * Request timed out. 23 * * * Request timed out. 24 * * * Request timed out. 25 * * * Request timed out. 26 * * * Request timed out. 27 * * * Request timed out. 28 * * * Request timed out. 29 * * * Request timed out. 30 * * * Request timed out. Trace complete.

Are you sure that IP is correct? since ping does not reach

	Source code
1 2 3 4 5 6 7 8	Pinging 206.253.173.50 with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 206.253.173.50: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

The IP is correct. It's from a previous thread that was in a post by Saito Hajime (I can't find the thread atm. I'll find it later tonight). The IP doesn't ping at all, and stopping where you did is perfectly normal.