Quote from: BitcoinBlaster51 on March 05, 2021, 11:00:42 AM

Just want to mention as a side note before getting into details. Virtual Memory settings on Windows may help. For ETH I've noticed VM size needs adjusted according to this formula:
Initial VM size = DAG size x Quantity of GPUs
Maximum VM size = Projected DAG size x Quantity of GPUs

In regards to the OP, I have been experiencing a similar issue described here: https://www.reddit.com/r/gpumining/comments/80r6j6/does_anyone_elses_windows_10_start_lagging/ Saw how the Reddit user Reed1981 mentioned using the "ethi" command for Claymore's dual Ethereum miner. This command adjusts the mining intensity, it's scale is from 0 - 8. Default is 8.

Although, I have been mining ETH with Ethminer through miningpoolhub.com. So I searched for a parameter list of Ethminer here: https://gist.github.com/jkcdarunday/e89dde8fa71e510596f45480c5529376
Noticed talk regarding OpenCL (Open Computing Language) configurations here: https://forum.ethereum.org/discussion/comment/31821/#Comment_31821

So far, I've adjusted:
--cl-local-work 64 (down from 128)
&
--cl-global-work 524288 (8192 * 64)

The default is 8192 that I found within the Ethminer parameter list.
--cl-local-work best operates with powers of 2 so I just scaled down one increment.

So far I will adjust these values if my rig continues its current issue. You may be able to attempt changing such values with T-Rex although I am not familiar with T-Rex.

Mining Rig:
PSU: EVGA 1600W G2 SUPERNOVA 80+G
Mobo: ASUS B250
Processor: INTEL I5-7500 @ 3.40Ghz
Storage: Kingston SUV400S37120G SSD 120GB
GPUs: 6 × Gigabyte GTX 1070 8GB
Core Clocks +125
Mem Clocks +270
PCI-e power adapters: 6 pin to dual 8 pin (6+2) VGA Y-splitter extension cables
Other: 6 risers powered by the extension cable above
RAM: 1 × CRUCIAL 8GB DDR4 2400Mhz SPLT CL16
OS: Windows 10 Pro v2004
Mining Software: Ethminer-0.18.0-cuda10.0-windows-amd64

An increase in virtual memory seems to have helped. @ dan_729 maybe try increasing VM and see what happens after a few days. That's what I'm currently doing. If the machine behaves normally for more than 2 or 3 days, I'd say it's safe to assume VM.