asus mobo. firmware responds very slowly

shmu26

Distinguished
Feb 18, 2014
443
1
18,815
mobo Asus B150M-K D3
American megatrends.

desktop custom built, a few months old

I did a system restore today, due to some minor windows issues having to do with file history, and then I had problems with the firmware

It started to splash the asus advert at startup, even though I previously set it to skip that.
So I tried to enter BIOS to reset that issue.

at first I thought it didn't work at all, but then I discovered that if I mash delete on startup, and then go to do the dishes, when I come back the BIOS screen is showing.
Great, so I tried to enter advanced settings, but again, it takes FOREVER to respond.

Okay, so let's say I don't want to go into BIOS, I just want to boot windows. It coughs a couple times during the firmware stage, and takes a few extra seconds, but then windows loads normally after that.

What to do?
I already have the most recent firmware.
I thought maybe I will flash it anyways, but it takes way too long to do anything in BIOS, and I am afraid it might get stuck in the middle, and then what?

edit: I tried to run a x64 VM, using VMware, and I get an error message that the intel VT-x settings in the firmware are not right. That's another tweak I had made in the BIOS that now has reverted to default.

second edit: ufi boot, windows 10 pro x64
 

shmu26

Distinguished
Feb 18, 2014
443
1
18,815
I just went back 24 hours. there were no driver changes since then, as far as I know.
I don't have a gpu, just integrated graphics, skylake i-5. no overclocking.
my firmware is up to date for sure.
 

shmu26

Distinguished
Feb 18, 2014
443
1
18,815
okay, I updated the drivers manually, and then I downloaded an asus EZ update utility, which said everything is up to date.
I tried using it to install the downloaded BIOS file, but I got an error message:
the model of the bios image doesn't match the bios rom currently present.
but this is wrong, because I am trying to install the same model.
I tried disabling windows firewall, but didn't help.
 

shmu26

Distinguished
Feb 18, 2014
443
1
18,815
I can't update the bios in the bios because that's the whole problem -- the firmware is not working right. I click on options, and it just hangs forever. I am afraid that even if I eventually get to the right place in bios, it will get stuck in the middle of the update, and my PC will be bricked.
 

shmu26

Distinguished
Feb 18, 2014
443
1
18,815
good morning,
I tried the battery trick but it didn't change anything, just asked me to set the time, and then back to the same situation.
I think I will just leave things as are, and wait and see, rather than trying to flash the BIOS and risk bricking it.

There is nothing mission-critical that I need to do in BIOS; windows 10 lets you boot to flash drive straight from the advanced options screen, so I am basically covered. I don't really need those x64 VMs, the ones I need are x86, and they work.

thanks to all for the help, if anyone has further suggestions, I am happy to hear them.

 

shmu26

Distinguished
Feb 18, 2014
443
1
18,815
okay, I mustered the patience to try and re-tweak my bios.
It wasn't as bad as I thought. Some screens load at almost normal speed.
anyways I got my intel cpu options sorted out, so I can run x64 VMs, and I also got rid of the ASUS advert at startup.
I even tried EZ Flash, but for some reason, it won't accept my CAP file, even though I downloaded it from the ASUS site, from the page for my exact mobo. Maybe it only allows upgrades, not a re-install of the same firmware version?
 

shmu26

Distinguished
Feb 18, 2014
443
1
18,815
I discovered that Windows was failing in its attempts to update my intel integrated graphics driver (this driver comes built-in with skylake processor, it is not related to the MOBO, and the driver is not on the MOBO manufacturer's site).
I downloaded driver from intel site
I tried to install, it failed
I succeeded in installing it after booting into safe mode

after this, the BIOS menu opened right away, and the firmware gave expected behavior.
Maybe the graphics driver was the problem all along?