Game don't start and closes

[Bri]

Hello everyone, I have had a problem for 2 days.
When starting the launcher it takes a long time to download the game files and also to be able to enter my username and password
When the loading screen starts the game closes.
This happens to me on my PC with an RX 6600, but on my laptop it does not happen with an RTX 3050
Both have Windows 11 with the 24H2 update and I connect via WiFi on both
If I completely uninstall the game and reinstall it on the PC when starting it for the first time everything goes normally, but when I exit the game I can't get back in

 

[Zaszgul]

Have a look in your DDO directory for
dndclient_[number].log
and/or
dndclient64_[number].log

These log files may help determine the issue. Look at the most recent one.

 

[drakiz]

Guess same issue I posted on general, also started Tuesday morning, CET.

https://forums.ddo.com/index.php?threads/launcher-not-working-error-checking-jpg-files-in-different-logo-folders.15678/#post-193998

I would not rule out, some windows update, that some .dll files lost its compatibility with ddo?

File dndclient.exe crashes on ACCESSS_VIOLATION
error module "ucrtbase.dll" crash when 32bit( client selection) FileVersion : 10.0.19041.3636 (WinBuild.160101.0800)
error module "ndtdll.dll" crash when 64 bit (client selection)

But still, after a reboot, and repair/reinstall Ithink I can log on once, before it crashes
But i gave up after trying more.

Regards
Drakiz

 

[Bri]

Hello, thanks for the advice.
The log file tells me the following:

000000000.000: Initializing display with title 'Dungeons and Dragons Online'...
000000000.000: Device_WIN32::Init: called.
000000000.000: Device_WIN32::InitTimer resolution successfully set to [1].
000000000.000: Device_WIN32::InitDEVICE| Detected operating system: Windows 7
000000000.000: DEVICE| Starting up the graphics engine...
000000000.000: Initializing the smartbox...
000000000.000: Initializing the user interface...
000000000.000: Client ready
000000006.954: ----CRASH REPORT START----
000000006.954: Program fault: ACCESS_VIOLATION (0xc0000005) trying to write to 0x0000001400000025
000000006.954: Detailed report:

Current local time: Wed Nov 27 09:52:38 2024


Version Report generated by CoreVersion: 2.0.143.1 (0x0200008F):
Language: English (United States)
CompanyName : Standing Stone Games, LLC.
FileDescription:
FileVersion: 7000.0052.8794.4004
InternalName: dndclient64
LegalCopyright: Copyright © 2016-2024 Standing Stone Games, LLC.
OriginalFilename: dndclient64.exe
ProductName: dndclient64 (WIN64)
ProductVersion: 7000.0052.8794.4004 dnd_live
Comments : compiled Sat Nov 16 00:36:51 2024 : RELEASE
TurbineBuildVersion: 7000.0052.8794.4004.RELEASE
TurbineType: Admin External

The only thing I have changed has been in the launcher to choose the video card from automatic to the one that detects RX 6600 and put it back to automatic, but the same thing keeps happening to me, the game closes in both cases

 

[Anurakh]

Many people are having problems getting into the game since Sunday. Others started having problems on Monday.

It's not your fault. The problem is on SSG's end.

 

[Anurakh]

More threads about this:

https://forums.ddo.com/index.php?threads/connections-issues-all-cet-morning.15538/post-194335

https://forums.ddo.com/index.php?threads/launcher-not-working-error-checking-jpg-files-in-different-logo-folders.15678/#post-194202

My partner and several of my guildies have the same problem than you. I can log in normally, although the client takes a little longer than usual, but not much. Some of my friends can log in, other have the same problem.

It is a fairly widespread problem, but not universal. It does not affect all clients.

 

[Zaszgul]

Hello, thanks for the advice.
The log file tells me the following:

000000000.000: Initializing display with title 'Dungeons and Dragons Online'...
000000000.000: Device_WIN32::Init: called.
000000000.000: Device_WIN32::InitTimer resolution successfully set to [1].
000000000.000: Device_WIN32::InitDEVICE| Detected operating system: Windows 7
000000000.000: DEVICE| Starting up the graphics engine...
000000000.000: Initializing the smartbox...
000000000.000: Initializing the user interface...
000000000.000: Client ready
000000006.954: ----CRASH REPORT START----
000000006.954: Program fault: ACCESS_VIOLATION (0xc0000005) trying to write to 0x0000001400000025
000000006.954: Detailed report:

Current local time: Wed Nov 27 09:52:38 2024


