Client Crashes Before Character Screen

[jalont]

Still nothing for the ticket. I suppose we wait til monday when they fix it with the "scheduled maintenance" without a single word to the community

I hope it is fixed on Monday. I've never had technical issues with DDO before. Is this common, stealth fixes without even an acknowledgement that they are aware the problem exists? I hope for the best, but this seems to be a specific problem targeting only certain people across their games. I wonder how they can find the conflict without actually talking to anyone who is faced with it? Perhaps they'll simply revert what they did during the last maintenance.

[Lucarr]

They do stealth fixes/changes all the time. Half the time it seems their "scheduled maintenance" is just a way for them to do the stealth updates without having to say what they did. I'm almost positive they know exactly what caused the problem and they just don't want to admit it. I just hope they extend mabar as a good will measure for those of us who have missed it due to the problem

[Lucarr]

Ok so the maintenance is come and gone and I still cant access so it apparently hasnt been fixed whatever it is. Still no tech support here, still no response to the ticket. I guess the amount of us having this problem isnt high enough for them to really care about it that much. Ill give it til u16 i suppose and if its not fixed by then or at least some sort of response for tech support I think I might just quit this game for good. There's been devs posting elsewhere on the forums so I know they're reading the posts. Again even just an acknowledgement of the problem and I'd be happy but we don't even get that...

[donfilibuster]

Since the issue is widespread everyone having this crashing since mabar was loaded please post here.
There's usually a tech dev that checks this subforum often, should read this and comment.

That'd be for the widespread part, it seems there's a fair amount of extra lag on top of the usual.
No one i know is surprised, since Mabar has done it in the past years.
Note that if the issue is related to mabar will only go away after the event.


Aside of that, help with the actual crashes may still vary from computer to computer, as is the usual.
Crashes are normally dealt by tech support on case by case, make sure you all sent your dxdiags in the ticket.

