Strange system event

I found this event from my system event logs:

The Acpi 2.0 _PCT object returned an invalid value of 11
Source intelppm
Event_ID 2

It seems to appear for every boot i have done. It would be nice to know what that message means and affects + possible way to fix it. It propably has something to do with power management. Any ideas?

I haven't had any serious problems with my laptop. But sometimes one of my hard drives have kept this "clicking" noice which also makes the HDD led flash briefly. I'm a bit worried about it, because that kind of sound is usually related to faulty HDD. It usually appears only when my laptop is idle with no applications running, but continues when I start a program. It stops if I run a program that heavily reads/writes on that drive. I have run many diagnostics, tests and benchmarks for both HDD's and everything seems fine. Sometimes I don't hear the clicking sound for days, sometimes for weeks. I have two HDD's, not in RAID. The paging file is in the other drive, not in the drive where Windows is installed.

Could it be that the event I described has something to do with this sound? Maby the HDD doesn't get enough power because of it?

Thanks for any help..

 

Could be a temp sensor reporting faulty readings...or it could be a heat problem. Does your laptop get really hot, and what are your core/HDD temperatures? Use Notebook Hardware Control to find out if you haven't already. Clicking noises in the HDD are not good, as you already know.

I would try reinstalling your OS and see if your event logs still report the error. Sometimes Windows system files get corrupted during updates and you'll get errors like this. This will also let you find out if your HDD is degrading, as most faulty HDD's will not progress far into a Windows installation...or at least do so very slowly.

 

ACPI is badly implemented in many laptops. I'd suggest updating your BIOS to the latest one, and getting all your Windows updates, as well as searching for that error message on Google before you reinstall Windows. Reinstalling the OS is a LAST resort, not a first one.

 

Thanks for your replies.

There's no heat problems and everything is updated. As I stated, I haven't had any performance issues or problems except those HDD clicking noises sometimes. The _PCT is an ACPI object that controls CPU performance. So I'm pretty sure that the event message has nothing to do with the HDD clicking. I have ran some benchmarks and tests for the CPU also and everything has worked flawlessly.

I'm suspecting that the event message may be cause of the Windows XP multicore hotfix ( KB896256). It's the only "optional" update I have done that actually affects ACPI functionality in someway. And yes, i have done the update 100% correctly.
It would be nice to know if anybody else has that message in their system event logs. Maby it's nothing to be worried about..

I don't want to do OS reinstall at this time. I have backupt my data, just in case. Here's what HDDGURU says about Fujitsu HDDs:

 

Hello there!

Unfortunately I don't have anything special to add, just that I've been having the exact same problem. My Amilo 1546 is exactly identical to yours...

Edit: Well I've noticed that much that if you turn on "silent mode", it will add another instance of that intelppm event...

 

Anything new about this?

I've found also (in addition to that silent mode-thing) that now when I don't have AntiVir starting automatically, there won't be intelppm-event on event log in startup... Don't have anything else either on autostart.

 

Apparently a new BIOS, new chipset drivers or Windows update have removed the "erronous" system event. I'm still experiencing the clicking sound sometimes though.

 

I also seen that error with my acer laptop It was because vista bios on xp install

are you run xp or vista?

If you machine came with vista you run xp I seen that before all i did was downgrade bios on my machine went away

you cound try upgrade or down see if goies away

 

Nope, this laptop came with XP. And as I already stated, I don't have the error event anymore.