Windows 10: BIOS POST on restart too long

Please review the forums rules about piracy.

*Arrow Forum Rules - Windows 10 Help Forums

 

I'm having this issue where the BIOS is taking very long to POST (mobo is a MSI B350). Typically 2-3 minutes. Strange thing is that this only occurs on a restart. When going from a shutdown machine to startup it POSTs and loads Windows quickly and normally (15 seconds?). I've googled around a bit but can't quite find a solution or a problem similar to mine. Any help in the right direction would be immensely appreciated!

Easy things I’ve tried so far:
unplug all usb peripherals on restart
update MOBO using MSI Live update 6
Clean install of latest NVIDIA graphics driver

As a side note - Not sure if coincidence or not, but I've been playing AC Origins for the past couple weeks with zero problems, but it has now started to randomly crash straight to desktop and feels like it has coincided with the BIOS issues. Could it be related?

:)

 

My Bios takes too long to load but it didn't use to!

I recently had an issue with my internet connection to the laptop which I am using(only my laptop can't connect to the internet). I went to acer page(Yes, I have an acer computer) and I downloaded all the wireless adapter drivers(you can find their names
at the end of this post). Since then when I open my computer it takes too long to open and it just loads something that didn't use to at the past.

When that is done it says : "no bootable file name" and then it boots and even when it had left the boot page it still keeps going so slow(something that didn't use to). I have tried lot of things but nothing solved it.

Wireless Adapter Names

1)Wireless LAN_Atheros_10.0.0.62_W10x64_A

2)Wireless LAN_Broadcom_7.35.267.0_W10x64_A

3)Wireless LAN_Intel_18.11.0.8_W10x64_A

***Post moved by the moderator to the appropriate forum category.***

 

My Bios takes too long to load but it didn't use to!

i went into bios and changed some things to its default nothing happend!

I said i downloaded some wireless drivers!

 

Do you have last BIOS installed ?

 

1) Open administrative command prompt and type or copy and paste:
2) sfc /scannow
3) dism /online /cleanup-image /restorehealth
4) chkdsk /scan
5) net user test /add
6) powercfg.exe /hibernate off
7) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread8) shutdown /r
9) logon with the new use named test
10) shutdown /r
11) sign on with the regular user
12) shutdown /s
13) Power on the computer
14) Open administrative command prompt and type or copy and paste:
15) powercfg.exe /hibernate on
16) shutdown /r
17) logon with the regular user
18) shutdown /r
19) logon with the user named test
20) shutdown /s

The above steps: check the operating system, drive file system, a new user, hibernation and fast startup.

Please report into the thread the findings of how the steps impact the boot.

If the BIOS post times are fine with hibernation off and problematic with hibernation on this is likely related to Windows fast startup.

In this case you would keep hibernation on and turn off Windows fast startup:
Turn On or Off Fast Startup in Windows 10 Windows 10 Tutorials

 

His problems are with BIOS not OS.

 

How can you determine the problem before seeing the impact of various steps?
Post On/Off Duration | Microsoft Docs

 

Ryzen boards and systems had/have problem with "Memory training" step when RAM, if not set manually has to cycle several times to set proper frequency and timing. That happens in BIOS no matter which OS. Last BIOS should fix that. Same was happening with my Ryzen and 3 different RAM sets and processors.

 

Microsoft Windows [Version 10.0.16299.371]
(c) 2017 Microsoft Corporation. All rights reserved.


C:\WINDOWS\system32>sfc /scannow


Beginning system scan. This process will take some time.


Beginning verification phase of system scan.
Verification 100% complete.


Windows Resource Protection did not find any integrity violations.


C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth


Deployment Image Servicing and Management tool
Version: 10.0.16299.15


Image Version: 10.0.16299.371


[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.


C:\WINDOWS\system32>chkdsk /scan
The type of the file system is NTFS.


Stage 1: Examining basic file system structure ...
615424 file records processed.
File verification completed.
9890 large file records processed.
0 bad file records processed.


Stage 2: Examining file name linkage ...
646 reparse records processed.
737048 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered to lost and found.
646 reparse records processed.


Stage 3: Examining security descriptors ...
Security descriptor verification completed.
60813 data files processed.
CHKDSK is verifying Usn Journal...
37899264 USN bytes processed.
Usn Journal verification completed.


Windows has scanned the file system and found no problems.
No further action is required.


1024146897 KB total disk space.
548287152 KB in 535987 files.
288616 KB in 60814 indexes.
0 KB in bad sectors.
756261 KB in use by the system.
65536 KB occupied by the log file.
474814868 KB available on disk.


4096 bytes in each allocation unit.
256036724 total allocation units on disk.
118703717 allocation units available on disk.


C:\WINDOWS\system32>net user test /add
The account already exists.


More help is available by typing NET HELPMSG 2224.




C:\WINDOWS\system32>powercfg.exe /hibernate off


C:\WINDOWS\system32>

 

The user test already exists so change the new user name to test4272018 or some other name so that there is a new user.
Then use the administrative command prompt command:

net user test4272018 /add

 

Yeah, it states that because I accidentally closed the command prompt while attempting to copy the information needed. So the "test" account is actually the one I was asked to create.

 

That being said. The problem still exists.

Countmike mentioned "having the last bios installed". I am unsure if he means flashing the bios or updating its drivers. As mentioned I have used Live update 6 to update drivers, but have not flashed the bios.

 

Run the beta log collector and post a zip into this thread:
Windows 10 Help Forums
(extract > open)
If there is any problem running the log collector then view the text and images in this thread: (post #5)
DM Log tool problem Solved - Windows 10 Forums


Please confirm:
1) Turning hibernation on or off had no impact?
2) Using an new user for logon had not impact?

 

This is correct.