Recommended Posts

I'm running 7 on my Dell Mini which has been upgraded to 2GB RAM and shut down is taking anywhere between 30-40 seconds. Checking the Event Viewer shows a lot of Event ID 200 entries, but very little information in them to allow me pinpoint exactly what is causing the issue. Any ideas on what I can do to improve it?

Edit: Here's one of the entries from Event Viewer.

Log Name:	  Microsoft-Windows-Diagnostics-Performance/Operational
Source:		Microsoft-Windows-Diagnostics-Performance
Date:		  24/09/2009 17:47:40
Event ID:	  200
Task Category: Shutdown Performance Monitoring
Level:		 Warning
Keywords:	  Event Log
User:		  LOCAL SERVICE
Computer:	  
Description:
Windows has shutdown: 
	 Shutdown Duration	:	30163ms
	 IsDegradation		:	false
	 Incident Time (UTC)	:	‎2009‎-‎09‎-‎24T16:45:00.753114500Z
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
	<Provider Name="Microsoft-Windows-Diagnostics-Performance" Guid="{CFC18EC0-96B1-4EBA-961B-622CAEE05B0A}" />
	<EventID>200</EventID>
	<Version>1</Version>
	<Level>3</Level>
	<Task>4007</Task>
	<Opcode>40</Opcode>
	<Keywords>0x8000000000010000</Keywords>
	<TimeCreated SystemTime="2009-09-24T16:47:40.799802500Z" />
	<EventRecordID>267</EventRecordID>
	<Correlation ActivityID="{00000000-9B28-0000-5EE9-7076363DCA01}" />
	<Execution ProcessID="1372" ThreadID="1384" />
	<Channel>Microsoft-Windows-Diagnostics-Performance/Operational</Channel>
	<Computer>Si-Mob</Computer>
	<Security UserID="S-1-5-19" />
  </System>
  <EventData>
	<Data Name="ShutdownTsVersion">1</Data>
	<Data Name="ShutdownStartTime">2009-09-24T16:45:00.753114500Z</Data>
	<Data Name="ShutdownEndTime">2009-09-24T16:45:30.916591800Z</Data>
	<Data Name="ShutdownTime">30163</Data>
	<Data Name="ShutdownUserSessionTime">3347</Data>
	<Data Name="ShutdownUserPolicyTime">1</Data>
	<Data Name="ShutdownUserProfilesTime">6</Data>
	<Data Name="ShutdownSystemSessionsTime">13625</Data>
	<Data Name="ShutdownPreShutdownNotificationsTime">7932</Data>
	<Data Name="ShutdownServicesTime">4996</Data>
	<Data Name="ShutdownKernelTime">13190</Data>
	<Data Name="ShutdownRootCauseStepImprovementBits">0</Data>
	<Data Name="ShutdownRootCauseGradualImprovementBits">0</Data>
	<Data Name="ShutdownRootCauseStepDegradationBits">0</Data>
	<Data Name="ShutdownRootCauseGradualDegradationBits">0</Data>
	<Data Name="ShutdownIsDegradation">false</Data>
	<Data Name="ShutdownTimeChange">0</Data>
  </EventData>
</Event>
 
Link to comment
https://www.neowin.net/forum/topic/826858-slow-shutdown/
Share on other sites

those both values are too high:

<Data Name="ShutdownPreShutdownNotificationsTime">7932</Data>

it takes 8 seconds to notify the running programs, that Windows wants to shutdown

<Data Name="ShutdownKernelTime">13190</Data>

this is the time which Windows needed to shutdown the rest (devices, drivers and windows itself)

Link to comment
https://www.neowin.net/forum/topic/826858-slow-shutdown/#findComment-591620682
Share on other sites

follow this guide:

http://www.msfn.org/board/index.php?showtopic=117154

to trace the shutdown process. Open the resulting etl file and look if you can see which applications need a long time to close correctly and if you can see why the kernel shutdown takes some time.

But you have to use the WPT 4.6 from the Windows 7 SDK. The version 4.1.1 from the linked page doesn't work on Windows 7.

Link to comment
https://www.neowin.net/forum/topic/826858-slow-shutdown/#findComment-591622696
Share on other sites

  • 1 month later...

i hadn't gotten a slow shutdown in a while but few mins ago i just did again... i actually have a bunch of warnings and errors in my event viewer as well... i dont know why. everytime i click "event log online help" i get "no results" on the microsoft site.

this is my results from the slow shutdown if anyone can help me... D;

Windows has started up: 
	 Boot Duration		:	63359ms
	 IsDegradation		:	false
	 Incident Time (UTC)	:	‎2009‎-‎11‎-‎07T10:18:41.718750000Z

