Fax System Crash

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I’m running XP Media Edition.

Previously and just a few days ago everything worked. I know of no system
change in the meantime. Recently, upon the finish of every send fax using
the Windows Fax client. I thought it might have something to do with Norton
AV, but removed it and the crashes continue.

Fax Client thinks the fax was not sent and so attempts to re-deliver. If I
let it run, it continues to send the fax, crash the computer, re-start the
computer and re-send the fax.

The following Events are noted:

Fax completes, then blue screen and memory dump (set to Kernel). The faxes
do go through to their destination. This behavior is consistent whether I
use the Fax client printer or send a cover letter using Send a Fax (cover
letter only).

Microsoft Recovered from a Serious Error scenario says it is a driver
problem, but has no solution.

This is the System Event Properties for the Error:

Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 12/12/2005
Time: 10:59:41 AM
User: N/A
Computer: RON
Description:
Error code 00000019, parameter1 00000020, parameter2 8822fc00, parameter3
8822fd88, parameter4 0a310001.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 30 30 30 30 30 30 31 0000001
0020: 39 20 20 50 61 72 61 6d 9 Param
0028: 65 74 65 72 73 20 30 30 eters 00
0030: 30 30 30 30 32 30 2c 20 000020,
0038: 38 38 32 32 66 63 30 30 8822fc00
0040: 2c 20 38 38 32 32 66 64 , 8822fd
0048: 38 38 2c 20 30 61 33 31 88, 0a31
0050: 30 30 30 31 0001

Other times it looks like this:
Error code 00000019, parameter1 00000020, parameter2 896ef2a0, parameter3
896ef428, parameter4 0a310005.

Or:
Error code 00000019, parameter1 00000020, parameter2 896ef428, parameter3
896ef2A0, parameter4 (missed it).

After restart, I am also getting the following system error:

Event Type: Error
Event Source: EventSystem
Event Category: (50)
Event ID: 4609
Date: 12/12/2005
Time: 10:55:51 AM
User: N/A
Computer: RON
Description:
The COM+ Event System detected a bad return code during its internal
processing. HRESULT was C0000005 from line 44 of
d:\qxp_slp\com\com1x\src\events\tier1\eventsystemobj.cpp. Please contact
Microsoft Product Support Services to report this error.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.


None of the Knowledge Base articles dealing with error 0x00000019 have
anything to do with XP, but rather most with Server 2003.

I have uninstalled and reinstalled the Fax service with no change in
behavior. Crashes upon every use.

Does anyone have an idea how I might run this down?

Thanks,
Ron
 
Are you sure you removed Norton completely? It can be tough to get rid of
and most Norton products routinely disable fax.
The blue screen sure does sound like a driver problem. Have you checked for
a newer modem driver? Is your modem on the Windows XP HCL list?
 
Tried Restroring your system to a date prior to any changes made just before
this problem occured?
 
Hi Russ,
Removed Norton completely?

Well, no. I use Go Back 4.0 and so still have that and Live Update
installed. Also, I cannot verify I have remnant Registry entries. Do you
have a suggestion regarding this?

Re: Modem driver
I have the latest driver. However, I read somewhere that MS has issued a
driver with an earlier version number, with some functionality removed. I
suspect that this may have been done due to OS imcompatibility, but I have
not been able to find this older driver anywhere.

Any other thoughts would be very much appreciated.

Regards,
Ron



Russ Valentine said:
Are you sure you removed Norton completely? It can be tough to get rid of
and most Norton products routinely disable fax.
The blue screen sure does sound like a driver problem. Have you checked for
a newer modem driver? Is your modem on the Windows XP HCL list?
--
Russ Valentine
[MVP-Outlook]
Ronald K said:
I'm running XP Media Edition.

Previously and just a few days ago everything worked. I know of no system
change in the meantime. Recently, upon the finish of every send fax using
the Windows Fax client. I thought it might have something to do with
Norton
AV, but removed it and the crashes continue.

Fax Client thinks the fax was not sent and so attempts to re-deliver. If
I
let it run, it continues to send the fax, crash the computer, re-start the
computer and re-send the fax.

The following Events are noted:

Fax completes, then blue screen and memory dump (set to Kernel). The
faxes
do go through to their destination. This behavior is consistent whether I
use the Fax client printer or send a cover letter using Send a Fax (cover
letter only).

