"Translator" process is hogging CPU, causing crashes - what is it?

Question

So in the past few weeks, my machine has seemed slower and slower each day. In the past week, my mouse will jump across my 2 screens erratically. I thought it was either the mouse or USB port so tried different configurations until it occurred to me that, on random days, after a random startup; all is well.
I popped open the Activity Monitor and now can confirm my problem. My machine works great when the process "Translator" behaves itself. Every time I get the erratic mouse, slow window response and (every time) an eventual freezing of my screen requiring forced restart - Translator is hogging all my CPU. If I sample it, my machine crashes to a freeze. It I get more info on it, I can see that Translator has to do with syncservices (why do so many problems on 10.5 have to do with syncservices?). I have tried Googling for more info on it, but there doesn't seem to be anything out there. If I force quit it (standard quit doesn't work), my system will hang.
Does anyone know what this is and how to fix my problem?
I know the standard next steps (create a new user account and migrate files sans ~/Library, re-install OS, etc.) but am afraid that the problem will resurface if ties to syncservices (I do use Mobileme to sync, have an iPhone and an iPod). I guess I'm looking for more info before proceeding with drastic and time intensive measures that may very well yield the same problem despite the effort.
Any help would be very much appreciated. It is worth noting that it took 5 full minutes for me to correct my spelling in this post due to the erratic mouse. Good times. I am off to restart - again.
"Translator" is process ID 1027 running under my user account.
Its at over 100% of my CPU
Its "Open Files and Ports" report is as follows:
/private/tmp
/System/Library/PrivateFrameworks/SyncLegacy.framework/Versions/A/Resources/Tran slator
/private/var/tmp/mds/messages/se_SecurityMessages
/System/Library/Frameworks/AddressBook.framework/Versions/A/Resources/ExchangeCo nduit.bundle/Contents/MacOS/ExchangeConduit
/usr/share/icu/icudt36b.dat
/System/Library/PrivateFrameworks/SyncLegacy.framework/Versions/A/SyncLegacy
/usr/lib/dyld
/private/var/db/dyld/dyldshared_cacheppc
/dev/null
/dev/null
/Users/evforsbe/Library/Application Support/SyncServices/Local/clientdata/9b84183c8bf1d69d5d6e9094b64883651efb4aa4/ recordids.synciddb
->0x2a82dd0
->0x2a41f68
/Users/evforsbe/Library/Application Support/SyncServices/Local/clientdata/9b84183c8bf1d69d5d6e9094b64883651efb4aa4/ constructedids.synciddb
/Users/evforsbe/Library/Application Support/SyncServices/Local/clientdata/9b84183c8bf1d69d5d6e9094b64883651efb4aa4/ recordids.synciddb
/Users/evforsbe/Library/Application Support/SyncServices/Local/clientdata/9b84183c8bf1d69d5d6e9094b64883651efb4aa4/ constructedids.synciddb
/Users/evforsbe/Library/Application Support/SyncServices/Local/data.syncdb
/Users/evforsbe/Library/Application Support/SyncServices/Local/data.syncdb
/Users/evforsbe/Library/Application Support/SyncServices/Local/clientdata/9b84183c8bf1d69d5d6e9094b64883651efb4aa4/ data.syncdb
/Users/evforsbe/Library/Application Support/SyncServices/Local/clientdata/9b84183c8bf1d69d5d6e9094b64883651efb4aa4/ constructedids.synciddb-journal
/Users/evforsbe/Library/Application Support/SyncServices/Local/clientdata/9b84183c8bf1d69d5d6e9094b64883651efb4aa4
/Users/evforsbe/Library/Application Support/SyncServices/Local/clientdata/9b84183c8bf1d69d5d6e9094b64883651efb4aa4/ recordids.synciddb-journal
/Users/evforsbe/Library/Application Support/SyncServices/Local/clientdata/9b84183c8bf1d69d5d6e9094b64883651efb4aa4
/Users/evforsbe/Library/Application Support/SyncServices/Local/clientdata/9b84183c8bf1d69d5d6e9094b64883651efb4aa4/ data.syncdb-journal
/Users/evforsbe/Library/Application Support/SyncServices/Local/clientdata/9b84183c8bf1d69d5d6e9094b64883651efb4aa4
192.168.200.222:60051->google.navigation.opendns.com:http

Answer 1

So by removing the Exchange sync for my Address Book prefs, I was able to completely clear-up the problem. That link to opendns was VERY VERY interesting. I looked at my routing tables and indeed, they hijack google DNS entries and cause all sorts of havoc as a consequence. As junky as my ISP's DNS service is (RoadRunner/Time Warner in SoCal), I believe I will switch back to them as I find I don't get the original problem, with Exchange enabled, when using their DNS instead of opendns.
What a mess and my thanks for the quick eye (I am going to mark your post as the solution for me)! I can't say that I am certain whether this is solely an opendns issue or if it is an issue with Exchange sync on the Mac, separate from opendns; however I am in a position where I don't really require either so both disabling Exchange and removing opendns are acceptable to me. Hopefully both Apple (exchange support - possibly fixed in Snow Leopard?) and OpenDNS (the idiot idea to re-route google dns) address their issues and can use issues such as mine to replicate the problem.
How would a home user with either little desire or knowledge ever diagnose an issue such as this? For every person like me, there has to be 10 who would believe their mouse needs replacing, then take it to the shop after that doesn't work, then get a new machine, etc. An entire sub-economy seeded by a simple software-based issue.