Serious error

Well, finally happened again! (Serious error recovery) Here is the error info produced:
BCCode : 4e BCP1 : 00000099 BCP2 : 00000418 BCP3 : 00000003

BCP4 : 00000000 OSVer : 5_1_2600 SP : 2_0 Product : 256_1

and the detail of that:

C:\DOCUME~1\CARLDE~1\LOCALS~1\Temp\WERcaf0.dir00\M ini123106-01.dmp

C:\DOCUME~1\CARLDE~1\LOCALS~1\Temp\WERcaf0.dir00\s ysdata.xml

Prior to that, on most other starts, the HP keyboard error has appeared: kbd.exe, and here is the detail of that error:

AppName: kbd.exe AppVer: 1.0.2.0 ModName: ole32.dll

ModVer: 5.1.2600.2726 Offset: 0004d130



Any hints would be most appreciated.



"Gerry Cornell" wrote in message ...
Happy

If you post full copies of the Reports from Event Viewer we can try to
eliminate these lesser errors. Any recurring error tends to create a
smokescreen so that seeing the cause of a serious problem becomes more
difficult to resolve.

A tip for posting copies of Error Reports! Run Event Viewer and double
click on the error you want to copy. In the window, which appears is a
button resembling two pages. 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.
Make sure this is the first paste after exiting from Event Viewer.

--

Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~


Happy wrote:
I ran the RAM test and everything seems fine. And of course, for a
problem that was happening one per hour (serious error - reboot) for
several days, it has not happened since my original post two days
ago....................... I have had the following three errors,
though: 1) KBD.exe (regular problem for several months), 2) Invalid
Backweb application 137903 (several months as well), and 3) Dr.
Watson postmortem debugger closed (new problem)
I will continue to use computer normally until the serious error
problem reoccurs, and then post back.
"Ron Martell" wrote in message
...
"Happy" wrote:

Thanks all for replies. Here are the messages that showed up in
the
"recovered from a serious error" box (& detail):
BCCode : 4e BCP1 : 00000099 BCP2 : 000064B4 BCP3 : 00000003

BCP4 : 00000000 OSVer : 5_1_2600 SP : 2_0 Product : 256_1


The two most common causes of the error (STOP 0x0000004E:
PFN_LIST_CORRUPT) are defective RAM and a buggy device driver.

Did you recently install any new hardware or update the drivers for
any existing items on your computer? Check with the manufacturer's
web sites for updated device drivers for any new items. If you
updated drivers recently then try rolling back to the previous
driver
version.

To check for possible defective RAM try one of the following free
memory diagnostic tests:
DocMemory http://www.simmtester.com
Windows Memory Diagnostic http://oca.microsoft.com/en/windiag.asp
Memtest86: http://www.memtest.org

Good luck


Ron Martell Duncan B.C. Canada
--
Microsoft MVP (1997 - 2006)
On-Line Help Computer Service
http://onlinehelp.bc.ca
Syberfix Remote Computer Repair

"Anyone who thinks that they are too small to make a difference
has never been in bed with a mosquito."

Happy


0x0000004E: PFN_LIST_CORRUPT
http://aumha.org/win5/kbestop.htm

http://msdn.microsoft.com/library/de...933845.xml.asp
if link broken try
http://snipurl.com/l6o7

What is the model number of your Logitech keyboard?

What is your computer make and model? When was it bought new?

Does your Windows XP CD include SP2 or did you instal it later by
downloading or using one of the SP2 CDs distributed by Microsoft in
2004?

Are there any yellow question marks in Device Manager? Right click on
the My Computer icon on your Desktop and select Properties. Hardware,
Device Manager. If yes what is the Device Error code?



--

Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~


"Happy" wrote in message
...
Well, finally happened again! (Serious error recovery) Here is the
error info produced:
BCCode : 4e BCP1 : 00000099 BCP2 : 00000418 BCP3 : 00000003
BCP4 : 00000000 OSVer : 5_1_2600 SP : 2_0 Product : 256_1
and the detail of that:
C:\DOCUME~1\CARLDE~1\LOCALS~1\Temp\WERcaf0.dir00\M ini123106-01.dmp
C:\DOCUME~1\CARLDE~1\LOCALS~1\Temp\WERcaf0.dir00\s ysdata.xml
Prior to that, on most other starts, the HP keyboard error has
appeared: kbd.exe, and here is the detail of that error:
AppName: kbd.exe AppVer: 1.0.2.0 ModName: ole32.dll
ModVer: 5.1.2600.2726 Offset: 0004d130

