untrackable error

[Annoyed and perplexed]

I found this absolutely brilliant response to
another "new users" question so I took their advice and
checked my Event Viewer for an error I've been getting.

====================================
Error code 1000008e, parameter1 c0000005, parameter2
fbd7b977, parameter3 f3237114, parameter4 00000000.
=====================================

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

I found this text flagged and went to the site. The
site reports:

There is no additional information about this issue in
the Error and Event Log Messages or Knowledge Base
databases at this time. You can use the links in the
Support area to determine whether any additional
information might be available elsewhere.

So I click on the link supplied and here's what it says

SYMPTOMS
You may experience any of the following symptoms:
Your computer automatically restarts.
After you log on, you receive the following error
message:

Microsoft Windows
The system has recovered from a serious error.
A log of this error has been created.
Please tell Microsoft about this problem.
We have created an error report that you can send to help
us improve Microsoft Windows. We will treat this report
as confidential and anonymous.
To see what data this error report contains, click here.
If the error message still appears and if you want to see
the data that the error report contains, click the click
here link at the bottom of the message box. You then see
error signature information that may be similar to:

BCCode : 00000050 BCP1 : 0xffffffe0 BCP2 : 0x00000001
BCP3 : 0xf30da010 BCP4 : 0x00000000 OSVer : 5_1_2600 SP :
0_0 Product : 256_1
You receive the following stop error message on a blue
screen:

A problem has been detected and Windows has been shut
down to prevent damage to your computer
Technical information:

*** STOP: 0x00000050 (0xffffffe0, 0x0x00000001,
0xf30da010, 0x00000000)
PAGE_FAULT_IN_NONPAGED_AREA
When you view the system log in Event Viewer, you may
notice an event ID 1003 entry with information that is
similar to:
Date: date
Source: System
Error Time: time
Category: (102)
Type: Error
Event ID: 1003
User: N/A
Computer: computer
Description: Error code 00000050, parameter1 0xffffffe0,
parameter2 0x00000001, parameter3 0xf30da010, parameter4
0x00000000. 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 35 00000MN 0020: 30
20 20 50 61 72 61 6d 0 Param 0028: 65 74 65 72 73 20 66
66 eters ff 0030: 66 66 66 66 64 31 2c

Notes
The symptoms of a stop error vary according to the
failure options of your computer system. For additional
information about how to configure system failure
options, click the following article number to view the
article in the Microsoft Knowledge Base:
307973 HOW TO: Configure System Failure and Recovery
Options in Windows

The four parameters that are included in the error
signature information (BCP x), and inside the parentheses
of the technical information for the Stop error may vary
according to the computer's configuration.
Not all Stop 0x00000050 errors are caused by the problem
that is described in the "Cause" section of this article.
CAUSE
This problem occurs because the driver for the USB
Universal Reader from Lexar Media, Inc is not compatible
with Windows XP.
RESOLUTION
To resolve this problem, obtain and install the latest
driver from Lexar Media, Inc.
STATUS
Lexar Media, Inc. has confirmed that this problem occurs
when you use a version of their Sausb.sys driver with
Windows XP that is earlier than version 4.6.


====================================
I don't have anything on my pC that resembles
Sausb.sys.... any ideas?

[Mary Sauer]

Found this:
USB: Lexar Media Combo Digital Film Reader (USB). There is a problem with the
SAUSB.SYS file, apparently part of the Win98 SE driver set for this device, retained
during an upgrade to Win XP. Deleting the file solved the problem. The newer version
4.3 SAUSB.SYS driver from Lexar's Web site works perfectly, and does not cause a
shutdown problem. (Tip from correspondent Eric Brown.) Though one correspondent
reported that the even newer version 4.5 driver (SAUSBI.SYS) also can be used in Win
XP , Lexar says this driver doesn't work on XP. One correspondent has confirmed that
this matches his experience in trying (unsuccessfully) to use 4.5 on both Widows 2000
and XP.

And this:
http://www.usb-drivers.com/drivers/54/54144.htm


Error Message: STOP 0x00000050 (0xffffffe0, 0x00000001, 0xf30da010, 0x00000000)
PAGE_FAULT_IN_NONPAGED_AREA
http://support.microsoft.com/?kbid=817197



