Roberto!!!
Happy New Year to you sir...let's see what's going on here:
.. checking things I found this in :
C:\MPTN\ETC\acpid.cfg
Alright...so one thing to start off with: consider turning ON the LOGs, in the same acpid.cfg file, at the very top you have the following section:
;############## General Deamon Settings ##################################
[ACPID]
; LogFile: Where to write the log file, full path, default=No log file
LogFile = G:\tmp\log\acpidaemon.log
; AcpiLog: Where to write the acpica$ log file, full path, default=don't create
AcpiLog = G:\tmp\log\AcpiCA.log
; ConfigCheckInterval: Delay in seconds between checking for config file changes, default=10
;ConfigCheckInterval = 10
...
The values above reflect my system config, so adjust accordingly. Point being, the acpidaemon.log & acpiCA.log files will have a LOT of useful info to look at.
Now let's look at the control values you were using:
...and changing only these two values changed everything completely.
; IdleCount: Number of CheckIntervals needed to determine system idle, default=5
IdleCount = 0.3125
; CheckInterval: Delay time between checking cpu load and temperature (seconds), default=1
CheckInterval = 1.3125
OK, so what exactly do these two settings do?
The ACPI daemon uses the CheckInterval as the frequency (in seconds) of checking the CPU Load & Temperature, further on, it uses the IdleCount value as the number of times the CPU Load & Temperature will be checked to determine if the system is experiencing a no-load situation, namely it appears to be in IDLE state.
From the ACPI perspective that would indicate that the CPU status can now be adjusted (and most likely set as INACTIVE) in order to lower the power consumption, which for battery operated machines is what matters!
The 'Power Manager Settings' section of the ACPI documentation (INF) file does a nice job of explaining this in pretty good details. The key take away here is that the recommendation is NOT to use CPU THROTTLING (which can be set in the [PreferredMode] section, if you have a specific reason to try a particular value).
OK, so this is all theory...how about Real-World???
Well, in my case the machine being a 24x7 box that's using a steady power supply I simply shut OFF the PowerMan function entirely because I found the control logic to be unsuitable for my purposes: CPU cores would constantly go off-line (to avoid power usage) and the time it took for them to spool back up (when the usage demanded it) took too long (regardless of how aggressive of the settings combination I would use).
So the advice I would give you is as follows: FOR TESTING PURPOSES ONLY, disable PowerMan, reboot and see what's going on.
To disable PowerMan you make the following adjustment:
;############## Power Manager Settings ###################################
[PowerMan]
; Enable: 1=enabled, 0=disabled, default=1
Enable = 0
Notice how I set 'Enable = 0', which disables it.
Test it out, if this addresses your issue and your BIOS does not report crazy CPU Temps, than you always have to option to simply NOT use PowerMan.