I've been beating my head against this for a couple days. Before I get into it, here's my system:
i7 7700k
MSI Z270 Gaming M5
16GB EVGA DDR4 3000 RAM (2x8GB)
1080Ti
SanDisk Extreme 120GB SSD (Boot drive)
PNY CS2211 480GB SSD
Toshiba 3TB 7200RPM HDD
Seagate 4TB Barracuda 7200RPM HDD
Windows 10 version 1709
Task Manager says BIOS time is 11 seconds. I know it could be lower, but I'd have to wipe my drive to GPT, so it's not something I'm especially concerned with at the moment unless it's directly related to my issue.
I've had this setup mostly unchanged for a little over a year. I added the 4TB HDD a few months back, nothing changed then. A week or 2 ago Windows 10 took a really long time to boot up. In the realm of 3 minutes instead of it's regular 5-10 seconds. I checked Event Viewer, fixed the errors it was giving me, still took a while to boot up but I gave up anyways and it was fixed the next day. Booted up like normal for the next week or so, until yesterday.
Yesterday I unhooked everything to physically rearrange my desk setup, and when I hooked it all back up Windows was back to taking a long time to boot. It's consistently a 3 minute long boot. BIOS seems to have no problem, keyboard and mouse light up and I can go into BIOS. After MSI splash screen, keyboard and mouse lights turn off, Windows logo comes on with the spinning circle and then 3 minutes later I'm on the login screen.
Things I've done:
Attempted startup repair, it said it couldn't repair. I'm assuming that means there was nothing wrong that it could find.
Rechecked errors in Event Viewer. It's back to giving me an error again about a DistributedCOM, but it happens well after logging in, and the system works fine once I'm logged in.
Checked SMART stats, everything comes up okay.
Safe Mode boot, which I thought used to give a list of drivers being loaded so I could see what was taking so long, but that appears to no longer be the case in Windows 10. Safe Mode boot still took 3 minutes.
Selective start-up with MSCONFIG, with boot log and OS boot information checked, and a regedit to enable verbose. Not super helpful, as there aren't timestamps. I've also tried to change the Timeout to 10 seconds, to see if that helped shorten the time. It still took the same 3 minutes.
SFC Scannow command, which came back with no "integrity violations"
Windows Performance Recorder with these settings: Boot, Light, File, 1 iteration, and these checked: First level triage, CPU usage, Disk I/O activity, File I/O activity, Registry I/O activity, and Networking I/O activity. It says that pre session init took 2 seconds, session init took 5 seconds, winlogon init took 6 seconds, explorer init took 1, and post boot took 26. It seems like post boot is the stuff loading up after I actually log on, as it's the last section, but even then the results say that everything took a little over 40 seconds, and not the 3 minutes I'm experiencing.
I have fast startup disabled in "Choose what the power buttons do" in Power Options.
Tried a startup with everything except a single monitor unplugged, no change.
Windows and drivers are up to date. Though my storage drivers say they were last updated in 2006, and my PNY SSD isn't recognized in Properties > Hardware. Like my other drives list the model number, but the PNY says "Unknown device". I'm still able to access it no problem. Additionally, from the Properties > Hardware page, if I choose Properties again, and then go over to Volumes, everything is blank on every drive. I had to use command prompt to check if my drives were GPT or MBR.
I also tried uninstalling the Windows update from April 11th, in case that was causing issues. No change.
I have a few more options to try out: I need to go buy a flash drive tomorrow for memtest, as I have no CD/DVD drive. Unplugging drives if memtest comes up clean, my computer is behind my monitors and it's a little awkward to get back there, then on the other side of it to get to where the drives are. If it still happens with drives unplugged and RAM passing, then a reinstall of Windows, and if none of that helps then my last resort will be to replace the SanDisk SSD and hope that fixes it.
Does anyone have any other suggestions I can try out?
Submitted April 17, 2018 at 04:01AM by a_park_bench https://ift.tt/2HmtV3l
0 komentar:
Post a Comment