In my case it turned out to be the Synaptics SMBus Touchpad driver. A clean install will not help you; I tried that and it has the same problem. You need to get an external mouse and use it to change to a different Mouse driver in the Device Manager. (I am using PS/2 Compatible) Do not touch your Touchpad even when Windows is starting. Doing so will cause the violation. Hopefully Microsoft will pull the Synaptics update soon. Stopping it from installing Automatically can be a real PITA, but it can be done.
It's already been 5 times. People need safe mode when something fails, not relying on some automatic system to dump them into safe mode (which doesn't work and may always fail in certain circumstances) no matter how well coded. There's a process to enable F8 in Windows 10, but it's too late in my case. Now I'm hosed. It's fine because it's just a test laptop, but this just proves MS's poor architecture.
Strange, sha-1 is those official from esd database 10074.0.150424-1350.fbl_impressive_CLIENTPRO_RET_x64fre_en-us.esd 24/04/2015 22:37:01 2,444.57 MB 6171FDB41101598D83604FD6C0BB4A51C0A88913 1AD8BE00BA0E3B3B899BDC9A7116AC6C16324E64D1EC8624C1E9620B91CC04C8