Microsoft Recovered from a Serious Error scenario says it is a driver
problem, but has no solution.

This is the System Event Properties for the Error:

Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 12/12/2005
Time: 10:59:41 AM
User: N/A
Computer: RON
Description:
Error code 00000019, parameter1 00000020, parameter2 8822fc00, parameter3
8822fd88, parameter4 0a310001.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 30 30 30 30 30 30 31 0000001
0020: 39 20 20 50 61 72 61 6d 9 Param
0028: 65 74 65 72 73 20 30 30 eters 00
0030: 30 30 30 30 32 30 2c 20 000020,
0038: 38 38 32 32 66 63 30 30 8822fc00
0040: 2c 20 38 38 32 32 66 64 , 8822fd
0048: 38 38 2c 20 30 61 33 31 88, 0a31
0050: 30 30 30 31 0001

Other times it looks like this:
Error code 00000019, parameter1 00000020, parameter2 896ef2a0, parameter3
896ef428, parameter4 0a310005.

Or:
Error code 00000019, parameter1 00000020, parameter2 896ef428, parameter3
896ef2A0, parameter4 (missed it).

After restart, I am also getting the following system error:

Event Type: Error
Event Source: EventSystem
Event Category: (50)
Event ID: 4609
Date: 12/12/2005
Time: 10:55:51 AM
User: N/A
Computer: RON
Description:
The COM+ Event System detected a bad return code during its internal
processing. HRESULT was C0000005 from line 44 of
d:\qxp_slp\com\com1x\src\events\tier1\eventsystemobj.cpp. Please contact
Microsoft Product Support Services to report this error.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.


None of the Knowledge Base articles dealing with error 0x00000019 have
anything to do with XP, but rather most with Server 2003.

I have uninstalled and reinstalled the Fax service with no change in
behavior. Crashes upon every use.

Does anyone have an idea how I might run this down?

Thanks,
Ron
Click to expand...
Click to expand...
 
No. I have no solutions to the myriad problems Norton's software has wreaked
upon the Fax Service. I sure wish they did.
Windows XP Fax is very intolerant of modem drivers. If the driver you are
using is on the Windows XP HCL list, there may be some recourse, but only if
you enable extensive PSS and debug logging procedures to pinpoint the
problem for Microsoft. --
Russ Valentine
[MVP-Outlook]
Ronald K said:
Hi Russ,
Removed Norton completely?

Well, no. I use Go Back 4.0 and so still have that and Live Update
installed. Also, I cannot verify I have remnant Registry entries. Do you
have a suggestion regarding this?

Re: Modem driver
I have the latest driver. However, I read somewhere that MS has issued a
driver with an earlier version number, with some functionality removed. I
suspect that this may have been done due to OS imcompatibility, but I have
not been able to find this older driver anywhere.

Any other thoughts would be very much appreciated.

Regards,
Ron



Russ Valentine said:
Are you sure you removed Norton completely? It can be tough to get rid of
and most Norton products routinely disable fax.
The blue screen sure does sound like a driver problem. Have you checked
for
a newer modem driver? Is your modem on the Windows XP HCL list?
--
Russ Valentine
[MVP-Outlook]
Ronald K said:
I'm running XP Media Edition.

Previously and just a few days ago everything worked. I know of no
system
change in the meantime. Recently, upon the finish of every send fax
using
the Windows Fax client. I thought it might have something to do with
Norton
AV, but removed it and the crashes continue.

Fax Client thinks the fax was not sent and so attempts to re-deliver.
If
I
let it run, it continues to send the fax, crash the computer, re-start
the
computer and re-send the fax.

The following Events are noted:

Fax completes, then blue screen and memory dump (set to Kernel). The
faxes
do go through to their destination. This behavior is consistent
whether I
use the Fax client printer or send a cover letter using Send a Fax
(cover
letter only).

Microsoft Recovered from a Serious Error scenario says it is a driver
problem, but has no solution.

This is the System Event Properties for the Error:

Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 12/12/2005
Time: 10:59:41 AM
User: N/A
Computer: RON
Description:
Error code 00000019, parameter1 00000020, parameter2 8822fc00,
parameter3
8822fd88, parameter4 0a310001.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 30 30 30 30 30 30 31 0000001
0020: 39 20 20 50 61 72 61 6d 9 Param
0028: 65 74 65 72 73 20 30 30 eters 00
0030: 30 30 30 30 32 30 2c 20 000020,
0038: 38 38 32 32 66 63 30 30 8822fc00
0040: 2c 20 38 38 32 32 66 64 , 8822fd
0048: 38 38 2c 20 30 61 33 31 88, 0a31
0050: 30 30 30 31 0001

