• Happy holidays, folks! Thanks to each and every one of you for being part of the Tom's Hardware community!

Really bad start/ post times

Zombie21

Reputable
Dec 30, 2015
61
0
4,630
So I have an i7 7700k, a TUF Z270 Mark 1 Motherboard, 16GB of DDR4 RAM And Windows 10 Pro on a 250GB NVMe M.2 SSD. I have No startup Programs and the post time is set to 0 seconds (despite still displaying and staying on the screen for more than 9)
I have another system that has an i5 4960k, An ASUS MAXIMUS VII RANGER motherboard, 8GB DDR3 RAM and a 250GB SATA SSD. Strangely this System boots 100x faster than that of the other system.
If anyone can give me any explanation or if you require anymore specs Please let me know!
 
Solution

That's a puzzling one, then. All I can think of is to try removing or disabling different parts/subsystems to get to a minimal configuration to see which one might be causing the delay; after that, it might be a matter of working with the motherboard manufacturer's tech support (and/or the manufacturer of the...
Have you disabled any fan headers that don't have fans connected to them (if the BIOS allows you to do this)? Some boards that I've used in the past have sat for several seconds waiting for non-existent fans to return tacho signals, then eventually timed out and continued booting. (It might be worth disabling other unused connectors, such as vacant SATA ports, too for the same reason.)
 


I've been able to disable all the SATA ports that aren't in use (port 5 and 6 are disabled automatically since i'm using M.2 devices) boot times are still 30+ seconds which is nonsense for an SSD.
I noticed that changing the post time does nothing (it's set to 0 seconds)so i wonder if it could be a component timing issue I have enabled S4+S5 in the ErP/EuP settings since the RGB lighting used to stay on even when shutdown
 

That's a puzzling one, then. All I can think of is to try removing or disabling different parts/subsystems to get to a minimal configuration to see which one might be causing the delay; after that, it might be a matter of working with the motherboard manufacturer's tech support (and/or the manufacturer of the part if it was something other than an onboard subsystem) to try and fix it.
 
Solution