Skip to content
View in the app

A better way to browse. Learn more.

MSFN

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

2ukiwis

Member
  • Joined

  • Last visited

  • Country

    United States
  1. yes, first always look for 3rd party tools/drivers. The mrxdav.sys belongs to the WebDAV Client, so stop this service for testing purpose. Hi MagicAndre Thanks for your help. I isolated my issue to the Intel Active Management driver IAMTVE.sys. It was not installed in Add Remove Programs so I deleted the .sys file then noticed a bang in device manager next to "Intel Active Management Technology - KVS" so I disabled that entirely. Voila, shutdown time is now only 8 seconds which is a nice reduction from 240 seconds. Woohoo, I'm a very happy camper. Cheers
  2. Thanks for your help. I'll try those things and let you know what happens. I noticed there was a few other drivers with long delays eg mrxdav.sys, mup.sys and fltmgr.sys. I guess the logic for not looking further into these is that they are part of the OS so the "low hanging fruit" 3rd party drivers are the ones to jump on? Or is it that you can see somewhere that these Microsoft drivers are "waiting" for the others before they can complete?
  3. I've uploaded another ZIP file to skydrive if you'd care to take a look? Thanks
  4. Ok, I'll have another go. FWIW there was no iPod attached when the traces were performed.
  5. Hi Andre I've been plagued with slow shutdown issues for months and have recently discovered xperf but I'm struggling to make head or tails of it... I've run the following command to generate 3 traces: xbootmgr -trace shutdown -traceFlags Latency+DISPATCHER+BASE+CSWITCH -StackWalk CSwitch+ReadyThread+ThreadCreate+Profile -noPrepReboot -numRuns 3 -resultpath %systemdrive%\traces -postBootDelay 60 When this had completed I generated the XML files for each using the following: xperf -i "shutdown_Latency+DISPATCHER+BASE+CSWITCH_1.etl" -o shutdown1.xml -a shutdown I can see from each of these files that there are 2 areas that are causing an issue: NTShutdownSystem and IoShutDownSystem @ 183 seconds and 80 seconds respectively -<intervals> <interval duration="179" endTime="4792" startTime="4613" name="WaitForWinstationShutdown"/> <interval duration="367" endTime="5333" startTime="4966" name="PreShutdownNotification"/> <interval duration="183682" endTime="193548" startTime="9866" name="NtShutdownSystem"/> <interval duration="-1" endTime="-1" startTime="0" name="ZeroHiberFile"/> <interval duration="148" endTime="112824" startTime="112676" name="FlushVolumes"/> <interval duration="0" endTime="112825" startTime="112825" name="ZeroPageFile"/> <interval duration="80007" endTime="192864" startTime="112857" name="IoShutdownSystem"/> <interval duration="-1" endTime="-1" startTime="0" name="WaitForProcesses"/> <interval duration="49" endTime="192913" startTime="192864" name="CmShutdownSystem"/> </intervals I'm not sure where to go from here and I'm hoping you can help me. I've uploaded a zipped .etl file from one of the traces to here: http://goo.gl/DLUVS

Account

Navigation

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.