The Zone in DC !!

[2x4]

I have not had this problem for quite some time, but now it has started up again. It happens with Sands and with Orchard. On my Druid. Thought maybe it was the pup doing it. I dismissed him but happened anyway.

It is happening at very high rate. Anyone have fix for this? I cleared my msconfig startup's but still is happening.

Suggestions please and thanks.

[teh_meh]

I bought a new comp early in the year. Not a techie but it's pretty loaded (tons of RAM and solid state drives). Haven't had one zone-crash since. I used to get it fairly regularly when tooning-over too much.

Point being, while I'm sure there are things they can do to help lower-end system users, it seems to be a user end tech problem rather than a 'bug'. At least in my XP anyways.

[Kylstrem]

Only thing that fixed it for me (after having it for years) was to finally move to Windows 7 64-bit.

Windows XP and Windows Vista and Windows 7 32-bit (With same videocard and memory) always had this problem. And it would happen with my first zone-in to the desert after I logged in and ran right to the desert (people have tried to call this a memory leak issue that would only happen after you have been logged on for a while and zoned into several other zones first... I disproved that for myself).

Once on the 64-bit version of Win 7, never seen it again (been at least 8 months if not longer).

[Kaytis]

It is not your fault. It is definitely a bug with the client. I used to crash zoning two or three times a night. If I had swapped a lot of toons first it was absolutely guaranteed when stepping into Sands.

I fixed it by upgrading from Windows 7 32-bits to Windows 7 64-bits. But I think that only helped because my computer has a ton of RAM. 32-bits Windows can only address some laughably small amount of memory. 64-bits Windows can address it all.

The client is leaking memory fiercely -especially when swapping toons. Eventually, something gets allocated, fails, the code does not check for failure, and boom, it faults when it tries to use the memory it thought it got.

Having a ton of memory and 64-bit OS hides the problem. It does not fix it. But the client can be used for a lot longer without crashing. Eventually the client will degrade, the frames per second will drop, and you will be chopping your way across the market place. But at least at that point you can choose to restart your client instead of it choosing for you.

I have noticed that when I quit after playing for hours and hours, that the client takes forever to actually quit. I suspect all the unfreed memory is slowly but surely being garbage collected out. The longer you play the longer it takes.

So my recommendation is a 64-bit operating system with a lot of RAM until such time as someone at Turbine thinks to run a leak detector on the client.

[Kylstrem]

It is not your fault. It is definitely a bug with the client. I used to crash zoning two or three times a night. If I had swapped a lot of toons first it was absolutely guaranteed when stepping into Sands.

I fixed it by upgrading from Windows 7 32-bits to Windows 7 64-bits. But I think that only helped because my computer has a ton of RAM. 32-bits Windows can only address some laughably small amount of memory. 64-bits Windows can address it all.

The client is leaking memory fiercely -especially when swapping toons. Eventually, something gets allocated, fails, the code does not check for failure, and boom, it faults when it tries to use the memory it thought it got.

Having a ton of memory and 64-bit OS hides the problem. It does not fix it. But the client can be used for a lot longer without crashing. Eventually the client will degrade, the frames per second will drop, and you will be chopping your way across the market place. But at least at that point you can choose to restart your client instead of it choosing for you.

I have noticed that when I quit after playing for hours and hours, that the client takes forever to actually quit. I suspect all the unfreed memory is slowly but surely being garbage collected out. The longer you play the longer it takes.

So my recommendation is a 64-bit operating system with a lot of RAM until such time as someone at Turbine thinks to run a leak detector on the client.


I think you are describing a different problem.


This is not related to the "zoning into Sands" causing a crash. As I have said and others have said, you can start DDO, load a character that is standing next to the sands entrance, try to zone into sands and have the client crash immediately.

Turbine broke something else this year with all their changes that is causing the massive "client lag" issue from swapping characters as well as the taking forever to close the client issue. These two problems are relatively new.

[2x4]

First, I am running windows vista 32 bit. I haven't upgraded just because I don't want to go through the process. I can upgrade my existing system to windows 7 64 bit and looks like I finally will.

The odd thing about this is that the zone in DC was a very rare occurance for the last year. Now it seems almost guaranteed. And it onkly happened in Sands but now it started up in sands and in the orchard. It never ever happened to me in the orchard before.

The windows upgrade sounds like it would compensate for whatever is happening but I wonder why I would have to do this if it was fine before. This is the part that is puzzling to me. It was working fine now it is back. I haven't changed anything on my PC so it is hard to think it is all me.

[BurningDownTheHouse]

Go to MyDDO.

Find player (not character) named missing_minds.

He has a post there that might help you (it helped me with the exact same issue).

This is a good place to thank him for it, so thanks and big kudos to you MM.

[MrkGrismer]

Zone in DC is 52... Fort.

[2x4]

Go to MyDDO.

Find player (not character) named missing_minds.

He has a post there that might help you (it helped me with the exact same issue).

This is a good place to thank him for it, so thanks and big kudos to you MM.

+1 for the suggestion.

mindless_minds information was very easy to follow and includes how to undo it if it doesn't work.

Ran the fix. Went to all of the problem spots in game last night. Not a single DC. Played about 3 hours. Game feels much better as well.

Thanks very much. I highly recommend this for anyone running Vista.