pikunsia :
Well Travis, I think this issue has to do with Win 8.1/10, but I doubt this is a Windows update problem. In my opinion this issue is exceptionally rare, strange. It is possible that the conflict is among the OS and something which has to do with the CPU. Since mid-September it happened to me just one time, never with Win7.
This "dead thread" is alive and well. I did a fresh clean install of Win10 2 weeks ago - completely reformatted and everything. No specific issue drove me to do this. I had upgrade from win7 to 8 to 8.1 to several iterations of Win10 previews and the official Win10 and on the official WIN10 upgrade my modern apps quit working. All else was fine though.
Since the reformat, everything has been perfect. Then last night it rolled and update (I'm on the insider fast track) and when it rebooted - bam.... this started. It does it every time I run the machine. And it is something muck later in the login process. SafeMode works fine. I can let it sit on my login screen indefinitely. But after login, it gets about 2/3 through the 15 seconds it takes to load startup items and stabilize and then crashes. So something loading in that last third is causing it.
The bootlog isn't really helping me. When I get home later I'm going to enable verbose logging and maybe use MSConfig in safemode and disable everything, then start adding halves of the startup items until I get it to fail. I'm hoping that works at least. If it crashes with everything turned off then I'll have to figure something else out. But either way, since everthing else seems fine, I can't see how it would be a CPU voltage issue unless Windows can directly impact the voltage.......
um.... That just made me think of something... Power management. Does the windows power saving feature for the processor usage have the ability to alter CPU voltage? If so, that sounds like it could be the culprit.