Any hints would be most appreciated.

Oops, I left out the "Blue screen" error message, "PFN_List_Corrupt" . This must be relevant....?
"Happy" wrote in message ...
Well, finally happened again! (Serious error recovery) Here is the error info produced:
BCCode : 4e BCP1 : 00000099 BCP2 : 00000418 BCP3 : 00000003

BCP4 : 00000000 OSVer : 5_1_2600 SP : 2_0 Product : 256_1

and the detail of that:

C:\DOCUME~1\CARLDE~1\LOCALS~1\Temp\WERcaf0.dir00\M ini123106-01.dmp

C:\DOCUME~1\CARLDE~1\LOCALS~1\Temp\WERcaf0.dir00\s ysdata.xml

Prior to that, on most other starts, the HP keyboard error has appeared: kbd.exe, and here is the detail of that error:

AppName: kbd.exe AppVer: 1.0.2.0 ModName: ole32.dll

ModVer: 5.1.2600.2726 Offset: 0004d130



Any hints would be most appreciated.



"Gerry Cornell" wrote in message ...
Happy

If you post full copies of the Reports from Event Viewer we can try to
eliminate these lesser errors. Any recurring error tends to create a
smokescreen so that seeing the cause of a serious problem becomes more
difficult to resolve.

A tip for posting copies of Error Reports! Run Event Viewer and double
click on the error you want to copy. In the window, which appears is a
button resembling two pages. 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.
Make sure this is the first paste after exiting from Event Viewer.

--

Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~


Happy wrote:
I ran the RAM test and everything seems fine. And of course, for a
problem that was happening one per hour (serious error - reboot) for
several days, it has not happened since my original post two days
ago....................... I have had the following three errors,
though: 1) KBD.exe (regular problem for several months), 2) Invalid
Backweb application 137903 (several months as well), and 3) Dr.
Watson postmortem debugger closed (new problem)
I will continue to use computer normally until the serious error
problem reoccurs, and then post back.
"Ron Martell" wrote in message
...
"Happy" wrote:

Thanks all for replies. Here are the messages that showed up in
the
"recovered from a serious error" box (& detail):
BCCode : 4e BCP1 : 00000099 BCP2 : 000064B4 BCP3 : 00000003

BCP4 : 00000000 OSVer : 5_1_2600 SP : 2_0 Product : 256_1


The two most common causes of the error (STOP 0x0000004E:
PFN_LIST_CORRUPT) are defective RAM and a buggy device driver.

Did you recently install any new hardware or update the drivers for
any existing items on your computer? Check with the manufacturer's
web sites for updated device drivers for any new items. If you
updated drivers recently then try rolling back to the previous
driver
version.

To check for possible defective RAM try one of the following free
memory diagnostic tests:
DocMemory http://www.simmtester.com
Windows Memory Diagnostic http://oca.microsoft.com/en/windiag.asp
Memtest86: http://www.memtest.org

Good luck


Ron Martell Duncan B.C. Canada
--
Microsoft MVP (1997 - 2006)
On-Line Help Computer Service
http://onlinehelp.bc.ca
Syberfix Remote Computer Repair

"Anyone who thinks that they are too small to make a difference
has never been in bed with a mosquito."

It is an HP Keyboard, Model # 5219URF 2+
The computer is an HP Model # M1080N, Product # PC099A-ABA, 512 RAM, 250Gig
HD, Pentium 4 Processor, Windows media centre version of XP.
Purchased new two years ago, it came with SP2 I believe. (I don't have a
disk)
There are no yellow question marks in "device manager".
"Gerry Cornell" wrote in message
...
Happy


0x0000004E: PFN_LIST_CORRUPT
http://aumha.org/win5/kbestop.htm

http://msdn.microsoft.com/library/de...933845.xml.asp
if link broken try
http://snipurl.com/l6o7

What is the model number of your Logitech keyboard?

What is your computer make and model? When was it bought new?

Does your Windows XP CD include SP2 or did you instal it later by
downloading or using one of the SP2 CDs distributed by Microsoft in 2004?

