You might be able to check recent expensive queries to try and identify the query that caused your tempdb issue. You can try seeing if Activity Monitor in SSMS will show you the query. Grant also had a really good SQLPASS web seminar that used DMVs to get info on long running queries. I believe the code he used was:

--Long running queries

select top 10 *

from sys.dm_exec_query_stats

cross apply sys.dm_exec_sql_text(sql_handle)

cross apply sys.dm_exec_query_plan(plan_handle)

order by total_elapsed_time/execution_count desc

Of couse these solutions are only good if SQL has not been restarted since the TempDB errors, as the DMVs will only collect metrics from the time SQL was started.