Client crash after char selection, tried all fixes

Started 5 Jun 2020
by Timtheenchanter
in Support Center
So here's the skinny on what happens and what I've attempted to amend the situation. I've attempted this on two separate laptops...

Phoenix launcher (as admin) loads. Username and PW is accepted. Client launches. I get a popup stating:

"C:\ProgramFiles (x86)\Electronics Arts\Dark Age of Camelot\Miles\6.5\msseax.m3d is either not designed to run on Windows or it contains an error. Try installing the program again using the original installation media or contact your system administaor or the software vendor for support. Error status 0xc000012f."

However, I can click okay and the client still loads to the realm/character selection screen. ( note, I have gone in and removed this file and the popup disappears, but the end state remains the same with or without this file in its specified folder).

I select or create a character, click play, and the game loading screen appears, makes it to 25% every time, and force shuts downs back out to windows. The client closes on its own.

So, what I've tried? Everything from every suggestion here. I've:
-Installed new
-Patched original client in full.
-Run PhoenixFixer multiple times from admin, first time go for downpatching to 1.125d, but I've still gone over and done it multiple times in a row for good measure.
-Download and run DotNetFx35 & C++ vc_redist.x86 (one computer needed this, the other did not)
-Verified all Windows updates are current
-Added exclusions in firewall and security, both the entire DAoC folder and individual files.
-Deleted and tried everything new, went through this list again. and nothing.

The game loading screen only ever makes it to 25% every time and freezes, force shuts down, and puts me back out to windows. Any help?
Mon 8 Jun 2020 7:07 PM by Timtheenchanter
Fix found:

If anyone has read this and experienced the same - client crash after hitting play from character screen, loading screen only making it 25%... just delete it all and try again. Turns out third time is the charm. I suppose the only logical explanation is perhaps poor internet and a file not loading properly during the client patch to full live version. I guess that's what I get trying to download and play on deployment. Needless to say, it's all working fine now.

Hopefully the board admins will add this as a possible error and fix solution for those that might experience the same.

Cheers!

There are some who call me, Tim?
This topic is locked and you can't reply.

Return to Support Center or the latest topics