I don't know when this happened but lately my boot process is crawling. It stops at the USB check for about 30 seconds then the memory test for 30+ seconds then checking the disks. Previously, it simply ran thru all of this and went straight into Windows. I looked thru the bios and couldn't see anything. Then I did a system config reset and just changed the screen logo to off. Still no change.
Any ideas?
upload your MSINFO32.nfo file.
- Click on the start button
- Type "msinfo32" (without quotes) in the search bar of the start menu, click the resulting link. It will open the System Information window.
- File>Save. In the "File Name" filed, put "MSINFO32" (without Quote), give the save location to desktop, and click the "save" button.
- Give the time for processing, it will save a .nfo file on your desktop.
- Zip it, and upload it following the instruction.
Thanks Arc,
Here's the zip.
Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.
- Click on the Start button
- Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
- Select the “Startup” tab.
- Deselect all items other than the antivirus.
- Apply > OK
- Accept then restart.
Also try Pura's boot time defrag. Puran Defrag - Automatically Defrag your Hard Disk Drives
Let us know :)
I think you may have misunderstood. Windows comes up quickly. No problem there. The problem is turning the computer on. The boot up process is what's slow. Once it hits the OS, everything is OK. The boot process is what is taking a long time.
My understanding is the boot sequence is not affected by disk sectors so defragging would not make a difference. I could be wrong there.
When you say "boot up process" do you mean when the windows flag is on the screen (or loading bar, depends on hardware, i think) or the time it takes to get there?
From a cold boot to the "Starting Windows" message. That whole process. Once Windows starts it snaps to ready in just a few seconds (SSD drive helps here). When the computer is turned on, the entire bootstrap process is painfully slow. Used to just pop thru all the messages and go to Windows. Now, there are long stops between each check. My BIOS does not appear to have the option of bypassing this process. My concern is more about something being wrong then the amount of time it takes since it only started doing this a couple of weeks ago.
I have not added any hardware to my system.
hmm, this is the closest i could find to your problem, see if any suggestions here help
(Warning: one option suggested includes taking out the CMOS Battery, it will reset any changes made to the BIOS and restore it to default)
Link >> >> ASUSTeK Computer Inc.-Forum- Taking forever to "auto detect sata port 1"
Got it narrowed down. It is, specifically, the USB controller group. When I first boot up the computer immediately stops at the "Initializing USB Controller," or something like that. Then it hits the first IDE disks then stops at another USB config. After that it boots up into Windows.
I went into the BIOS and disabled the "Legacy USB Support." This decreased the wait time substantially and I didn't get the second USB message. I also disabled "NEC USB 3.0 Controller," since I'm not using any USB 3 devices. The boot time has decreased but I still get that long pause at the "Initializing..." message.
For testing purposes, I disabled the USB connection completely. The computer booted faster then I could read the messages but, of course, I couldn't use my KB+M.
With USB enabled, I can use all of my USB devices but I have that pause. It's a lot better than before but I'd really like to know what the pause is about, especially, if it's an indicator of something wrong.
just remember, if the OS crashes, and you want to reinstall from a USB drive, you will have to reset it so you can use USB devices again. Also, since the problem is partially fixed, you can decide to mark the thread as solved, or you can send us a pic of the "initializing" screen and we may continue to try and fix the problem
Quote