I HIGHLY recommend finding err.exe from microsoft.com and getting it. Putting that error code into it yields the following:
C:\Users\joseph.e.kaplan>err 0x80092013
# for hex 0x80092013 / decimal -2146885613 :
CRYPT_E_REVOCATION_OFFLINE winerror.h
# The revocation function was unable to check revocation
# because the revocation server was offline.
# 1 matches found for "0x80092013"
Basically, CRL checking did not work on the certificate used to sign the token in question. This is common in cases where the CRL referenced in the certificate (or one of the other certs in the chain) could not be reached from the server doing the verification.
My experience is that you have to disable revocation checking to make ADFS work reliably because revocation checking itself is hard to make work consistently. The steps to disable differ depending on which version of Windows server you use (it is in the GUI in 2008 but not in 2003 so requires manual trust policy file modification).