Are there any yellow question marks in Device Manager? Right click on
the My Computer icon on your Desktop and select Properties. Hardware,
Device Manager. If yes what is the Device Error code?



--

Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~


"Happy" wrote in message
...
Well, finally happened again! (Serious error recovery) Here is the error
info produced:
BCCode : 4e BCP1 : 00000099 BCP2 : 00000418 BCP3 : 00000003
BCP4 : 00000000 OSVer : 5_1_2600 SP : 2_0 Product : 256_1
and the detail of that:
C:\DOCUME~1\CARLDE~1\LOCALS~1\Temp\WERcaf0.dir00\M ini123106-01.dmp
C:\DOCUME~1\CARLDE~1\LOCALS~1\Temp\WERcaf0.dir00\s ysdata.xml
Prior to that, on most other starts, the HP keyboard error has appeared:
kbd.exe, and here is the detail of that error:
AppName: kbd.exe AppVer: 1.0.2.0 ModName: ole32.dll
ModVer: 5.1.2600.2726 Offset: 0004d130

Any hints would be most appreciated.

Gerry Cornell--- because the computer keeps shutting off, I have not had a
chance to follow the links you sent. I will keep trying, or use my son's
laptop when he gets home. Thanks for your help so far!
"Gerry Cornell" wrote in message
...
Happy


0x0000004E: PFN_LIST_CORRUPT
http://aumha.org/win5/kbestop.htm

http://msdn.microsoft.com/library/de...933845.xml.asp
if link broken try
http://snipurl.com/l6o7

What is the model number of your Logitech keyboard?

What is your computer make and model? When was it bought new?

Does your Windows XP CD include SP2 or did you instal it later by
downloading or using one of the SP2 CDs distributed by Microsoft in 2004?

Are there any yellow question marks in Device Manager? Right click on
the My Computer icon on your Desktop and select Properties. Hardware,
Device Manager. If yes what is the Device Error code?



--

Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~


"Happy" wrote in message
...
Well, finally happened again! (Serious error recovery) Here is the error
info produced:
BCCode : 4e BCP1 : 00000099 BCP2 : 00000418 BCP3 : 00000003
BCP4 : 00000000 OSVer : 5_1_2600 SP : 2_0 Product : 256_1
and the detail of that:
C:\DOCUME~1\CARLDE~1\LOCALS~1\Temp\WERcaf0.dir00\M ini123106-01.dmp
C:\DOCUME~1\CARLDE~1\LOCALS~1\Temp\WERcaf0.dir00\s ysdata.xml
Prior to that, on most other starts, the HP keyboard error has appeared:
kbd.exe, and here is the detail of that error:
AppName: kbd.exe AppVer: 1.0.2.0 ModName: ole32.dll
ModVer: 5.1.2600.2726 Offset: 0004d130

Any hints would be most appreciated.

The keyboard model number does not correspond with keyboard listed on HP site. The number seems to refer to the receiver not the keyboard. Please recheck the information on the keyboard.. Please also confirm that the Receiver for the keyboard and mouse is connected to a USB port.

Try removing the cable from the Receiver to the USB port and an old non-USB wired keyboard and mouse to another spare port. If you do this does the computer boot?

--

Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~


"Happy" wrote in message news Oops, I left out the "Blue screen" error message, "PFN_List_Corrupt" .. This must be relevant....?

I have rechecked, and that is the number. The keyboard is a wireless HP, and came with the machine. It has FCC # and S/N if that would be any help.The keyboard receiver is connected to a USB port. The mouse is an HP wired model, and is connected to the mouse input plug. (Mouse is model N3 + optical)

I tried another keyboard, an IBM, ( turned off computer, unplugged the receiver connected the other wired keyboard) and everything fired up fine (am now typing with that one) I still got the KBD.exe error on reboot. I am using the same HP optical wired mouse as before.



"Gerry Cornell" wrote in message ...
The keyboard model number does not correspond with keyboard listed on HP site. The number seems to refer to the receiver not the keyboard. Please recheck the information on the keyboard.. Please also confirm that the Receiver for the keyboard and mouse is connected to a USB port.

Try removing the cable from the Receiver to the USB port and an old non-USB wired keyboard and mouse to another spare port. If you do this does the computer boot?

--

Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~


