is a spike of 30% actually causing you a problem?

If you really want to know the SQL causing the issue run a server side profiler trace (google that) and a perfmon trace over the same time frame.

when done you can run the profiler gui to display the trace and call the perfmon trace into the profiler gui, they will be displayed in tandem and you will be able to see exactly what was running when the CPU spiked.