Serious error

  • Thread starter Thread starter Happy
  • Start date Start date
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
~~~~~~~~~~~~~~~~~~~


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.



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
~~~~~~~~~~~~~~~~~~~


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
~~~~~~~~~~~~~~~~~~~

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
 
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.
 
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

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
~~~~~~~~~~~~~~~~~~~
 
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" .
 
Happy

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

--

Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~
 
Before.
Gerry Cornell said:
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

In that case you may no longer have a problem. Let's wait and see!


--

Regards.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~
 
I do still have the PFN_LIST_CORRUPT problem-- it has occurred twice today.
The other hasn't reoccurred, though. I am still trying to decipher the
memory checking utilities-- 2 of them needed a floppy, and I don't have one
with this computer. The other has a complex method of utilizing a CD for
writing to, and then checking memory, which I haven't figured out yet (have
ruined 3 CD's....)
 
Happy

Another way to test memory if you have say 3 sticks is to remove one
and observe for a day or so. Then swap it back in and take another
out. As long as only one is bad you can isolate which and replace.

--

Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~
 
Thanks, I have 2. I wasn't aware you could do this, so will give it a try.
My computer is running really slow by times, with high CPU speed (50%) by
times for extended periods, so will keep working at it.
 
Live.sri said:
Check these cases:

1. Display driver installation problems
Would trying another monitor help?
2. Check the RAM Modules. Try to rum Microsoft Memory Tester s/w.
Having trouble with that one. Going to try Memtest86 tomorrow.
3. Is your processor is OverLocking ? Try to put it on default settings.
??? Not sure how to do this..........
 
Just to update everyone who has been helping me with my "plight". Ran memory tests, and had the shop run tests on motherboard and other hardware, and everything checked out. So, I did a System Recovery, added more RAM, reinstalled everything, (fun, fun) and it works great! really flies!
Thanks to all for steering me in various directions to find answers. I appreciate it, and hopefully have learned a little in the process. The consensus seems to be that there was one or more faulty drivers, perhaps combined with a few other cumulative errors.
 
Back
Top