Keyboard/CPU conflict?

[Michael]

First I'd like to thank the people who have replied to my previous posts.
Your input has been very much appreciated. It seems I've come across a
problem that is not very common. That is if it's not a first! My system is
as follows -

Windows XP sp2 (I had this problem before I installed the patch)
3.06 Gig Intel Pentium 4
120 Gig Hard Drive (No partition yet)
1024 Meg Memory
NVIDIA GeForce4 Ti 4200 with AGP8X
On Board sound - Realtek AC'07 Audio
On Board network - NetComm NB1300 USB Network Adapter
- Realtek RTL8139 Family PCI Fast Ethernet NIC
PS2 Keyboard - Microsoft Natural Multimedia Keyboard 1.0A

The problem I'm having is my CPU usage jumps up to over 90% whenever I press
(and hold down) any of the keys on my keyboard. This causes the whole system
to slow down and stall until I release the key again. Even typing too
quickly makes it jump up over 30%. I've tried removing drivers and replacing
them. Network, Sound and Keyboard this did nothing. I tried updating the
drivers which didn't help either. I can't find any conflicts anywhere,
according to System Information everything's fine. I also went into BIOS and
changed the IRQ selector from manual to auto to see if letting the computer
pic the IRQ settings would make a difference. It didn't! I'm not too keen on
changing BIOS settings as I don't know a lot about them and I'm told it can
be quite damaging if I change something I shouldn't. Any advice would most
welcome at this stage as putting it in the shop and paying $65 an hour
doesn't really appeal to me!

Much Obliged
Michael

 

[Blahblah]

USB or PS/2 connector?

blahblah

 

[__SPooKY__]

he said it was a PS2 keyboard

USB or PS/2 connector?

blahblah

--
*****

The internal section of THe-SPooKY-NeTWoRK is NOW back...
If your BNC ain't working, yer under suspician
give us a shout if you just need a new one...

*****

'I can never think of a good quote for signatures.'
Danny (aka __SPooKY__)

 

[Blahblah]

duh, I was answering these after having been throwing up AND having the runs
for 3 hours pretty continuosly... :/ guess I just didnt' catch that part.
I've seen this on another computer before, I'll put a watch on this thread
and update ya when I remember what the fix was. One thought, mayhaps a
keylogger running computing/catching length of time a key is pressed?

blahblah

 

[__SPooKY__]

lol - figured ya just missed it, he dint say nuffin so i said it so ya can
answer him before he came back - but yes, keylogger sounds right - never had
the problem myself tho so i'm prolly wrong (usually am )

duh, I was answering these after having been throwing up AND having the runs
for 3 hours pretty continuosly... :/ guess I just didnt' catch that part.
I've seen this on another computer before, I'll put a watch on this thread
and update ya when I remember what the fix was. One thought, mayhaps a
keylogger running computing/catching length of time a key is pressed?

blahblah

--
*****

The internal section of THe-SPooKY-NeTWoRK is NOW back...
If your BNC ain't working, yer under suspician
give us a shout if you just need a new one...

*****

'I can never think of a good quote for signatures.'
Danny (aka __SPooKY__)

 

[Michael]

I've got Adaware and Spybot SD neither had found anything. I've found
anti-keylogger software but do I really need to download it? Isn't this the
kind of stuff SpybotSD it suppose to find?

 

[Gary G. Taylor]

I've got Adaware and Spybot SD neither had found anything. I've found
anti-keylogger software but do I really need to download it? Isn't this
the kind of stuff SpybotSD it suppose to find?

Those applications complement each other, not duplicate: they each
specialize in their own particular part of the malware universe. I would
strongly suggest getting fresh updates of ALL of them and running them.

 

[Blahblah]

keep in mind if some person today codes a keylogger, hacks into your system
and places it, then you are out of luck as AV and Spyware programs only look
for KNOWN programs (and some virus like activity), so unfortunately it is
likely something unknown at this time, check your startup files in
hklm/software/microsoft/windows/currentversion/run-runonece-runservices and
such, might be something in there, I have seen some sophisticated keyloggers
that were actually wrappers around a dll file, in which case it is almost
impossible to find unless you know what you are looking for.

blahblah

P.S. have you tried doing an os/repair? winxp's repair is awesome, put your
cd in, reboot to the cd, let it go through, hit enter to install windows,
then when it searches for existing copies of windows select the current
install and repair it you will need to do updates again after, but thats
it. likely will fix your program IF there is nothing in your startup
locations