Why does an SSD disk periodically load into a hundred for no reason?

Question

Windows

The point, in fact, is the question.
There are no programs on the computer, nothing at all. Only pure Windows.
And with a completely random frequency, the disk load soars to 100%, the computer just dies - the cursor sometimes lags, the keys work with a delay. I'm not talking about apps at all. However, there are no "usual" explanations for this.
Task manager, perfmon, procmon - they all show that there is no load on the disk. Here in general. There are no processes that now write / read something in volumes sufficient to explain such wild brakes. Sometimes read and sometimes write speeds (according to the dispatcher) really jump up to 100MB / s, but none of the above tools can show what kind of ingenious process is doing this.
In general given:
10 freshly arrived computers
i3-9100
8GB DDR4
H310M-R r2.0
SSD ADATA SU650 240 (we have been buying them for a long time, never had any problems)
We fill the system with Acronis from a stable image, which has been checked a bunch of times and it’s definitely not the case, read below
Updates Windows are disabled (tried to update in case of a series of "well, what if")
What they tried to come up with:
- Different versions of firewood for the sata controller
- Other images on win10 that are
- Clean installation of win10 different builds (1809, 1903, 1909, LTSC ). Moreover, they tried it with drivers and without them at all, the result is the same
- Searching for sata ports on the mother and replacing sata cables
- Mother firmware to the latest BIOS version (well, what if)
One nuance. Inserting a disk into a known working mother (or vice versa) is currently not possible. There are only these 10 computers and the devil knows where and what the marriage is. Yes, we do not exclude the possibility of marriage, but I would like to understand what and where it can be at all.
Does anyone have any experience with these carousels?
I would be grateful for any advice. thanks in advance

Answer 1

I would boot into any linux, or one could even install for tests. And then look at the behavior. If there is no such thing, then the matter is in the software - Windows itself, drivers. If the workload is similar - look first at the output of dmesg | tail.
Or filter by "disk", "interrupt". Further, if something interesting comes out, someone will tell you, I can’t do it right away. After - iotop, htop.
But in general, if both OS have the same problems, then something with the hardware, 100%. Well, remove the disk and bring it home in order to try it on a known good other hardware - I think there is no problem.

Answer 2

Turn on the swap file and everything will be ok. By default, it is disabled on Windows 10 when installing the system on an SSD, but half of Maykovsky's software even requires it. Not to mention third-party software. Therefore, enable the paging file, restart the computer and look at the result. If nothing changes, discard what happens in the event log during the "slotting in a hundred".

Answer 3

If no application loads the disk, in the read / write column the values ​​\u200b\u200bare near zero, and the load is on the shelf, then the problem is in IO. Or a broken SATA cable, or broken disk memory, or disk firmware glitches.

Answer 4

The problem was either in the firmware of the disk, I encountered this on the GoodRam ssd, the system would freeze tightly for a couple of tens of seconds and could get enough sleep in bsod, it was cured by flashing the ssd controller, or in a conflict between the ssd and the hard drive, the same GoodRam ssd could not get up next to the hdd, because. e. We installed a system with auto partitioning of ssd and disconnected hdd, it was successfully installed, reboot - setup - shutdown - connect hdd - turn on - and the system does not boot - livecd - go into disk layouts, and ssd without partitioning and the amount of memory is equal to the amount of cache - magic !!! So they did not win the last situation. In one disk it works without problems, as soon as you pick up another disk (flash drive) and reboot everything flies to nowhere.