BSOD with Driver_Power_State_Failure after waking from sleep

Ever since updating to Windows 10 I have periodically had a problem with my computer when I wake it from sleep. The symptoms of this are as follows:

• The machine will wake from sleep fine and I'm able to put in my password etc. After 30s to a minute, the machine will give me a BSOD citing Driver_Power_State_Failure (occasionally it has been something else but this is the main culprit.) It then collects data cycling up to 100% but does not reboot automatically. I need to do this manually. When I do so, the machine will reboot normally.
• On a couple of occasions in the last month, the machine will simply not wake from sleep at all and neither does it respond when I press the power or reset buttons. The only way I can get it to start again is by manually turning off the power supply and then turning it on again. I am not sure if this is related to the BSOD issue or whether it is a separate issue.
• I have previously had an issue where the machine would appear to wake from sleep but the screen would remain dead and the keyboard was unresponsive (though the num lock light was showing.) I can't recall having this issue recently and am unsure whether this is a separate issue.
• It normally seems to occur after the machine has been asleep (hybrid sleep) for some time.
• Of late I've noticed that it often seems to coincide with me opening a new program or file immediately after waking the machine from sleep.

I have tried several things to fix the issue as follows:

• I've tried to run Driver Verifier but have never managed to get the machine to start up successfully even with only one driver selected. (In fact I have to manually import the original registry settings to turn off Driver Verifier again in order to get my machine going again.)
• I have uninstalled and unplugged a USB video capture device but that has made no difference.
• I have completely uninstalled the drivers for my graphics card and then reinstalled using Microsoft's default drivers. No difference.
• I've made sure that I am running the latest drivers, have checked Windows update etc.

It's tricky to pin things down to a particular driver without using Driver Verifier and I'm not sure how to decipher the dump files and error logs generated each time this happens. That's why I've come here for help!

Here's a zip with all of the relevant data. Attachment 61143

Any help you can give would be very much appreciated!