Fax Console Crashes

  • Thread starter Thread starter Beth Laird
  • Start date Start date
B

Beth Laird

My Fax console crashes only upon closing it---but only on one of the two
accounts. Get blue screen with "Page Fault in Non-Paged area," then it
dumps the memory to disk, and then reboots back up fine. Then it goes to
Online Crash analysis where I get the report "Error caused by Device
Driver." Can anyone help me solve this problem please? Thanks
 
Unfortunately, Windows XP Fax has proven to be incompatible with many common
modems and drivers, particularly older ones, even if the manufacturers claim
they are "compatible" with Windows XP. Modem incompatibility is not apparent
during installation or the initial setup. It only becomes apparent when you
first try to send or receive a fax. The Fax Service will dial or will answer
an incoming fax but then fail with any of a number of unhelpful error
messages such as "Line is busy," "There is no answer," or "Reception error."
There will be nothing in Event Viewer to give a clue as to where the problem
might lie.

These errors have been nearly impossible to track down. To do so requires
enabling both PSS and debug logging of fax transmissions, both of which
require fairly extensive registry changes. For the time being, the best
advice is to attempt to use XP Fax only if you have a modem that is listed
on the Windows XP Hardware Compatibility List and using the latest drivers.
 
The blue screen that you see is because of a badly written driver. The
driver name will be shown while the blue screen appears. What is that name?

What modem are you using?

Some possible solutions that you can try out:
Check out the modem manufacturers support site and see if there are any
updated drivers.

Please revert back with any further questions.

--
Shyama Hembram
Microsoft Printing, Imaging and Fax Team
This posting is provided "AS IS" with no warranties, and confers no rights.
Please do not send email directly to this alias. This alias is for newsgroup
purposes only.
 
I just ran the crash again to get the driver name, but it doesn't give a
driver name on the blue screen. This is how it reads:

A problem has been detected and windows has been shut down to prevent damage
to your computer.
PAGE_FAULT_IN_NONPAGED_AREA
Technical information:
Stop: 0x00000050 (0xFFBFFFF8, 0x00000000, 0x8053434E, 0x00000000)
(*note: these numbers are the same for every crash*)
Beginning dump of physical memory
Dumping physical memory to disk....then it counts to about 100 and reboots,
and goes to MS On-Line Crash Analysis---"Error Caused by Device Driver"
(*note: that's most of it---it also says to check newly installed
hardware and software, etc., and contact my administrator, etc.)

I have a U.S. Robotics 56K FAX INT V5.19.1, Product ID 66297700; Model #2977
(it is a OEM modem)
I ran the modem detector to get this information. It is a PCI modem,
purchased in Aug 2001.
I checked the USR website for driver update, and I have the newest driver
update (dated July 1999)

If it's the driver that's causing the problem---the modem's old
(manufactured 1999), then I should buy a new modem. I want to find out the
cause, before I go to unnecessary expense. I called Microsoft on 9/26/03
and was on the phone for over 6 hrs. with NO resolution, plus I used up one
of my WinXP incidences----SRX030926603419, Wayne in Nova Scotia was my tech.
He never called me back---we got disconnected after 6 hrs. invested into
resolving the problem. Frustrating... I should have gone to newsgroups
first!
Thank you for your help!!!!!
 
This is a very common driver problem and usually the suspected driver's name
is shown in this kind of problems. You can try few more steps to identify
the faulty component. The answers to the following questions/tasks will lead
to something.
1. When the system boots up, look for the faulty driver name in the
eventlog.
2. Check that when you disable the modem from device manager you no longer
see this error.
3. Make sure that you have the latest service packs from windows update and
try to get this error.

--
Shyama Hembram
Microsoft Printing, Imaging and Fax Team
This posting is provided "AS IS" with no warranties, and confers no rights.
Please do not send email directly to this alias. This alias is for newsgroup
purposes only.
 
Shyama,
1. The system boots up pretty darn fast & it's hard to read everything so
quickly, but I booted up at least 10 times to look for a driver name and
didn't see one named.
2. When I disabled the USR modem on the account that was crashing, the
system immediately crashed when I tried to close the Device Manager. Blue
screen with very same error message.
3. I do have ALL the updates installed on my computer. I run Win Update
weekly.

Any more suggestions? Thank you very much for your advice! It is greatly
appreciated!
Beth
 
Back
Top