First off, kudoz to Siva! I have a more clear picture now that I can better read through the log. I definitely have a bit of reworking to do, though I do not have the luxury of always accessing objects in the same order all the time. But that's a story for another time. I was hoping I could get a lamen's explanation for deadlocks that read:
"Transaction (Process ID ###) was deadlocked on lock | communication buffer resources with another process and has been chosen as the deadlock victim. Rerun the transaction.."
It then prints out node after node of what appears to be chinese. From MSDN I gathered that it's attempting to reroute the Query somehow. Is this worse than the regular deadlocks discussed in the article? And what the heck is it trying to do?