W10 Slow after a couple days - Need HELP!!!!

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • tcipps
    PCHF Member
    • Jun 2021
    • 4

    #1

    W10 Slow after a couple days - Need HELP!!!!

    Iโ€™l start off by saying iโ€™ve tried nearly everything i could think of. I come here in desperation. Built a new PC - fresh install of W10. From the start been having this issue. When i boot W10 everything is zippy fast and after a couple days gets really sluggish like opening โ€œthis pcโ€ takes 3-4 seconds vs instantly.
    • Iโ€™ve run memtest86 on each stick individually to see if problem wit RAM - came back 0 errors
    • Manually set RAM frequency to 3200mhz in BIOS on auto set to 2200 i think
      -Manually set NVMe to Gen 3 - Samsung Magician Results - Sequencial READ/WRITE (MB/s) - 3566/3028 - Random IOPS READ/WRITE - 280517/257080
    • Checking Temp using HWMonitor - nothing above 40C - CPU will reach around the 60C if iโ€™m doing heavy use Stock Cooler
      -Basic stuff Task Manager Idle 2%CPU - Memory at 28% usage most taking up by Windows explorer at 260MB - GPU 1% - Disk 0% - Network 0%
      -Tried turning page file on/off
      -Windows is all up to date
      -No A/V programs except W10 protection defaults
      -Check Power Plan Settings
      -Turned off nearly every Windows Service that didnโ€™t look essential.
      -All background programs closed.
      -Virus Scan with Malware bytes, bitdefender and spybot.

    My Specs:
    PSU - Thermatake 850w 80+Gold
    Mobo - ASUS AM4 TUF Gaming X570-Plus
    CPU - AMD Ryzen 7 3800x 3.9GHz
    Ram - G.Skill Ripjaws V Series 16GB x 2 - (Connected to Proper Channels on Board)
    SSD - Samsung 970 Evo Plus M.2 500Gb
    Graphic - Gigabyte GTX1070
    Edit - Samsung 840 evo SSD - Samsung Magician Results - Sequencial READ/WRITE (MB/s) - 7489/5653 - Random IOPS READ/WRITE - 158447/79833
    (Faster read /write than m.2 but slower IOPS than m.2 if that means anything)

    Any Suggestions or advice would be extremely helpful. Im not sure if itโ€™s Hardware or Software issue. I really donโ€™t know what else i can try.

    Thanks
  • Bruce
    PCHF Moderator
    • Oct 2017
    • 10697

    #2
    gโ€™day tcipps and welcome to the forum,

    first up, you want to test it without any added software.
    Iโ€™d be reinstalling a fresh Win10 and running it just with nothing but the OS for a few days and seeing if the problem occurs.
    thatโ€™ll tell you whether itโ€™s your hardware setup or the extra software you are loading.

    if no issues, then add one software at a time, running it for a few days, and seeing if it repeats.

    Comment

    • tcipps
      PCHF Member
      • Jun 2021
      • 4

      #3
      thanks for the reply i got a spare drive i might have to do that. With W11 coming out maybe il just do that instead.

      Comment

      • Bruce
        PCHF Moderator
        • Oct 2017
        • 10697

        #4
        if you can limp along until then, but Win11 is months away I reckon.
        MS is great on big announcements and even better at blowing deadlines!!!
        I havenโ€™t even seen a promised timeline for Win11 yet.

        Comment

        • tcipps
          PCHF Member
          • Jun 2021
          • 4

          #5
          Reformatted with fresh copy of windows right from microsoft website on the Samsung 840evo SSD instead of the M.2. Pretty bare bones in terms of software and same thing blazing fast for a 2-3 days then just sluggish until next restart.

          Comment

          • Bruce
            PCHF Moderator
            • Oct 2017
            • 10697

            #6
            when you say sluggish, is it the PC slow, like opening programs, or the internet, as in changing pages, downloading files?

            and when you saying rebooting fixes it, I take it by that you leave your PC on all the time.
            the longer a PC is left on the more they glitch, thatโ€™s why even big companies schedule downtime for maintenance, all they usually do is reboot everything.
            all RAM suffers what they call memory leakage, itโ€™s when the power doesnโ€™t refresh the NAND cells in time to keeo their contents alive, and the memory drops a 0 or 1 here and there. over time these accumulate and start showing themselves in different ways; BSOD, errors, etc.

            sounds like your rig may be prone more than usual, maybe overclocking, or incompatible RAM modules.
            quick test would be to power off each night after use and see how it performs for a few days.

            Comment

            • tcipps
              PCHF Member
              • Jun 2021
              • 4

              #7
              Thanks for all your input and advice Bruce really appreciate it.

              Ya I run it 24/7 mainly cause I got about 4-5 users using it as plex server. My previous comp that died i ran for months without issues.

              In terms of slow little things like opening start menu will take 2-3 seconds.

              Is it worth trying different sick of rams or any manual settings in BIOS?

              In my original post bios had it running at 2200mhz I had to manually kick it up.

              Comment

              • Bruce
                PCHF Moderator
                • Oct 2017
                • 10697

                #8
                go into File Explorer > View > Options and turn off any fluffy stuff like Show file icons, and Show file size.
                also in Control Panel > System >Advanced > Performance Settings > change to Adjust for best performance.

                it may help, as what you describe seems Explorer related.

                as to memory, yeah, set the BIOS to auto so itโ€™s set to whatever the native clock speed of the RAM is.

                other potential helpers may be to put the pagefile on a second drive if you have one. get it off the boot SSD drive.
                maybe turn off services using O&O ShutUp10 and Easy Services Optimizer (use the Safe option along the bottom).
                and go into msconfig and Task Manager to see what is running that can be disabled.

                Comment

                Working...