Outlook 2003 Hanging on exit

[Matt Williamson]

I know this is a common problem and I've read everything that is available
on the web that I can find regarding this occurence. The symptoms in the
case are that the process Outlook.exe remains in memory with very high CPU
utilization 60-98% after exiting the program. This is Outlook 2003 sp2
running on Exchange 2003 sp2. It does happen when I launch Outlook /safe as
well, so I know it's not an Add-in causing it. I have Google desktop
installed but I've killed the process and disabled its add-in. No help. I do
use word as the Email editor but it doesn't help to kill Winword.exe either.
I've gone through the list of processes and killed everything related to AV,
Syncing PDA, etc. I don't have Skype on this workstation. I'd really like to
get this solved because more than just an annoyance, it's preventing some
CDO code that I wrote from running properly.

TIA

Matt

 

[DL]

Does it also occur if you start win in Safe mode?

 

[Matt Williamson]

Does it also occur if you start win in Safe mode?

Yes. If I start in safe mode with network support, the same thing happens.
It's not another program interfering. I ran process monitor and filtered for
Outlook.exe after closing it while it is spiking the CPU and this is what I
get repeatedly. The buffer overflow looks like a possible problem but I'm
not sure how to troubleshoot further.

18366 3:40:13.5232138 PM OUTLOOK.EXE 2176 RegQueryValue
HKLM\System\CurrentControlSet\Services\Tcpip\Linkage\Bind BUFFER OVERFLOW
Length: 144
18367 3:40:13.5232317 PM OUTLOOK.EXE 2176 RegQueryValue
HKLM\System\CurrentControlSet\Services\Tcpip\Linkage\Bind BUFFER OVERFLOW
Length: 144
18368 3:40:13.5232423 PM OUTLOOK.EXE 2176 RegQueryValue
HKLM\System\CurrentControlSet\Services\Tcpip\Linkage\Bind SUCCESS Type:
REG_MULTI_SZ, Length: 696, Data:
\Device\{D9C56594-9151-4432-A52C-2A43D46EC9B2},
\Device\{CEFEBC60-BDFA-4121-997C-14F072DF3ED2},
\Device\{270FC095-6FFC-4FBE-AD6B-054BC5EAA214},
\Device\{D91A66EB-BDEF-4860-ADC3-82E7B655E826},
\Device\{A2C8446B-32FC-47DB-B0BF-24A22DE03A27}, \Device\NdisWanIp,
\Device\{A969B0F2-1D88-4AB3-9B6E-1E68E73B0595},
\Device\{A83FB030-DE63-4506-88A2-F3E37B737055}
18369 3:40:13.5233781 PM OUTLOOK.EXE 2176 RegQueryValue
HKLM\System\CurrentControlSet\Services\Tcpip\Linkage\Bind BUFFER OVERFLOW
Length: 144
18370 3:40:13.5233890 PM OUTLOOK.EXE 2176 RegQueryValue
HKLM\System\CurrentControlSet\Services\Tcpip\Linkage\Bind BUFFER OVERFLOW
Length: 144
18371 3:40:13.5233985 PM OUTLOOK.EXE 2176 RegQueryValue
HKLM\System\CurrentControlSet\Services\Tcpip\Linkage\Bind SUCCESS Type:
REG_MULTI_SZ, Length: 696, Data:
\Device\{D9C56594-9151-4432-A52C-2A43D46EC9B2},
\Device\{CEFEBC60-BDFA-4121-997C-14F072DF3ED2},
\Device\{270FC095-6FFC-4FBE-AD6B-054BC5EAA214},
\Device\{D91A66EB-BDEF-4860-ADC3-82E7B655E826},
\Device\{A2C8446B-32FC-47DB-B0BF-24A22DE03A27}, \Device\NdisWanIp,
\Device\{A969B0F2-1D88-4AB3-9B6E-1E68E73B0595},
\Device\{A83FB030-DE63-4506-88A2-F3E37B737055}

 

[DL]

There was a mention on SysInternals forum of repairing Tcpip, which
apparently cured the problem for one but not others.
Also the entry for 'NdisWanIp' , being a driver have been any driver updates
from none PC manufacturers, or HW manu. sites?

You might try running Outlook through this tool
http://www.dependencywalker.com/ (An MS app) and see if it shows any err
modules.