Slow SSD Boot with long OtherKernelInitDuration delay

Page 7 of 11 FirstFirst ... 56789 ... LastLast

  1. Posts : 2,528
    Windows 10 Pro x64
       #61

    The bulk of the boot time here appears to be due to autochk running - your session init time is 20.5 seconds, and 18.7 seconds of that is autochk running. I can't explain it - it's happening below what Windows has control over, unfortunately, so it is indeed some sort of issue at the hardware level. The interesting bits you've found with using the WD drive might indicate that as the issue, although it would be interesting to try a different drive (if you can acquire one, even temporarily) to see if it happens with *any* other drive, or just that particular one:

      My Computer


  2. Posts : 66
    Windows 7 Home 64bit
    Thread Starter
       #62

    I think I have a problem with autochk.exe.
    Attached Thumbnails Attached Thumbnails Slow SSD Boot with long OtherKernelInitDuration delay-autochk.jpg   Slow SSD Boot with long OtherKernelInitDuration delay-autochk2.png  
      My Computer


  3. Posts : 2,528
    Windows 10 Pro x64
       #63

    I dunno - remove the WD and see if it goes away. Unfortunately, what's happening here is below Windows, so software tracing tools running inside Windows aren't likely to be helpful in getting too much deeper than this.
      My Computer


  4. Posts : 66
    Windows 7 Home 64bit
    Thread Starter
       #64

    From looking at the second jpeg from my email above, it appears I also have a big delay with ntdll.dll. Are the two related?
      My Computer


  5. Posts : 4,161
    Windows 7 Pro-x64
       #65

    Autochk runs in the following situations:
    • If you try to run Chkdsk on the boot volume
    • If Chkdsk cannot gain exclusive use of the volume
    • If the volume is flagged as dirty
      My Computer

  6.    #66

    I agree with Carl that it's surely hardware, but complete the Clean Boot by entering msconfig>Services, select Hide All MS services, then uncheck all but AV.

    Check back frequently there and in msconfig>Startup after reboots to make sure nothing writes back in - if so turn it off in Program Prefs or uninstall. You now have a Clean Boot.

    Also here are steps for a baseline perfect reinstall based on hundreds we've helped with here: Reinstalling Windows 7

    It's important to NOT change out drivers from those issued by the installer and quickly updated via optional Windows Updates, unless performance points to them. We see issues regularly where OEM drivers are swapped in willy-nilly causing performance problems which are hard to trace. Win7 is the authority on its drivers - this is NOT your father's XP.
      My Computer


  7. Posts : 66
    Windows 7 Home 64bit
    Thread Starter
       #67

    I started a check disk session on the WD drive before I saw these responses, and it's going to take a little time to complete. In the meantime, I ran autoruns and discovered that autochk.exe is scheduled to run at boot even though I never scheduled it to do so in Task Scheduler. How can that be? Surely I can disable this without reinstalling Windows, can't I?
    Attached Thumbnails Attached Thumbnails Slow SSD Boot with long OtherKernelInitDuration delay-autocheck.jpg  
      My Computer


  8. Posts : 4,161
    Windows 7 Pro-x64
       #68

    See post #65. It could be the disk is flagged as "Dirty".
      My Computer


  9. Posts : 66
    Windows 7 Home 64bit
    Thread Starter
       #69

    carwiz said:
    See post #65. It could be the disk is flagged as "Dirty".
    I'm running a surface scan on the 2TB WD, and it's taking forever to complete. I can't run a fsutil dirty query on the drive until it finishes. We'll see what it comes up with.

    Edit: Neither drive has been flagged as dirty.
    Last edited by Raillex; 25 Oct 2011 at 00:28.
      My Computer


  10. Posts : 66
    Windows 7 Home 64bit
    Thread Starter
       #70

    Alright, here is what I know.

    I do not have dirty bits on either drive. I checked both drives for errors and found none.

    I prevented chkdsk from running on the WD and then both drives by running chkntfs /x c: e: at the command prompt. Both times the boot times were idenitical to the delay with chkdsk enabled (~38 seconds). I ran a boot trace after disabling chkdsk on the WD, and although chkdsk didn't start running until the 7 second mark instead of the 1.5 second mark this time, all the other services started running at approximately the same time they did on the run I did earlier this evening. I didn't run Boot Trace with chkdsk disabled on both drives because it became clear to me that chkdsk was NOT the cause of the boot delay.

    I then turned off all services and startup programs except Microsoft entries and Security Essentials AV. Nothing changed.

    I will pull a SATA storage drive out of my other rig when I have time and see what happens. If the boot lag continues, the answer has to be related to the mobo, bios, or both.
      My Computer


 
Page 7 of 11 FirstFirst ... 56789 ... LastLast

  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 07:08.
Find Us