Windows XP Pro/Outlook Explorer Conflict

[Alan Campbell]

I had been using Windows XP Home on my Dell Inpiron 2500
(900 mhz-256 mb) Laptop for over a year with no problems
with Outlook Explorer. Friday I upgrade to Windows XP Pro
to gain access to a network domain. Since then Outlook has
crashed 3 times sending a report to Microsoft and
restarting. Two times this happened at home while
connected to cable modem through a wireless router, and
once at work while connected to the network through the
built-in 10/100 port. Any ideas? No new drivers other than
the ones XP installed in the conversion. I redid all of
the Windows critical and recommended updates after the
installation.

[Gerry Cornell]

Alan

Are we talking about Windows Explorer, Internet Explorer, Outlook =
Express or Microsoft Outlook? You need to provide a copy of the Error =
Report and describe what you are doing when the error occurs!

Look in Event Viewer for error messages?=20

1. To open Event Viewer, click Start, click Control Panel, double-click =
Administrative Tools, double-click Event Viewer and select System for =
system errors or Application for application errors. Look for Error in =
the Type column and double click on Error to reveal a Description of the =
error. This can be copied by using Clipboard Viewer (see later).
=20
2. Part of the Description of the error will include a link, which you =
should double click for further information and you can copy using copy =
and paste.
http://go.microsoft.com/fw.link/events.asp
(Please note the hyperlink above is for illustration purposes only)

3. For some errors you will find "+ Related Knowledge Base Article", =
which if double clicked takes you to the Knowledge Base Article =
containing a suggested solution.

There always seems to be a step 2 but not always a step 3.=20

A tip for posting copies of Error Reports (Step 1). Run Event Viewer and =
double click on the error you want to copy. In the window which appears =
is a button resembling two pages. Double click the button and close =
Event Viewer. Now start your message ( email )and do a paste into the =
body of the message. This will paste the info from the Event Viewer =
Error Report complete with links into the message. Make sure this is the =
first paste after exiting from Event Viewer. It can be helpful to place =
a shortcut to Event Viewer on your Desktop.

=20
~~~~~~


Hope this helps.

Gerry
~~~~~~~~~~~~~~~~~~~~~~~~
FCA

Stourport, Worcs, England
Enquire, plan and execute.
~~~~~~~~~~~~~~~~~~~~~~~~
Please tell the newsgroup how any=20
suggested solution worked for you.
http://dts-l.org/goodpost.htm
~~~~~~~~~~~~~~~~~~~~~~~~

"Alan Campbell" > wrote in message =
...
> I had been using Windows XP Home on my Dell Inpiron 2500=20
> (900 mhz-256 mb) Laptop for over a year with no problems=20
> with Outlook Explorer. Friday I upgrade to Windows XP Pro=20
> to gain access to a network domain. Since then Outlook has=20
> crashed 3 times sending a report to Microsoft and=20
> restarting. Two times this happened at home while=20
> connected to cable modem through a wireless router, and=20
> once at work while connected to the network through the=20
> built-in 10/100 port. Any ideas? No new drivers other than=20
> the ones XP installed in the conversion. I redid all of=20
> the Windows critical and recommended updates after the=20
> installation.

[Alan]

There are two types of errors, one referencing bucket
24770708 Event Type: Error
Event Source: Microsoft Office 10
Event Category: None
Event ID: 1001
Date: 5/5/2003
Time: 9:43:44 AM
User: N/A
Computer: ALAN
Description:
Fault bucket 24770708.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 42 75 63 6b 65 74 3a 20 Bucket:
0008: 32 34 37 37 30 37 30 38 24770708
0010: 0d 0a ..

The other referencing Microsoft Outlook

