- Joined
- Jun 4, 2013
- Messages
- 165 (0.04/day)
- Location
- Switzerland
System Name | Upgraded Not-So-Silent-Anymore Black Box That Computes |
---|---|
Processor | Intel i7-6700k @ 4.4Ghz / 1.24V |
Motherboard | Asus Sabertooth Z170S |
Cooling | BeQuiet Dark Rock 3 |
Memory | 2x 8GB 3000Mhz Corsair Vengeance LP (CL15) |
Video Card(s) | Asus Strix GTX1080 |
Storage | 256GB Samsung 850 Pro / 500GB Samsung 840 Evo / 3TB WD Green |
Display(s) | 24" Asus PB248Q (1.920x1.200) |
Case | Fractal Define R3 / 3x 120mm Corsair AF case fans |
Audio Device(s) | Asus Xonar DX |
Power Supply | Corsair RM750i |
Mouse | Logitech G700 |
Keyboard | Logitech G710+ |
Software | Windows 10 Professional / Arch Linux Dualboot |
Recently, I've bought a Clevo P641 barebone (14”, HM175 Chipset, i7-7700HQ, GTX1050Ti + 2x 8GB DDR4-2400, m.2 512GB 960 Pro, SATA 1TB 950 Evo, AC-7265 WIFI). Whilst the system is very fast I have the strange problem that, whenever I right click empty space in the explorer, the mouse will freeze for 1 second. If I right click on a file or folder this does not happen, and it is exclusive to Windows since Linux does not show the same behavior.
So far, I’ve tried to clean up the context menu, installed the Samsung SSD driver, tried my memory’s various XMP profiles, reinstalled USB drivers, messed with power settings and other things, but I am at a loss as to what could be the cause here. My company also had a second device with similar hardware that showed the same symptoms.
Personally, I start to believe that there is either a driver issue here, or a general incompatibility between this barebone and the RAM. But maybe you guys have an idea as to what else I could try? It’s not a serious problem since the system overall runs very fast, but I’d love to solve it.
So far, I’ve tried to clean up the context menu, installed the Samsung SSD driver, tried my memory’s various XMP profiles, reinstalled USB drivers, messed with power settings and other things, but I am at a loss as to what could be the cause here. My company also had a second device with similar hardware that showed the same symptoms.
Personally, I start to believe that there is either a driver issue here, or a general incompatibility between this barebone and the RAM. But maybe you guys have an idea as to what else I could try? It’s not a serious problem since the system overall runs very fast, but I’d love to solve it.
Last edited: