I don't need to troubleshoot the BSOD (AMD RAID driver is implicated, see below), but I'd really like to get the legacy boot menu to display every time, even after the cold start (as it was with version 1607). It's still Metro and not legacy boot menu, but at least the boot finished fine when the menu is displayed. The BSOD crash happens (roughly) 9 out of 10 times, but very rarely the proper Metro boot menu is displayed after the cold start. I don't understand at all why there is that difference between the cold star and warm start.

I've set the boot loader preference with both EasyBCD and the command line, but with cold start Metro boot loader forces itself. What the heck is going on that after powering on the system that Metro boot loader is used, but with warm restart the desired legacy boot loader is used? I don't like Metro boot loader and would like to use the legacy one, but the system ignores the preference with cold start. When I select any OS from that menu there is no crash.

It takes a memory dump and reboots on its own, but then it correctly displays the legacy boot menu. So, when the system is powered on it doesn't display the boot menu, but immediately starts booting 'something' (Metro boot loader behavior) and crashes with DRIVER_POWER_STATE_FAILURE message. I've set the boot loader to be again the black Vista/Windows 7 style boot menu, but the system seems to be ignoring the setting when cold starting (after power on). A few weeks ago I've upgraded to version 1703 and immediately boot problems started. I've been using the legacy (non-Metro) boot loader then and everything was fine. It's a dual boot system with another (maintenance) Windows 10 partition on it. I've built a new PC a few months ago and initially installed Windows 10 version 1607.