Hello Mr. Randal,
Finally got a response from premier support below is their final statements.
As per our research this is a known issue only occurs on SQL SERVER 2012 Instances when you attempt to query certain DMV’s from a connection using NOLOCK hint or with read uncommitted Isolation level, when other connections are creating and dropping temporary tables. The error message is specific to the transaction which was trying to query the DMVs in READ UNCOMMITED or NOLOCK hint and will not have any impact on other user queries or data that is using TEMPDB database.
These errors are not going to cause any impact on the SQL server.
You can use READ COMMITTED isolation level as workaround to this problem.