Haven't Crashed in Years, Many Recently

Discussion in 'Player Support' started by minimind, Sep 2, 2019.

  1. minimind Augur

    Hi all,

    I have been running ultra-smooth with EQ and Windows both for probably 5 years. Not a crash in sight. Recently (within the last 3 weeks or so), I've been getting crashes every other day-- sometimes just EQ, sometimes a Win10 BSOD.

    Last night, I left a pair of characters in the lobby over night to soak up buffs. I came back to one of the clients. The other had crashed. Here's the relevant part of dump. Who can help provide some insight?

    [Mon Sep 02 06:13:59 2019]01392:Exception in RunGame GameLoop Code = c0000005 ADDR=3E6FE54A
    [Mon Sep 02 06:13:59 2019]01393:EAX=3e6fe54a EBX=3bda4880 ECX=4c52f584 EDX=4c52f584
    [Mon Sep 02 06:13:59 2019]01394:ESI=626d29ec EDI=626d294c EBP=0188d7c0 ESP=0188d75c
    [Mon Sep 02 06:13:59 2019]01395:process was trying to WRITE invalid data.
    [Mon Sep 02 06:13:59 2019]01396:Invalid access occurred at virtual address 0x3e6fe54a.
    [Mon Sep 02 06:14:00 2019]01397:Fatal error occurred in mainthread! (Release Client #630)

    [Mon Sep 02 06:14:00 2019]01398:Client Version: Aug 15 2019 14:36:17
    [Mon Sep 02 06:14:00 2019]01399:Skin Directory: UIFiles\Aug2013\

    [Mon Sep 02 06:14:00 2019]01400:Graphics DLL Loaded: Graphics DLL Version 2.00.112532
    [Mon Sep 02 06:14:00 2019]01401:Graphics Build Date: Aug 15 2019 14:37:48
    [Mon Sep 02 06:14:00 2019]01402:Video Card: NVIDIA GeForce GTX 1060 3GB,

    [Mon Sep 02 06:14:00 2019]01403:Crash (char = Thickn, zone = guildlobby)

    [Mon Sep 02 06:14:00 2019]01404:Local Player's World location at time of crash: 500.830475, -23.795511, 5.075920.

    [Mon Sep 02 06:14:00 2019]01405:Gamestate at crash = 5

    [Mon Sep 02 06:14:00 2019]01406:processor: 4 of type 586
    [Mon Sep 02 06:14:00 2019]01407:Memory: Load: 47, Total Phys: 8124, Avail Phys: 4288, Total Page: 10044, Avail Page: 3046, Total Virtual: 4095, Avail Virtual: 2282, FreeBlocks: 2039,44,24,12,11,11,11,10,9,8
    [Mon Sep 02 06:14:00 2019]01408:pools: Temp: 1703936(0). Persistent: 45594272(45583702). OnDemand: 25427968(25352556). Zone: 17463192(17390162)
    [Mon Sep 02 06:14:00 2019]01409:MaxTextures: 120013k, CurrentTextures: 99553k, HighQualityTextures: 92112k
    [Mon Sep 02 06:14:00 2019]01410:CPU: Intel(R) Core(TM) i5-7400 CPU @ 3.00GHz 10000

    [Mon Sep 02 06:14:00 2019]01411:Memory Mode: Maximum
  2. Aanuvane Augur

    I posted over in the bug forum as well, but I'm now experiencing an unacceptable number of crashes as well. I don't know how to pull this type of information out, but basically what is happening in my case....

    I run three accounts regularly. I have a full group of these three accounts with three mercs. I stopped using chat window tabs because that was preventing me from even logging in the character that was trying to use tabs.

    Ever since the last patch, one (or more) of my accounts will become completely unresponsive when zoning. The latest problem I had was about 12:20pm EDT today, I used a druid port to move my group from Sarith to The Grounds. After casting, two characters eventually became active in The Grounds, but I had to manually stop the third account with Task Manager and log it back in. The character is always in the destination zone, they just never make it all the way in. In this particular instance, one character landed in The Grounds initially and the account was initially responsive, but then it also became unresponsive, so that second account also had to be manually stopped and restarted.

    That second type of unresponsiveness actually started after I got a new computer and have been trying to use bluetooth to connect to a Google Home device as the computer's "speaker". I stopped using the Google Home in this way while playing EQ to avoid the random freezing while playing. The most recent freezing while zoning only started after the last patch.

    Any thoughts?
  3. Gregwarrian New Member

    I have been having client crashes to on zoning and some on login after not having had any for years. Hope this patch fixes it.
  4. minimind Augur

    Thanks for reminding me of this thread. I'll make sure to follow up tonight to see if the crashing is alleviated.
  5. Lilpatt New Member

    I have been having the same problem recently with Lilpatt crashing on zoning again for the first time in ages. This was not a problem for the longest time. I box three accounts on two separate computers but the one that crashes is always the one on the stand alone system. I am on The Rathe so boxing is permitted on same computer, just don't know why this started back up. It used to be mainly with zoning into or out of Valley but now it seems FM and a couple others like to join in.

  6. minimind Augur

    I logged in tonight after the patch. Left myself idling in the Lobby to soak up buffs. I came back two hours later and EQ had crashed.
  7. minimind Augur

    Final post.

    I've solved the problem in my case. After much analysis of my crash dumps, I began to suspect that I had a hardware RAM problem. However, none of my memory scans pulled up errors. I was so annoyed by the crashes, I went bargain hunting and decided to lay out $60 for new RAM. I went from 8GB of stock generic DDR4-2400 to 16GB of Crucial. Otherwise the same specs.

    I've left multiple accounts logged in for multiple days and not a single crash.

    I don't think the issue was the amount of RAM, but I do think there was an issue with the RAM itself.
    Sarkaukar likes this.
  8. Sarkaukar Augur

    In the 1st post you had noted BSOD. Anything from heat to component failure. Looks like you have resolved it with memory. With that said, it may not have been memory perse but voltage irregularities /speed/heat.

    • Clear out all dust buildup on heatsinks. (too many never perform any real cleaning, especially laptops. And several desktop AMD cpu heatsinks usually have to be removed to do a thorough cleaning /shudders..)
    • Set Power Options to High Performance
    • Is PSU appropriate for system setup, especially if it is a mfg brand and not self built.
    • Locking down speeds via bios. Turbo boost is a layman's temp overclocking program which usually entails increasing the BLCK/base frequency.
    • Running Stress Tests such as Prime95 Blended Torture test, etc. as a double check
    Also Windows 10 updates by default also updates device drivers, which can fubar things up.. One has to jump through a few hoops to disable that feature.

Share This Page