I'm not sure you should be looking at Profiler to track that error, but if you do want to try it anyway, it sounds like you should be tracking queries.
A couple of questions. What edition / version / SP setup for SQL do you have? What about your OS for SQL Server? Do you have consistent OSs for the PCs?
Does SQL Server exist on an IIS server and do you have it exposed to a Web page?
Buffer errors tend to be Denial of Service attacks or other hacks (kernal exploits, etc.) because not all the appropriate Service Packs have been applied or security on your server is not as tight as it should be. I would start here first before worrying about Profiler.
If you want to do Profiler anyway, try the following events and do NOT exclude system IDs because you want to see if it might be a server issue.
ErrorLog & EventLog under Errors & Warnings, SP:StmtStarting, SP:Starting & RPC:Starting under Stored Procedures, and then pick a few items under T-SQL (SQL: StmtStarting & Exec Prepared SQL). These items should get you started.
Catadmin - MCDBA, MCSA
"No, no. Yes. No, I tried that. Yes, both ways. No, I don't know. No again. Are there any more questions?"
-- Xena, "Been There, Done That"