Windows 10 Shutting down slowly all of a sudden

[chenw]

Hey all,

My windows 10, starting from yesterday, suddenly started to take its sweet time shutting down.

Normally, the schedule of of shutdown looks like this:

1. Hitting the shutdown button -> Seeing the blue shutdown screen with spinning fidget: ~5s
2. Spinning fidget -> Screen losing connection to computer: ~10s
3. Screen losing connection -> motherboard shutting down: ~5s

Starting from yesterday, it suddenly started to slowdown on all steps, especially the last step:

1. Hitting the shutdown button -> Seeing the blue shutdown screen with spinning fidget: ~30s
2. Spinning fidget -> Screen losing connection to computer: ~30s
3. Screen losing connection -> motherboard shutting down: ~1m

The last part has me worried the most, and when actually using the OS, my spinners feel a bit sluggish and everything seem to take longer than usual, boot times is pretty much the same as before though.

I have tried clean boot but that didn't help, they still take bloody ages.

I am going to backup my OS drive and reinstall my OS, but while I am waiting on doing that, what are other possible culprits for windows behaving this way besides startup and malware?

My windows 10 is still on AU, the CU is taking is bloody sweet time getting here on my version...

FYI, the system specs are:

i7-4790k
Z97x-UD5H
G.Skill F3-2400C10Q-32GTX (I got this RAM kit 2 weeks ago)
MSI GTX 1080
840 EVO 240GB SSD
MX100 512GB
3TB Toshiba
3TB HGST
6TB Toshiba

Thanks!

 

[Colif]

have you tried a restart?

try running trial version of hdtune on ssd and hdd, look on the health tabs

check windows update history and see if you got anything recently. MIght have also come from the windows store as some drivers are on there too.

You don't have to wait for CU, you can download the upgrade assitsnt from the 1st button here - run it and it will upgrade PC to latest version

 

[chenw]

The OS in question is Enterprise version, CU has not been released for that version yet, upgrade assistant always came back as "not available for your version" or something along those lines.

Restart works fine, I had to do that when I tried to get windows to boot clean, it's the shutdown that's the issue.

I'll check windows update, but I REALLY doubt it as I don't do updates during weekends, my NOD32 would have nagged me about my OS not being up to date and I usually promptly check for updates then, and it usually happens during weekdays.

I'll double check just to be sure. I haven't downloaded ANYTHING from windows store in a long time, but I will check that also.

I'll check the HDtune when I get back home, though I have a hunch that something in the background is nagging my HDD, not the fact my HDD are going.

The main that confuses me was that I haven't actually done ANYTHING to the OS itself during the weekend, no installing, no updates I am aware of, nothing, and it suddenly started shutting down slower, in fact my computer has been on continuously since saturday night until monday morning, and it's not the first time I have left that computer on for a weekend. NOD32 scan also came clean on the OS.

 

[Colif]

Is this a Work PC or your own? If work, you should talk to IT unless that is you.

Enterprise is on its own different update process, I didn't think to ask about what version you had - I just knew lots of people still hadn't been offered it on Home or Pro yety either

if clean startup doesn't change anything, it makes me wonder what is cause as startup programs are usually the main reason shutdown is slow (only makes sense if you consider what Fast Startup does). You could turn it off and see if it makes any difference - https://www.tenforums.com/tutorials/4189-turn-off-fast-startup-windows-10-a.html

 

[chenw]

I picked Colif's solution for solving the slow shutdown on my system, now my system shuts down like normal.

However, this time round, my startup is now taking its time, and I no longer believe its OS or software related, at least not entirely.

My post gets stuck on "64" code for significant amount of time (up to about half a minute, usually it jumps through it), and after the windows 10 logo shows up, getting to the login background, the OS takes another 30 seconds for the username to show and boot into the OS properly, and the startup applications that used to take fairly short amount of time to load now takes longer.

My 3dmark also couldn't run properly as it seems to completely unable to get my systeminfo, whether that is OS, program or hardware related, I don't know.

But the long post definitely doesn't feel right with me...

 

[Colif]

have you got the newest bios?

No clear cause of error here: https://forum.giga-byte.co.uk/index.php?topic=15318.0

according to page 119 of your manual, 63-67 = CPU DXE initialization is started

Driver eXecution Environment (DXE) Phase
The Driver Execution Environment (DXE) phase is where most of the system initialization is performed. Pre-EFI Initialization (PEI), the phase prior to DXE, is responsible for initializing permanent memory in the platform so that the DXE phase can be loaded and executed. The state of the system at the end of the PEI phase is passed to the DXE phase through a list of position-independent data structures called Hand-Off Blocks (HOBs). HOBs are described in detail in the Platform Initialization Hand-Off Block Specification.
There are several components in the DXE phase:

“DXE Foundation”
“DXE Dispatcher”
A set of “DXE Drivers”

The Dxe Core produces a set of Boot Services, Runtime Services, and DXE Services. The DXE Dispatcher is responsible for discovering and executing DXE drivers in the correct order. The DXE drivers are responsible for initializing the processor, chipset, and platform components as well as providing software abstractions for system services, console devices, and boot devices. These components work together to initialize the platform and provide the services required to boot an operating system. The DXE phase and Boot Device Selection (BDS) phases work together to establish consoles and attempt the booting of operating systems. The DXE phase is terminated when an operating system is successfully booted. The Dxe Core is composed of boot services code, so no code from the Dxe Core itself is allowed to persist into the OS runtime environment. Only the runtime data structures allocated by the Dxe Core and services and data structured produced by runtime DXE drivers are allowed to persist into the OS runtime environment."

http://www.tomshardware.com/forum/336587-31-motherboard-stuck-error-code-stands-initialized

the actual cause seems to vary, can be ram, can be a USB drive... its hardware not responding to PC, just need to work out what.

 

[chenw]

Yes, the BIOS is the latest, F10.

I'll spend more time playing around, after thinking about it, I think I MIGHT have a few suspects.

I'll report back when I get more testing done. I did try RAM, though it didn't work, I didn't test it thoroughly enough.

 

[Colif]

run on bare minimum, remove all extra hdd, d/c any speakers, unplug all USB, take off everything that isn't needed. Run on igpu if motherboard has one.

I had slow start ups last year and couldn't work it out. I was blaming a new GPU I had recently got as problems seemed to be related. That was a distraction, the actual cause was my speakers were dying and I only figured that out after a clean install which I did with PC in another room. It booted normal until I attached speakers.

I never suspected speakers as they had always worked. They were part of my room, I looked right past them. I have learned that lesson now.

 

[chenw]

Well I think I found the culprit.

I started simple, plugging the stuff outside of the case before moving into the case, and long behold, after I unplugged all USBs barring mouse and keyboard, the long bootup times were no were more. I think one of the USB hubs on my monitor is starting to give out. So far everything is back to normal again.

Thanks for the suggestions! I was looking into spare parts not 24 hours ago