Other times it looks like this:
Error code 00000019, parameter1 00000020, parameter2 896ef2a0,
parameter3
896ef428, parameter4 0a310005.

Or:
Error code 00000019, parameter1 00000020, parameter2 896ef428,
parameter3
896ef2A0, parameter4 (missed it).

After restart, I am also getting the following system error:

Event Type: Error
Event Source: EventSystem
Event Category: (50)
Event ID: 4609
Date: 12/12/2005
Time: 10:55:51 AM
User: N/A
Computer: RON
Description:
The COM+ Event System detected a bad return code during its internal
processing. HRESULT was C0000005 from line 44 of
d:\qxp_slp\com\com1x\src\events\tier1\eventsystemobj.cpp. Please
contact
Microsoft Product Support Services to report this error.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.


None of the Knowledge Base articles dealing with error 0x00000019 have
anything to do with XP, but rather most with Server 2003.

I have uninstalled and reinstalled the Fax service with no change in
behavior. Crashes upon every use.

Does anyone have an idea how I might run this down?

Thanks,
Ron
Click to expand...
Click to expand...
Click to expand...
 
Thanks for the insight, Russ.

Regards,
Ron

Russ Valentine said:
No. I have no solutions to the myriad problems Norton's software has wreaked
upon the Fax Service. I sure wish they did.
Windows XP Fax is very intolerant of modem drivers. If the driver you are
using is on the Windows XP HCL list, there may be some recourse, but only if
you enable extensive PSS and debug logging procedures to pinpoint the
problem for Microsoft. --
Russ Valentine
[MVP-Outlook]
Ronald K said:
Hi Russ,
Removed Norton completely?

Well, no. I use Go Back 4.0 and so still have that and Live Update
installed. Also, I cannot verify I have remnant Registry entries. Do you
have a suggestion regarding this?

Re: Modem driver
I have the latest driver. However, I read somewhere that MS has issued a
driver with an earlier version number, with some functionality removed. I
suspect that this may have been done due to OS imcompatibility, but I have
not been able to find this older driver anywhere.

Any other thoughts would be very much appreciated.

Regards,
Ron



Russ Valentine said:
Are you sure you removed Norton completely? It can be tough to get rid of
and most Norton products routinely disable fax.
The blue screen sure does sound like a driver problem. Have you checked
for
a newer modem driver? Is your modem on the Windows XP HCL list?
--
Russ Valentine
[MVP-Outlook]
I'm running XP Media Edition.

Previously and just a few days ago everything worked. I know of no
system
change in the meantime. Recently, upon the finish of every send fax
using
the Windows Fax client. I thought it might have something to do with
Norton
AV, but removed it and the crashes continue.

Fax Client thinks the fax was not sent and so attempts to re-deliver.
If
I
let it run, it continues to send the fax, crash the computer, re-start
the
computer and re-send the fax.

The following Events are noted:

Fax completes, then blue screen and memory dump (set to Kernel). The
faxes
do go through to their destination. This behavior is consistent
whether I
use the Fax client printer or send a cover letter using Send a Fax
(cover
letter only).

Microsoft Recovered from a Serious Error scenario says it is a driver
problem, but has no solution.

This is the System Event Properties for the Error:

Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 12/12/2005
Time: 10:59:41 AM
User: N/A
Computer: RON
Description:
Error code 00000019, parameter1 00000020, parameter2 8822fc00,
parameter3
8822fd88, parameter4 0a310001.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 30 30 30 30 30 30 31 0000001
0020: 39 20 20 50 61 72 61 6d 9 Param
0028: 65 74 65 72 73 20 30 30 eters 00
0030: 30 30 30 30 32 30 2c 20 000020,
0038: 38 38 32 32 66 63 30 30 8822fc00
0040: 2c 20 38 38 32 32 66 64 , 8822fd
0048: 38 38 2c 20 30 61 33 31 88, 0a31
0050: 30 30 30 31 0001

Other times it looks like this:
Error code 00000019, parameter1 00000020, parameter2 896ef2a0,
parameter3
896ef428, parameter4 0a310005.

