Could not continue scan with NOLOCK due to data movement SQL Server 2008 R2
There's at least three possibilities: 


SQL Server Management Studio was running a query that it shouldn't have
Something else was running a query it shouldn't have (like an SSMS add-in, which isn't likely based on the sounds of the question)
The engine was experiencing difficulties executing a normal SSMS query (that it shouldn't have)


I'd troubleshoot #1 by running SSMS from another machine, pointed at this particular laptop. If it works okay, then the laptop's SSMS is the problem - reinstall that.

If the other machine's SSMS gets the same error when connecting to the laptop's engine, then uninstall and reinstall the SQL Server engine on the affected laptop. (It's some type of corruption issue, and not worth the $500 MS support call to troubleshoot - if it was a production server, I'd answer otherwise.)