--
Mary Sauer MS MVP
http://office.microsoft.com/clipart/
http://www.mvps.org/msauer/getting_started.htm
"Annoyed and perplexed" > wrote in message
...
> I found this absolutely brilliant response to
> another "new users" question so I took their advice and
> checked my Event Viewer for an error I've been getting.
>
> ====================================
> Error code 1000008e, parameter1 c0000005, parameter2
> fbd7b977, parameter3 f3237114, parameter4 00000000.
> =====================================
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
>
> I found this text flagged and went to the site. The
> site reports:
>
> There is no additional information about this issue in
> the Error and Event Log Messages or Knowledge Base
> databases at this time. You can use the links in the
> Support area to determine whether any additional
> information might be available elsewhere.
>
> So I click on the link supplied and here's what it says
>
> SYMPTOMS
> You may experience any of the following symptoms:
> Your computer automatically restarts.
> After you log on, you receive the following error
> message:
>
> Microsoft Windows
> The system has recovered from a serious error.
> A log of this error has been created.
> Please tell Microsoft about this problem.
> We have created an error report that you can send to help
> us improve Microsoft Windows. We will treat this report
> as confidential and anonymous.
> To see what data this error report contains, click here.
> If the error message still appears and if you want to see
> the data that the error report contains, click the click
> here link at the bottom of the message box. You then see
> error signature information that may be similar to:
>
> BCCode : 00000050 BCP1 : 0xffffffe0 BCP2 : 0x00000001
> BCP3 : 0xf30da010 BCP4 : 0x00000000 OSVer : 5_1_2600 SP :
> 0_0 Product : 256_1
> You receive the following stop error message on a blue
> screen:
>
> A problem has been detected and Windows has been shut
> down to prevent damage to your computer
> Technical information:
>
> *** STOP: 0x00000050 (0xffffffe0, 0x0x00000001,
> 0xf30da010, 0x00000000)
> PAGE_FAULT_IN_NONPAGED_AREA
> When you view the system log in Event Viewer, you may
> notice an event ID 1003 entry with information that is
> similar to:
> Date: date
> Source: System
> Error Time: time
> Category: (102)
> Type: Error
> Event ID: 1003
> User: N/A
> Computer: computer
> Description: Error code 00000050, parameter1 0xffffffe0,
> parameter2 0x00000001, parameter3 0xf30da010, parameter4
> 0x00000000. 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 35 00000MN 0020: 30
> 20 20 50 61 72 61 6d 0 Param 0028: 65 74 65 72 73 20 66
> 66 eters ff 0030: 66 66 66 66 64 31 2c
>
> Notes
> The symptoms of a stop error vary according to the
> failure options of your computer system. For additional
> information about how to configure system failure
> options, click the following article number to view the
> article in the Microsoft Knowledge Base:
> 307973 HOW TO: Configure System Failure and Recovery
> Options in Windows
>
> The four parameters that are included in the error
> signature information (BCP x), and inside the parentheses
> of the technical information for the Stop error may vary
> according to the computer's configuration.
> Not all Stop 0x00000050 errors are caused by the problem
> that is described in the "Cause" section of this article.
> CAUSE
> This problem occurs because the driver for the USB
> Universal Reader from Lexar Media, Inc is not compatible
> with Windows XP.
> RESOLUTION
> To resolve this problem, obtain and install the latest
> driver from Lexar Media, Inc.
> STATUS
> Lexar Media, Inc. has confirmed that this problem occurs
> when you use a version of their Sausb.sys driver with
> Windows XP that is earlier than version 4.6.
>
>
> ====================================
> I don't have anything on my pC that resembles
> Sausb.sys.... any ideas?
>

[Annoyed and Perplexed]

Mary,

I don't have a Lexar Media Combo Digital Film Reader. I
did a search and couldn't find an SAUSB.SYS file so I
don't think this is the problem.
>-----Original Message-----
>Found this:
>USB: Lexar Media Combo Digital Film Reader (USB). There
is a problem with the
>SAUSB.SYS file, apparently part of the Win98 SE driver
set for this device, retained
>during an upgrade to Win XP. Deleting the file solved
the problem. The newer version
>4.3 SAUSB.SYS driver from Lexar's Web site works
perfectly, and does not cause a
>shutdown problem. (Tip from correspondent Eric Brown.)
Though one correspondent
>reported that the even newer version 4.5 driver
(SAUSBI.SYS) also can be used in Win
>XP , Lexar says this driver doesn't work on XP. One
correspondent has confirmed that
>this matches his experience in trying (unsuccessfully)
to use 4.5 on both Widows 2000
>and XP.
>
>And this:
>http://www.usb-drivers.com/drivers/54/54144.htm
>
>
>Error Message: STOP 0x00000050 (0xffffffe0, 0x00000001,
0xf30da010, 0x00000000)
>PAGE_FAULT_IN_NONPAGED_AREA
>http://support.microsoft.com/?kbid=817197
>
>
>
>--
>Mary Sauer MS MVP
>http://office.microsoft.com/clipart/
>http://www.mvps.org/msauer/getting_started.htm
>"Annoyed and perplexed" > wrote in
message
...
>> I found this absolutely brilliant response to
>> another "new users" question so I took their advice and
>> checked my Event Viewer for an error I've been getting.
>>
>> ====================================
>> Error code 1000008e, parameter1 c0000005, parameter2
>> fbd7b977, parameter3 f3237114, parameter4 00000000.
>> =====================================
>>
>> For more information, see Help and Support Center at
>> http://go.microsoft.com/fwlink/events.asp.
>>
>> I found this text flagged and went to the site. The
>> site reports:
>>
>> There is no additional information about this issue in
>> the Error and Event Log Messages or Knowledge Base
>> databases at this time. You can use the links in the
>> Support area to determine whether any additional
>> information might be available elsewhere.
>>
>> So I click on the link supplied and here's what it says
>>
>> SYMPTOMS
>> You may experience any of the following symptoms:
>> Your computer automatically restarts.
>> After you log on, you receive the following error
>> message:
>>
>> Microsoft Windows
>> The system has recovered from a serious error.
>> A log of this error has been created.
>> Please tell Microsoft about this problem.
>> We have created an error report that you can send to
help
>> us improve Microsoft Windows. We will treat this report
>> as confidential and anonymous.
>> To see what data this error report contains, click
here.
>> If the error message still appears and if you want to
see
>> the data that the error report contains, click the
click
>> here link at the bottom of the message box. You then
see
>> error signature information that may be similar to:
>>
>> BCCode : 00000050 BCP1 : 0xffffffe0 BCP2 : 0x00000001
>> BCP3 : 0xf30da010 BCP4 : 0x00000000 OSVer : 5_1_2600
SP :
>> 0_0 Product : 256_1
>> You receive the following stop error message on a blue
>> screen:
>>
>> A problem has been detected and Windows has been shut
>> down to prevent damage to your computer
>> Technical information:
>>
>> *** STOP: 0x00000050 (0xffffffe0, 0x0x00000001,
>> 0xf30da010, 0x00000000)
>> PAGE_FAULT_IN_NONPAGED_AREA
>> When you view the system log in Event Viewer, you may
>> notice an event ID 1003 entry with information that is
>> similar to:
>> Date: date
>> Source: System
>> Error Time: time
>> Category: (102)
>> Type: Error
>> Event ID: 1003
>> User: N/A
>> Computer: computer
>> Description: Error code 00000050, parameter1
0xffffffe0,
>> parameter2 0x00000001, parameter3 0xf30da010,
parameter4
>> 0x00000000. 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 35 00000MN 0020: 30
>> 20 20 50 61 72 61 6d 0 Param 0028: 65 74 65 72 73 20 66
>> 66 eters ff 0030: 66 66 66 66 64 31 2c
>>
>> Notes
>> The symptoms of a stop error vary according to the
>> failure options of your computer system. For additional
>> information about how to configure system failure
>> options, click the following article number to view the
>> article in the Microsoft Knowledge Base:
>> 307973 HOW TO: Configure System Failure and Recovery
>> Options in Windows
>>
>> The four parameters that are included in the error
>> signature information (BCP x), and inside the
parentheses
>> of the technical information for the Stop error may
vary
>> according to the computer's configuration.
>> Not all Stop 0x00000050 errors are caused by the
problem
>> that is described in the "Cause" section of this
article.
>> CAUSE
>> This problem occurs because the driver for the USB
>> Universal Reader from Lexar Media, Inc is not
compatible
>> with Windows XP.
>> RESOLUTION
>> To resolve this problem, obtain and install the latest
>> driver from Lexar Media, Inc.
>> STATUS
>> Lexar Media, Inc. has confirmed that this problem
occurs
>> when you use a version of their Sausb.sys driver with
>> Windows XP that is earlier than version 4.6.
>>
>>
>> ====================================
>> I don't have anything on my pC that resembles
>> Sausb.sys.... any ideas?
>>
>
>
>.
>

[Rick \Nutcase\ Rogers]

Hi,

Most likely cause: Faulty, mismatched, or incompatible ram sticks. If you
want to check the memory, there are free programs here:

http://www.simmtester.com/page/products/doc/download.asp
http://oca.microsoft.com/en/windiag.asp

But keep in kind that a thorough test can only be done with test equipment
at a computer shop.

--
Best of Luck,

Rick Rogers aka "Nutcase" MS-MVP - Win9x
Windows isn't rocket science! That's my other hobby!
http://mvp.support.microsoft.com/
Associate Expert - WinXP - Expert Zone
www.microsoft.com/windowsxp/expertzone
Win98 Help - www.rickrogers.org

"Annoyed and perplexed" > wrote in message
...
> I found this absolutely brilliant response to
> another "new users" question so I took their advice and
> checked my Event Viewer for an error I've been getting.
>
> ====================================
> Error code 1000008e, parameter1 c0000005, parameter2
> fbd7b977, parameter3 f3237114, parameter4 00000000.
> =====================================
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
>
> I found this text flagged and went to the site. The
> site reports:
>
> There is no additional information about this issue in
> the Error and Event Log Messages or Knowledge Base
> databases at this time. You can use the links in the
> Support area to determine whether any additional
> information might be available elsewhere.
>
> So I click on the link supplied and here's what it says
>
> SYMPTOMS
> You may experience any of the following symptoms:
> Your computer automatically restarts.
> After you log on, you receive the following error
> message:
>
> Microsoft Windows
> The system has recovered from a serious error.
> A log of this error has been created.
> Please tell Microsoft about this problem.
> We have created an error report that you can send to help
> us improve Microsoft Windows. We will treat this report
> as confidential and anonymous.
> To see what data this error report contains, click here.
> If the error message still appears and if you want to see
> the data that the error report contains, click the click
> here link at the bottom of the message box. You then see
> error signature information that may be similar to:
>
> BCCode : 00000050 BCP1 : 0xffffffe0 BCP2 : 0x00000001
> BCP3 : 0xf30da010 BCP4 : 0x00000000 OSVer : 5_1_2600 SP :
> 0_0 Product : 256_1
> You receive the following stop error message on a blue
> screen:
>
> A problem has been detected and Windows has been shut
> down to prevent damage to your computer
> Technical information:
>
> *** STOP: 0x00000050 (0xffffffe0, 0x0x00000001,
> 0xf30da010, 0x00000000)
> PAGE_FAULT_IN_NONPAGED_AREA
> When you view the system log in Event Viewer, you may
> notice an event ID 1003 entry with information that is
> similar to:
> Date: date
> Source: System
> Error Time: time
> Category: (102)
> Type: Error
> Event ID: 1003
> User: N/A
> Computer: computer
> Description: Error code 00000050, parameter1 0xffffffe0,
> parameter2 0x00000001, parameter3 0xf30da010, parameter4
> 0x00000000. 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 35 00000MN 0020: 30
> 20 20 50 61 72 61 6d 0 Param 0028: 65 74 65 72 73 20 66
> 66 eters ff 0030: 66 66 66 66 64 31 2c
>
> Notes
> The symptoms of a stop error vary according to the
> failure options of your computer system. For additional
> information about how to configure system failure
> options, click the following article number to view the
> article in the Microsoft Knowledge Base:
> 307973 HOW TO: Configure System Failure and Recovery
> Options in Windows
>
> The four parameters that are included in the error
> signature information (BCP x), and inside the parentheses
> of the technical information for the Stop error may vary
> according to the computer's configuration.
> Not all Stop 0x00000050 errors are caused by the problem
> that is described in the "Cause" section of this article.
> CAUSE
> This problem occurs because the driver for the USB
> Universal Reader from Lexar Media, Inc is not compatible
> with Windows XP.
> RESOLUTION
> To resolve this problem, obtain and install the latest
> driver from Lexar Media, Inc.
> STATUS
> Lexar Media, Inc. has confirmed that this problem occurs
> when you use a version of their Sausb.sys driver with
> Windows XP that is earlier than version 4.6.
>
>
> ====================================
> I don't have anything on my pC that resembles
> Sausb.sys.... any ideas?
>