Or:
Error code 00000019, parameter1 00000020, parameter2 896ef428,
parameter3
896ef2A0, parameter4 (missed it).

After restart, I am also getting the following system error:

Event Type: Error
Event Source: EventSystem
Event Category: (50)
Event ID: 4609
Date: 12/12/2005
Time: 10:55:51 AM
User: N/A
Computer: RON
Description:
The COM+ Event System detected a bad return code during its internal
processing. HRESULT was C0000005 from line 44 of
d:\qxp_slp\com\com1x\src\events\tier1\eventsystemobj.cpp. Please
contact
Microsoft Product Support Services to report this error.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.


None of the Knowledge Base articles dealing with error 0x00000019 have
anything to do with XP, but rather most with Server 2003.

I have uninstalled and reinstalled the Fax service with no change in
behavior. Crashes upon every use.

Does anyone have an idea how I might run this down?

Thanks,
Ron
Click to expand...
Click to expand...
Click to expand...
 
Is it possible to add a commercial fax client that would correct the problem?
Could you recommend one?

Many thanks,
Ron

Russ Valentine said:
No. I have no solutions to the myriad problems Norton's software has wreaked
upon the Fax Service. I sure wish they did.
Windows XP Fax is very intolerant of modem drivers. If the driver you are
using is on the Windows XP HCL list, there may be some recourse, but only if
you enable extensive PSS and debug logging procedures to pinpoint the
problem for Microsoft. --
Russ Valentine
[MVP-Outlook]
Ronald K said:
Hi Russ,
Removed Norton completely?

Well, no. I use Go Back 4.0 and so still have that and Live Update
installed. Also, I cannot verify I have remnant Registry entries. Do you
have a suggestion regarding this?

Re: Modem driver
I have the latest driver. However, I read somewhere that MS has issued a
driver with an earlier version number, with some functionality removed. I
suspect that this may have been done due to OS imcompatibility, but I have
not been able to find this older driver anywhere.

Any other thoughts would be very much appreciated.

Regards,
Ron



Russ Valentine said:
Are you sure you removed Norton completely? It can be tough to get rid of
and most Norton products routinely disable fax.
The blue screen sure does sound like a driver problem. Have you checked
for
a newer modem driver? Is your modem on the Windows XP HCL list?
--
Russ Valentine
[MVP-Outlook]
I'm running XP Media Edition.

Previously and just a few days ago everything worked. I know of no
system
change in the meantime. Recently, upon the finish of every send fax
using
the Windows Fax client. I thought it might have something to do with
Norton
AV, but removed it and the crashes continue.

Fax Client thinks the fax was not sent and so attempts to re-deliver.
If
I
let it run, it continues to send the fax, crash the computer, re-start
the
computer and re-send the fax.

The following Events are noted:

Fax completes, then blue screen and memory dump (set to Kernel). The
faxes
do go through to their destination. This behavior is consistent
whether I
use the Fax client printer or send a cover letter using Send a Fax
(cover
letter only).

Microsoft Recovered from a Serious Error scenario says it is a driver
problem, but has no solution.

This is the System Event Properties for the Error:

Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 12/12/2005
Time: 10:59:41 AM
User: N/A
Computer: RON
Description:
Error code 00000019, parameter1 00000020, parameter2 8822fc00,
parameter3
8822fd88, parameter4 0a310001.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 30 30 30 30 30 30 31 0000001
0020: 39 20 20 50 61 72 61 6d 9 Param
0028: 65 74 65 72 73 20 30 30 eters 00
0030: 30 30 30 30 32 30 2c 20 000020,
0038: 38 38 32 32 66 63 30 30 8822fc00
0040: 2c 20 38 38 32 32 66 64 , 8822fd
0048: 38 38 2c 20 30 61 33 31 88, 0a31
0050: 30 30 30 31 0001

Other times it looks like this:
Error code 00000019, parameter1 00000020, parameter2 896ef2a0,
parameter3
896ef428, parameter4 0a310005.

Or:
Error code 00000019, parameter1 00000020, parameter2 896ef428,
parameter3
896ef2A0, parameter4 (missed it).

After restart, I am also getting the following system error:

Event Type: Error
Event Source: EventSystem
Event Category: (50)
Event ID: 4609
Date: 12/12/2005
Time: 10:55:51 AM
User: N/A
Computer: RON
Description:
The COM+ Event System detected a bad return code during its internal
processing. HRESULT was C0000005 from line 44 of
d:\qxp_slp\com\com1x\src\events\tier1\eventsystemobj.cpp. Please
contact
Microsoft Product Support Services to report this error.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.


None of the Knowledge Base articles dealing with error 0x00000019 have
anything to do with XP, but rather most with Server 2003.

I have uninstalled and reinstalled the Fax service with no change in
behavior. Crashes upon every use.

Does anyone have an idea how I might run this down?

Thanks,
Ron
Click to expand...
Click to expand...
Click to expand...
 
Russ,
Could v.92 have something to do with a system crash? I have tried with both
call waiting enabled and disabled with the same result, but could there be
some other angle?

Regards,
Ron

Russ Valentine said:
No. I have no solutions to the myriad problems Norton's software has wreaked
upon the Fax Service. I sure wish they did.
Windows XP Fax is very intolerant of modem drivers. If the driver you are
using is on the Windows XP HCL list, there may be some recourse, but only if
you enable extensive PSS and debug logging procedures to pinpoint the
problem for Microsoft. --
Russ Valentine
[MVP-Outlook]
Ronald K said:
Hi Russ,
Removed Norton completely?

Well, no. I use Go Back 4.0 and so still have that and Live Update
installed. Also, I cannot verify I have remnant Registry entries. Do you
have a suggestion regarding this?

Re: Modem driver
I have the latest driver. However, I read somewhere that MS has issued a
driver with an earlier version number, with some functionality removed. I
suspect that this may have been done due to OS imcompatibility, but I have
not been able to find this older driver anywhere.

Any other thoughts would be very much appreciated.

Regards,
Ron



Russ Valentine said:
Are you sure you removed Norton completely? It can be tough to get rid of
and most Norton products routinely disable fax.
The blue screen sure does sound like a driver problem. Have you checked
for
a newer modem driver? Is your modem on the Windows XP HCL list?
--
Russ Valentine
[MVP-Outlook]
I'm running XP Media Edition.

Previously and just a few days ago everything worked. I know of no
system
change in the meantime. Recently, upon the finish of every send fax
using
the Windows Fax client. I thought it might have something to do with
Norton
AV, but removed it and the crashes continue.

Fax Client thinks the fax was not sent and so attempts to re-deliver.
If
I
let it run, it continues to send the fax, crash the computer, re-start
the
computer and re-send the fax.

The following Events are noted:

Fax completes, then blue screen and memory dump (set to Kernel). The
faxes
do go through to their destination. This behavior is consistent
whether I
use the Fax client printer or send a cover letter using Send a Fax
(cover
letter only).

Microsoft Recovered from a Serious Error scenario says it is a driver
problem, but has no solution.

This is the System Event Properties for the Error:

Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 12/12/2005
Time: 10:59:41 AM
User: N/A
Computer: RON
Description:
Error code 00000019, parameter1 00000020, parameter2 8822fc00,
parameter3
8822fd88, parameter4 0a310001.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 30 30 30 30 30 30 31 0000001
0020: 39 20 20 50 61 72 61 6d 9 Param
0028: 65 74 65 72 73 20 30 30 eters 00
0030: 30 30 30 30 32 30 2c 20 000020,
0038: 38 38 32 32 66 63 30 30 8822fc00
0040: 2c 20 38 38 32 32 66 64 , 8822fd
0048: 38 38 2c 20 30 61 33 31 88, 0a31
0050: 30 30 30 31 0001

Other times it looks like this:
Error code 00000019, parameter1 00000020, parameter2 896ef2a0,
parameter3
896ef428, parameter4 0a310005.

Or:
Error code 00000019, parameter1 00000020, parameter2 896ef428,
parameter3
896ef2A0, parameter4 (missed it).

After restart, I am also getting the following system error:

Event Type: Error
Event Source: EventSystem
Event Category: (50)
Event ID: 4609
Date: 12/12/2005
Time: 10:55:51 AM
User: N/A
Computer: RON
Description:
The COM+ Event System detected a bad return code during its internal
processing. HRESULT was C0000005 from line 44 of
d:\qxp_slp\com\com1x\src\events\tier1\eventsystemobj.cpp. Please
contact
Microsoft Product Support Services to report this error.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.


None of the Knowledge Base articles dealing with error 0x00000019 have
anything to do with XP, but rather most with Server 2003.

