Syslogd runaway + powerpoint

Question

Found out in /var/log/system.log what cause my syslogd process to use up to 100% of my CPU
Here is the message in the log at the same time syslogd runaway:
Jul 16 16:48:08 U233 [0x0-0x1f01f].com.microsoft.PowerPoint[151]: Ignoring Quick
draw drawing between QDBeginCGContext and QDEndCGContext
Jul 16 16:49:20: --- last message repeated 1389 times ---
Jul 16 16:48:09 U233 [0x0-0x1f01f].com.microsoft.PowerPoint[151]: Ignoring Quick
draw drawing between QDBeginCGContext and QDEndCGContext
Jul 16 16:49:50: --- last message repeated 675 times ---
Jul 16 16:49:44 U233 [0x0-0x1f01f].com.microsoft.PowerPoint[151]: Ignoring Quick
draw drawing between QDBeginCGContext and QDEndCGContext
Jul 16 16:51:27: --- last message repeated 101281 times ---
Indeed I'm using Powerpoint to make a presentation, syslogd runaway multiple times a day (~dozen) since i started making my presentation.
syslogd never gave me problem when I was doing other stuff. Previous use of Powerpoint didn't produced that syslogd runaway so I'm guessing it comes from either the last 10.5.4 Leopard upgrade or Microsoft Office 2004 upgrade.
-Activity Monitor / Quiting process doesn't work, just stop it temporarily and it comes back
Any suggestion to stop my Macbook pro getting so hot?
P.S. There could be similar post but the since the search is desactivated i couldn't find them

Answer 1

Update:
I went to the Apple Store and talked to a Genius. Long story short, I was told that they have been seeing this issue allot since the release of Leopard. A "simple" archive/install was recommended to correct the problem. No explanation. A Terminal command to kill the offending process was also not offered when I asked (nothing I have tried works via this route). Hey, Apple, are you taking note of this?!
Of course, an archive/install is not as simple as it should be, especially when you only have the Mac OS X 10.5 upgrade disk. I have had to make a clone of my hard drive, reformat it, reinstall Tiger, update, reinstall Leopard, update, then move my data over via Migration Assistant. I hit a snag at that point ( see this post: http://discussions.apple.com/thread.jspa?threadID=1286935&tstart=0 ). For what it is worth, I still have the Syslogd issue while booted up into my Leopard clone volume. More information as I progress...
“Technological change is like an axe in the hands of a pathological criminal.” (Albert Einstein, 1941),
Dr. Z.