Replying to anish:
guys...I got rid of this bizarre error by a bizarre solution... [Snip]
Are you still seeing this with the latest version of VirtualBox and updated Additions?