Overclock.net banner
Cancel
Create thread New Forums

Windows takes 30+ minutes to boot UPDATED...issue resolved itself?

Tags
bios boot overclock windows windows 10
Jump to Latest
1 - 20 of 23 Posts
C

CarSalesman

· Registered
Joined
·
3,724 Posts
Discussion starter · #1 ·
Windows is taking 30-60+ minutes to boot.

Wouldn't boot into safe mode (although I did not give it 30 minutes, it may have).

Turned off my overclock, XMP, same result. Overclock was nothing crazy, just 5.6Ghz P-core 4.5 Ghz E-core 5.0Ghz ring on a 13700k. I considered the possibility of having fried my CPU but I haven't even reached 80 degrees C during benchmarks and had it undervolted with Vcore showing 1.360v and VID 1.413v.

Did automatic startup repair both from the boot drive and from a windows install USB, sometimes it says it repaired things, sometimes it says "couldn't repair." Same result.

Went into command prompt using recovery tool and input some commands using DISKPART among others to try to repair the boot files, same results.

This morning after leaving computer running all night it was loaded into windows just fine; everything seems normal.

I'm afraid to turn off/restart the PC now for fear of it being inoperable during excessive boot timeframes.

I have read a few folks on here mention they corrupted their BIOS while working on establishing a stable overclock, should I reflash BIOS to be safe?

My options are to deal with it and rarely turn off pc, reinstall windows, or reflash bios.

Any ideas or input?

Thoughts are appreciated.
 
#2 ·
It sounds like a failing hard drive. Replace it with a solid state drive.
 
Save
Reply Quote Rep+ Rep+
Discussion starter · #3 ·
#4 ·
I'm not sure why you haven't reflashed your BIOS already, and simply booted up with pure stock (everything auto) just to rule it out.
Run the DISM and SFC CMD commands to make sure the OS is in working condition.
 
Save
Reply Quote Rep+ Rep+
Discussion starter · #5 ·
Ichirou said:
I'm not sure why you haven't reflashed your BIOS already, and simply booted up with pure stock (everything auto) just to rule it out.
Run the DISM and SFC CMD commands to make sure the OS is in working condition.
Click to expand...
Thank you for the input!

Just did both those CMD commands. The system file checker found items to repair! But still same issue with slow boot.

Restarted PC and updated to latest BIOS via BIOS flash. Still slow boots.

Disabled fast boot in windows (not bios, that is already disabled by default). Currently waiting for it to finish loading back in so I can try disabling all the non-Microsoft startup apps and reinstall graphics drivers and try one more time to see if it does slow boot again…

Next is fresh windows install on new Western Digital PCIE4x4 M.2 i’m picking up at BestBuy tomorrow.
 
#6 ·
Where is it hanging? On POST, on subsidiary firmware loading (if board has such) or Windows loading?

Will it boot to a USB stick at a "normal" speed? (e.g.: Ubuntu 22.04 live)
 
#8 ·
Memory training. Remove all adjustments, inc XMP set everything to default,AUTO. Might need to update bios or reinstall Windows if it continues. Maybe try a different HDD w/new Windows install before you do to check.
 
Discussion starter · #10 ·
Paradigm Shifter said:
Where is it hanging? On POST, on subsidiary firmware loading (if board has such) or Windows loading?

Will it boot to a USB stick at a "normal" speed? (e.g.: Ubuntu 22.04 live)
Click to expand...
It gets stuck loading windows with the teal/turquoise windows logo and the spinning white dots that make a circle below it.

I timed it last night, one time it took 18 minutes and the next time 29 minutes to get into Windows. When I was gaming last night, sound was glitching out intermittently, game also staggered here and there.

I don't have an alternative OS to boot to apart from a Windows 10 boot/installation USB.

I am buying a second M.2 today to try a Windows install on that; I don't want to reformat my current OS boot drive until I can image it onto an external HDD that I am getting soon in the mail from rewards points from work.
 
Discussion starter · #11 · (Edited)
Hold my Pickle said:
Hi, have you checked your windows error logs after finally booting?
Click to expand...
Yes, the only thing that appeared odd was the time gap between when boot began and the last minute before it finished. As in there were lines timestamped when boot began and then like 27 min later 10 more lines and then windows finally loaded in.
 
Discussion starter · #12 ·
Digitalwolf said:
After you set the bios back to let's call it defaults... did you ever try a fresh install on the new 980? Was the OS install done with the OC settings?
Click to expand...
No, BIOS was all default when I did Windows install. I may have had XMP on.
 
Discussion starter · #13 ·
Redwoodz said:
Memory training. Remove all adjustments, inc XMP set everything to default,AUTO. Might need to update bios or reinstall Windows if it continues. Maybe try a different HDD w/new Windows install before you do to check.
Click to expand...
Thanks, going down that path right now.
 
Discussion starter · #14 ·
I also reinstalled my video drivers and checked the box to remove previous install and confirmed it is still slow booting.
 
#15 ·
A month a two ago this randomly happened to me, not sure it matters, but same 980 pro. I tried pretty much all the steps you've gone through, and thankfully remembered a I had an image backup from a couple days ago, The restored image, got rid of the problem and has never come back.. but you bet your ass I've been backing up my install religiously now.

