You're probably accessing a more recent database with a 9.2.0.1 client.
Apparently the bug is not published, but I found a repost here: System.AccessViolationException: Attempted to read or write protected memory - MSDN Forums
In fact, tracking this one down this morning inspired me to join the club.