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

    • AMAZON needs to take total accountability for this.
    • Server Summit had a heap of announcements, ADCS changes are baller.
    • Nice, hope they *finally* fixed the issue with the NTFS driver where the system would completely brick during large file copies using the built in driver. It's been broken for years requiring me to use the older, slower, NTFS-3G FUSE driver.
    • Windows 11 KB5094126 BSODing, freezing, forcing BitLocker lockout, breaks OneDrive, and more by Sayan Sen Microsoft released Windows 11 KB5094126 and KB5093998 last week as the latest Patch Tuesday updates. Following that the company also published the accompanying dynamic updates under KB5094149, KB5095971, and KB5094156. While Microsoft has so far not acknowledged any major problems with the release, some users online are running into problems. These range from OneDrive and Dropbox access issues, BitLocker recovery lockouts, to blue screens and BSODs. The most common one seems to be happening with HP systems wherein affected users say they hit 0xc0430001 BSOD (blue screen of death) error code after the KB5094126 update. We wonder if this could be related to the recent bug we covered on HP devices wherein the ongoing Secure Boot certificate updates are leading to similar issues. While we are not certain, users affected by this issue likely need to ensure that the boot.stl file is included on the installation media (such as a USB installer or ISO), if the above-mentioned dynamic updates are deployed. If this file is missing, computers may fail to boot from the installation media and could display the error 0xc0430001. This STL file is used by Secure Boot to verify that the boot files are trusted, so it must match the same Windows version and system architecture. To ensure the file is included, Microsoft recommends using the Update WinPE script, which automatically updates the image and handles the required files. Alternatively, you can manually copy the boot.stl file from the Windows\Boot\EFI folder on a Windows device and place it in the matching folder on your installation media before deploying the updated image. Aside from blue screening some users also note their systems have been freezing following the update. This could be happening to Lenovo PCs specifically. In the case of the OneDrive and Dropbox access issues, a user figured out that there could be a conflict with UAC. He explained: "Okay, so I did some digging, and in our environment KB5094126 breaks OneDrive and Dropbox in Explorer. I went through all our GPOs and found out that the combination of disabling UAC and having my user being a local admin breaks OneDrive in Explorer. ... If I enable UAC again, then it works, even with KB5094126 still installed." Hopefully, Microsoft will look into these issues. Source: Microsoft forum (link1, link2, link3, link4), Reddit (link1, link2, link3, link4)
    • It is when it's a desktop in my house though for a PC that's lightly used and not really important when it is. If it was a laptop, it would be a different story. The real solution is varied and begins starting at post #22 in that thread.
  • 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
      508
    2. 2
      +Edouard
      197
    3. 3
      PsYcHoKiLLa
      138
    4. 4
      ATLien_0
      90
    5. 5
      Steven P.
      80
  • Tell a friend

    Love Neowin? Tell a friend!