I've viewed all of the discussion to date, and even though I've never used either Outllook or this furry creature, the following would be my modes for checking further into the situation:
1. Programs can run from three places at startup and are discussed in [Q314106]: the Startup groups, the Run and RunOnce lines in the registry, and the "run=" and "load=" lines in the Win.ini file.
2. When you start Windows, dozens of programs are already running - many of them invisible and running in the background. "AutoStart Viewer" allows you to see every autostart on your system, all on the one screen. In addition, it gives you complete control over the autostart references, and allows you to modify or delete them at will. Key features are:
? Over 50 different autostart locations monitored!
? Right-click menu allows you to take complete control over each autostart
? Add New Autostart feature allows you to add new programs to automatically start
? Save/Print functions allow you to take snapshots
? Resizable, easy-to-use interface that shows every autostart on the one display
? All sizes, positions and settings are remembered
3. Windows Installation ("Setup" compact disc) [Q310760] & [Q307848] - used when the computer cannot be started in Safe Mode, neither Last Known Good nor Recovery Console was successful, and there are no backup sets to use with Automated System Recovery. Could this puppy be a service -- simply find out perhaps.
? When hardware or software is installed that installs a device or service that is incompatible with the current version of Windows, the service or device driver may be started automatically which may not allow Windows to remain running long enough to shut it down or disable the incompatible device driver. To resolve this issue, start the Recovery Console and log on to the computer using the following steps:
a. Start your computer with the Windows boot disks, or with the Windows CD-ROM disk.
b. When the Welcome to Setup dialog box is displayed, press R to repair, and then press C to start the Recovery Console. Choose to install Windows and log on with the Administrator account.
c. From the %SystemRoot%\System32 folder at the command prompt, type listsvc, and then press Enter. Locate the service or driver that is causing the problem in the list provided.
Warning: Selecting the wrong service or device could cause further problems.
d. Type disable servicename (where servicename is the name of the service), and then press Enter.
Warning: The disable command prints the old start_type of the service before resetting it to SERVICE_DISABLED. Be sure to record the old start_type information in case it is needed to re-enable the service.
e. Type exit to restart the computer.
4. The article [Q286350] discusses Autodump+ (ADPlus.vbs) a new tool from Microsoft Product Support Services (PSS) that can troubleshoot any process or application that stops responding (hangs) or fails (crashes) and is a console-based Microsoft Visual Basic script. AD+ has three modes of operation:
? Hang Mode is used to troubleshoot process hangs, 100 percent CPU utilization, and other problems that do not involve a crash. When you use AD+ in hang mode, you must wait until the process or processes hang before you run the script (that is, it is not perisistent like crash mode).
? Crash Mode is used to troubleshoot crashes that result in Dr. Watson errors, or any other type of error that causes a program or service to terminate unexpectedly. When you use AD+ in crash mode, you must start AD+ before the crash occurs. AD+ can be configured to notify an administrator or a computer of a crash through the '-notify' switch.
? Quick Mode is a light-weight version of hang mode that produces mini memory dumps of the specified processes and a debug log file with extended debugging information. For processes that consume large amounts of virtual memory, quick mode can be significantly faster than regular hang mode.
a. You should use AD+ to capture debugging information if you are experiencing the following problems:
? Processes that hang.
? Processes that consume 100 percent CPU on a single processor computer, 50 percent CPU on a dual processor computer, 25 percent CPU on a quad processor computer, and so on.
? Processes that crash or shut down unexpectedly.
b. You should not use AD+ in the following situations:
? If you need to troubleshoot a program or process that terminates unexpectedly upon startup. You can only use AD+ with processes that start successfully. If you need to troubleshoot processes that terminate unexpectedly upon startup, "User Mode Process Dump" may be a better solution.
? Alternatively, you can use the latest "debuggers" to manually debug the process.
? If there is a noticeable performance impact when you use AD+ in crash mode. This is usually caused by dynamic-link libraries (DLLs) or programs that throw a large number of Microsoft Visual C++ EH exceptions (which occur when you use the C++ throw statement or when you use try/catch blocks). Programs that write a large amount of information to the debug output stream can also cause a performance degradation. In the vast majority of cases, AD+ does not impact performance noticeably when it is running in crash mode.
Please look at my entries the furry irratant
You may be able to assist
Thank you sheard

Chowhound
Comic Vine
GameFAQs
GameSpot
Giant Bomb
TechRepublic