On one of those spur-of-the-moment things, I purchased an Acer Aspire 5520g in the new year with dedicated nVidia 8400m G graphics – it was at sale price and had most of the features I was looking for. The following week however, I realised that I had purchased an expensive slideshow viewer when the thing came anywhere near games like COD4 and Bioshock.
Once the AS5 thermal grease was halfway bedded in, I bios-overclocked the card and got back to playing games!
However, I did start to become concerned that my keyboard was feeling a little warm after running intensive games. I ordered a Zalman Notebook Cooler ZM-NC2000 and decided to start monitoring the temperature sensors to see what impact the cooler had… at which point I realised that no one utility accurately captured the sensor information I was looking for – and none displayed my machine-specific sensor information in D3D 9 and 10 games or logged it to Perfmon/Reliability and Performance Monitor.
…so gaming became hacking:
On the chance that the implementation behind some of the sources of sensor data will be of use to someone, I’ll cover some of the details when I can - probably focusing on the D2D injection (esp. D3D 10) and the Vista ACPI-querying driver I authored.