How to know which query is resulting in errors in the trace?
I would add the events SQL:BatchStarting and/or SP:StmtStarting as well. That way, you can compare the SPID (the session ID) and find which query executed on which SPID.

For the record, Profiler is being replaced by Extended Events (XE for short) as of SQL Server 2008, though the GUI is really only usable as of 2012 in my opinion.