hi again, Bassie:
Thanks for the additional information on your system, Mobo, RAM, and HDDs. I believe that you made a mistake that is quite common for home users, and that is you attempted the Update with additional external drives plugged in to your Mobo other than your bootdrive (C: drive).
This is definitely verboten-forbidden on OS updates, and any licensed Tech will tell you the same!
Even if it's worked for you in the past on earlier versions of W10 or earlier versions of Windows, this is never a good idea!
Just as it's also never a good idea to perform an OS Update or Upgrade with ANY OTHER
devices plugged into the Motherboard other than your GPU card. This includes all secondary storage devices (HDD, RAID, NAS, SAN
, etc.), eSATA, Firewire, and other USB devices such as printers, scanners, WACOM tablets, webcams, etc. etc.
We've seen this problem going all the way back to Win2k and earlier with Windows, and that's why professionals are aware of this. Most Home Users don't read the fine print, but the Microsoft Windows license and install docs actually tell you this, but it's in itty-bitty fine print.
With the crush of all the people we are helping with W10 CU issues, I guess I didn't ask you specifically for all your HW specs; but, maybe I did or one of the other fine fellows helping you here did, but I'm just now noticing this reading the latest posts back from you--my bad!!
In any case, if you are looking for a culprit for why BSODs are randomly occurring on your machine after the first attempt at the v1703 CU Update--this would be an excellent candidate!!
So, before you throw in the towel on updating your computer to the CU version; try my advice here. Physically disconnect and or remove both those WD external drives from your machine (take them out of the case!), and unplug ALL
devices that plug in to your ASUS Mobo as mentioned; storage devices, printers, scanners, webcams, etc. Attempt to run the Update on your SSD drive (the Samsung), and see if it continues to BSOD. Like you said, your hardware works perfectly on v1607, so lets see what it does without all the peripherals and secondary external storage devices removed. Hopefully, it works better!
If not, at least we've removed this very common problem from the mix, and the real problem lies elsewhere, possibly with Mobo drivers, or GPU card drivers, and the dumps submitted will help kemical and others try to track down the problem. I forget, did you remember to visit the ASUS website and download all the BIOS
drivers for that Mobo and install them?? If not, you may need to do that in order for that Mobo to run v1703 CU version. We've seen very similar problems with earlier W10 builds as I've mentioned.
Give it a try when you can and keep us posted! You're story is now turning into a Journey of computer exploration.