Event Type: Error
Event Source: Microsoft Office 10
Event Category: None
Event ID: 1000
Date: 5/5/2003
Time: 9:39:33 AM
User: N/A
Computer: ALAN
Description:
Faulting application outlook.exe, version 10.0.4510.0,
faulting module ntdll.dll, version 5.1.2600.1106, fault
address 0x00001baa.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 6f 75 74 ure out
0018: 6c 6f 6f 6b 2e 65 78 65 look.exe
0020: 20 31 30 2e 30 2e 34 35 10.0.45
0028: 31 30 2e 30 20 69 6e 20 10.0 in
0030: 6e 74 64 6c 6c 2e 64 6c ntdll.dl
0038: 6c 20 35 2e 31 2e 32 36 l 5.1.26
0040: 30 30 2e 31 31 30 36 20 00.1106
0048: 61 74 20 6f 66 66 73 65 at offse
0050: 74 20 30 30 30 30 31 62 t 00001b
0058: 61 61 0d 0a aa..


There is not update on either available on Knowledgebase.
>-----Original Message-----
>Alan
>
>Are we talking about Windows Explorer, Internet Explorer,
Outlook Express or Microsoft Outlook? You need to provide
a copy of the Error Report and describe what you are doing
when the error occurs!
>
>Look in Event Viewer for error messages?
>
>1. To open Event Viewer, click Start, click Control
Panel, double-click Administrative Tools, double-click
Event Viewer and select System for system errors or
Application for application errors. Look for Error in the
Type column and double click on Error to reveal a
Description of the error. This can be copied by using
Clipboard Viewer (see later).
>
>2. Part of the Description of the error will include a
link, which you should double click for further
information and you can copy using copy and paste.
>http://go.microsoft.com/fw.link/events.asp
>(Please note the hyperlink above is for illustration
purposes only)
>
>3. For some errors you will find "+ Related Knowledge
Base Article", which if double clicked takes you to the
Knowledge Base Article containing a suggested solution.
>
>There always seems to be a step 2 but not always a step
3.
>
>A tip for posting copies of Error Reports (Step 1). Run
Event Viewer and double click on the error you want to
copy. In the window which appears is a button resembling
two pages. Double click the button and close Event Viewer.
Now start your message ( email )and do a paste into the
body of the message. This will paste the info from the
Event Viewer Error Report complete with links into the
message. Make sure this is the first paste after exiting
from Event Viewer. It can be helpful to place a shortcut
to Event Viewer on your Desktop.
>
>
>~~~~~~
>
>
>Hope this helps.
>
>Gerry
>~~~~~~~~~~~~~~~~~~~~~~~~
>FCA

>Stourport, Worcs, England
>Enquire, plan and execute.
>~~~~~~~~~~~~~~~~~~~~~~~~
>Please tell the newsgroup how any
>suggested solution worked for you.
>http://dts-l.org/goodpost.htm
>~~~~~~~~~~~~~~~~~~~~~~~~
>
>"Alan Campbell" > wrote
in message ...
>> I had been using Windows XP Home on my Dell Inpiron
2500
>> (900 mhz-256 mb) Laptop for over a year with no
problems
>> with Outlook Explorer. Friday I upgrade to Windows XP
Pro
>> to gain access to a network domain. Since then Outlook
has
>> crashed 3 times sending a report to Microsoft and
>> restarting. Two times this happened at home while
>> connected to cable modem through a wireless router, and
>> once at work while connected to the network through the
>> built-in 10/100 port. Any ideas? No new drivers other
than
>> the ones XP installed in the conversion. I redid all of
>> the Windows critical and recommended updates after the
>> installation.
>.
>

[Gerry Cornell]

Alan

I searched Google and found one other seemingly identical report of your =
problem.
http://groups.google.com/groups?hl=3Den&lr=3Dlang_en&ie=3DUTF-8&oe=3DUTF-=
8&selm=3DuLpndLqrCHA.1668%40TK2MSFTNGP09

There is no indication the problem was resolved.

Have you installed all the updates for Office. There has been at least =
one for Outlook post Service Pack 2. Otherwise I can only suggest you =
post your problem to an Outlook newsgroup.

http://office.microsoft.com/productupdates/mainCatalog.aspx

~~~~~~


Hope this helps.

Gerry
~~~~~~~~~~~~~~~~~~~~~~~~
FCA

