Does this still happen with the latest VirtualBox version? The bug seems to be in guest properties from the limited information provided.
Could you upgrade VirtualBox and see if it's fixed now?
