If you are *SURE* those snapshots are deleted (committed) from ESX you can delete them manually, by deleting ONLY the snapshot files don't touch the original *.VMDK files or you will delete your VM.
The datastore probably isn't able to allocate space for the VM paging file. You can get around this by making ALL of the RAM in that one VM "reserved", that way ESX will not try to create a paging file. Also turn off logging for that VM, it should start now...
IF your VM is thin provisioned, and there is ZERO space left on the datastore it will probably freeze again..