The first thing I would do is see if Intel has a newer driver than HP is offering you. I normally recommend getting drivers from the OEM, but it's possible that HP just doesn't want to test Intel's newer driver for their older hardware, so they're not staying current with Intel. Make sure you have the HP driver available in case of a bad result, but I've never had an issue with a driver from Intel.
Secondly, r-click issues can be caused by shell extensions. If you go here and get the free Shell Extensions Manager http://www.nirsoft.net/utils/shexview.html - just run the executable (there's no installer). Turn off all the 3rd party (non-Microsoft) shell extensions and see if the problem still happens. If yes, re-enable everything and move on. If no, re-enable one at a time or small groups until you see which shell extension is causing the blue screen. You can then either upgrade the app in question, leave the shell extension disabled, or contact the vendor tech support for the app in question.
Lastly, hardware acceleration. Probably the best thing would be to just disable it and see what happens. If you start having a bad experience with graphics-related tasks, you'll probably have to contact HP and hope for the best. But especially on business PCs with minimal graphics needs, you might not notice enough of an effect to matter.
dnickason, Sorry I missed your reply. I later determined in Jan'12 that a new driver from Intel had been released and used that. I had already tired r-click extensions but they did not work for me. Finally, yes we just tinkered with hw acceleartion and no issues were observed.
Thanks very much for your advise. A bit late though :-)