Where else could an event be triggering an automated SQL Profiler trace

I have discovered trace output in \MSSQLDATA\MSSQL.1\MSSQL\LOG that I have not kicked off.  It is at various times and limited to 20MB.  So that tells me a server event is kicking off a pre-defined trace.  The trace contains mostly hash warnings and sort warnings.

I have looked through my Agent Jobs, Agent Alerts, and perfmon and don't find anything that is set up to kick off a trace under a specified condition.

I have checked the job activity, SQL error logs, SQL server logs, and the server's event viewer for any odd events or event times that correlate with the times of the traces.

I have checked each database's sys.sql_modules for a definition containing '%sp_trace%'.

Where else can I check to find what would be triggering these traces?

Our app logins don't have permissions high enough to run traces, I verified:
"You do not have permission to run 'SP_TRACE_CREATE'"

This is Enterprise SQL 2005 64-bit SP2 running active/passive on a Win2003 SP2 clustered pair.
Start Free Trial