Stourport, Worcs, England
Enquire, plan and execute.
~~~~~~~~~~~~~~~~~~~~~~~~
Please tell the newsgroup how any=20
suggested solution worked for you.
http://dts-l.org/goodpost.htm
~~~~~~~~~~~~~~~~~~~~~~~~


"Alan" > wrote in message =
...
> There are two types of errors, one referencing bucket=20
> 24770708 Event Type: Error
> Event Source: Microsoft Office 10
> Event Category: None
> Event ID: 1001
> Date: 5/5/2003
> Time: 9:43:44 AM
> User: N/A
> Computer: ALAN
> Description:
> Fault bucket 24770708.
>=20
> For more information, see Help and Support Center at=20
> http://go.microsoft.com/fwlink/events.asp.
> Data:
> 0000: 42 75 63 6b 65 74 3a 20 Bucket:=20
> 0008: 32 34 37 37 30 37 30 38 24770708
> 0010: 0d 0a .. =20
>=20
> The other referencing Microsoft Outlook
>=20
> Event Type: Error
> Event Source: Microsoft Office 10
> Event Category: None
> Event ID: 1000
> Date: 5/5/2003
> Time: 9:39:33 AM
> User: N/A
> Computer: ALAN
> Description:
> Faulting application outlook.exe, version 10.0.4510.0,=20
> faulting module ntdll.dll, version 5.1.2600.1106, fault=20
> address 0x00001baa.
>=20
> For more information, see Help and Support Center at=20
> http://go.microsoft.com/fwlink/events.asp.
> Data:
> 0000: 41 70 70 6c 69 63 61 74 Applicat
> 0008: 69 6f 6e 20 46 61 69 6c ion Fail
> 0010: 75 72 65 20 20 6f 75 74 ure out
> 0018: 6c 6f 6f 6b 2e 65 78 65 look.exe
> 0020: 20 31 30 2e 30 2e 34 35 10.0.45
> 0028: 31 30 2e 30 20 69 6e 20 10.0 in=20
> 0030: 6e 74 64 6c 6c 2e 64 6c ntdll.dl
> 0038: 6c 20 35 2e 31 2e 32 36 l 5.1.26
> 0040: 30 30 2e 31 31 30 36 20 00.1106=20
> 0048: 61 74 20 6f 66 66 73 65 at offse
> 0050: 74 20 30 30 30 30 31 62 t 00001b
> 0058: 61 61 0d 0a aa.. =20
>=20
>=20
> There is not update on either available on Knowledgebase.
> >-----Original Message-----
> >Alan
> >
> >Are we talking about Windows Explorer, Internet Explorer,=20
> Outlook Express or Microsoft Outlook? You need to provide=20
> a copy of the Error Report and describe what you are doing=20
> when the error occurs!
> >
> >Look in Event Viewer for error messages?=20
> >
> >1. To open Event Viewer, click Start, click Control=20
> Panel, double-click Administrative Tools, double-click=20
> Event Viewer and select System for system errors or=20
> Application for application errors. Look for Error in the=20
> Type column and double click on Error to reveal a=20
> Description of the error. This can be copied by using=20
> Clipboard Viewer (see later).
> >=20
> >2. Part of the Description of the error will include a=20
> link, which you should double click for further=20
> information and you can copy using copy and paste.
> >http://go.microsoft.com/fw.link/events.asp
> >(Please note the hyperlink above is for illustration=20
> purposes only)
> >
> >3. For some errors you will find "+ Related Knowledge=20
> Base Article", which if double clicked takes you to the=20
> Knowledge Base Article containing a suggested solution.
> >
> >There always seems to be a step 2 but not always a step=20
> 3.=20
> >
> >A tip for posting copies of Error Reports (Step 1). Run=20
> Event Viewer and double click on the error you want to=20
> copy. In the window which appears is a button resembling=20
> two pages. Double click the button and close Event Viewer.=20
> Now start your message ( email )and do a paste into the=20
> body of the message. This will paste the info from the=20
> Event Viewer Error Report complete with links into the=20
> message. Make sure this is the first paste after exiting=20
> from Event Viewer. It can be helpful to place a shortcut=20
> to Event Viewer on your Desktop.
> >
> >=20
> >~~~~~~
> >
> >
> >Hope this helps.
> >
> >Gerry
> >~~~~~~~~~~~~~~~~~~~~~~~~
> >FCA
>
> >Stourport, Worcs, England
> >Enquire, plan and execute.
> >~~~~~~~~~~~~~~~~~~~~~~~~
> >Please tell the newsgroup how any=20
> >suggested solution worked for you.
> >http://dts-l.org/goodpost.htm
> >~~~~~~~~~~~~~~~~~~~~~~~~
> >
> >"Alan Campbell" > wrote=20
> in message ...
> >> I had been using Windows XP Home on my Dell Inpiron=20
> 2500=20
> >> (900 mhz-256 mb) Laptop for over a year with no=20
> problems=20
> >> with Outlook Explorer. Friday I upgrade to Windows XP=20
> Pro=20
> >> to gain access to a network domain. Since then Outlook=20
> has=20
> >> crashed 3 times sending a report to Microsoft and=20
> >> restarting. Two times this happened at home while=20
> >> connected to cable modem through a wireless router, and=20
> >> once at work while connected to the network through the=20
> >> built-in 10/100 port. Any ideas? No new drivers other=20
> than=20
> >> the ones XP installed in the conversion. I redid all of=20
> >> the Windows critical and recommended updates after the=20
> >> installation.
> >.
> >