[Annoyed and Perplexed]

Well I got the crash to happen... or so should I say, IT
happened.

The first thing I was was

msmsgs.exe - Application error

The instruction at "0x5d39e155" referenced memory
at "0x00000000". The memory could not be "read".

Click on OK to terminate the program
Click on CANCEL to debug the program

So I clicked OK... then up comes a similar message for
OPXPApp.exe but before I could write down the exact
message, I get a BSOD. Since I'd tweaked the settings,
the BSOD stayed on my screen allowing me to write down
the tech info. Here's what it said:

Technical Information

***STOP: 0x0000008E (0xC0000005, 0xFBA88977, 0xF2E23114,
0x00000000)

***ALCXWDM.SYS - Address FBA88977 base at FBA25000, Date
Stamp 3efffd5e


So it looks like I've got a problem with a drive. Now
it's off to google to see if I can find the source. Me
thinks its my sound card but I'll find out shortly.
>-----Original Message-----
>Hi,
>
>Most likely cause: Faulty, mismatched, or incompatible
ram sticks. If you
>want to check the memory, there are free programs here:
>
>http://www.simmtester.com/page/products/doc/download.asp
>http://oca.microsoft.com/en/windiag.asp
>
>But keep in kind that a thorough test can only be done
with test equipment
>at a computer shop.
>
>--
>Best of Luck,
>
>Rick Rogers aka "Nutcase" MS-MVP - Win9x
>Windows isn't rocket science! That's my other hobby!
>http://mvp.support.microsoft.com/
>Associate Expert - WinXP - Expert Zone
>www.microsoft.com/windowsxp/expertzone
>Win98 Help - www.rickrogers.org
>
>"Annoyed and perplexed" > wrote in
message
...
>> I found this absolutely brilliant response to
>> another "new users" question so I took their advice and
>> checked my Event Viewer for an error I've been getting.
>>
>> ====================================
>> Error code 1000008e, parameter1 c0000005, parameter2
>> fbd7b977, parameter3 f3237114, parameter4 00000000.
>> =====================================
>>
>> For more information, see Help and Support Center at
>> http://go.microsoft.com/fwlink/events.asp.
>>
>> I found this text flagged and went to the site. The
>> site reports:
>>
>> There is no additional information about this issue in
>> the Error and Event Log Messages or Knowledge Base
>> databases at this time. You can use the links in the
>> Support area to determine whether any additional
>> information might be available elsewhere.
>>
>> So I click on the link supplied and here's what it says
>>
>> SYMPTOMS
>> You may experience any of the following symptoms:
>> Your computer automatically restarts.
>> After you log on, you receive the following error
>> message:
>>
>> Microsoft Windows
>> The system has recovered from a serious error.
>> A log of this error has been created.
>> Please tell Microsoft about this problem.
>> We have created an error report that you can send to
help
>> us improve Microsoft Windows. We will treat this report
>> as confidential and anonymous.
>> To see what data this error report contains, click
here.
>> If the error message still appears and if you want to
see
>> the data that the error report contains, click the
click
>> here link at the bottom of the message box. You then
see
>> error signature information that may be similar to:
>>
>> BCCode : 00000050 BCP1 : 0xffffffe0 BCP2 : 0x00000001
>> BCP3 : 0xf30da010 BCP4 : 0x00000000 OSVer : 5_1_2600
SP :
>> 0_0 Product : 256_1
>> You receive the following stop error message on a blue
>> screen:
>>
>> A problem has been detected and Windows has been shut
>> down to prevent damage to your computer
>> Technical information:
>>
>> *** STOP: 0x00000050 (0xffffffe0, 0x0x00000001,
>> 0xf30da010, 0x00000000)
>> PAGE_FAULT_IN_NONPAGED_AREA
>> When you view the system log in Event Viewer, you may
>> notice an event ID 1003 entry with information that is
>> similar to:
>> Date: date
>> Source: System
>> Error Time: time
>> Category: (102)
>> Type: Error
>> Event ID: 1003
>> User: N/A
>> Computer: computer
>> Description: Error code 00000050, parameter1
0xffffffe0,
>> parameter2 0x00000001, parameter3 0xf30da010,
parameter4
>> 0x00000000. 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 35 00000MN 0020: 30
>> 20 20 50 61 72 61 6d 0 Param 0028: 65 74 65 72 73 20 66
>> 66 eters ff 0030: 66 66 66 66 64 31 2c
>>
>> Notes
>> The symptoms of a stop error vary according to the
>> failure options of your computer system. For additional
>> information about how to configure system failure
>> options, click the following article number to view the
>> article in the Microsoft Knowledge Base:
>> 307973 HOW TO: Configure System Failure and Recovery
>> Options in Windows
>>
>> The four parameters that are included in the error
>> signature information (BCP x), and inside the
parentheses
>> of the technical information for the Stop error may
vary
>> according to the computer's configuration.
>> Not all Stop 0x00000050 errors are caused by the
problem
>> that is described in the "Cause" section of this
article.
>> CAUSE
>> This problem occurs because the driver for the USB
>> Universal Reader from Lexar Media, Inc is not
compatible
>> with Windows XP.
>> RESOLUTION
>> To resolve this problem, obtain and install the latest
>> driver from Lexar Media, Inc.
>> STATUS
>> Lexar Media, Inc. has confirmed that this problem
occurs
>> when you use a version of their Sausb.sys driver with
>> Windows XP that is earlier than version 4.6.
>>
>>
>> ====================================
>> I don't have anything on my pC that resembles
>> Sausb.sys.... any ideas?
>>
>
>
>.
>

