Char Jackson wrote:

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

Char Jackson wrote:

Hmm, I started wondering about UEFI which, I believe, is used by your
mobo. I haven't delved into that.

When you boot using the USB thumb drive, I'm not sure how UEFI is
involved. When booting from a SSD or HDD, UEFI is involved. The whole
UEFI scheme was Microsoft wanting to lockdown an installation of their
Windows product. It seems to irritate Linux users because of the
SecureBoot protection.

Can you find a SecureBoot option in the BIOS and see what happens when
you disable it?

https://www.avira.com/en/support-for...tail/kbid/1811
https://docs.microsoft.com/en-us/win...ng-secure-boot

You'd think they have the firmware issue some bitch message that your OS
wasn't properly signed but knowing Microsoft they might've convinced the
BIOS makers to just immediately shutdown without a clue to the user.

The SecureBoot option comes disabled by default. I did go looking for it
to make sure, but I didn't need to disable it.

Charlie suggested checking the vcore voltage, which might have been too
low. I bumped it from 0.971v to 1.1v and I'm testing it now. The system
booted from the HDD for the first time and has been running now for
about 45 minutes. I'm optimistic.

I was looking through the data spec sheet at:

https://www.intel.com/content/dam/ww...heet-vol-1.pdf

to see what was the recommended normal operating voltage for Vcore or
Vcc. It says 1.52V maximum. Minimum is 0V (zero). Well, yeah, that
means unpowered. But you'd think they would list a recommended, normal,
typical, or optimal voltage.

Apparently there is some ambiguity regarding what is getting measured.
CPU-z looks to report Vcc but some users are saying the BIOS is report
VID. VID is the nominal voltage assigned to the cores in the BIOS where
Vcore/Vcc is the resulting voltage on the cores after regulation of VID.
If the BIOS uses the programmed voltages vs frequency coded in the CPU
at manufacture time, it uses VID when using the preset values or use
Vcore if you alter to a different voltage than VID.

https://www.anandtech.com/show/13468...aichi-review/3

That shows screen captures of the BIOS screens. Ugh, what a bunch of
noise in the UI. Lots of fluff instead of just grouped text of black
text on a white background. The OC Tweaker tab panel seems to be where
you set the voltage but their pic obliterated the CPU Core voltage
setting with them showing the popup dialog for selecting voltage mode.
With some BIOSes showing VID instead of Vcc, I'm not sure if "CPU
Core/Cache Voltage" is showing VID or Vcc.

According to the above data sheet:

Each processor is programmed with a maximum valid voltage identification
value (VID) that is set at manufacturing and cannot be altered.
Individual maximum VID values are calibrated during manufacturing such
that two processors at the same frequency may have different settings
within the VID range.

Okay, so I guess VID is something that is query-able so the BIOS knows
what voltage to use by default. If the BIOS was not configured for
overclocking, the expectation is that CPU is operable at the VID it
reports to the BIOS. At different frequencies, the CPU is programmed
for a different VID. I suppose the data sheet indicates the variance in
Vcc based on clock frequency but I got lost in that document. Since
you're not overriding the default settings with overclocking, the
expection is the programmed VID is what the CPU should work with.

https://www.overclock.net/forum/5-in...t-cpu-vid.html

That has some overclockers discussing VID and Vcore. I have to wonder
why the CPU has a failure when it is running at it programmed
non-overclocked (non-adjusted VID) values that it says it should work
at. Makes me wonder if there's a failing in the CPU or in the
regulation on the mobo to the CPU (BIOS specifies the VID but the CPU
doesn't get the expect Vdrop to have adequate Vcore).