As you can see on the screenshot. Task Manager is saying that the Active Time of my NVM.e system drive has a lot of peaks that start to happen after a few minutes of using the PC and they won’t go away unless I restart. I have tried so many things that I gave up and formatted the whole drive and reinstalled Windows from scratch. I have also tried the chkdsk command and this problem won’t go away. This started to happen just a few days ago, out of the blue. The whole system freezes at every peak you see on the screenshot and the main tab of Task Manager reports the Disk Usage as being ~1%, so there is no process using the disk. Resource Monitor is also reporting the same thing.

Edit: I have narrowed down the problem to a insanely high Response Time on Resource Monitor (up to 2000ms). It is usually the “System” process that is having this high Response Time. Any way of fixing or at least knowing the root cause of this?

  • Walt J. Rimmer@lemmy.world
    link
    fedilink
    English
    arrow-up
    3
    ·
    11 months ago

    Getting a second OS on that drive is doable, but I mean, I find it a headache sometimes, not sure about other people. But if you’ve got a spare flash drive, you can live boot into some free distro to run some tests.

    But, sorry, no idea what the root cause of it might be. Last time I saw something like this was when I had a Windows 8 laptop that got an update to Windows 10 and I got hit with a rare bug that apparently only occurred in some Windows 8 laptops that updated to Windows 10 where my boot drive (an HDD) would be constantly at 100% read/write without actually reading or writing anything. But it was sure trying to. There were about seven potential solutions for that and none of them worked for me. I ended up just mostly ditching the laptop as it had other issues as well, like a failing WiFi adapter somehow.

    • JoshNautes@lemmy.mlOP
      link
      fedilink
      English
      arrow-up
      2
      ·
      11 months ago

      That 100% disk usage problem was definitely not rare. I had this issue with almost everything Windows 10 computer using an HDD as the system drive.