[Perplexed and Annoyed]

Mary,

Please see my response to Rick above. The problem seems
to be with a drive associated with my sound card. I'm
going to diagnose it right now.

>-----Original Message-----
>Found this:
>USB: Lexar Media Combo Digital Film Reader (USB). There
is a problem with the
>SAUSB.SYS file, apparently part of the Win98 SE driver
set for this device, retained
>during an upgrade to Win XP. Deleting the file solved
the problem. The newer version
>4.3 SAUSB.SYS driver from Lexar's Web site works
perfectly, and does not cause a
>shutdown problem. (Tip from correspondent Eric Brown.)
Though one correspondent
>reported that the even newer version 4.5 driver
(SAUSBI.SYS) also can be used in Win
>XP , Lexar says this driver doesn't work on XP. One
correspondent has confirmed that
>this matches his experience in trying (unsuccessfully)
to use 4.5 on both Widows 2000
>and XP.
>
>And this:
>http://www.usb-drivers.com/drivers/54/54144.htm
>
>
>Error Message: STOP 0x00000050 (0xffffffe0, 0x00000001,
0xf30da010, 0x00000000)
>PAGE_FAULT_IN_NONPAGED_AREA
>http://support.microsoft.com/?kbid=817197
>
>
>
>--
>Mary Sauer MS MVP
>http://office.microsoft.com/clipart/
>http://www.mvps.org/msauer/getting_started.htm
>"Annoyed and perplexed" > wrote in
message
...
>> I found this absolutely brilliant response to
>> another "new users" question so I took their advice and
>> checked my Event Viewer for an error I've been getting.
>>
>> ====================================
>> Error code 1000008e, parameter1 c0000005, parameter2
>> fbd7b977, parameter3 f3237114, parameter4 00000000.
>> =====================================
>>
>> For more information, see Help and Support Center at
>> http://go.microsoft.com/fwlink/events.asp.
>>
>> I found this text flagged and went to the site. The
>> site reports:
>>
>> There is no additional information about this issue in
>> the Error and Event Log Messages or Knowledge Base
>> databases at this time. You can use the links in the
>> Support area to determine whether any additional
>> information might be available elsewhere.
>>
>> So I click on the link supplied and here's what it says
>>
>> SYMPTOMS
>> You may experience any of the following symptoms:
>> Your computer automatically restarts.
>> After you log on, you receive the following error
>> message:
>>
>> Microsoft Windows
>> The system has recovered from a serious error.
>> A log of this error has been created.
>> Please tell Microsoft about this problem.
>> We have created an error report that you can send to
help
>> us improve Microsoft Windows. We will treat this report
>> as confidential and anonymous.
>> To see what data this error report contains, click
here.
>> If the error message still appears and if you want to
see
>> the data that the error report contains, click the
click
>> here link at the bottom of the message box. You then
see
>> error signature information that may be similar to:
>>
>> BCCode : 00000050 BCP1 : 0xffffffe0 BCP2 : 0x00000001
>> BCP3 : 0xf30da010 BCP4 : 0x00000000 OSVer : 5_1_2600
SP :
>> 0_0 Product : 256_1
>> You receive the following stop error message on a blue
>> screen:
>>
>> A problem has been detected and Windows has been shut
>> down to prevent damage to your computer
>> Technical information:
>>
>> *** STOP: 0x00000050 (0xffffffe0, 0x0x00000001,
>> 0xf30da010, 0x00000000)
>> PAGE_FAULT_IN_NONPAGED_AREA
>> When you view the system log in Event Viewer, you may
>> notice an event ID 1003 entry with information that is
>> similar to:
>> Date: date
>> Source: System
>> Error Time: time
>> Category: (102)
>> Type: Error
>> Event ID: 1003
>> User: N/A
>> Computer: computer
>> Description: Error code 00000050, parameter1
0xffffffe0,
>> parameter2 0x00000001, parameter3 0xf30da010,
parameter4
>> 0x00000000. 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 35 00000MN 0020: 30
>> 20 20 50 61 72 61 6d 0 Param 0028: 65 74 65 72 73 20 66
>> 66 eters ff 0030: 66 66 66 66 64 31 2c
>>
>> Notes
>> The symptoms of a stop error vary according to the
>> failure options of your computer system. For additional
>> information about how to configure system failure
>> options, click the following article number to view the
>> article in the Microsoft Knowledge Base:
>> 307973 HOW TO: Configure System Failure and Recovery
>> Options in Windows
>>
>> The four parameters that are included in the error
>> signature information (BCP x), and inside the
parentheses
>> of the technical information for the Stop error may
vary
>> according to the computer's configuration.
>> Not all Stop 0x00000050 errors are caused by the
problem
>> that is described in the "Cause" section of this
article.
>> CAUSE
>> This problem occurs because the driver for the USB
>> Universal Reader from Lexar Media, Inc is not
compatible
>> with Windows XP.
>> RESOLUTION
>> To resolve this problem, obtain and install the latest
>> driver from Lexar Media, Inc.
>> STATUS
>> Lexar Media, Inc. has confirmed that this problem
occurs
>> when you use a version of their Sausb.sys driver with
>> Windows XP that is earlier than version 4.6.
>>
>>
>> ====================================
>> I don't have anything on my pC that resembles
>> Sausb.sys.... any ideas?
>>
>
>
>.
>