My guess is you don't have a backup to try, but at least there may be some piece of mind it probably isn't the hardware. Just my guess.
 
#16 ·
CarSalesman said:
I am buying a second M.2 today to try a Windows install on that; I don't want to reformat my current OS boot drive until I can image it onto an external HDD that I am getting soon in the mail from rewards points from work.
Click to expand...
Why don't you try cloning the old drive onto the new m.2 drive first. If that works, great. If not, you can try a clean install after that on the new drive.

You can use Macrium Reflect to clone the drive and if you need to you can make a boot drive for Macrium on a USB.
 
Save
Reply Quote Rep+ Rep+
Discussion starter · #17 ·
UltraMega said:
Why don't you try cloning the old drive onto the new m.2 drive first. If that works, great. If not, you can try a clean install after that on the new drive.

You can use Macrium Reflect to clone the drive and if you need to you can make a boot drive for Macrium on a USB.
Click to expand...
I may try that. I think I already have Clonezilla on a USB.

I may also just do fresh windows install on the new M.2 cuz I am tired of my computer not working properly and feel it is a higher likelihood of finding the culprit/solution sooner.
 
Discussion starter · #18 ·
thornygravy said:
A month a two ago this randomly happened to me, not sure it matters, but same 980 pro. I tried pretty much all the steps you've gone through, and thankfully remembered a I had an image backup from a couple days ago, The restored image, got rid of the problem and has never come back.. but you bet your ass I've been backing up my install religiously now.

My guess is you don't have a backup to try, but at least there may be some piece of mind it probably isn't the hardware. Just my guess.
Click to expand...
Thanks for posting your experience. I don't; I've only had this rig running for a little over a week, got it running two Sundays ago. Only thing I don't want to hassle with is my personalized World of Warcraft game and addon settings. It will be nice to just grab them off of my current SSD.
 
#19 ·
CarSalesman said:
It gets stuck loading windows with the teal/turquoise windows logo and the spinning white dots that make a circle below it.

I timed it last night, one time it took 18 minutes and the next time 29 minutes to get into Windows. When I was gaming last night, sound was glitching out intermittently, game also staggered here and there.

I don't have an alternative OS to boot to apart from a Windows 10 boot/installation USB.

I am buying a second M.2 today to try a Windows install on that; I don't want to reformat my current OS boot drive until I can image it onto an external HDD that I am getting soon in the mail from rewards points from work.
Click to expand...
Hm. I've seen Windows do some odd things when there were firmware conflicts (between an Intel SATA controller and the firmware in a Sandisk SSD in my case) which manifest as regular soft locks of up to 90 seconds after every 5-10 seconds of actual use, but these continued after Windows was loaded. I'm usually pretty sceptical of the use of Event Viewer (no, Microsoft, "Event 41" is not a useful troubleshooting output, nor is that freakin' sad emoticon - the system restarted unexpectedly, you think I didn't freakin' notice?!) but are any reports being generated when you get sound glitching or jerking? You've already said there is a big empty gap in the boot logs, which is why I tend to find Event Viewer about as useful as a chocolate teapot.

One of the great things about Linux is that (with some exceptions, usually revolving around technical support) it is free. Free to download, free to install, free to use. I also find Linux a lot less forgiving than Windows - if there is a hardware problem, Linux will usually flag it up quickly while Windows will either ignore it or just try to keep fumbling along as best it can. All you'll need is a USB stick and downloading a 2GB .iso file from, say, Ubuntu.

If you have access to a second system, I would download the Windows Media Creation toolkit and set up a Windows image using that - I've had issues with Windows 11 installing on some systems if I use any other image writing tool. I recommend a second system to avoid potential corruption of the image by creating it on a system which has obvious issues.

For troubleshooting, I would certainly not clone the current Windows install. For whatever reason there is something wrong with it, and since the exact cause is unknown, eliminating a possible cause from the list of variables is simply "best practice" for troubleshooting.

If cause uncertain (which it is) I wouldn't even have XMP enabled for initial testing. You mention a 13700K but don't mention board or RAM type (DDR4? DDR5?) so I would recommend going to whatever the lowest JEDEC rating is (2133MHz for DDR4, 4800MHz for DDR5) and running memtest via a bootable image (again, the Ubuntu live image should provide an option to run memtest) to prove the RAM is stable, even at lowest rated speeds. I have no experience with DDR5 right now, so I don't know how the "ECC" in DDR5 handles errors; will it spew errors into a log, will it try to silently correct, will it scream about the problem at boot? If it just tries to silently correct, the problem could be caused by bad RAM and the ECC going crazy. But like I said, I have no idea how DDR5 handles it. Honestly I have no idea how or whether memtest would even show errors in DDR5.
 
#20 ·
Oh yes make sure it is not connected to the net as Microsoft maybe trying to load drivers/update!!!
 
1 - 20 of 23 Posts
About this Discussion
22 Replies
8 Participants
Last post:
CarSalesman
Overclock.net
posts
28M
members
562K
Since
2004
The premier forum for overclocking experts and enthusiasts. Discuss hardware optimization, custom builds, benchmarking, cooling solutions, and pushing the boundaries of computing performance. From beginner guides to extreme overclocking, join our technical community to master system tuning.
Full Forum Listing
Explore Our Forums
Intel CPUs Hardware News NVIDIA PC Gaming Water Cooling