Meanwhile you may want to troubleshoot on your own to see if the game can cope with the extra lag.
Try dx9 as already noted, also try turn down the graphics, then the usual step by step from the bottom down to find where it chokes.
Also check for regular causes of crashing to rule out common problems, like a full scandisk and check memory for damages.
(video cards can also fry, players have had it, but don't know how to check that)

[Lucarr]

If ya look at my 1st post you see that I dont even make it to the game. The client crashing is at the point where the character selection screen would show up. The client goes through the full loading bar and then crashes with a windows error message saying "the dndclient.exe has stopped working." Ive already tried uninstall, reinstall. Tried resetting graphics through the repair menu in the launcher as I cant even get into the game to change the graphics manually. I've posted my dxdiag here and in the ticket. Attached with the initial submission of the ticket and the requested reply after sending said ticket so it exists in 3 places now all easily available to tech support.

I do not believe this to be related to mabar itself due to the fact it worked fine the night before the last maintenance session before the one today. I've also experience near zero lag leading up to this current problem. I cant say whether or not I would lag now because I cant log in to see so thats an unrelated matter to my current problem.

[Marcus-Hawkeye]

updated drivers and such?

Try using a different profile on your machine if possible.

[Lucarr]

Ya everythings updated fully and all and theres only 1 profile on my comp as I'm the only one to use it. And as I said earlier, the game was working fine up to about 2am the night before/of the maintenance. However you want to view it.

[jalont]

Support finally got back to me, but nothing has helped. I did some more poking around and found this, which I'm 99.9 percent sure is tied to the error: 5884:6020:128353239:ERROR:chrome_url_request_conte xt.cc(94)] Cannot use V8 Proxy resolver in single process mode.

I did some searching on this, but it's all above my head. Perhaps someone smarter than me? This was in a hidden chromium folder and was created on the date of the store maintainance (the day our problems started) and it modifies after a DDO load attempt. Obviously Awesomium is attempting to call up Chrome, but there's a problem somewhere.

[donfilibuster]

Ok you are correct, not getting to the selection screen makes the issue not related to the other issues that occur after you pick a character.

Unfortunately, being a crash issue the tech devs will look first at your computers and that'd take time.
Since your reports are in the queue, if they find it be widespread there's a good chance it get fixed.

Do you have a ddoclient.log? the crashes should dump some data in here.

For the suspicious chrome folders, make sure the firewall and antivirus are picking up that the files have changed.
You should still scan your disk and memory, since those are common causes of crashing.
(playing other games is not enough, each game loads in a different way and thus not prompt a fault)

[jalont]

Ok you are correct, not getting to the selection screen makes the issue not related to the other issues that occur after you pick a character.

Unfortunately, being a crash issue the tech devs will look first at your computers and that'd take time.
Since your reports are in the queue, if they find it be widespread there's a good chance it get fixed.

Do you have a ddoclient.log? the crashes should dump some data in here.

For the suspicious chrome folders, make sure the firewall and antivirus are picking up that the files have changed.
You should still scan your disk and memory, since those are common causes of crashing.
(playing other games is not enough, each game loads in a different way and thus not prompt a fault)

Checked the launcher logs, and I'm getting that same error, so it is confirmed as the problem.

Launched Game Process ID (PID): 4256 10/29/2012 11:57:41 PM
[4256] STDERR: [4256:640:1482914:ERROR:chrome_url_request_context. cc(94)] Cannot use V8 Proxy resolver in single process mode. 10/29/2012 11:57:58 PM
[4256] STDERR: 10/29/2012 11:57:58 PM
The running game client has been terminated. 10/29/2012 11:58:02 PM
Transition to phase: AuthenticationControl 10/29/2012 11:58:02 PM
The last played world is Argonnessen 10/29/2012 11:58:02 PM
GetLauncherConfig from: "http://gls.ddo.com/launcher/ddo/dndlauncher.server.config.xml" 10/29/2012 11:58:30 PM
Launcher shutting down 10/30/2012 12:05:27 AM
Launcher execution ends: 10/30/2012 12:05:27 AM


I don't use a Proxy (perhaps I can change the proxy setting in settings, but to what? I don't know anything about proxies, I just know there's a setting for it in there. I have a feeling I'm going to have to do a clean install of Windows. Pretty sure there's a registry conflict that will be impossible to find. I do hope they get this figured out though.


ETA: Apparently the logs contain each server's current server population, so... that was exciting.

[donfilibuster]

[4256] STDERR: [4256:640:1482914:ERROR:chrome_url_request_context. cc(94)] Cannot use V8 Proxy resolver in single process mode. 10/29/2012 11:57:58 PM

Like you already noted, a google search on this points to awesomium so it's a good lead. (appears it isn't about using a proxy yourself)
Skimming a little i saw that maybe the folders may have the wrong permissions, u may want to check that.


OP's problem may be different tho, has to look at the log to see what it says.

[Lucarr]

As best I can tell my prob is caused by the same thing. When I look at more details on the windows crash message it says failed component awesomium.dll. Ive searched every turbine folder I could find and couldn't find the log though. Kinda feel like a idiot on that part considering I built my rig from scratch and what not lol. Any help finding that would be appreciated. Can confirm it is that same prob then

[jalont]

As best I can tell my prob is caused by the same thing. When I look at more details on the windows crash message it says failed component awesomium.dll. Ive searched every turbine folder I could find and couldn't find the log though. Kinda feel like a idiot on that part considering I built my rig from scratch and what not lol. Any help finding that would be appreciated. Can confirm it is that same prob then

In Windows 7, its in the hidden AppData folder C:\Users\Me\AppData\Local\Turbine

ETA: Also, looking through the Awesomium forums for this specific error, it seems that only Windows 7 uses the awesomium.dll file. For XP, it uses the AwesomiumProcess file instead. I don't have time at the moment, but perhaps try to reinstall DDO as Windows XP then change the compatibility for the program to Windows XP. No idea if that's possible or if it'll work, but that's going to be my next attempt.

[Lucarr]

I'm running vista and its doing it to me. The problem details from the crash are:
Problem signature:
Problem Event Name: APPCRASH
Application Name: dndclient.exe
Application Version: 1.20.2.8017
Application Timestamp: 508a05dc
Fault Module Name: Awesomium.dll
Fault Module Version: 1.6.3.0
Fault Module Timestamp: 4eb5e298
Exception Code: c0000005
Exception Offset: 00a44e22
OS Version: 6.0.6002.2.2.0.768.3
Locale ID: 1033
Additional Information 1: 8d37
Additional Information 2: 4f06c3204dda1ad54435c343c1111079
Additional Information 3: ca1e
Additional Information 4: 6b9e297591267abc549e427371bf043d