Version Report generated by CoreVersion: 2.0.143.1 (0x0200008F):
Language: English (United States)
CompanyName : Standing Stone Games, LLC.
FileDescription:
FileVersion: 7000.0052.8794.4004
InternalName: dndclient64
LegalCopyright: Copyright © 2016-2024 Standing Stone Games, LLC.
OriginalFilename: dndclient64.exe
ProductName: dndclient64 (WIN64)
ProductVersion: 7000.0052.8794.4004 dnd_live
Comments : compiled Sat Nov 16 00:36:51 2024 : RELEASE
TurbineBuildVersion: 7000.0052.8794.4004.RELEASE
TurbineType: Admin External

The only thing I have changed has been in the launcher to choose the video card from automatic to the one that detects RX 6600 and put it back to automatic, but the same thing keeps happening to me, the game closes in both cases

Is there more to the log? It should terminate with the line
" ----CRASH REPORT END----"

 

[Bri]

Hello
Thanks for your answers
It seems that the problem has been solved with this maintenance since I have been able to enter the game without problems.
Greetings.
Bri

 

[Cordovan]

We are actively investigating this issue. Once we know more we will let you know.

 

[Axcarth]

We are actively investigating this issue. Once we know more we will let you know.

Thank you, Cordovan, for those words. I'll be looking forward to any updates!

 

[Deathbringer]

Same issue since Monday night... Hope SSG fix this soon

 

[Asterphen]

Maybe it is like air conditioning for the city during the heat of summer.... rolling blackouts. I could log in last night, not this morning. Deathbringer has nothing since monday night, and Bri is back on. I shall monitor when deathbringer gets back on and start my two day timer from then. Irregardless, my raids will be off timer by then.

 

[Mindos]

We are actively investigating this issue. Once we know more we will let you know.

I hope you get it fixed withing 24 hours. Black friday sales are up.
I hope you get if fixed within 30 days. Don't want to fall behind on VIP rewards.

So many people are going to miss out on double bonus sales, timed progressions, good will....

Why does a very slow launcher that DOES download pictures sometimes have this problem...
When a launcher with -skiprawdownload -nosplash DOES NOT have this problem?

I mean, what can slowly or error-ly downloading a picture cause a hard crash to desktop for the client??? So bad that you can't just go back to the skip option launcher? How in the world does a picture error ruin the client FOREVER?

It doesn't matter what launcher you use either, official or unofficial, doesn't matter what user account windows, what game account, what 32 or 64 client, etc

So something besides a picture gets corrupted? What file? Where is it? Who designed this thing so that good gets overwritten with bad?

Copying the contents of the backup folder into the main folder doesn't work.

 

[Bri]

Hello
Thanks for your answers
It seems that the problem has been solved with this maintenance since I have been able to enter the game without problems.
Greetings.
Bri

I'm quoting myself because it happened to me again, I thought it had been resolved but it keeps happening.
I hope it gets resolved soon for everyone
Regards.
Bri.

 

[Bri]

Is there more to the log? It should terminate with the line
" ----CRASH REPORT END----"

There are a few more lines but from the OS:

Version information for error module C:\WINDOWS\System32\ucrtbase.dll:
Language: English (United States)
CompanyName: Microsoft Corporation
FileDescription : Microsoft® C Runtime Library
FileVersion: 10.0.26100.1882 (WinBuild.160101.0800)
InternalName: ucrtbase.dll
LegalCopyright: © Microsoft Corporation. All rights reserved.
OriginalFilename: ucrtbase.dll
ProductName: Microsoft® Windows® Operating System
ProductVersion: 10.0.26100.1882



000000007.274: ----CRASH REPORT END----

 

[J1NG]

Try (re)installing the Visual C++ drivers from Microsoft. See if that helps.

J1NG

:: edit ::
Try grabbing the latest distributable of Visual C++ and install from it after removing any existing installation on your system first. Get the version appropriate to your system (x86 or x64 version depending if 32bit or 64bit OS+CPU)

https://learn.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-170#latest-microsoft-visual-c-redistributable-version

 

[Zaszgul]

As J1NG stated, uninstalling and reinstalling MS Visual C++ 2015-2022 is what fixed my problem, which was similar to yours (my crash log was referencing MSVCP140.dll, but they are both a part of Visual C++).

 

[Asterphen]

As J1NG stated, uninstalling and reinstalling MS Visual C++ 2015-2022 is what fixed my problem, which was similar to yours (my crash log was referencing MSVCP140.dll, but they are both a part of Visual C++).

This fixed my issue as well. I can use the 644 bit client again. Thanks j1ng