Sign in with
Sign up | Sign in
Your question
Solved

UEFI Shell BIOS Configuration

Last response: in Motherboards
Share
August 16, 2013 7:04:03 PM

I know it's possible to read the BIOS settings and save them to a text file using the EFI Shell.

What I'm wondering is if it's possible to change bios settings using a similar method. This would have numerous advantages when used to configure multiple systems... But the main reason I am asking is because I am helping a friend with a seriously strange problem. His VCore is too low and is causing his new PC to crash before he can get into the BIOS settings and make the necessary changes.

I'm thinking it may be possible to remove all IDE/SATA cables which would force the PC to boot into the UEFI Shell and then quickly run a pre-configured command to alter the VCore.

Then again, this may not work either... But I'm at a loss for other possible solutions at the moment.

Motherboard is an Asus Z87-Pro running the 1205 Bios.
a c 217 V Motherboard
August 16, 2013 7:09:52 PM

Did you try a hard reset of the BIOS to its default state (jumper or pull the battery method)?
m
0
l
a c 169 V Motherboard
August 16, 2013 7:19:17 PM

Gabis said:
I know it's possible to read the BIOS settings and save them to a text file using the EFI Shell.

What I'm wondering is if it's possible to change bios settings using a similar method. This would have numerous advantages when used to configure multiple systems... But the main reason I am asking is because I am helping a friend with a seriously strange problem. His VCore is too low and is causing his new PC to crash before he can get into the BIOS settings and make the necessary changes.

I'm thinking it may be possible to remove all IDE/SATA cables which would force the PC to boot into the UEFI Shell and then quickly run a pre-configured command to alter the VCore.

Then again, this may not work either... But I'm at a loss for other possible solutions at the moment.

Motherboard is an Asus Z87-Pro running the 1205 Bios.


If the VCore is too low and won't reset via normal reset methods then there's something physically faulty with the power delivery on the board and it should be RMAed. The Intel 8 series motherboards only work with a single series of CPUs, so there's no inter-generation compatibility issues.
m
0
l
Related resources
August 16, 2013 10:03:38 PM

COLGeek said:
Did you try a hard reset of the BIOS to its default state (jumper or pull the battery method)?


The BIOS is in it's default setting and has been reflashed multiple times.
m
0
l
August 16, 2013 10:07:39 PM


If the VCore is too low and won't reset via normal reset methods then there's something physically faulty with the power delivery on the board and it should be RMAed. The Intel 8 series motherboards only work with a single series of CPUs, so there's no inter-generation compatibility issues.[/quotemsg]

This is the second board with the same issue. He is unable to return the board for another model, only replacements. I find it highly unlikely that he received two boards that are faulty.

Regardless of this particular problem, I still want to know if it's possible to change bios settings from the EFI shell. It seems like it should be, and I believe Intel even provides such a tool for its workstation boards but I'm unable to find a solid answer.
m
0
l
a c 217 V Motherboard
August 17, 2013 7:13:21 AM

If you can't get into the BIOS, how do you know the VCore is too low?
m
0
l
August 17, 2013 6:08:36 PM

COLGeek said:
If you can't get into the BIOS, how do you know the VCore is too low?


Because that's the blue screen error that appears whenever you try to load up Windows. Have swapped motherboards, psu, tested ram and cpu on another system...

so no one knows anything about EFI Shell coding then?
m
0
l

Best solution

a c 169 V Motherboard
August 17, 2013 6:14:28 PM

Gabis said:
COLGeek said:
If you can't get into the BIOS, how do you know the VCore is too low?


Because that's the blue screen error that appears whenever you try to load up Windows. Have swapped motherboards, psu, tested ram and cpu on another system...

so no one knows anything about EFI Shell coding then?


That's very odd. I'd love to see a picture of that error if you can get one. I find it odd that he can get to the point where Windows begins to load but not into the UEFI settings.

I forgot to mention this above, but on the Intel 8 series motherboards, the voltage regulator for the CPU has been integrated into the Intel Haswell microprocessor package. Its possible that your friend has a dud CPU rather than two dud motherboards.
Share
August 17, 2013 6:59:09 PM

Interesting. I did not know that about the 8 series. Thanks for the info.

We tested the CPU in another machine and it booted fine, but we didn't test it long. Just a swap and pop to see if it was working. I forgot to mention that the PC was up and running fine for about a week before these issues arose. So maybe it would have worked for a little while in the other system and eventually failed as well.

I was also very surprised by the blue screen for VCore. Windows gets to the point where it starts to finish the installation, because my friend tried a reformat when the first intermittent crashing occurred. Then it BSOD's. What's even more interesting is that Safe Mode will work even longer, but will still BSOD before you can accomplish anything significant in the way of diagnostics. For whatever reason, the BIOS causes the crashes faster than either.

I'll try to get you a pic of the BSOD code. It doesn't specifically say VCore, but the code references that as being the cause of the crash.
m
0
l
a c 169 V Motherboard
August 17, 2013 10:06:51 PM

Gabis said:
Interesting. I did not know that about the 8 series. Thanks for the info.

We tested the CPU in another machine and it booted fine, but we didn't test it long. Just a swap and pop to see if it was working. I forgot to mention that the PC was up and running fine for about a week before these issues arose. So maybe it would have worked for a little while in the other system and eventually failed as well.

I was also very surprised by the blue screen for VCore. Windows gets to the point where it starts to finish the installation, because my friend tried a reformat when the first intermittent crashing occurred. Then it BSOD's. What's even more interesting is that Safe Mode will work even longer, but will still BSOD before you can accomplish anything significant in the way of diagnostics. For whatever reason, the BIOS causes the crashes faster than either.

I'll try to get you a pic of the BSOD code. It doesn't specifically say VCore, but the code references that as being the cause of the crash.


That is very strange. My experience with the 8 series motherboards is non-existent at the moment so I'd need to see a picture before I can comment further. If it was just a crash when booting into Windows or installing Windows I'd not be surprised, but crashing and erroring out when trying to enter the UEFI settings? That's extremely unusual.
m
0
l
September 2, 2013 5:15:47 PM

Was having trouble logging in for a few days, so I kind of forgot about this thread. Just wanted to post and say thank you for the help and info about the CPU regulated voltages!

Returned the CPU to the retailer and the PC has been running smoothly ever since. This one had me scratching my head quite a bit haha Thanks again!
m
0
l
a c 169 V Motherboard
September 2, 2013 7:01:17 PM

Gabis said:
Was having trouble logging in for a few days, so I kind of forgot about this thread. Just wanted to post and say thank you for the help and info about the CPU regulated voltages!

Returned the CPU to the retailer and the PC has been running smoothly ever since. This one had me scratching my head quite a bit haha Thanks again!


Excellent. This is the first confirmation that I've had of a Haswell CPU having a flaky internal voltage regulator.
m
0
l
!