• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

New build, extremely long load time.

Page 2 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.
EVERYTHING I find on the internet related to this problem has no solution. The only consensus I have found is that some newer motherboards are checking every single connected drive for a boot option; even all the ports in the card reader.

The card reader can be slowing it down at two points. During the initial post, it has to detect all the USB devices. If this is one of those 1,000 in 1 card readers, it's probably adding multiple devices to the detection process and since they are all removable media, it's probably polling each one to see if there's media in it. As dbcooper mentioned, you may be able to decrease the drive timeout to improve this, just be aware if you ever need to boot off a CD or USB, you may need to change that setting back.

Secondly, check your boot order. If you have USB before your SSD in the boot order, it's again going to be checking that card reader for media before allowing your SSD to boot. I would check your BIOS settings and verify the reader isn't in your boot order. Especially since if it IS in the boot order before the SSD, if the computer is rebooted with a card in the reader, it's going to try to boot off that card.
 
Thank you for the suggestions everyone. The USB card reader is not set in the boot order at all. Here is something that seems strange to me. It sets the default boot device as "windows boot manager." If I change this to the SSD where Win 7 is installed....on startup is says "No boot device selected" (or some derivative of that). It will ONLY boot to Windows with "Windows Boot Manager" selected.

KiL
 
Also....I will hunt the bios for a drive time setting that may be adjustable.

Failing that.....is there something in this "Windows boot manager" that I can change to perhaps take the USB drives out of the boot equation?

That is assuming of course the problem remains with the new card readers (I should know in a day or two if Newegg ship times stay what they typically are).

KiL
 
Thank you for the suggestions everyone. The USB card reader is not set in the boot order at all. Here is something that seems strange to me. It sets the default boot device as "windows boot manager." If I change this to the SSD where Win 7 is installed....on startup is says "No boot device selected" (or some derivative of that). It will ONLY boot to Windows with "Windows Boot Manager" selected.

KiL

This is because you installed in EUFI mode.
 
Thank you for the suggestions everyone. The USB card reader is not set in the boot order at all. Here is something that seems strange to me. It sets the default boot device as "windows boot manager." If I change this to the SSD where Win 7 is installed....on startup is says "No boot device selected" (or some derivative of that). It will ONLY boot to Windows with "Windows Boot Manager" selected.

KiL

Hello KingLou, as VL pointed out, the boot manager settings must stay the same on the installed OS. Unless Windows is failing to boot properly, there is no real reason to change it.

As for the card reader, you would probably be better off returning it, and either getting something better (may help), or getting a USB unit (averting the problem.) Thousands of desktops, laptops, convertibles, tablets, etc. with card readers ship every day and do not have this problem, so I think this problem can be averted, just whether or not it is worth the time, effort, and expense.

Can you give a link to the unit you have now?
 
Yes...here is the unit I originally purchased:

http://www.newegg.com/Product/Product.aspx?Item=N82E16820192021

Since I am building my dad two separate PCs, I purchased two card readers, and I returned them both. Kinda weird...the first one I put in caused a boot time of 1 min 5 sec to Windows. The second one caused a boot time of 1 min 28 sec to Windows. Repeatably.


The units I ordered to replace them are this one:

http://www.newegg.com/Product/Product.aspx?Item=N82E16820223103


I am really hoping this clears up the issue. I used the same Rosewill card reader in a PC build for my brother about 6 months ago with no issues so we will see. But as I said, the limited information I have found on the web in regards to this issue seems to indicate it MAY just be an issue with newer motherboards and how they are handling these card readers.

I hope that's not actually the case, but worst case scenario....it's not all that bad anyway. I'm just a perfectionist. The computer this is replacing is about 12 years old, if that tells you anything about my dad's handle on PC performance. He would have never noticed it if I didn't mention it, but that's just not my way. If it's not right, I'm gonna figure out why. My pride is on the line after all. 😛

Here's the thing. He almost never powers down his PCs anyway. So it's, in the grand scheme, a very very minor issue. But for my own sanity I'm hoping to get to the bottom of it. Especially if I ever happen to build a PC in the future for someone in the future that actually does care that it takes 40 seconds longer to boot than it should (like me).

Regardless, I will update this thread with my findings on the new card readers.

KiL
 
Just to put this one to rest with a final conclusion. I tried out the new card reader and the issue stayed the same. Normal windows boot time without the card reader (under 20 seconds). With it plugged in, about 1 min 20 sec windows boot time.

I decided to try the other motherboard, even though my gut was telling me there wouldn't be a difference. Apparently my gut was off, and I should have done this earlier. With the new motherboard, everything is now perfect. Sooo...back goes the motherboard.

Thank you for everyone's input and patience with me as I pulled my hair out troubleshooting this annoyance.

KiL
 
Back
Top