c4c20625   
   From: esquel@sommarskog.se   
      
   Mark D Powell (Mark.Powell2@hp.com) writes:   
   > Yes, I am certain that the posted information is for the same SQL   
   > Server since the messages were copied from the current SQL Server   
   > Error Log accessed via SQL Server Management Studio running on the   
   > database server.  No other instances are configured to the tool.  I   
   > just copied and pasted from the bottom of the log display, that is, I   
   > double clicked a log entry and copiled from the bottom portion of the   
   > window that SSMS opens.   
      
   Well, you confirmed my assumption from where you got the message.   
      
   Next time you see this, run xp_readerrorlog from the query window,   
   and see if you can see the same error message.   
      
   > I have another 20 or so SQL Server installations running and I have   
   > never seen this issue on any of them.  This installation is running   
   > under VM but then agains so are several of my other systems.   
      
   One possibility is that the clock had drifted, and just had been   
   corrected. I don't know common this is with server-class VMs, but I   
   remember I had severe problems with the time get very fast or slow in   
   my VMs a couple of years back. I think the problem is related to   
   power-saving features in the CPU and/or BIOS.   
      
      
   --   
   Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se   
      
   Links for SQL Server Books Online:   
   SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx   
   SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)