Is this a Bug? System Assertion Failure On Manual Update Stats SQL 2008 R2 SP2

System:

SQL 2008 R2 SP2 Enterprise x64 (10.50.4000.0)

Windows 2008 R2 Enterprise X64 SP1 (6.1.7601)

Error Message:

Updating [dbo].[Bob]
Location:     statutil.cpp:3225
Expression:   m_fInitialized && m_statBlob.CbSize() && iKey >= -1 && iKey < m_statBlob.GetHeader()->GetKeyCount()
SPID:         70
Process ID:   7848
Msg 3624, Level 20, State 1, Line 1
A system assertion check has failed. Check the SQL Server error log for details. Typically, an assertion failure is caused by a software bug or data corruption. To check for database corruption, consider running DBCC CHECKDB. If you agreed to send dumps to Microsoft during setup, a mini dump will be sent to Microsoft. An update might be available from Microsoft in the latest Service Pack or in a QFE from Technical Support.

*************

Issue:

On one of my systems I've had failures on two separate databases when updating stats.  Below is the error from one of them.  These databases are quite large (300 GB).  The table for the example below has 1.1 million records.

The table has 6 stats, updating any of them causes the below failure.  DBCC Runs clean across the database and even checking the table separately.

Using Google I've found this link although there is no mention of issues with statshttp://support.microsoft.com/kb/2728534?wa=wsignin1.0

Has anyone else experienced this issue?  Does the above "fix" resolve this issue for stats as well?

Table:

CREATE TABLE dbo.Bob
(
	[UserID] [nvarchar](15) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL		
	,[AccessLevel] [smallint] NOT NULL
	,[SchemeID] [int] NOT NULL
	,[ApplicationName] [varchar](255) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL
	,CONSTRAINT [PK_bob] PRIMARY KEY CLUSTERED  
	(
		[UserID] ASC,
		[AccessLevel] ASC,
		[SchemeID] ASC,
		[ApplicationName] ASC
	)
	WITH 
		(
			PAD_INDEX  = OFF
			, STATISTICS_NORECOMPUTE  = OFF
			, IGNORE_DUP_KEY = OFF
			, ALLOW_ROW_LOCKS  = ON
			, ALLOW_PAGE_LOCKS  = ON
			, FILLFACTOR = 90
		)
);

Update#1

Just tried to compress this table wit DATA_COMPRESSION = PAGE and had the below.  With the DBCC results coming back clean I guess this is looking like a bug and possibly something similar to the one reported above.

Msg 3624, Level 20, State 1, Line 2

A system assertion check has failed. Check the SQL Server error log for details.

Typically, an assertion failure is caused by a software bug or data corruption.

To check for database corruption, consider running DBCC CHECKDB.

If you agreed to send dumps to Microsoft during setup, a mini dump will be sent to Microsoft.

An update might be available from Microsoft in the latest Service Pack or in a QFE from Technical Support.

Msg 0, Level 20, State 0, Line 0

A severe error occurred on the current command. The results, if any, should be discarded.