Program crashes immediately on character load

Gigabyte 970A-D3P Mobo old and now newest BIOS
AMD FX8320 CPU
tried two HD Radeon HD 7770 and HD 6650 graphics cards
Multiple AMD radeon crimson and adrenaline drivers
Windows 10 64bit pro
I know old hardware, but new OS load
I have now 4 characters I can play them fine up to around level 8 to 5 and now the program will crash after loading the environment
I have updated the patcher, disabled the antivirus, reinstalled the game, I had some newer C++ runtime and .NET stuff I uninstalled and did:
https://forum.playphoenix.online/viewtopic.php?f=26&t=5468
All the stuff in that post.
I am sure that I can start another character and it will play fine but after a few levels it gets stuck When it sticks:

I can get the character list screen to load and I can click on the toon
when I launch the game it loads, I briefly see the enviornment then crash.
I do notice that the three green network dots are all red, but I have done a ping and tracert on playphoenix.online (or what ever it was in the post) and the networking looks ok ping times low 100ms and tracert completes.

Thank you so much for making this game, wow what memories. Any help is appreciated. I will post more as I troubleshoot.

Sat 2 Mar 2019 7:51 PM by robinls

Yes allowed me to create a fifth character, got to level 4 before the first crash.
I found this in the debug log:
Got new NiD3DRender: 24ef840
[10285916] OS Version: Windows 6.2
[10285917] Adapter: [AMD Radeon HD 6670]
[10285917] Driver Version 8.17.10.1404
[10285917] WHQL Certified: No
[10285917] VendorID: 1002 (6758)
[10286449] Video Memory: 4095mb
[10286994] Version Loaded: 1.124 (b1385)
[10286995] Client Version: [live1385] - 06:05PM on Nov.16.2017
[10286995] Physical System Memory Approx: 4095MB
[10287005] Housing Installed = 1
[10287008] Frontiers Installed = 1
[10287008] Client Type: Catacombs
Server: 195.201.199.11
Port: 10300 (42)
Charname:
Realm: 0
Sound system: on.
Time to load sounds: 1187
... lots between that and the final error
[10502211] NDL World Initialized.
Error Loading Animation Template #2359 (anims\giant_attack1.kfa)!

There is also a critical log and it has loads of errors but the time stamp is before my last crash...

Sat 2 Mar 2019 8:14 PM by Pedro

I have a very similar build (without the dual cards, just a single AMD HD) and I don't experience this.

Seems like you already took all the known approaches from the third party and network point of view. Some of the things that caused what you described in the past for me (past as in back in live):

- Wrong/invalid UI
- Playing behind a router that may have rules in place to block gaming or high usage from one machine. In this case unplug the router and plug your machine directly to the internet modem.
- Graphic settings too high or a custom setting (anti aliasing, etc, that may have no existed way back then and the game is not coded to handle it well) do cause the game to freeze and crash when you move around or get too many spell effects happening.

I usually also have another PC or laptop with a different OS version in case I need to test application incompatibilities, not saying that DAoC (a 20 year old program) is not compatible with Win10, but maybe something installed in it.

Sat 2 Mar 2019 8:16 PM by Pedro

Ps I posted before you added the error log.

Have you tried changing realms see if it repeats the same error?

Sat 2 Mar 2019 8:18 PM by Pedro

Also if you move the offending file (Dark Age of Camelot\anims) to another location and re-launch the patcher to have it re-download it, any improvement?

Sat 2 Mar 2019 8:23 PM by robinls

Good points. No custom anything, and I did the rename the .dat file to reset the graphics. No custom UI.
To clear up, I only have one graphic card in at a time, I started with the HD 7770 and thought it or its drivers was the problem but removed all drivers and tried another card and different set of drivers with same behavior.

Hopefully this doesn't limit my support from some smart hib/mid,

but I only ever play albion so I will try the other realms now.

Sun 3 Mar 2019 7:47 PM by robinls

A second reinstall seems to have made the difference. Not sure what the root problem is. The first reinstall did not do it. Anyway this thread can be closed, not sure how that is done.