Motherboard: MSI Gaming Plus Z370
Processor: Intel Core i9-9900K @5.0 GHz
Graphics: Asus ROG Strix RTX 2080 Ti
Memory: Corsair Vengeance LPX 4000 MHz 32 GB
Storage: Samsung 970 Pro 500 GB [Windows 10]
Storage: Samsung 850 Evo 500 GB
Storage: Samsung 850 Evo 500 GB
Storage: Western Digital Black 6 TB 256 MB Cache
Storage: Western Digital Black 6 TB 256 MB Cache
Power: EVGA SuperNOVA Modular P2 80+ Platinum
Issue: So basically I have found the issue to be located on the M.2 970 Pro drive. It's not a huge deal, it's more of an observation. When first starting an application or first loading Windows, everything will freeze for less than 1 second or up to a total of 3 seconds before I am able to move the mouse again. Afterwards the issue goes away. If I play a game off the drive, or am actively using the drive, the issue is not present. It seems to be a latency issue, and I am curious if maybe my drive is saturating the interface, running a bit too warm or something else? When running my system on a SATA 3 drive, the issue is no longer present. Drivers are up to date from Samsung and I have tried with or without the samsung NVM driver. Ideas?
Processor: Intel Core i9-9900K @5.0 GHz
Graphics: Asus ROG Strix RTX 2080 Ti
Memory: Corsair Vengeance LPX 4000 MHz 32 GB
Storage: Samsung 970 Pro 500 GB [Windows 10]
Storage: Samsung 850 Evo 500 GB
Storage: Samsung 850 Evo 500 GB
Storage: Western Digital Black 6 TB 256 MB Cache
Storage: Western Digital Black 6 TB 256 MB Cache
Power: EVGA SuperNOVA Modular P2 80+ Platinum
Issue: So basically I have found the issue to be located on the M.2 970 Pro drive. It's not a huge deal, it's more of an observation. When first starting an application or first loading Windows, everything will freeze for less than 1 second or up to a total of 3 seconds before I am able to move the mouse again. Afterwards the issue goes away. If I play a game off the drive, or am actively using the drive, the issue is not present. It seems to be a latency issue, and I am curious if maybe my drive is saturating the interface, running a bit too warm or something else? When running my system on a SATA 3 drive, the issue is no longer present. Drivers are up to date from Samsung and I have tried with or without the samsung NVM driver. Ideas?
Last edited: