Results 1 to 4 of 4

Thread: Zone to Desktop

  1. #1
    Community Member
    Join Date
    Feb 2015
    Posts
    2

    Default Zone to Desktop

    Hello all,

    I will sometimes try and zone from one area to another, and end up crashing to desktop. It does not seem to matter from where to where, and it doesn't do it all the time. When I log back in, I will be in the zone I was trying to get to. Any ideas?

    Thanks for any help.

  2. #2

    Default

    That issue has plagued the game for years. It's usually a driver issue in Windows, a sound card being the most likely culprit. I've experienced the same problem under Linux using Wine - depending on the Wine and kernel version - which leads my to believe a deprecated, malformed or redundant DX call is being made. It's truly one of those bugs that is buried so deep in the code it may never be found.
    The newest computer can merely compound, at speed, the oldest problem in the relations between human beings, and in the end the communicator will be confronted with the old problem, of what to say and how to say it. - Edward R. Murrow (1964)

  3. #3
    Community Member magaiti's Avatar
    Join Date
    Dec 2016
    Posts
    925

    Default

    Zoning is a curious thing; full of hope and promise one minute, then everything goes pear-shaped.

  4. #4
    Community Member
    Join Date
    Mar 2012
    Posts
    33

    Default

    I remember being DC'd when switching zones and was happy when that seemed to be fixed. This is different, this is a crash to desktop and I haven't seen it until these most recent patches. The crashlog offset and exception type (STATUS_NO_MEMORY) are consistent and to me indicate something that is probably fixable.

    Last several crashes:
    Faulting application name: dndclient.exe, version: 5000.50.2069.4017, time stamp: 0x61631fd7
    Faulting module name: ntdll.dll, version: 10.0.18362.1679, time stamp: 0x35191cc1
    Exception code: 0xc0000017
    Fault offset: 0x000d922e
    Last 8 crashes were all same exception/offset.

    There was one other crash for a different game version of ACCESS_VIOLATION ~11 days ago with a different offset
    Faulting application name: dndclient.exe, version: 5000.50.1338.4016, time stamp: 0x61300764
    Faulting module name: dndclient.exe, version: 5000.50.1338.4016, time stamp: 0x61300764
    Exception code: 0xc0000005
    Fault offset: 0x000fd420

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