dndclient.exe error

[youngsheep67]

This is a follow-up thread regarding the fact every time I log on the first time, the windows would initially crash, forcing me to relog a second time. Subsequent relogs seem to be fine. At the end of the logging off, I also encountered an error message, indicating a dndclient.exe error message. Then it asks me if I want to send the error message off to Microsoft. "Error signature"-AppName: dndclient.exe. This problem started after the last ddo update. Is there an easy way to fix this problem? I google the dndclient.exe problem, and it indicates that the file may be corrupted. Any thoughts will be greatly appreciated. Tired of crashing every time I log on; worse, I think it might crash my entire computer some day if the problem gets worse. Thank you.

[Dulcimerist]

You're experiencing the dndclient crashes when exiting DDO as well? This is the crash type that I've been experiencing since Update 13, as well as quite a few other players. Here are the main threads about this issue:

http://forums.ddo.com/showthread.php?t=364096
http://forums.ddo.com/showthread.php?t=365278

After doing a survey about DDO crashing when trying to exit DDO after Update 13, nVidia graphics and 32-bit operating systems are the commonality so far. Perhaps something in the update isn't getting along with one or both of those factors.

If I were to wager a guess, Update 13 seems to have worsened the underlying memory leak issue in DDO. There's been a theory that DDO loads audio files into memory, forgets to unload them from memory when it's done with them, and eventually there's insufficient free memory remaining. This results in a crash or a nonfunctioning of certain hardware, such as the scroll wheel of a mouse. Audio files being the culprit is further hinted at with regard to the "phantom sounds" issue, where sometimes audio from a quest will mysteriously repeat itself minutes or hours later during a gaming session. Perhaps Update 13 introduced even more audio data to DDO, without the ability of DDO to unload these new files after the game doesn't need them in memory anymore.

No official workaround or fix has been discovered yet, but you could try some of the possible remedies discussed in the two threads I linked to.

This issue shouldn't cause any permanent damage to your computer, so I wouldn't worry about that.

I would highly recommend sending in a tech support ticket describing this problem in detail, just to let Turbine know that this issue is affecting more players than just a few isolated cases.