C
Chad Harris
I'm on an XP SP2 box regularly SFC'd Perf Disk Defragged, Spyware scanned,
and fully updates with what MSFT offers.
Recently IE has been closed with an Oleaut 32.dll error that shows up in
Event Viewer and on the deaktop with this error. I often can prevent IE
from crashing by opening new instances of iexplore.exe or the shell
explorer.exe but not with this. It closes all my browser windows.
Description:
Faulting application iexplore.exe, version 6.0.2900.2180, faulting module
ole32.dll, version 5.1.2600.2595, fault address 0x0008e1d7.
I have searched and read what's on MSFT's site and in the MSKBs on
Oleaut32.dll and not found anything to prevent this including running SFC
successfully.
I reregistered it fwiw with a REGSRV32 Oleaut32.dll command in the run box.
The IE repair tool is for IE5X offered in the MSKBs; I would have thought
the fix would have been in XPRTM, SP1 or SP2.
http://support.microsoft.com/?kbid=194177
I also saw this fix and wonder if anyone has experience with it:
http://64.233.161.104/search?q=cach...om/faq/ie.htm+oleaut32.dll+MSKB&hl=en&start=8
Of course MSFT hasn't found a way to link up useufl information with the
error, and although they talk about improving this at Redmond and at
meetings all the time, I don't expect real time error help that works to
see daylight until Blackcomb rears it's head--certainly not in Longhorn.
Does anyone have any practical fixes, downloads, ect to prevent this
annoying IE crash.
Tia,
Chad Harris
_______________________________________________________________
and fully updates with what MSFT offers.
Recently IE has been closed with an Oleaut 32.dll error that shows up in
Event Viewer and on the deaktop with this error. I often can prevent IE
from crashing by opening new instances of iexplore.exe or the shell
explorer.exe but not with this. It closes all my browser windows.
Description:
Faulting application iexplore.exe, version 6.0.2900.2180, faulting module
ole32.dll, version 5.1.2600.2595, fault address 0x0008e1d7.
I have searched and read what's on MSFT's site and in the MSKBs on
Oleaut32.dll and not found anything to prevent this including running SFC
successfully.
I reregistered it fwiw with a REGSRV32 Oleaut32.dll command in the run box.
The IE repair tool is for IE5X offered in the MSKBs; I would have thought
the fix would have been in XPRTM, SP1 or SP2.
http://support.microsoft.com/?kbid=194177
I also saw this fix and wonder if anyone has experience with it:
http://64.233.161.104/search?q=cach...om/faq/ie.htm+oleaut32.dll+MSKB&hl=en&start=8
Of course MSFT hasn't found a way to link up useufl information with the
error, and although they talk about improving this at Redmond and at
meetings all the time, I don't expect real time error help that works to
see daylight until Blackcomb rears it's head--certainly not in Longhorn.
Does anyone have any practical fixes, downloads, ect to prevent this
annoying IE crash.
Tia,
Chad Harris
_______________________________________________________________