Actually, from the crashdump, Driver Verifier caught the Intel WiDi (Wireless Display;intelaud.sys) driver trying to corrupt pool memory (region of memory reserved for driver/kernel use). It's dated March 9, 2011 so see if there's an update for it, otherwise, I'm not quite sure why that particular driver is needed? Either way I believe it must be dealt with.
Do not neglect the possibility, however, that this could actually be a hardware malfunction manifesting as a driver issue. Resolve the software-side, test stability, and if it's unstable again, run Driver Verifier again. However, I would not put it past HP and several other OEMs to have a bad system slip past their inspection that happened to fall into your hands.
