Hmm, an interesting thought, but I am as confident as possible in saying that this isn't a BIOS/Controller/Chipset problem. The reason is that this is now my 3rd reformat, even though I only mentioned the last reformat. I am running the most recent version of all drivers
and BIOS, etc., and have been doing so all along. This particular issue popped up only recently, just before my last reformat, and it has persisted.
FYI- I am running multiple sets of drives, now, even though my profile lists only 6. Currently, I run 6 drives via an Areca RAID6 + an OS/Apps SSD; however, I also have an additional 4 drives that are non RAID/JBOD via my MOBO's onboard Marvell controller. It makes no difference where I am trying to save a particular file to, even though I don't think that would make a significant difference anyhow. Also, I have tested without my RAID card and all other drives but my OS/Apps. No difference.
Also, I have a separate drive that contains a basic installation of Win7x64. I use this for testing, etc. It has no additional software installed beyond drivers, etc. It exhibits no problems.
I am fully aware that because I have found relatively few complaints regarding this issue following the MS update it is most likely that I 3rd part application is causing this problem. I'm posting here to fish for likely problems.
If it helps, when the dialog hangs, it does so instantaneously. ProcMon & ProcExp, etc. all report nothing unusual. Neither does MS event viewer. Curiously, when the dialog box hangs, ProcMon hangs as well.