[Alan]

Yes, all available updates for both Windows XP Pro and MS
Office Standard have been installed. Interestingly enough
I had no problems with MS Outlook before upgrading from XP
Home to XP Pro, and no additional equipment or software
was added. Good thing is that I have not had any further
problems since the couple Sunday and one Monday.
If the problem persists/returns, I will follow your
suggestion and address it to an Outlook newsgroup.
Thanks for your help.

>-----Original Message-----
>Alan
>
>I searched Google and found one other seemingly identical
report of your problem.
>http://groups.google.com/groups?hl=en&lr=lang_en&ie=UTF-
8&oe=UTF-8&selm=uLpndLqrCHA.1668%40TK2MSFTNGP09
>
>There is no indication the problem was resolved.
>
>Have you installed all the updates for Office. There has
been at least one for Outlook post Service Pack 2.
Otherwise I can only suggest you post your problem to an
Outlook newsgroup.
>
>http://office.microsoft.com/productupdates/mainCatalog.asp
x
>
>~~~~~~
>
>
>Hope this helps.
>
>Gerry
>~~~~~~~~~~~~~~~~~~~~~~~~
>FCA

>Stourport, Worcs, England
>Enquire, plan and execute.
>~~~~~~~~~~~~~~~~~~~~~~~~
>Please tell the newsgroup how any
>suggested solution worked for you.
>http://dts-l.org/goodpost.htm
>~~~~~~~~~~~~~~~~~~~~~~~~
>
>
>"Alan" > wrote in message
...
>> There are two types of errors, one referencing bucket
>> 24770708 Event Type: Error
>> Event Source: Microsoft Office 10
>> Event Category: None
>> Event ID: 1001
>> Date: 5/5/2003
>> Time: 9:43:44 AM
>> User: N/A
>> Computer: ALAN
>> Description:
>> Fault bucket 24770708.
>>
>> For more information, see Help and Support Center at
>> http://go.microsoft.com/fwlink/events.asp.
>> Data:
>> 0000: 42 75 63 6b 65 74 3a 20 Bucket:
>> 0008: 32 34 37 37 30 37 30 38 24770708
>> 0010: 0d 0a ..
>>
>> The other referencing Microsoft Outlook
>>
>> Event Type: Error
>> Event Source: Microsoft Office 10
>> Event Category: None
>> Event ID: 1000
>> Date: 5/5/2003
>> Time: 9:39:33 AM
>> User: N/A
>> Computer: ALAN
>> Description:
>> Faulting application outlook.exe, version 10.0.4510.0,
>> faulting module ntdll.dll, version 5.1.2600.1106, fault
>> address 0x00001baa.
>>
>> For more information, see Help and Support Center at
>> http://go.microsoft.com/fwlink/events.asp.
>> Data:
>> 0000: 41 70 70 6c 69 63 61 74 Applicat
>> 0008: 69 6f 6e 20 46 61 69 6c ion Fail
>> 0010: 75 72 65 20 20 6f 75 74 ure out
>> 0018: 6c 6f 6f 6b 2e 65 78 65 look.exe
>> 0020: 20 31 30 2e 30 2e 34 35 10.0.45
>> 0028: 31 30 2e 30 20 69 6e 20 10.0 in
>> 0030: 6e 74 64 6c 6c 2e 64 6c ntdll.dl
>> 0038: 6c 20 35 2e 31 2e 32 36 l 5.1.26
>> 0040: 30 30 2e 31 31 30 36 20 00.1106
>> 0048: 61 74 20 6f 66 66 73 65 at offse
>> 0050: 74 20 30 30 30 30 31 62 t 00001b
>> 0058: 61 61 0d 0a aa..
>>
>>
>> There is not update on either available on
Knowledgebase.
>> >-----Original Message-----
>> >Alan
>> >
>> >Are we talking about Windows Explorer, Internet
Explorer,
>> Outlook Express or Microsoft Outlook? You need to
provide
>> a copy of the Error Report and describe what you are
doing
>> when the error occurs!
>> >
>> >Look in Event Viewer for error messages?
>> >
>> >1. To open Event Viewer, click Start, click Control
>> Panel, double-click Administrative Tools, double-click
>> Event Viewer and select System for system errors or
>> Application for application errors. Look for Error in
the
>> Type column and double click on Error to reveal a
>> Description of the error. This can be copied by using
>> Clipboard Viewer (see later).
>> >
>> >2. Part of the Description of the error will include a
>> link, which you should double click for further
>> information and you can copy using copy and paste.
>> >http://go.microsoft.com/fw.link/events.asp
>> >(Please note the hyperlink above is for illustration
>> purposes only)
>> >
>> >3. For some errors you will find "+ Related Knowledge
>> Base Article", which if double clicked takes you to the
>> Knowledge Base Article containing a suggested solution.
>> >
>> >There always seems to be a step 2 but not always a
step
>> 3.
>> >
>> >A tip for posting copies of Error Reports (Step 1).
Run
>> Event Viewer and double click on the error you want to
>> copy. In the window which appears is a button
resembling
>> two pages. Double click the button and close Event
Viewer.
>> Now start your message ( email )and do a paste into the
>> body of the message. This will paste the info from the
>> Event Viewer Error Report complete with links into the
>> message. Make sure this is the first paste after
exiting
>> from Event Viewer. It can be helpful to place a
shortcut
>> to Event Viewer on your Desktop.
>> >
>> >
>> >~~~~~~
>> >
>> >
>> >Hope this helps.
>> >
>> >Gerry
>> >~~~~~~~~~~~~~~~~~~~~~~~~
>> >FCA
>>
>> >Stourport, Worcs, England
>> >Enquire, plan and execute.
>> >~~~~~~~~~~~~~~~~~~~~~~~~
>> >Please tell the newsgroup how any
>> >suggested solution worked for you.
>> >http://dts-l.org/goodpost.htm
>> >~~~~~~~~~~~~~~~~~~~~~~~~
>> >
>> >"Alan Campbell" >
wrote
>> in message news:041301c31310$2a307890
...
>> >> I had been using Windows XP Home on my Dell Inpiron
>> 2500
>> >> (900 mhz-256 mb) Laptop for over a year with no
>> problems
>> >> with Outlook Explorer. Friday I upgrade to Windows
XP
>> Pro
>> >> to gain access to a network domain. Since then
Outlook
>> has
>> >> crashed 3 times sending a report to Microsoft and
>> >> restarting. Two times this happened at home while
>> >> connected to cable modem through a wireless router,
and
>> >> once at work while connected to the network through
the
>> >> built-in 10/100 port. Any ideas? No new drivers
other
>> than
>> >> the ones XP installed in the conversion. I redid all
of
>> >> the Windows critical and recommended updates after
the
>> >> installation.
>> >.
>> >
>.
>