Game Crashes after launch

[E.Avendale]

Was playing without difficulty 2 days ago. Came back to it today. Enter in user and pword, select server, then almost immediately after it goes full-screen, it crashes and I get a windows box telling me it "needs to close". Sometimes it crashes before it switches to full-screen mode.

From the DDO file dndclient.log:

000000002.206: ----CRASH REPORT START----
000000002.206: Program fault: ACCESS_VIOLATION (0xc0000005) trying to read from 0x06F8E0F7
000000002.206: Detailed report:

Current local time: Thu Oct 01 01:13:15 2009


Version Report generated by CoreVersion : 2.0.99 (0x02000063):
Language: English (United States)
CompanyName : Turbine, Inc.
FileDescription :
FileVersion : 01.09.04.8045
InternalName : dndclient
LegalCopyright : Copyright © 1997-2009 Turbine, Inc.
OriginalFilename : dndclient.exe
ProductName : dndclient
ProductVersion : 01.09.04.8045 unlimited_patch1
Comments : compiled Tue Sep 15 05:28:07 2009 : retail
TurbineBuildVersion : 01.09.04.8045.retail
TurbineType : Player External

Version information for error module C:\Program Files\Turbine\Dungeons and Dragons Online - Eberron Unlimited\binkw32.dll:



000000002.206: ----CRASH REPORT END----


Any suggestions as to what may be causing this access violation?

[E.Avendale]

Tried to load again today. After it dl'ed the patched stuff, I got a 201 error. So I'm reinstalling now.

No idea whether I'll be able to get in, though, if reinstalling doesn't fix the access violation.

Edit: Btw, I've only found one place with anything like "verify and repair", and all it does is allow you to reset the video options to default. Do you only get the repair option when it's fully downloaded?

[E.Avendale]

After re-downloading and re-installing: Got it to work just fine after it downloaded enough to play. Then I let the downloader go until the full game was installed, and it still plays just fine. I'm thinking the intro movie it was trying to play hadn't downloaded completely/properly yet, since the previous install wasn't done, and so it was crashing due to that. Not sure why the update would have caused a 201, but I don't know that it's too important since it's working now.

So, no savvy technical info to help people who have already tried un- and re-installing, but for those who haven't here's just one more testimonial to let you know it might actually work. Good luck.