Results 1 to 9 of 9
  1. #1
    Community Member Shade's Avatar
    Join Date
    Feb 2006
    Posts
    7,951

    Default Game crash when closing DDO

    Whenever I close DDO, my client crash's. It's just a client crash in ddo.exe - no .dll referenced.

    Doesn't always happen, but does it around 90% of the time. As I press exit, the screen goes black like loading the desktop then the error comes up, or often it doesn't come up and im left hanging on a black screen. But the box is in the backgroudn so if I hit enter - it will close the crash dialog and get me to the desktop.

    System specs:
    Alienware Area51 7500 - Alienware 680I SLI Motherboard
    Core2Duo E6850
    Geforce 8800GT
    2GB DDR-800
    1TB Hard Drive (Dual drive raid array)
    Windows XP MCE 2005 SP3 (RC1)
    Forceware Driver v169.21 (Official WHQL)
    Most other drivers up to date and xp hotfixes installed

  2. #2
    Customer Service Representative
    Join Date
    Apr 2007
    Posts
    1,193

    Default

    IF it is only crashing on exit first try disabling the launcher staying active while playing. If that does not help please post your dxdiag as well as info on any other apps you run in the background.

  3. #3
    Community Member Shade's Avatar
    Join Date
    Feb 2006
    Posts
    7,951

    Default

    Yea it's only when I exit. I always keep the launcher disabled.

    No background programs running really. Just a couple require driver apps for my soundcard and keyboard:
    rthdcpl.exe - Realtek Sound driver
    itype.exe - MS Intellitype for my keyboard

    Here is my DxDiag:
    http://wave.prohosting.com/garak128/DxDiag.txt

  4. #4
    Community Member
    Join Date
    Sep 2009
    Posts
    13

    Default

    Im having the same issue.

    100% of the time. I exit the game, and the ddo.exe crashes throwing a windows error saying it failed. Ive submitted it to MS using the normal way, but they probably wont do anything about it being that its most likely not a windows issue.

    My gf has an identical computer (i built both at the same time. Same parts and all) and hers never crashes on exit. Makes no sense.

  5. #5
    Community Member Warbler's Avatar
    Join Date
    Apr 2006
    Posts
    128

    Default

    same issue

  6. #6
    Community Member Shade's Avatar
    Join Date
    Feb 2006
    Posts
    7,951

    Default

    Quote Originally Posted by Warbler View Post
    same issue
    wow major necro..

    Heres my update years later heh:
    The issue did eventually go away. Couldn't pinpoint what did it as I rebuilt my system entirely pretty much. That or one of the last 9000 patches.

    Only crashs I get now are the common memory leak one, usually about 2-4 hours in.

    u might wanna post som system specs and stuff if you to fix it.

    Some general advice would be to fully update stuff tho:
    Windows updates, video card drivers, VC++ versions especially.
    Also may wanna grab updated msxml if your running XP.. (W7 has good ones built in)

  7. #7
    Community Member Shade's Avatar
    Join Date
    Feb 2006
    Posts
    7,951

    Default

    mm spoke too soon lol.. Bug is back, at least for lamannia.

  8. #8
    Community Member
    Join Date
    Oct 2009
    Posts
    2,187

    Default

    Ah - if you are getting the standard windows error message (submit this to Microsoft, etc., blahblah) on the lammania preview server, try resetting your graphics options in-game to default and reselect anything you want.

    This was happening to me when I first started messing with the lammania server this week and that fixed the problem for me. My supposition was that some change in the new update did not properly "carry over" from the previous update of my settings on lammania. This is not all that unexpected for a preview update on a preview server where every bit of polish has not been added yet.

    (I wondered if "repairng graphics" in the client would do the same thing.)

  9. #9
    Community Member donfilibuster's Avatar
    Join Date
    Nov 2009
    Posts
    4,063

    Default

    On exit the process take ages to deallocate all the ram thrown into disk swap.
    The more toon switches you did the longer it takes, so restarting every now and then helps.

    Any difficulty with ram and disk swap can lead to the crash on exit... or on load, or in between.
    Could not discard damaged ram or disk even since it can happen out of the blue.

    It used to be the fastest way to relog to just alt-tab into the task manager and kill ddoclient manually.
    But these days if you do so then the launcher will take longer to start, altough still faster than waiting.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

This form's session has expired. You need to reload the page.

Reload