NVIDIA Driver Issue

Jrel · 05-06-2010, 08:30 PM

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.

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.

I've run a full file scan twice and even redownloaded the Everquest2.exe client

This is the error I get in the event viewer:

Log Name: ApplicationSource: Application ErrorDate: 5/6/2010 6:08:39 PMEvent ID: 1000Task Category: (100)Description:

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.

Wingrider01 · 05-07-2010, 07:43 AM

Nyfe@Butcherblock wrote:

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.
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.
I've run a full file scan twice and even redownloaded the Everquest2.exe client
This is the error I get in the event viewer:
Log Name: ApplicationSource: Application ErrorDate: 5/6/2010 6:08:39 PMEvent ID: 1000Task Category: (100)Description:
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.

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

Jrel · 05-08-2010, 11:40 AM

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?

Wingrider01 · 05-08-2010, 03:38 PM

Nyfe@Butcherblock wrote:

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?

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.

Other possiblities for that particualr crash are

- faulty ram

- a virus

- a root kit

- a damaged registry

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.

Jrel · 06-03-2010, 10:47 AM

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.

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.

Ldarax · 06-03-2010, 12:47 PM

ACT is a memmory hog since it seem to keep all currently used Logfiles in memmory.

I have seen mine take up to almost 1GB mem.

Jrel · 06-04-2010, 05:35 PM

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.

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.

Jrel · 06-28-2010, 09:56 AM

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.

I've bugged it to Mozilla and also to Nvidia.

Would a Dev here like me to submit a stack trace log from Everquest2.exe using Windbg? I'm familiar with using Windbg.

Wingrider01 · 06-28-2010, 12:56 PM

Nyfe@Butcherblock wrote:

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.
I've bugged it to Mozilla and also to Nvidia.
Would a Dev here like me to submit a stack trace log from Everquest2.exe using Windbg? I'm familiar with using Windbg.

257.21 is out, and stable on Windows 7 64 bit and Vista.

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

Jrel · 06-28-2010, 01:25 PM

Thanks for the info. My video driver was already upgraded before my last post.

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.

05-07-2010, 07:43 AM	#2
Wingrider01 Loremaster Join Date: Nov 2004 Posts: 5,999	Nyfe@Butcherblock wrote: 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. 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. I've run a full file scan twice and even redownloaded the Everquest2.exe client This is the error I get in the event viewer: Log Name: ApplicationSource: Application ErrorDate: 5/6/2010 6:08:39 PMEvent ID: 1000Task Category: (100)Description: 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. 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 __________________ Fixing computer issues, one SOC7 at a time. Yes Jim, the user has experienced the dreaded PICNIC error

05-08-2010, 03:38 PM	#4
Wingrider01 Loremaster Join Date: Nov 2004 Posts: 5,999	Nyfe@Butcherblock wrote: 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? 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. Other possiblities for that particualr crash are - faulty ram - a virus - a root kit - a damaged registry 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. __________________ Fixing computer issues, one SOC7 at a time. Yes Jim, the user has experienced the dreaded PICNIC error

06-28-2010, 12:56 PM	#9
Wingrider01 Loremaster Join Date: Nov 2004 Posts: 5,999	Nyfe@Butcherblock wrote: 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. I've bugged it to Mozilla and also to Nvidia. Would a Dev here like me to submit a stack trace log from Everquest2.exe using Windbg? I'm familiar with using Windbg. 257.21 is out, and stable on Windows 7 64 bit and Vista. 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 __________________ Fixing computer issues, one SOC7 at a time. Yes Jim, the user has experienced the dreaded PICNIC error

05-06-2010, 08:30 PM	#1
Jrel Server: Butcherblock Guild: Blackstar Rising Rank: Senior Member Loremaster Join Date: Jul 2008 Posts: 452	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. 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. I've run a full file scan twice and even redownloaded the Everquest2.exe client This is the error I get in the event viewer: Log Name: ApplicationSource: Application ErrorDate: 5/6/2010 6:08:39 PMEvent ID: 1000Task Category: (100)Description: 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.

05-08-2010, 11:40 AM	#3
Jrel Server: Butcherblock Guild: Blackstar Rising Rank: Senior Member Loremaster Join Date: Jul 2008 Posts: 452	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?

06-03-2010, 10:47 AM	#5
Jrel Server: Butcherblock Guild: Blackstar Rising Rank: Senior Member Loremaster Join Date: Jul 2008 Posts: 452	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. 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.

06-03-2010, 12:47 PM	#6
Ldarax Loremaster Join Date: Dec 2004 Posts: 90	ACT is a memmory hog since it seem to keep all currently used Logfiles in memmory. I have seen mine take up to almost 1GB mem.

06-04-2010, 05:35 PM	#7
Jrel Server: Butcherblock Guild: Blackstar Rising Rank: Senior Member Loremaster Join Date: Jul 2008 Posts: 452	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. 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.

06-28-2010, 09:56 AM	#8
Jrel Server: Butcherblock Guild: Blackstar Rising Rank: Senior Member Loremaster Join Date: Jul 2008 Posts: 452	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. I've bugged it to Mozilla and also to Nvidia. Would a Dev here like me to submit a stack trace log from Everquest2.exe using Windbg? I'm familiar with using Windbg.

06-28-2010, 01:25 PM	#10
Jrel Server: Butcherblock Guild: Blackstar Rising Rank: Senior Member Loremaster Join Date: Jul 2008 Posts: 452	Thanks for the info. My video driver was already upgraded before my last post. 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.