Windows 10: How can I log processes/sevices that are causing slow shutdown?

Please run this log collector and post a zip into this thread:
Use extract > open
log collector v2-beta08.zip

 

Clear page file on shutdown

Start Registry Editor (Regedt32.exe).

Change the data value of the ClearPageFileAtShutdown value in the following registry key to a value of 1:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management
If the value does not exist, add the following value:
Value Name: ClearPageFileAtShutdown
Value Type: REG_DWORD
Value: 1

This change does not take effect until you restart the computer.

Hope it help.

 

I have a cheap Asus DG soundcard I purchased when my onboard sound crapped out. I used to boot 15 seconds, shut down quick with an occasional Office related hang.

Somewhere here In a thread about C-media drivers that the card used can be the source, I tried just to hack away the issue in the registry , made some progress. Installed a different Xonar Driver and the hang is almost nonexistent now.
I confirmed it the EV logs. However it's time for a new clean install of OS, I'm a lazy..........

When I opened up the case their was a petrified onion bagel, with cream cheese and a dead Palmetto bug.

I must of been drunk or stoned years ago, I prefer to think aliens left it.

 

I downloaded the ADK onto a play machine just to see what it did. Quite a lot actually and provided more information that mostly I didn't understand . I'm not going to post any logs because of the potential to give away information I might not want to, especially as I'm not sure exactly what it's collected.

However, after the latest updates I did on Mar 19th, the shut down time seems to have improved and I not going to spend anymore time on this problem

Thanks for all your help anyway

 

Glad you got it sorted. Misbehaving drivers are among the hardest performance degrading issues to diagnose. Sounds like you got a pretty good handle on it. And now, if the same symptoms present again, you have at least one thing to check immediately that may lead to a (re)repair of the issue. Good job!

One more thing: please mark the thread solved (click the green checkbox at the top of the page that's labeled "Mark as solved," depicted below), so other visitors to this thread will know it's been addressed and be able to learn from the fix/workaround that you uncovered.





Thanks,
--Ed--