+ System 

  - Provider 

   [ Name]  Microsoft-Windows-Diagnostics-Performance 
   [ Guid]  {CFC18EC0-96B1-4EBA-961B-622CAEE05B0A} 

   EventID 100 

   Version 2 

   Level 2 

   Task 4002 

   Opcode 34 

   Keywords 0x8000000000010000 

  - TimeCreated 

   [ SystemTime]  2009-11-07T10:20:47.208984300Z 

   EventRecordID 129 

  - Correlation 

   [ ActivityID]  {00000100-0000-0000-B282-FAAD935FCA01} 

  - Execution 

   [ ProcessID]  1244 
   [ ThreadID]  3844 

   Channel Microsoft-Windows-Diagnostics-Performance/Operational 

   Computer Alex-PC 

  - Security 

   [ UserID]  S-1-5-19 


- EventData 

  BootTsVersion 2 
  BootStartTime 2009-11-07T10:18:41.718750000Z 
  BootEndTime 2009-11-07T10:20:45.818359300Z 
  SystemBootInstance 36 
  UserBootInstance 35 
  BootTime 63359 
  MainPathBootTime 27359 
  BootKernelInitTime 27 
  BootDriverInitTime 1550 
  BootDevicesInitTime 4089 
  BootPrefetchInitTime 57013 
  BootPrefetchBytes 368201728 
  BootAutoChkTime 0 
  BootSmssInitTime 5858 
  BootCriticalServicesInitTime 1064 
  BootUserProfileProcessingTime 1654 
  BootMachineProfileProcessingTime 534 
  BootExplorerInitTime 9575 
  BootNumStartupApps 7 
  BootPostBootTime 36000 
  BootIsRebootAfterInstall false 
  BootRootCauseStepImprovementBits 0 
  BootRootCauseGradualImprovementBits 0 
  BootRootCauseStepDegradationBits 0 
  BootRootCauseGradualDegradationBits 0 
  BootIsDegradation false 
  BootIsStepDegradation false 
  BootIsGradualDegradation false 
  BootImprovementDelta 0 
  BootDegradationDelta 0 
  BootIsRootCauseIdentified false 
  OSLoaderDuration 2085 
  BootPNPInitStartTimeMS 27 
  BootPNPInitDuration 5319 
  OtherKernelInitDuration 3335 
  SystemPNPInitStartTimeMS 8645 
  SystemPNPInitDuration 320 
  SessionInitStartTimeMS 8975 
  Session0InitDuration 1330 
  Session1InitDuration 310 
  SessionInitOtherDuration 4216 
  WinLogonStartTimeMS 14833 
  OtherLogonInitActivityDuration 761 
  UserLogonWaitDuration 572

Link to comment
https://www.neowin.net/forum/topic/826858-slow-shutdown/#findComment-591815564
Share on other sites

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Anyway to download these versions without being on the Experimental builds?
    • Nothing is stopping you from continuing with your testing cadence. If updates are released every 2 weeks instead of 4, and you test once every 4 weeks, the exact same amount of patches will still be available for you in those 4 weeks. For example: Before 4th week - patch 1, 2, 3, 4 After 2nd week - patch 1 and 2 4th week - patch 3 and 4 Still the same amount after 4.
    • Everyone else has said it. I'm gonna say it - you don't know what you're talking about. I do. I have two laptops. One work, one personal. I have access to two more laptops - both personal. At home I manually update my personal laptop when I see on Neowin that there is an update - I carry on and only apply the updates when I am ready. My work one only updates when my workplace decides to send it - I carry on and only apply the updates (when they actually arrive, which is usually days after the release) when I switch off the laptop at the end of the day as usual. The two other personal laptops only get updated when I get to it which is rarely - the people who own them carry on using them until I get to it and update them. All of the browsers on all laptops are configured to restore the tabs when launched. Google and Microsoft have changed from 6 weeks to 4, and it looks like it's going to move to 2. None of these changes affect how any of these browsers on the laptops are used. Not one jot. My advice to you is stop panicking whenever you see an update. Just carry on with what you're doing. This even benefits you in a way - from your comment you sound like you don't like the changes or the frivolous new features - great - then carry on as before!
    • AMAZON needs to take total accountability for this.
    • Server Summit had a heap of announcements, ADCS changes are baller.
  • Recent Achievements

    • Week One Done
      Jeroen Wilms earned a badge
      Week One Done
    • Week One Done
      rolfus earned a badge
      Week One Done
    • One Month Later
      Leroy Jethro Gibbs earned a badge
      One Month Later
    • Conversation Starter
      flexorcist earned a badge
      Conversation Starter
    • One Month Later
      AndreaB earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      509
    2. 2
      +Edouard
      198
    3. 3
      PsYcHoKiLLa
      138
    4. 4
      ATLien_0
      90
    5. 5
      Steven P.
      81
  • Tell a friend

    Love Neowin? Tell a friend!