You haven't really answered my other questions. Though I guess previous overclocking attempts (regardless if failed or successful) may have potentially caused hardware damage with the device.

The screenshot from top isn't helpful either, you need to be the one viewing it not us. There should be at least a process under CPU% somewhere that is causing the device to overheat. At least with the CPU being maxxed out it will use its maximum specified frequency.

Also with conky running, you can see on where it says Load1 avg. DIO. Mem. Those are also some of the useful fields when you have conky running for at least 5 minutes.

The load average is over 5 minute intervals, its collected from uptime command, the DIO is most likely Dynamic Input/Output and Mem is obviously memory usage. If any of those are high, notably load average or DIO it means that there is a process/kernel thread somewhere that is hanging up or some process that is thrashing I/O.

An output of your dmesg (into pastebin) along with maemo-list-user-packages would be handy.