Windows 7 x64 15 minute+ shutdown (timeout?)


  1. Cas
    Posts : 4
    win xp
       #1

    Windows 7 x64 15 minute+ shutdown (timeout?)


    Hi guys,

    I've had x64 win7 installed for about a month, no troubles until now.

    The last few days, whenever I shut down the PC for the night the "shutting down" screen is displayed for more than 15 minutes, at this point I just turn it off via the front power button on the case as I'm afraid to leave it all night saying that as I'm not that tech savvy.

    Is there any way to figure out what's going on with the shutdown process? The following morning it starts up fine, and I restart with a disk check that comes up fine.
      My Computer


  2. Posts : 13,354
    Windows 7 Professional x64
       #2

    Welcome!

    That is usually caused by a program that takes forever to close. What happens if you shut down as soon as it boots?

    Next time, before you shut down, end half of the processes in Task Manager. Be sure to record which ones you close!

    If the shutdown is quick, you know the rogue process is in that half. If not, try the other half. From there you can narrow it down further until you identify which program is causing the hang.
      My Computer


  3. Posts : 28,845
    Win 8 Release candidate 8400
       #3

    Cas said:
    Hi guys,

    I've had x64 win7 installed for about a month, no troubles until now.

    The last few days, whenever I shut down the PC for the night the "shutting down" screen is displayed for more than 15 minutes, at this point I just turn it off via the front power button on the case as I'm afraid to leave it all night saying that as I'm not that tech savvy.

    Is there any way to figure out what's going on with the shutdown process? The following morning it starts up fine, and I restart with a disk check that comes up fine.

    Go into event viewer (type eventvwr in search) go to windows log>application tab. Look for things like app hang, app crash, etc. Note any critical errors(they have red in the left column) and copy the event ID and source code. Let us know what they are

    Ken
      My Computer


  4. Cas
    Posts : 4
    win xp
    Thread Starter
       #4

    Okay, there are three entries at the time of the shutdown, as follows:

    9009 The Desktop Window Manager has exited with code (0x40010004)

    6000 The winlogon notification subscriber <SessionEnv> was unavailable to handle a notification event.

    1532 The User Profile Service has stopped.
      My Computer


  5. Cas
    Posts : 4
    win xp
    Thread Starter
       #5

    asdf
    Last edited by Cas; 12 Nov 2019 at 20:49.
      My Computer


  6. Posts : 28,845
    Win 8 Release candidate 8400
       #6

    Cas said:
    Same shutdown issues last night. Here are event ID's that occurred when turning the system ON this morning:

    4625 - The EventSystem sub system is suppressing duplicate event log entries for a duration of 86400 seconds. The suppression timeout can be controlled by a REG_DWORD value named SuppressDuplicateDuration under the following registry key: HKLM\Software\Microsoft\EventSystem\EventLog.

    300 - Windows (2688) Windows: The database engine is initiating recovery steps.

    302 - Windows (2688) Windows: The database engine has successfully completed recovery steps.

    903 - Security SPP The Software Protection service has stopped.

    6000 - The winlogon notification subscriber <SessionEnv> was unavailable to handle a notification event.
    here is obviously some database corruption. Do you have a backup from before this problem to restore?

    BTW the duplicate event log and database recovery is what is taking it so long to boot.

    Ken
      My Computer


  7. Cas
    Posts : 4
    win xp
    Thread Starter
       #7

    asdf
    Last edited by Cas; 12 Nov 2019 at 20:49.
      My Computer


  8. Posts : 28,845
    Win 8 Release candidate 8400
       #8

    Cas said:
    Would the database corruption be from the incomplete shutdown last night? Or would that exist before and is causing the incomplete shutdown timeouts?
    Could be either but event viewer should provide an answer. Just see how far back the corruption goes.


    Ken
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 02:05.
Find Us