More info about the Windows 8 Release Preview freezing issue

So Paul Thurrott just wrote a piece on the responses he received from his earlier Windows 8 Release Preview distress beacon. To quickly recap, the operating system, for some users, at random, seems to slowly hang -- one app at a time -- eventually forcing a reboot. We know the issue was confirmed by Microsoft and has reportedly already been fixed in newer builds of Windows 8. Unfortunately we don't know why it's happening yet or if it's something easily worked around. Paul, however, seems to be on the right track with his comment about chipsets:

Many of the comments were interesting. A majority of those who had experienced the hang issue have SSD (instead of hard drive) storage. All of them had “Sandy Bridge” or newer Intel-based chipsets in their PCs. Interesting.

I say "right track" because as soon as I read that, I revisited some of the crash dumps provided by some kind folks on Neowin. Using my limited kernel debugging skills, I opened a few memory dumps and displayed a call stack from each processor. Lo' and behold the system appears tied up in the Intel Processor Driver (intelppm.sys) when the issue occurs. (I can't tell you what Processor 0 is up to because I had these users crash their system using CrashOnCtrlScroll. Dump analysis tips are very welcome.)

0: kd> ~1
1: kd> kc
Call Site
intelppm!MWaitIdle
intelppm!AcpiCStateIdleExecute
nt!PpmIdleExecuteTransition
nt!PoIdle
nt!KiIdleLoop

1: kd> ~2
2: kd> kc
Call Site
intelppm!MWaitIdle
intelppm!AcpiCStateIdleExecute
nt!PpmIdleExecuteTransition
nt!PoIdle
nt!KiIdleLoop

2: kd> ~3
3: kd> kc
Call Site
intelppm!MWaitIdle
intelppm!AcpiCStateIdleExecute
nt!PpmIdleExecuteTransition
nt!PoIdle
nt!KiIdleLoop

This is obviously far from conclusive -- all this really shows is a bunch of processor cores idling -- but this bug is shaping up to be Intel specific no known workaround at the moment. Hope we hear more soon.