"Happy" wrote in message news Oops, I left out the "Blue screen" error message, "PFN_List_Corrupt" . This must be relevant....?

Well that makes life a little easier.

Let's try identifying the keyboard a different way.

This freeware programme is excellent for getting information about
your computer:
Everest Home Edition (freeware)
http://www.majorgeeks.com/download4181.html

Tip: To copy select Report, Quick Report, Plain Text, highlight
required text, right click and select copy. However, whilst this is
fine for posting small amounts of information into newsgroup messages
longer reports will irritate other newsgroup subscribers.


--

Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~

"Happy" wrote in message
...
I have rechecked, and that is the number. The keyboard is a wireless
HP, and came with the machine. It has FCC # and S/N if that would be
any help.The keyboard receiver is connected to a USB port. The mouse
is an HP wired model, and is connected to the mouse input plug. (Mouse
is model N3 + optical)

I tried another keyboard, an IBM, ( turned off computer, unplugged the
receiver connected the other wired keyboard) and everything fired up
fine (am now typing with that one) I still got the KBD.exe error on
reboot. I am using the same HP optical wired mouse as before.

This is the info I located, using Everest Home Edition (nice program!) It
doesn't mention HP, but here it is:

Keyboard Properties:
Keyboard Name HID Keyboard Device
Keyboard Type IBM enhanced (101-
or 102-key) keyboard
Keyboard Layout US
ANSI Code Page 1252 - Western
European (Windows)
OEM Code Page 437
Repeat Delay 1
Repeat Rate 31


"Gerry Cornell" wrote in message
...
Well that makes life a little easier.

Let's try identifying the keyboard a different way.

This freeware programme is excellent for getting information about your
computer:
Everest Home Edition (freeware)
http://www.majorgeeks.com/download4181.html

Tip: To copy select Report, Quick Report, Plain Text, highlight required
text, right click and select copy. However, whilst this is fine for
posting small amounts of information into newsgroup messages longer
reports will irritate other newsgroup subscribers.


--

Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~

"Happy" wrote in message
...
I have rechecked, and that is the number. The keyboard is a wireless HP,
and came with the machine. It has FCC # and S/N if that would be any
help.The keyboard receiver is connected to a USB port. The mouse is an HP
wired model, and is connected to the mouse input plug. (Mouse is model N3
+ optical)

I tried another keyboard, an IBM, ( turned off computer, unplugged the
receiver connected the other wired keyboard) and everything fired up fine
(am now typing with that one) I still got the KBD.exe error on reboot. I
am using the same HP optical wired mouse as before.

philo-- Gulp--- I think I will try other things first, I am nervous of
altering the registry, having run into problems before doing it. I have
printed the article off however, and will try it later in the week if other
things fail. Thanks for the tip.
"philo" wrote in message
...

"Happy" wrote in message
...
My computer reboots at irregular intervals, and indicates it has
"recovered
from a serious error". Other than that, it is working fine. Any thoughts
on
what the source of this is, and where I should start to look to solve it?
Thanks in advance!




You could try running verifier
and see if there are any driver problems

http://support.microsoft.com/kb/244617

Happy

Download and install the driver dated June 2006 version 1.0.2.6
http://h10025.www1.hp.com/ewfrf/wc/s...product=426502

--

Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~


Happy wrote:
This is the info I located, using Everest Home Edition (nice
program!) It doesn't mention HP, but here it is:

Keyboard Properties:
Keyboard Name HID Keyboard
Device Keyboard Type IBM
enhanced (101- or 102-key) keyboard
Keyboard Layout US
ANSI Code Page 1252 -
Western
European (Windows)
OEM Code Page 437
Repeat Delay 1
Repeat Rate 31


"Gerry Cornell" wrote in message
...
Well that makes life a little easier.

Let's try identifying the keyboard a different way.

This freeware programme is excellent for getting information about
your computer:
Everest Home Edition (freeware)
http://www.majorgeeks.com/download4181.html

Tip: To copy select Report, Quick Report, Plain Text, highlight
required text, right click and select copy. However, whilst this is
fine for posting small amounts of information into newsgroup
messages longer reports will irritate other newsgroup subscribers.


--

Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~

"Happy" wrote in message
...
I have rechecked, and that is the number. The keyboard is a
wireless
HP, and came with the machine. It has FCC # and S/N if that would
be
any help.The keyboard receiver is connected to a USB port. The
mouse
is an HP wired model, and is connected to the mouse input plug.
(Mouse is model N3 + optical)

