Just wanted to provide a clue that I stumbled on, and a potential workaround. My problem was with a late 2015 iMac after adding an internal hard drive and trying to create a Windows boot partition using Boot Camp Assistant (which failed). The crashes were exactly the same as those reporting a blank screen or freezes requiring a restart after waking from sleep.
Briefly, I spent a week and tried everything to fix this: reset SMC and NVRAM, repaired the volume several ways, repaired permissions through the command line, reverted to old systems, and on and on. I went so far as to install a fresh Sierra system on a fresh internal SSD and still had the crashes/freezes. No apps or extensions added to the system – no partitions to the drive. All as vanilla as possible, and it still crashed on waking. It also happened when booting from external Thunderbolt drives.
The thing I found was that the system only crashes when I put it to sleep, not when I let it "fall" asleep. If you've got a MacBook, then closing your lid is the equivalent of putting it to sleep. I would suggest trying to let the machine fall asleep with the lid open or tilted... deep sleep, not just screen blanking. See if the machine wakes properly. It works well enough for me that I'm living with this small workaround. Apparently, there's a different code sequence for 'falling' vs. 'putting' to sleep.
If you're struggling with this, you've probably already searched a number of forums, and you've probably seen that this is not limited to recent operating systems or hardware – it dates back to at least 2009 as far as I could see. Sleep is also one of the trickiest things to get right with a Hackintosh, so I think it's a rather fragile part of the MacOS architecture... and one that appears to be getting even more fragile. It seems that hardware changes may trigger this, since it happened to me on fresh systems and boot drives that were previously problem-free. One thing I did not check was RAM – faulty RAM or motherboards were other reported causes, but I'm not sure that correlates with what you all have reported here.
I think it's time that Apple re-engineer this part of the system – it's obviously been problematic for a long time and is likely to only get worse as they lock down the system even more with SIP, APFS, default disk encryption (coming soon), etc.
In the meantime, I hope this helps somebody. I'll update if I find anything else along the way.