Clearly states awesomium.dll as the fault.

Checked logs and have pretty much the same this at jalont except with khyber as the server. Also found the chromium folder and have the same awesomium log:
[3760:2080:466723:ERROR:chrome_url_request_context. cc(94)] Cannot use V8 Proxy resolver in single process mode.

Also tech support finally got back to me and said to try a clean reboot. Did this and it didnt help so as best as I understand that means its not my computer. Replied to them saying it didn't work and am waiting for response back now.

[jalont]

I'm running vista and its doing it to me. The problem details from the crash are:
Problem signature:
Problem Event Name: APPCRASH
Application Name: dndclient.exe
Application Version: 1.20.2.8017
Application Timestamp: 508a05dc
Fault Module Name: Awesomium.dll
Fault Module Version: 1.6.3.0
Fault Module Timestamp: 4eb5e298
Exception Code: c0000005
Exception Offset: 00a44e22
OS Version: 6.0.6002.2.2.0.768.3
Locale ID: 1033
Additional Information 1: 8d37
Additional Information 2: 4f06c3204dda1ad54435c343c1111079
Additional Information 3: ca1e
Additional Information 4: 6b9e297591267abc549e427371bf043d

Clearly states awesomium.dll as the fault.

Checked logs and have pretty much the same this at jalont except with khyber as the server. Also found the chromium folder and have the same awesomium log:
[3760:2080:466723:ERROR:chrome_url_request_context. cc(94)] Cannot use V8 Proxy resolver in single process mode.

Also tech support finally got back to me and said to try a clean reboot. Did this and it didnt help so as best as I understand that means its not my computer. Replied to them saying it didn't work and am waiting for response back now.

There's some type of conflict, probably in the registry, but I don't know how to find it. Oddly, Eve Online uses Awesomium as well, and it's working fine for me, so this is something specific to the way Turbine is using the file and something specific to what they did during the 24th maintenance. I will wait for support to get back to me, but I feel that there are only three options to fix this. 1. Find the conflict in regedit and delete it. It's probably a toolbar/bloatware/malware/adware entry. I've gone through and deleted everything I felt comfortable deleting that I could find, but apparently haven't found it yet. Perhaps you'll have better luck. Most people that managed to fix it via this route deleted all instances of google, chrome and toolbars (especially search for incredbar or incredibar).

2. Reinstall Windows

3. The devs get involved and either revert what they did on the 24th or use the information to come up with some sort of solution. At this point, I'm not sure the devs are even aware of this problem.

[Coffee]

I have two machines and play with son in the evenings. One machine works, one machine does not.

I have tried the same fixes described above to no effect.

[Lucarr]

Ive tried just about everything I can think of with no progress. Ive been working with tech support trying various fixes. Attempt to run the client under a clean boot with everything but microsoft devices disabled, Uninstalling avg antivirus from computer( apparently some sort of compatibility issue there with some users), look for and delete a program called sendori if it exists on comp. Nothing has worked so far. I also noticed my awesomium process was running xp service pack2 by default. Tried turning that off and fail. Turned it back on and made the launcher run xp compatibility and still fail so I'm out of ideas now. Waiting for another reply from tech

[jalont]

Just wanted to let everyone know that I solved the problem... by reinstalling Windows. Luckily, I only use this computer for games, so I simply threw my Steam and gaming folders on a partition and reinstalled from another partition. This makes me think that this problem is caused by some registry conflict, but there's no way to be sure.

[Coffee]

Reinstalling windows?!

I can't believe that it has been 5 days and no response or solution to this by DDO. This should be critical enough to at least respond and give a timeline for affected players.

[donfilibuster]

I can't believe that it has been 5 days and no response or solution to this by DDO. This should be critical enough to at least respond and give a timeline for affected players.

The situation right now is kind of special, with delays and lots of bugs to keep them busy like the "character already in game".
I wouldn't count on getting fast replies on tickets while this lasts.