I tried another keyboard, an IBM, ( turned off computer, unplugged
the receiver connected the other wired keyboard) and everything
fired up fine (am now typing with that one) I still got the KBD.exe
error on reboot. I am using the same HP optical wired mouse as
before.

Worked great!!!!!! Cleared up the problem, and I programmed a couple of
"quick launch" buttons to test, first time they have worked in over a year!
And the error message has disappeared. Thank you very much, from Nova
Scotia!
Now working on the "PFN List Corrupt" Error, trying to decipher the memory
test suggestions. Interesting, I had another error, same blue screen, "Page
Fault in Non-Paged Area".
"Gerry Cornell" wrote in message
...
Happy

Download and install the driver dated June 2006 version 1.0.2.6
http://h10025.www1.hp.com/ewfrf/wc/s...product=426502

--

Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~


Happy wrote:
This is the info I located, using Everest Home Edition (nice
program!) It doesn't mention HP, but here it is:

Keyboard Properties:
Keyboard Name HID Keyboard
Device Keyboard Type IBM
enhanced (101- or 102-key) keyboard
Keyboard Layout US
ANSI Code Page 1252 - Western
European (Windows)
OEM Code Page 437
Repeat Delay 1
Repeat Rate 31


"Gerry Cornell" wrote in message
...
Well that makes life a little easier.

Let's try identifying the keyboard a different way.

This freeware programme is excellent for getting information about
your computer:
Everest Home Edition (freeware)
http://www.majorgeeks.com/download4181.html

Tip: To copy select Report, Quick Report, Plain Text, highlight
required text, right click and select copy. However, whilst this is
fine for posting small amounts of information into newsgroup
messages longer reports will irritate other newsgroup subscribers.


--

Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~

"Happy" wrote in message
...
I have rechecked, and that is the number. The keyboard is a wireless
HP, and came with the machine. It has FCC # and S/N if that would be
any help.The keyboard receiver is connected to a USB port. The mouse
is an HP wired model, and is connected to the mouse input plug.
(Mouse is model N3 + optical)

I tried another keyboard, an IBM, ( turned off computer, unplugged
the receiver connected the other wired keyboard) and everything
fired up fine (am now typing with that one) I still got the KBD.exe
error on reboot. I am using the same HP optical wired mouse as
before.

Happy

That's good news.

Now post a copy of the "Page Fault in Non-Paged Area" BSOD error and
related Event Viewer Report..

--

Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~

Happy wrote:
Worked great!!!!!! Cleared up the problem, and I programmed a couple
of "quick launch" buttons to test, first time they have worked in
over a year! And the error message has disappeared. Thank you very
much, from Nova Scotia!
Now working on the "PFN List Corrupt" Error, trying to decipher the
memory test suggestions. Interesting, I had another error, same blue
screen, "Page Fault in Non-Paged Area".

Page_Fault_in_nonpaged_area. 0x00000050 (OXEC84000, 0x00000000, 0x804EABD7,
0x00000001)
I didn't catch the event viewer as it only happened once, the preceeding
was on the "blue screen" .
"Gerry Cornell" wrote in message
...
Happy

That's good news.

Now post a copy of the "Page Fault in Non-Paged Area" BSOD error and
related Event Viewer Report..

--

Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~

Happy wrote:
Worked great!!!!!! Cleared up the problem, and I programmed a couple
of "quick launch" buttons to test, first time they have worked in
over a year! And the error message has disappeared. Thank you very
much, from Nova Scotia!
Now working on the "PFN List Corrupt" Error, trying to decipher the
memory test suggestions. Interesting, I had another error, same blue
screen, "Page Fault in Non-Paged Area".

Happy

Did this error occur before or after you installed the replacement
driver?

--

Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~



Happy wrote:
Page_Fault_in_nonpaged_area. 0x00000050 (OXEC84000, 0x00000000,
0x804EABD7, 0x00000001)
I didn't catch the event viewer as it only happened once, the
preceeding was on the "blue screen" .
"Gerry Cornell" wrote in message
...
Happy

That's good news.

Now post a copy of the "Page Fault in Non-Paged Area" BSOD error
and
related Event Viewer Report..

--

Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~