NVIDIA Driver Issue

[Jrel]

<p>Been having a problem with Everquest2.exe client crashing immediately before any character fully logs into a zone (or the character select screen) everytime I shut EQ down for a while and then try starting it up again right after (or a few hours later).  This has been happening since the 27 April update.</p><p>I'm running Vista 64 Ultimate SP 1. The NVidia driver ver 8.17.11.9745 I've been using have been working fine since I updated them 13 April 2010.</p><p>I've run a full file scan twice and even redownloaded the Everquest2.exe client</p><p>This is the error I get in the event viewer:</p><p> Log Name:      ApplicationSource:        Application ErrorDate:          5/6/2010 6:08:39 PMEvent ID:      1000Task Category: (100)Description:</p><p>Faulting application EverQuest2.exe, version 1.0.0.1, time stamp 0x4bdf261d, faulting module nvd3dum.dll, version 8.17.11.9745, time stamp 0x4bb7dd53, exception code 0xc0000005, fault offset 0x0027fc52, process id 0xa68, application start time 0x01caed70e1fa2e70. </p>

[Wingrider01]

<p><cite>Nyfe@Butcherblock wrote:</cite></p><blockquote><p>Been having a problem with Everquest2.exe client crashing immediately before any character fully logs into a zone (or the character select screen) everytime I shut EQ down for a while and then try starting it up again right after (or a few hours later).  This has been happening since the 27 April update.</p><p>I'm running Vista 64 Ultimate SP 1. The NVidia driver ver 8.17.11.9745 I've been using have been working fine since I updated them 13 April 2010.</p><p>I've run a full file scan twice and even redownloaded the Everquest2.exe client</p><p>This is the error I get in the event viewer:</p><p> Log Name:      ApplicationSource:        Application ErrorDate:          5/6/2010 6:08:39 PMEvent ID:      1000Task Category: (100)Description:</p><p>Faulting application EverQuest2.exe, version 1.0.0.1, time stamp 0x4bdf261d, faulting module nvd3dum.dll, version 8.17.11.9745, time stamp 0x4bb7dd53, exception code 0xc0000005, fault offset 0x0027fc52, process id 0xa68, application start time 0x01caed70e1fa2e70. </p></blockquote><p>c0000005 is a driver issue, it can be corrupted, try completely uninstalling the current driver, run a driver cleaner and installaing a fresh download of the driver</p>

[Jrel]

<p>Thank you for the help, but I haven't had any issues with LOTRO, Dragon Age, WoW or Torchlight. Why will reinstalling the video driver (again by the way) fix my Everquest 2 issue?</p>

[Wingrider01]

<p><cite>Nyfe@Butcherblock wrote:</cite></p><blockquote><p>Thank you for the help, but I haven't had any issues with LOTRO, Dragon Age, WoW or Torchlight. Why will reinstalling the video driver (again by the way) fix my Everquest 2 issue?</p></blockquote><p>Use the driver you mention, play eq2, wow, and STO, no c5 crash errors, since the crash is pointing to a nvidia module it is logical that the error is in the driver, given the graphic capabilities of WOW and it can run on a TRS-80, it does nothing to push the various capabilities of the card and driver like EQ2 does.</p><p>Other possiblities for that particualr crash are</p><p>- faulty ram</p><p>- a virus</p><p>- a root kit</p><p>- a damaged registry</p><p>without any more details on the systems the most logical and easiest test is to completely remove  driver and clean the registry then reinstall from a fresh copy. The audio driver would be the next choice, this would only be true if you are runnig a Nvidia chipset mother board.</p>

[Jrel]

<p>I was fairly certain it wasn't a driver problem because no one else was having it.  Faulty ram? possibly.  Virus? Checked but No. Rootkit? Checked but No.  Damaged Registry? No.</p><p>I found my solution by accident earlier today.  I have a habit of leaving ACT open for days at a time.  For some reason, after about 5 days or so of leaving ACT on, it starts causing the nvd3dum.dll issue with the Everquest2.exe program.  Just closing ACT allows EQ2 to run again without getting this error.</p>

[Ldarax]

<p>ACT is a memmory hog since it seem to keep all currently used Logfiles in memmory.</p><p>I have seen mine take up to almost 1GB mem.</p>

[Jrel]

<p>For current logfiles, it shouldn't be a memory hog. I've got ACT set to split mine at 30 MBs. I've had it open two days and it is sitting at 34 MBs in Task Manager.</p><p>Since I like to open up a bunch of old zones for comparison from time to time, and forget to clear them, I can see how it would take more memory then.</p>

[Jrel]

<p>Guess I spoke too soon. I'm still having this issue.  The game crashes right before the mini-screen says "Adding character to zone" and "Lloading resources", and the Welcome to Everquest II window.</p><p>I've bugged it to Mozilla and also to Nvidia. </p><p>Would a Dev here like me to submit a stack trace log from Everquest2.exe using Windbg?  I'm familiar with using Windbg.</p>

[Wingrider01]

<p><cite>Nyfe@Butcherblock wrote:</cite></p><blockquote><p>Guess I spoke too soon. I'm still having this issue.  The game crashes right before the mini-screen says "Adding character to zone" and "Lloading resources", and the Welcome to Everquest II window.</p><p>I've bugged it to Mozilla and also to Nvidia. </p><p>Would a Dev here like me to submit a stack trace log from Everquest2.exe using Windbg?  I'm familiar with using Windbg.</p></blockquote><p>257.21 is out, and stable on Windows 7 64 bit and Vista.</p><p>You might want to consider doing yourself a large favor and upgrade to Windows 7 64 bit, it is light years ahead of vista and a lot more stable, faster and forgiving</p>

[Jrel]

<p>Thanks for the info. My video driver was already upgraded before my last post. </p><p>I'm going to upgrade to Win 7 after SP 1 is out. I've got a ton of music creation software, and ensuring compatibility, and re-authorizing all of it, plus VSTs, will be a meticulous process (I've had experience with upgrading this machine from Win XP to Vista).  I don't want to run the risk of the Win7 upgrade possibly failing on this machine unless I've got a good free week or two allotted.</p>