Outlook 2003 100% CPU Utilisation

[Craig Mann]

Hi

Can anyone explain why a desktop computer running Outlook 2003 suddenly is
hogging the cpu upto 100% utilisation?

There are no viruses on the system.

I temporarily disabled the smtp service just to ensure there was no spurious
program attempting to use the smtp service to send out unsolicited mail,
this did not solve the problem.

I have checked that the software is patched up-to-date to resolve any known
issues, the software was already up-to-date.

There are no memory leaks or sudden increase in pagefile size.

If I kill the application and reboot the machine, when outlook starts, it
appears to run as normal but then goes up to 100% cpu utilisation.

There are no syncronisation problems between the application and the
exchange server that it connects to. I've even set the application to work
off-line and it still hogs the cpu upto 100%

Can anyone explain this or tell me where I can look to resolve the issue?

Thanks
Craig

 

[Roady [MVP]]

How does it behave when you start Outlook in safe mode?
Also see http://www.howto-outlook.com/faq/outlookdoesntstart.htm

--
Robert Sparnaaij [MVP-Outlook]
www.howto-outlook.com

Tips of the month:
-FREE tool; QuickMail. Create new Outlook items anywhere from within Windows
-Properly back-up and restore your Outlook data

-----
Hi

Can anyone explain why a desktop computer running Outlook 2003 suddenly is
hogging the cpu upto 100% utilisation?

There are no viruses on the system.

I temporarily disabled the smtp service just to ensure there was no spurious
program attempting to use the smtp service to send out unsolicited mail,
this did not solve the problem.

I have checked that the software is patched up-to-date to resolve any known
issues, the software was already up-to-date.

There are no memory leaks or sudden increase in pagefile size.

If I kill the application and reboot the machine, when outlook starts, it
appears to run as normal but then goes up to 100% cpu utilisation.

There are no syncronisation problems between the application and the
exchange server that it connects to. I've even set the application to work
off-line and it still hogs the cpu upto 100%

Can anyone explain this or tell me where I can look to resolve the issue?

Thanks
Craig