I fixed my EQ2 crashing!

[tuckera78]

<p>I have recently had the crash to desktop problem that I have been hearing an awful lot about in the EQ2 community. I</p><p>had it bad. I was wracking my brain trying to figure it out. Long story short: I uninstalled ESET NOD32 System Security</p><p>software (it's an anti-virus/anti-spyware/anti-malware/spam filter type software all rolled into one) and BINGO! No more</p><p>crashing! After a couple days of trying different things I realized that around the time I started crashing was around the</p><p>time I decided to switch from Panda Cloud Free Edition to ESET NOD32. So, I uninstalled it to see if it had anything to do</p><p>with it, and sure enough, it did. Not only have I played COMPLETELY crash free, my framerate improved and game</p><p>performance has improved.</p><p>I realize that probably not everyone who is having crash problems is running ESET NOD32, however, it may be worth a</p><p> look to see if maybe your anti-virus/anti-spyware program(s) are causing EQ2 to crash. It sure fixed mine beautifully. I</p><p>hope this helps some other people as much as it helped me. <img src="/eq2/images/smilies/3b63d1616c5dfcf29f8a7a031aaa7cad.gif" border="0" /></p>

[Alenna]

<p><cite>tuckera78 wrote:</cite></p><blockquote><p>I have recently had the crash to desktop problem that I have been hearing an awful lot about in the EQ2 community. I</p><p>had it bad. I was wracking my brain trying to figure it out. Long story short: I uninstalled ESET NOD32 System Security</p><p>software (it's an anti-virus/anti-spyware/anti-malware/spam filter type software all rolled into one) and BINGO! No more</p><p>crashing! After a couple days of trying different things I realized that around the time I started crashing was around the</p><p>time I decided to switch from Panda Cloud Free Edition to ESET NOD32. So, I uninstalled it to see if it had anything to do</p><p>with it, and sure enough, it did. Not only have I played COMPLETELY crash free, my framerate improved and game</p><p>performance has improved.</p><p>I realize that probably not everyone who is having crash problems is running ESET NOD32, however, it may be worth a</p><p> look to see if maybe your anti-virus/anti-spyware program(s) are causing EQ2 to crash. It sure fixed mine beautifully. I</p><p>hope this helps some other people as much as it helped me. <img src="/eq2/images/smilies/3b63d1616c5dfcf29f8a7a031aaa7cad.gif" border="0" /></p></blockquote><p>Since I'm using hte same anti virus and anti spyware I was before AoD it is not that it is something they did wiht the code in AoD not our side. each patch it is getting worse.</p>

[tuckera78]

<p>While it may be true that the problem was started by something they did in the patching that made the client</p><p>incompatable with the anti-virus/anti-spyware programs, It doesn't change the fact that they are now causing crashes.</p>

[TSR-JoshuaM]

<p>There are many issues that result in crashing, many are client side, some are server side, some can be fixed via troubleshooting, some need development attention, and so on.  </p><p>Antivirus can definitely be among those causes and information like this can at least help people take a look to see, and test, which group of problems they are part of.</p><p>Many things have changed with our patches and expansions and a majority of the community are not experiencing issues.  This is not to say that any experienced issues now cannot be server side, they definitely can be, but the intent of Technical Support is to get all the relevant information, make recommendations in an attempt to resolve the issue, and escalate anything else that we can't resolve to our development team when it becomes apparent it is a server side issue.  </p><p>In the meantime, be sure what group you are in, participate in the troubleshooting process, don't discount every suggestion simply because "it started last patch", as we patch every week and every problem occurs since the "last patch".  It's much more efficient and allows us to provide better service to you.</p><p>So, in a nutshell, if you are crashing post your DXDIAG information or open a support ticket with both DXDIAG/MSINFO.  Had I come across ESET or Panda in your MSINFO files I would have recommended you disable it, if it didn't work I'd eliminate that as a cause and move on, if nothing else can be found then it goes to development.  This same logic is what must be applied to every reported issue.</p><p>Locking this thread up.</p>