Client keeps crashing and can't open support ticket

Discussion in 'Players Supporting Players' started by Sasfer, Mar 21, 2015.

  1. Sasfer Member

    I tried to open a support ticket through the website with the text below but I can't select the second option under in-games issues, technical or anything as no other drop down boxes appear preventing me from submitting a ticket.

    Hi, I've only recently came back after a few years away and I'm having issues with eq2 crashing. I've googled and looked at the forums and tried some things in attempt to solve the problems with out much luck. Unless there is a way to making the client more stable I won't bother purchasing the newest expansion and continue playing.

    It crashes in two different ways. The first is Eq2 stops responding, windows searches for a solution that does nothing and I get kicked to desktop.
    The seconds and much more frequent error is labelled a fatal error. I've attached a screenshot of this error to help identity the fault. I've also attached DxDiag and MsInfo incase they can help too.

    Thanks in advance

    As I can't included the screenshot of the fault It says:

    "Fatal Error" in the border
    Everquest II has detected an unrecoverable error and must shutdown.
    <verify> G:\live\eq2\framework\render\DDST\Texture.cpp (235):
    !"Unknown DDS texture Flags"
    014e734d

    Can anyone help or shall I just give up and find something out to spend my money on?
  2. Lamatu Active Member

    You can try going to options>performance>textures and lowering the quality. Be sure to have advanced enabled in options.

    There are three textures drop menus and the first is the one you should try lowering than what it's currently at.

    As for your trouble doing a petition, you should be able to click the grey arrow to the left to open the second option for the drop down menu.
  3. Sasfer Member

    Thanks Lamatu but unfortunately I've already tried lowering gfx to the lowest they with go and the crashes still happen. My system is more than capable of running eq2. Currently Eq2 isn't pushing my components at all as I monitor my temps at all times. Even with fans set to Low Speed ( Medium and High still available) the max temp my system, cpu and gfx temperatures get in EQ2 are at least 10c lower than when playing games like Shadows of Mordor on maxed settings including Nvidia's DSR.

    I7-4790 @4Ghz
    16GB Ram
    Nvidia GTX 970
    480GB SSD
    Realtek onboard sound and a SB Audigy sound card.
    I play in windowed 1920x1080 if that helps.

    So far I've tried removing the cache file and folders along with character_isettings,
    Lowering all graphic options to minimum,
    Adjusting Sound provider from Miles to Dolby ( what the hell happened hardware supported sound, EAX?)
    I left my system on overnight so it could fully patch instead of streaming while playing.

    Inside Eq2 folder I've found the alert log and outofmemory files.

    Part of the alert file:
    build="SOEBuild=11828L" version="SOEVersionString=2015/3/18 11:31:31" build_type="USER OPTIMIZED" ls_address="none" zone="exp03_rgn_greater_faydark" loc="206.67 121.73 381.93" performance="7" alert="G:\live\eq2\framework\core\util\Filer.cpp(1381): STREAM File [0E8852C0C13C47CD] expected CRC[C688] recd[195E]"

    There are loads of the above chunk with slight variations in the numbers/letter until the segments:

    build="SOEBuild=11828L" version="SOEVersionString=2015/3/18 11:31:31" build_type="USER OPTIMIZED" ls_address="none" zone="exp03_rgn_greater_faydark" loc="217.42 128.50 395.31" performance="7" alert="G:\live\eq2\framework\vdl\VdlErr.cpp(85): (VDL Parser) shaders/characters/accessories/wieldable_items/weapons/bow/long_bow/dreadnaughts_longbow.vdl(1) : Error, Unknown class q
    "
    build="SOEBuild=11828L" version="SOEVersionString=2015/3/18 11:31:31" build_type="USER OPTIMIZED" ls_address="none" zone="exp03_rgn_greater_faydark" loc="217.42 128.50 395.31" performance="7" alert="G:\live\eq2\framework\vdl\VdlErr.cpp(85): (VDL Parser) shaders/characters/accessories/wieldable_items/weapons/bow/long_bow/dreadnaughts_longbow.vdl(1) : Error, Unknown class d
    "
    build="SOEBuild=11828L" version="SOEVersionString=2015/3/18 11:31:31" build_type="USER OPTIMIZED" ls_address="none" zone="exp03_rgn_greater_faydark" loc=" 84.74 65.50 251.54" performance="7" alert="G:\live\eq2\framework\render\DDSTexture.cpp(295): File cooked/characters/accessories/wearable_items_textures/exp09/starter_robes/leather_handfeet_spec.dds with DDS extension is not a dds file."
    build="SOEBuild=11828L" version="SOEVersionString=2015/3/18 11:31:31" build_type="USER OPTIMIZED" ls_address="none" zone="exp03_rgn_greater_faydark" loc=" 85.74 37.36 225.68" performance="7" alert="G:\live\eq2\framework\render\DDSTexture.cpp(295): File cooked/interiors/sourceimages/animations/honey/honeycomb_color000.dds with DDS extension is not a dds file."

    Part of the OutOfMemory file:

    Size Count Owner
    -------------------------------------------------------------------------------
    92043345 46039 0x00FAD6FC
    78294992 38531 0x01B660F0
    60256000 2 0x0189E44F
    36890456 1696 0x01B0FCAB
    32266681 29321 0x01AB89DB
    1350205 667 0x0188429A
    1346956 313 (Thread local cache entry)

    loads of the above repeats until:
    Global MemoryManager Stats:
    LifetimeAllocations: 1130940
    LifetimeFrees: 745701
    LifetimeMemoryAllocated: 18994970946
    LifetimeMemoryFreed: 18078211829
    CurrentSystemAllocations: 7958
    LifetimeSystemAllocations: 16019
    LifetimeSystemFrees: 8061
    CurrentSystemMemAllocated: 1000407040
    CurrentAllocatedMemory: 916759117 (91.64% of CurrentSystemMemAllocated)
    CurrentFreeMemory: 72395760 (7.24% of CurrentSystemMemAllocated)
    CurrentAllocatedBlocks: 385239
    CurrentFreeBlocks: 4972
    CurrentUniqueFreeBlocks: 994 (19.99% of CurrentFreeBlocks)
    PeakSystemMemAllocated: 1001193472
    PeakAllocatedMemory: 978341690
    PeakFreeMemory: 107588912
    PeakFreeBlocks: 6301
    PeakUniqueFreeBlocks: 1215
    LifetimeBlockAllocations: 16734804
    LifetimeBlockFrees: 10260107
    CurrentBlockAllocatorTotalSize: 431791872
    CurrentBlockAllocatorFreeSpace: 5239648 (1.21% of CurrentBlockAllocatorTotalSize)
    CurrentBlockTrackerAllocs: 244994
    MutexLocks: 29016998
    MutexWaits: 254014 (0.88% of MutexLocks)
    Per-Thread Cache for Thread 8604
    LifetimeAllocations: 296504838 (96.39% of AllocationRequests(307604166))
    LifetimeFrees: 296505162 (96.55% of FreeRequests(307095255))
    Cache: 260048 bytes/324 entries (802 bytes average)
    Per-Thread Cache for Thread 8016
    LifetimeAllocations: 189 (0.35% of AllocationRequests(54770))
    LifetimeFrees: 242 (100.00% of FreeRequests(242))
    Cache: 220896 bytes/53 entries (4167 bytes average)
    Per-Thread Cache for Thread 5088
    LifetimeAllocations: 39972 (8.42% of AllocationRequests(474652))
    LifetimeFrees: 40013 (90.45% of FreeRequests(44238))
    Cache: 239904 bytes/41 entries (5851 bytes average)
    Per-Thread Cache for Thread 8932
    LifetimeAllocations: 42222 (8.86% of AllocationRequests(476813))
    LifetimeFrees: 42259 (91.12% of FreeRequests(46375))
    Cache: 245280 bytes/37 entries (6629 bytes average)
    Per-Thread Cache for Thread 8104
    LifetimeAllocations: 106949 (17.14% of AllocationRequests(623824))
    LifetimeFrees: 106978 (96.06% of FreeRequests(111366))
    Cache: 175696 bytes/29 entries (6058 bytes average)
    Per-Thread Cache for Thread 4584
    LifetimeAllocations: 82271 (15.11% of AllocationRequests(544512))
    LifetimeFrees: 82303 (95.51% of FreeRequests(86171))
    Cache: 175920 bytes/32 entries (5497 bytes average)
    Per-Thread Cache for Thread 7760
    LifetimeAllocations: 4 (16.67% of AllocationRequests(24))
    LifetimeFrees: 9 (100.00% of FreeRequests(9))
    Cache: 7312 bytes/5 entries (1462 bytes average)
    Per-Thread Cache for Thread 5956
    LifetimeAllocations: 82322 (57.49% of AllocationRequests(143186))
    LifetimeFrees: 87323 (33.63% of FreeRequests(259641))
    Cache: 262144 bytes/5001 entries (52 bytes average)
    Per-Thread Cache for Thread 7456
    LifetimeAllocations: 1 (50.00% of AllocationRequests(2))
    LifetimeFrees: 1905 (100.00% of FreeRequests(1905))
    Cache: 130496 bytes/1904 entries (68 bytes average)
    Per-Thread Cache for Thread 8048
    LifetimeAllocations: 15320 (68.23% of AllocationRequests(22454))
    LifetimeFrees: 22460 (63.79% of FreeRequests(35207))
    Cache: 262128 bytes/7140 entries (36 bytes average)

    The Texture and dds parts have me stumped but the outofmemory part has me suspecting a memory leak so I'm going to try manually increasing Virtual Memory to see if that helps.
  4. Lamatu Active Member

    So you did go to options/advanced>display>texture resolution and lowered those three drop down menus? I had the location wrong in my first post.

    Do you only crash while zoning or within a minute of zoning?
  5. Laiina Well-Known Member

    This does not sound like an issue that will be solved by lowering the graphics. It sounds like either a corrupt or missing file that it is trying to access, or a bug in the graphics or DX9/DX10/DX11 for the graphics card driver.

    Try doing a complete file check from the launcher window, and make sure you have a recent graphics driver.

    I assume that you are not trying to put the EQ2 files on the SSD, because they will not fit. Only the .exe and related files should be on the SSD, the rest on a separate drive.
  6. Sasfer Member

    Since I increased virtual memory and clicked extreme performance followed by manually lowering everything else it hasn't crashed in almost 4 hours. Will leave settings as they are for now and if it doesn't crash I'll switch Gfx back to what I had them set at tomorrow to see if the crashing resumes. If it doesn't crash then increasing Virtual memory fixed it. If it crashes then I know its a setting of some sort in the display options and I'll just have to keep tweaking till I find the culprit.

    Thanks for the advice
  7. Bashem Well-Known Member

    First thing to do is open launchpad and click the advanced tool on button on the lower left hand side of the launchpad and the select validate game assets to see if you have any missing or corrupt game files!
  8. flameweaver Well-Known Member

  9. Reggie777 Member

    Good Luck! I've been struggling with this problems now for months. Tried everything the tech suggested. Reinstalled directx, deleted this and that. And still no relief. Constantly getting kicked off, and client not working error. After 10 years a member of EQ2, I'm about ready to call it quits. Now, I have a ghost image when I play. The target arrows are not on the target, the "fires" are not where they're supposed to be, and I have a pale shadow image of my toon below my actual location. Getting tired asking the techs for help. They are nice enough. But have not been able to fix ANY of the problems I've encountered. Please forgive my frustrations. But... the game I've loved for all these years is broken for me.
  10. Bashem Well-Known Member

    People who want to see how many game runs with there setup should check out this link.
    It has Everquest II in the dropdown list as well as many many other games .
    I use to check my own computers and other computers that I am working on.

    http://www.systemrequirementslab.com/cyri
    Laiina likes this.
  11. Sasfer Member

    Eq2 has been quite stable for a week or so now with maybe 1 or 2 crashes in total. Bearing in mind I'm currently of work so on Eq2 for the vast majority of the day and stay logged in and /afk when popping to shops, cooking food and stuff. So it's been running pretty much none stop all day everyday. I have fiddled with graphics settings constantly and that doesn't seem to effect it.

    After Validating Game Assets Eq2 would work fine temporarily. I sometimes run 2 accounts at the same time and I would make sure streaming was only active on one at a time. Even when I only used a single account it would still happened. Now I've disabled streaming I have ran two separate accounts at once without the crashes. I can only assume that when streaming it was corrupting data somehow.

    Anyway its all fixed now :)