SSD Bootup Slowed Way Down Right After "Fixing" Home Network

Page 6 of 7 FirstFirst ... 4567 LastLast

  1. Posts : 7
    8.1u1
       #51

    There is some low hanging fruit, some not so much. I'm dealing with kids, more soon
      My Computer


  2. Posts : 97
    Windows 7 Professional 64-bit
    Thread Starter
       #52

    I've done a round or two of traces and have delayed Crashplan at startup. 1st time through it saved 15 seconds, but subsequent bootups the system reverted to 1 minute 30 seconds.

    Emsisoft developer, Fabian, suggested: "32 to 50 seconds does sound excessive indeed. You can try to disable "Protect the computer even if no user is logged on" under "Protection"/"File Guard". That may help your boot times a bit. If it doesn't please let me know so we can look into what exactly is taking so much time during boot."

    I'm going to run a fresh trace, then disable that and run a 2nd trace, then at Jeff's (windowsperf) request, I'm going to disable "Emsisoft Protection Service" and retrace. Also, disable the Asus Com service which is known to have a memory leak and delay startups.

    More fun than you can shake a mouse at!
      My Computer


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

    New trace???
      My Computer


  4. Posts : 97
    Windows 7 Professional 64-bit
    Thread Starter
       #54

    Thanks for checking in! Jeff has been busy with family so we haven't had the results of the last trace yet.

    BUT, something changed just yesterday. I got a weird alert that my F: drive was bad. The only thing on the F: drive is my OS' pagefile.sys file. Moved it there 2 months ago because I was down to 14 GB available on the SSD C: drive.

    Checked the drive. It was okay. Noticed that I was down from 35 GB to 16 GB on my C: drive. ???. Pagefile.sys apparently ran back to the C: drive due to whatever that F: drive hiccup was.

    So I used my AX64 Time Machine program and snapped back 3 days to when things were working fine (except the long boot time, of course) and when it rebooted, it was quicker than usual. Huh???

    I noticed that the F: drive had the pagefile.sys again. The C: drive had the 35.7 GB it should have available. I have noooooooo idea how that pagefile.sys got back on the F: drive if I only restored the C: drive. Magic?

    New boot up time comparison (black is the most recent slow, Red is the new faster):
    00:00 00:00 Press start button
    00:03 00:03 Asus logo on black screen
    00:06 00:06 Windows boot manager screen with options for Windows; Macrium Recovery; and AX64 Recovery
    00:09 00:09 Windows logo on black background
    00:36 00:36 Light blue Windows Welcome screen
    01:15 Purple desktop background, with no icons
    01:35 00:52 Purple desktop background, Icons show up, popup for which drives were recognized, and I'm ready to go

    M
    uch better.

    Would a new trace reveal what happened?
      My Computer


  5. Posts : 2,528
    Windows 10 Pro x64
       #55

    A new trace would tell what's different - compared to the previous one it might tell what happened, yes.
      My Computer


  6. Posts : 97
    Windows 7 Professional 64-bit
    Thread Starter
       #56

    Tortured. On December 31st, Emsisoft delivered an update which included a fix for the network issue I had been having. I didn't reboot until days later (this morning, January 2nd) to finalize that update. But upon rebooting, my system has reverted to the very long boot up issue. I am NOT convinced it was the update.

    I ran AX64 to restore back to December 29th when the system was working great with faster boot up. But the long boot is still there. I then restored to the same time frame with Macrium Reflect, including the MBR. No difference.

    Remember, that my system "fixed" itself when I got the popup alert that my F: drive was bad --- causing the pagefile.sys to revert to the C: drive, upon which I then restored back --- and the pagefile.sys went back to the F: drive --- and the boot up was faster.

    I had taken a Macrium image of the F: drive right after that, thinking I could use it (not really understanding what the pagesys.file really is. Anyway, on a lark, or naivety, I used Macrium to restore the F: drive to that magic moment. No change. Arrrrgghhh.

    Might some funkiness with the pagefile.sys show up in the trace?

    I lost my chance at running a trace when it was booting fast (holiday obligations got in the way.) So upset about that. Might have given a clue as to what the conflict is.

    So now what? Jeff, can you analyze that last trace we did?
      My Computer


  7. Posts : 2,528
    Windows 10 Pro x64
       #57

    Can you get a new trace please? A lot has been done, and I'd personally like to see something current so as not to miss anything.
      My Computer


  8. Posts : 97
    Windows 7 Professional 64-bit
    Thread Starter
       #58

    What we learned from my brief period of faster boot time, is where the delay is taking place

    00:36 00:36 Light blue Windows Welcome screen
    01:15 ------Purple desktop background, with no icons
    01:35 00:52 Purple desktop background, Icons show up, popup for which drives were recognized

    Could all of this be the result of some funkiness with the pagefile.sys file?
      My Computer


  9. Posts : 97
    Windows 7 Professional 64-bit
    Thread Starter
       #59

    I will do it this afternoon. Thank you!
      My Computer


  10. Posts : 97
    Windows 7 Professional 64-bit
    Thread Starter
       #60

    I have provided Jeff and Carl with the traces.
      My Computer


 
Page 6 of 7 FirstFirst ... 4567 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 04:41.
Find Us