Attempt to access expired blob handle

Question

We get a random error in our test environment after upgrading from SQL server 2008 R2 to 2012.
System.Data.SqlClient.SqlException (0x80131904): 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.
A severe error occurred on the current command.  The results, if any, should be discarded.
Location:  tmpilb.cpp:2576
Expression:  fFalse
SPID:   55
Process ID:  1552
Description:  Attempt to access expired blob handle (3)
The weird thing is that is looks almost exactly like the below kb article, we are using a matching scenario as the symptons described in the below kb.
support.microsoft.com/kb/2644794/
It did not make this issue in 2008 R2, we then took the database from 2008 R2 and attached to the 2012 db server, and then
Event viewer (throws a lot of the 4 below errors):
Level Date   Source   Event Id Task category
Error 01-04-2014 17:42:00 MSSQL$DGOFFICEMAINSQL 17310  Server
 A user request from the session with SPID 58 generated a fatal exception. SQL Server is terminating this session. Contact Product Support Services with the dump produced in the log directory.
Error 01-04-2014 17:41:59 MSSQL$DGOFFICEMAINSQL 17065  Server
 SQL Server Assertion: File: <tmpilb.cpp>, line = 2576 Failed Assertion = 'fFalse' Attempt to access expired blob handle (3). This error may be timing-related. If the error persists after rerunning the statement, use DBCC CHECKDB to check the database
for structural integrity, or restart the server to ensure in-memory data structures are not corrupted.
Error 01-04-2014 17:41:58 MSSQL$DGOFFICEMAINSQL 3624  Server
 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.
Error 01-04-2014 14:47:41 MSSQL$DGOFFICEMAINSQL 17066  Server
 SQL Server Assertion: File: <qxcntxt.cpp>, line=1137 Failed Assertion = '!"No exceptions should be raised by this code"'. This error may be timing-related. If the error persists after rerunning the statement, use DBCC CHECKDB to check
the database for structural integrity, or restart the server to ensure in-memory data structures are not corrupted.
(DBCC CHECKDB) has been run, and no errors seems to occur
All usefull ideas are welcome :)

Answer 1

OMG weirdest thing ever:
I have installed SQL server 2012 SP1 on my Windows 7 machine, running the program against the same database, then I tried to replicate the error:
Using IE 11 going to the page that causes the issue, validating in event viewer at the same time, nothing happens, everything looks good.
Using Newest FF or Chrome, CONSISTANTLY throws 3 event logs, everytime I go to the page, 2x event id 17065 and 1 x 17066, I assume it throws the other errors upon too many, or too frequent errors.
But WHY, I simply cannot wrap my brain around why such a feature inside the SQL server, should be able to act differently based on the browser.
Error 01-04-2014 17:41:59 MSSQL$DGOFFICEMAINSQL 17065  Server
 SQL Server Assertion: File: <tmpilb.cpp>, line = 2576 Failed Assertion = 'fFalse' Attempt to access expired blob handle (3). This error may be timing-related. If the error persists after rerunning the statement, use DBCC CHECKDB to check the database
for structural integrity, or restart the server to ensure in-memory data structures are not corrupted.
Error 01-04-2014 14:47:41 MSSQL$DGOFFICEMAINSQL 17066  Server
 SQL Server Assertion: File: <qxcntxt.cpp>, line=1137 Failed Assertion = '!"No exceptions should be raised by this code"'. This error may be timing-related. If the error persists after rerunning the statement, use DBCC CHECKDB to check the database
for structural integrity, or restart the server to ensure in-memory data structures are not corrupted.
I am still very interested in good ideas!!!