There could be a connection between the wide-spread buffering and your issue.
An application programmer could probably identify the code where the error is occuring, without ever running the program. However, they wouldn't be able to identify the corrupted database record that's causing the program to fail. They don't have direct database access. They use methods and functions, controlled by the DBA, to access database records. A DBA might run a database query to identify a corrupted record, but not a line of code. I get your point though. Cox should do something to identify the cause of the issue and then fix it.
Does Cox still have your current password? (You're far more trusting than I am).
What I was trying to get across is that you might be able to identify/eliminate a corrupted contact as the cause of your issue. Then, do the ELSE part of my post. Contact cox.help@cox.com using an email account from which you can receive a reply. (Too much time and effort has been wasted because you can't receive a reply with your existing email account). Ask them for your ticket number. That will show a ticket was created and you can reference it in future communication with Cox. Ask if the "Phone Tools Team" has identified the cause of the issue. It's been a month. It's time to escalate.