Frequent crashes launching IE6 SP1 on Win2k

[Martin Vuille]

IE6 6.0.2800.1106 with updates: SP1, Q818529, Q330994
Win2k Pro SP4 with all updates

When I launch IE, frequently but not every time IE will
crash
immediately. Sometimes I can launch IE ten times in a row
with no problem, and sometimes it will fail ten times in a
row. I have reinstalled IE6 and SP1 and Q818529, to no
avail.

The cause of the crash is

Unhandled exception at 0x71702959 in IEXPLORER.EXE:
0xC0000005
Access violation reading location 0x00000000

and the stack traceback is

SHDOCVW.DLL!
CAggregatedUnknown::CUnkInner::QueryInterface() + 0x12
SHDOCVW.DLL!CAggregatedUnknown::QueryInterface()
+ 0x14
SHDOCVW.DLL!CIEFrameAuto::QueryInterface() + 0x15

SHDOCVW.DLL!CBaseBrowser2::WndProcBS() + 0x326f8

browseui.dll!CCommonBrowser::WndProcBS() + 0x1e

browseui.dll!CShellBrowser2::WndProcBS() + 0xd9

browseui.dll!IEFrameWndProc() + 0x49
USER32.DLL!_UserCallWinProc@20() + 0x18
USER32.DLL!_DispatchClientMessage@20() + 0x2f
USER32.DLL!___fnDWORD@4() + 0x22
NTDLL.DLL!_KiUserCallbackDispatcher@12() + 0x13

USER32.DLL!_SendMessageWorker@20() + 0x2e3
USER32.DLL!_SendMessageW@16() + 0x43
indicdll.dll!_IndicDll_ShellHookProc@12() + 0xd1

USER32.DLL!_DispatchHookW@16() + 0x2e
USER32.DLL!_CallHookWithSEH@16() + 0x3a
USER32.DLL!___fnHkINDWORD@4() + 0x22
NTDLL.DLL!_KiUserCallbackDispatcher@12() + 0x13

USER32.DLL!_CallNextHookEx@16() + 0x73
HOOKDLL.DLL!6e6017f9()
USER32.DLL!_DispatchHookA@16() + 0x4d
USER32.DLL!_CallHookWithSEH@16() + 0x3a
USER32.DLL!___fnHkINDWORD@4() + 0x22
NTDLL.DLL!_KiUserCallbackDispatcher@12() + 0x13

imm32.dll!_ImmSetActiveContext@12() + 0xa3
USER32.DLL!_FocusSetIMCContext@8() + 0x25
USER32.DLL!_ImeSystemHandler@16() + 0xab
USER32.DLL!_ImeWndProcWorker@20() + 0x52
USER32.DLL!___fnDWORD@4() + 0x22
NTDLL.DLL!_KiUserCallbackDispatcher@12() + 0x13

USER32.DLL!_SetForegroundWindow@4() + 0xb
browseui.dll!CShellBrowser2::OnCreate() + 0x66
SHDOCVW.DLL!CBaseBrowser2::WndProcBS() - 0x61
browseui.dll!CCommonBrowser::WndProcBS() + 0x1e

browseui.dll!CShellBrowser2::WndProcBS() - 0x15e

browseui.dll!IEFrameWndProc() - 0x17
USER32.DLL!_UserCallWinProc@20() + 0x18
USER32.DLL!_DispatchClientMessage@20() + 0x2f
USER32.DLL!___fnINLPCREATESTRUCT@4() + 0x64
NTDLL.DLL!_KiUserCallbackDispatcher@12() + 0x13

USER32.DLL!__CreateWindowEx@52() + 0xbd
USER32.DLL!_CreateWindowExW@48() + 0x2e
shlwapi.dll!_CreateWindowExWrapW@48() + 0x3c
KERNEL32.DLL!_GetVersionExA@4() + 0xa0
KERNEL32.DLL!_GetModuleHandleForUnicodeString@4()
+ 0x38
USER32.DLL!_PostMessageW@16() + 0x37
browseui.dll!BrowserProtectedThreadProc() + 0x44

NTDLL.DLL!_LdrpLoadDll@20() + 0x117cc
KERNEL32.DLL!_ExpandEnvironmentStringsW@12() +
0x4e
GDI32.DLL!_GetSystemPaletteEntries@16() + 0x26
ADVAPI32.DLL!_LocalBaseRegCreateKey@32() + 0x181

SHELL32.DLL!__OpenKeyForFolder@16() + 0x6f
shlwapi.dll!_StrDupW@4() + 0x2b
SHELL32.DLL!_SHGetFolderPathW@20() + 0x7a
SHELL32.DLL!_SHGetSpecialFolderPathW@16() + 0x1a

SHDOCVW.DLL!__AorW_SHGetSpecialFolderPath@16() +
0x15b66
NTDLL.DLL!_RtlQueryEnvironmentVariable_U@12() +
0xe7
NTDLL.DLL!_RtlFreeHeap@12() + 0x1ed
KERNEL32.DLL!_lstrcmpiA@8() + 0x21
SHDOCVW.DLL!_DelayloadNotifyHook@8() + 0x28
SHDOCVW.DLL!___delayLoadHelper2@8() + 0x13d
00000023()
SHDOCVW.DLL!_IEWinMain@8() + 0xa7
IEXPLORE.EXE!WinMainT() + 0x2dc
IEXPLORE.EXE!_ModuleEntry@0() + 0x97
KERNEL32.DLL!_BaseProcessStart@4() + 0x3d

Any suggestions would be appreciated.
MV

 

[Robert Aldwinckle]

There are a few .dlls in that traceback which I wasn't even aware of
so that might be where I would start experimenting. The problem
is that you have identified that your problem is only intermittent so
any changes you make don't necessarily prove anything.

However, FWIW here are the modules I would focus on.
indicdll.dll Keyboard Language Indicator Shell Hook Extension
HOOKDLL.DLL Not found!
imm32.dll Windows 2000 IMM32 API Client DLL


First, obviously, you should find out where that hookdll.dll comes from.
The other two seem legitimate but from features which I could do without
at least temporarily. Otherwise, if the versions of those modules that you
have check out at the DLL Help Database with the products that you have
installed, perhaps an SFC /scannow would be in order?


Good luck

Robert Aldwinckle

 

[Martin Vuille]

There are a few .dlls in that traceback which I wasn't even aware of
so that might be where I would start experimenting. The problem
is that you have identified that your problem is only intermittent so
any changes you make don't necessarily prove anything.

However, FWIW here are the modules I would focus on.
indicdll.dll Keyboard Language Indicator Shell Hook Extension
HOOKDLL.DLL Not found!
imm32.dll Windows 2000 IMM32 API Client DLL


First, obviously, you should find out where that hookdll.dll comes
from. The other two seem legitimate but from features which I could do
without at least temporarily. Otherwise, if the versions of those
modules that you have check out at the DLL Help Database with the
products that you have installed, perhaps an SFC /scannow would be
in order?

You are good!

It may be too early to be sure, but it looks like indicdll.dll was
the problem.

Hookdll.dll is legit, it's part of XDesk, a virtual desktop product.

In case you're interested, indicdll.dll adds a small indicator in the
system tray showing which keyboard locale is currently enabled. I
configured an alternate kb locale that I use for composing text in
French using "dead keys" to make-up the accented letters.

Do you know what imm32.dll is for? I googled for it and found lots of
people having problems with it, but nothing very informative.

In any case, thanks a bunch for your suggestions. I feel my annoyance
factor going down already!

MV