The set of queries below generates a stack dump when run on SQL 2012 SP1. It runs successfully on SQL 2008 R2. I believe the problem has something to do with BIGINTs and duplicate possible return values. Removing any one of the rows, or "shortening" any of the AccountId values (e.g. remove the leading 830362286364 from each value) eliminates the problem. Removing the "TOP 1" or the ORDER BY from the query also eliminates the problem, as does changing the "TOP 1" to "TOP 2" or "TOP 3".
The problem isn't in the query execution either... simply attempting to generate the execution plan is enough to cause the error.
I can provide a crash dump if it helps, but I've been able to reproduce this on every SQL 2012 instance I have access to, so I'm guessing you won't need it. :)