I have uninstalled and reinstalled the Fax service with no change in
behavior. Crashes upon every use.

Does anyone have an idea how I might run this down?

Thanks,
Ron
Click to expand...
Click to expand...
Click to expand...
 
v.92?
--
Russ Valentine
[MVP-Outlook]
Ronald K said:
Russ,
Could v.92 have something to do with a system crash? I have tried with
both
call waiting enabled and disabled with the same result, but could there be
some other angle?

Regards,
Ron

Russ Valentine said:
No. I have no solutions to the myriad problems Norton's software has
wreaked
upon the Fax Service. I sure wish they did.
Windows XP Fax is very intolerant of modem drivers. If the driver you are
using is on the Windows XP HCL list, there may be some recourse, but only
if
you enable extensive PSS and debug logging procedures to pinpoint the
problem for Microsoft. --
Russ Valentine
[MVP-Outlook]
Ronald K said:
Hi Russ,
Removed Norton completely?

Well, no. I use Go Back 4.0 and so still have that and Live Update
installed. Also, I cannot verify I have remnant Registry entries. Do
you
have a suggestion regarding this?

Re: Modem driver
I have the latest driver. However, I read somewhere that MS has issued
a
driver with an earlier version number, with some functionality removed.
I
suspect that this may have been done due to OS imcompatibility, but I
have
not been able to find this older driver anywhere.

Any other thoughts would be very much appreciated.

Regards,
Ron



:

Are you sure you removed Norton completely? It can be tough to get rid
of
and most Norton products routinely disable fax.
The blue screen sure does sound like a driver problem. Have you
checked
for
a newer modem driver? Is your modem on the Windows XP HCL list?
--
Russ Valentine
[MVP-Outlook]
I'm running XP Media Edition.

Previously and just a few days ago everything worked. I know of no
system
change in the meantime. Recently, upon the finish of every send fax
using
the Windows Fax client. I thought it might have something to do
with
Norton
AV, but removed it and the crashes continue.

Fax Client thinks the fax was not sent and so attempts to
re-deliver.
If
I
let it run, it continues to send the fax, crash the computer,
re-start
the
computer and re-send the fax.

The following Events are noted:

Fax completes, then blue screen and memory dump (set to Kernel).
The
faxes
do go through to their destination. This behavior is consistent
whether I
use the Fax client printer or send a cover letter using Send a Fax
(cover
letter only).

Microsoft Recovered from a Serious Error scenario says it is a
driver
problem, but has no solution.

This is the System Event Properties for the Error:

Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 12/12/2005
Time: 10:59:41 AM
User: N/A
Computer: RON
Description:
Error code 00000019, parameter1 00000020, parameter2 8822fc00,
parameter3
8822fd88, parameter4 0a310001.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 30 30 30 30 30 30 31 0000001
0020: 39 20 20 50 61 72 61 6d 9 Param
0028: 65 74 65 72 73 20 30 30 eters 00
0030: 30 30 30 30 32 30 2c 20 000020,
0038: 38 38 32 32 66 63 30 30 8822fc00
0040: 2c 20 38 38 32 32 66 64 , 8822fd
0048: 38 38 2c 20 30 61 33 31 88, 0a31
0050: 30 30 30 31 0001

Other times it looks like this:
Error code 00000019, parameter1 00000020, parameter2 896ef2a0,
parameter3
896ef428, parameter4 0a310005.

Or:
Error code 00000019, parameter1 00000020, parameter2 896ef428,
parameter3
896ef2A0, parameter4 (missed it).

After restart, I am also getting the following system error:

Event Type: Error
Event Source: EventSystem
Event Category: (50)
Event ID: 4609
Date: 12/12/2005
Time: 10:55:51 AM
User: N/A
Computer: RON
Description:
The COM+ Event System detected a bad return code during its internal
processing. HRESULT was C0000005 from line 44 of
d:\qxp_slp\com\com1x\src\events\tier1\eventsystemobj.cpp. Please
contact
Microsoft Product Support Services to report this error.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.


None of the Knowledge Base articles dealing with error 0x00000019
have
anything to do with XP, but rather most with Server 2003.

I have uninstalled and reinstalled the Fax service with no change in
behavior. Crashes upon every use.

Does anyone have an idea how I might run this down?

Thanks,
Ron
Click to expand...
Click to expand...
Click to expand...
 
Back
Top