Hmm that is strange. Maybe Adblock is causing some issues seeing as how the HP site can be a bit flimsy: http://support.hp.com/gb-en/drivers/selfservice/hp-envy-17-2000-3d-edition-notebook-pc-series/5046239/model/5069404#Z7_3054ICK0K8UDA0AQC11TA930C7
HP forums are a form of purgatory ;D. Our AMD mobility modding site used to get flooded by people from the HP forums trying to get fixes for their mobility devices. My laptop was one of those really strange ones which should have received Win 8 support from HP but never did precisely because of the switchable Intel + AMD graphics.
Am currently working on modding AMD 16.101.x drivers for mobility devices since pre GCN devices have also seen their last days of support from AMD. Much like a farewell driver and then I will take another crack at trying to understand how to mod IDT drivers properly. Last time I tried it just turned into a bit of a mess.
Complaining to MS might be the better strategy at this point since they are able to push Tempo into creating a new driver if there are severe issues with Win 10 + IDT. We tried a similar approach once when all newer AMD drivers caused people with the whole Mobility 5xxx gen and some 6xxx gens to only show a blackscreen on Win 10. It took the whole community to complain on the MS boards for AMD to finally fix the issues so that people could use Win 10. Unfortunately IDT drivers don't have the same type of leverage.
This driver does not have the DPC Latency fix which was introduced in driver 368.95.
I've measured the DPC Latency values with both drivers.
There's quite a difference.
It's best to stay with driver 368.95 at this time.