On Mon, 17 Dec 2018 23:26:06 -0600, VanguardLH wrote:

Paul wrote:

Char Jackson wrote:


This afternoon I took a recent Win10 ISO image and burned it to an m.2
NVMe drive. I disconnected the optical drive and the SATA HDD, then
installed the m.2 drive. Twice, out of about 20 boot attempts, I saw a
flash of the initial login screen from Win10, but in every case the
system would power down, pause, and restart. So it's not a Samsung 2TB
SATA HDD issue.

A thread with a good deal of weirdness in it.

http://www.tomshardware.com/answers/...rd-owners.html

One person may have damaged a CPU.

Hard to believe they don't test this stuff and monitor
the voltage settings the BIOS is using, under lab
conditions.

Paul

Flashing back to 1.30 (from 1.80) would be one of those "frickin'
frackin' son-of-a-brishing azzholes".

When you upgrade the BIOS, did the updater offer to save the current
code into a .bin file (so you could revert)? You could then go back to
1.20 that came in the mobo, see if that works, try 1.30 (or something
just incrementally next in version), and keep walking forward until the
mobo puked again, and then step back a version.

I read in their forum that you can, under normal circumstances, go from
any BIOS version to any other BIOS version. Choosing to believe that, I
skipped the step where I could have saved 1.20 to a storage device,
especially since plugging in a storage device had a habit of making the
whole system unstable. I got lucky and the upgrade went well.