I had a similar problem. It turned out to be a job running that would switch the database to SIMPLE to load some tables in the hopes of getting minimal logging and then back to full followed by a full backup to restart the log chain.
--Jeff Moden
Change is inevitable... Change for the better is not.