OK, so I've started seeing the dreaded core shutdown issue on my 1.6 Air. And I don't think it is temperature related. This is a bug in the GMA X3100 graphics driver! Happens when I play WoW, on even low graphics settings. Game starts out beautifully with high frame rates but after 5 or so minutes the system drops to an unplayable crawl. When this happens Activity Monitor shows that one core is off, and the other is pegged at 100% activity by the kernel_task process (PID 0), which is taking up 50-60% of the CPU. I am now convinced this is a bug in the GMA X3100 driver and **not** temperature related, for a few reasons: I tried placing the Air on a cold A/C vent when this happens, dropping the temperature to real low levels and it still didn't help. On the other hand, quitting WoW immediately brought the other core back to life and kernel_task returned to its usual 1% of CPU use. If this had been temperature related why would everything return to normal *seconds* after quitting the offending program? Also, I tried opening a few Terminals and running "yes > /dev/null", which is a good way to exercise the CPU. Both cores shot up to 100% usage and the temperature sky-rocketed beyond anything I had seen before, but no core shutdown and no system slow-downs. So... the fact this happens in WoW and for many others while playing longer Flash Player videos, while others never see it (presumably never tasking teh graphics part of their system) points to it being graphics related... either a hardware bug, or more probably a driver bug. Since drivers run in kernel space, I believe there is a bug in the GMA X3100 driver which is causing this, as evidenced by the kernel space process (kernel_task) eating up all the CPU time of the single functioning core while this goes on. Anyone else see similar things?