the article you found when searching for you error code was written in Nov 2008 and is related to Microsoft Virtual Server 2005 and not to Hyper-V. The BIN file you find inside your VM's folder is something that didn't exist in MSVS but is new in Hyper-V.
If you create a snapshot of a running VM in Hyper-V, there are two files created: a .vsv and a .bin, where the .bin file is containing the memory information of th machine and the .vsv contains special informations about the processes and so on. So deleting one of them brings the VM in an instable state. If you want to delete one, you need to delete both files. This means, that everything is lost, taht was in the memory of the VM and was not written to its hard drive.
If you delete both files, you can use the remaining.vhd file to point a newly created VM to it. This will work, no matter what hardware you are using. You can even "move" a .vhd from MSVS to Hyper-V or from Hyper-V R1 to R2.
One thing, you should be aware of, is, that moving VHDs between different versions of virtualisation plattforms can lead to a problem with the integration services inside the VM. So you may need to uninstall and reinstall them.
If you need further information about this, here is a very good blog entry: http://blogs.technet.com/roblarson/archive/2008/04/26/virtual-machine-snapshots-with-hyper-v.aspx
Hope that helps. If not, give me a call.
Best regards from good old Germany,
Save the Earth, it's the only planet with chocolate.