SSD taking 2 minutes to boot

[InternetSwag]

If I check boot time though it says 9.42 seconds

I'm stuck on this screen for about 2 minutes;

Then before I get into Windows this Asus screen says (scanning and repairing H drive complete: 100%).

But when I get into Windows to check this H drive;

H drive is nothing? What can I do about this?

I updated my motherboard BIOS and it made no difference.

 

[ponder]

Delete H

Else backup, format, reinstall.

Why do you have so many partitions?

 

[InternetSwag]

Delete H

Else backup, format, reinstall.

Why do you have so many partitions?

I have 4 Drives, 2 ssd and 2 hdd

 

[InternetSwag]

I formatted H, seemed to be a bit faster, but still long imo.
i deleted H drive its now just 100mb of unallocated data
It no longer says scanning and repairing H drive but the boot time is still long.

Could it be wrong sata connections from drives to mobo?

 

[sajunky]

Start disconnecting drives one by one to see which one cause a delay.

 

[Soul Assassin]

Do you have fast boot enabled in the BIOS and also check if maybe your motherboard has a mix of SATA II and SATA III and make sure the SSD's are connected to SATA III.

 

[InternetSwag]

Start disconnecting drives one by one to see which one cause a delay.

I'll have to check this out tonight.

Do you have fast boot enabled in the BIOS and also check if maybe your motherboard has a mix of SATA II and SATA III and make sure the SSD's are connected to SATA III.

I do have fast boot enabled, but tbh I can't say which sata's are connected where, I'll have to check it out.

 

[PhireSide]

i deleted H drive its now just 100mb of unallocated data

As far as I know that may have been the SYSTEM RESERVED partition from an old installation. If I recall correctly Windows 7 made a 100mb partition. Windows 8.1 and up made them 350mb by default. Oddly enough on my fresh install of Windows 10 has a 100mb partition and a 549mb partition

Edit: Also how are you connecting four drives to a laptop?

 

[sajunky]

As far as I know that may have been the SYSTEM RESERVED partition from an old installation. If I recall correctly Windows 7 made a 100mb partition. Windows 8.1 and up made them 350mb by default. Oddly enough on my fresh install of Windows 10 has a 100mb partition and a 549mb partition

All correct and nothing to worry about.

 

[EasyUp Web Hosting]

Post a screen shot of Disk Management. That will tell us on which drive the 100mb partition was on.

Did your BIOS maybe change from UEFI to Legacy boot?

 

[shel0319]

Don't recommend using fast boot with Windows 10, with an SSD you should never need it. What is your mobo model?

Even on Sata 2, or if you have your Sata mode set incorrectly it wouldn't take that long to boot. Imo you have a hardware or driver issue which is causing the slow boot up time, check your system log as well as device manager - if you don't find anything there try booting without your other drives and any other critical hardware and add them back one by one till you've found the culprit.

If you're still stuck test all your drives with a diagnostic tool like crystaldiskinfo or seatools.

If everything above checks out fine you may need to reinstall / repair windows.

 

[InternetSwag]

Sorry guys been super swamped, I'm off tomorrow tho then I can check all the troubleshooting out.

So I used a screenshot I found online, sorry I don't actually have this problem in a laptop, it's just the exact same screen that I get.

I can post this rig so long tho;

Z370 A Prime
8GB ballistix RAM 2400
Gigabyte 1070 Ti G1
OCZ Arc 100 SSD
Kingston 240GB SSD (kingston sa400s37240g)
1tb Toshiba 7200 RPM
500GB Samsung 5400 HDD (really old by now)
Antec 750w PSU
8700 non k

I think I've had this issue since I assembled the PC about a month ago, only recently has it annoyed me enough to actually look into it.

 

[sajunky]

I think I've had this issue since I assembled the PC about a month ago, only recently has it annoyed me enough to actually look into it.

It looks like a clue. You have a boot sector pointing to the non-existing drive. It happens when you move a boot drive from some other PC's. You have to refresh boot sector on the boot drive to fix the problem.