[Sharon F]

On Fri, 31 Oct 2003 17:07:55 -0800, Annoyed and Perplexed wrote:

> Well I got the crash to happen... or so should I say, IT
> happened.
>
> The first thing I was was
>
> msmsgs.exe - Application error
>
> The instruction at "0x5d39e155" referenced memory
> at "0x00000000". The memory could not be "read".
>
> Click on OK to terminate the program
> Click on CANCEL to debug the program
>
> So I clicked OK... then up comes a similar message for
> OPXPApp.exe but before I could write down the exact
> message, I get a BSOD. Since I'd tweaked the settings,
> the BSOD stayed on my screen allowing me to write down
> the tech info. Here's what it said:
>
> Technical Information
>
> ***STOP: 0x0000008E (0xC0000005, 0xFBA88977, 0xF2E23114,
> 0x00000000)
>
> ***ALCXWDM.SYS - Address FBA88977 base at FBA25000, Date
> Stamp 3efffd5e
>
>
> So it looks like I've got a problem with a drive. Now
> it's off to google to see if I can find the source. Me
> thinks its my sound card but I'll find out shortly.


OPxpapp.exe is part of the OmniPass software from Softex. I believe that's
software for scanners. Sound familiar? If yes, that's something else you
could check out. The alxcwdm.sys file, as you've already figured out, is an
audio driver.

--
Sharon F
MS MVP - Windows Shell/User