- Joined
- Jul 30, 2019
- Messages
- 2,589 (1.45/day)
System Name | Not a thread ripper but pretty good. |
---|---|
Processor | Ryzen 9 5950x |
Motherboard | ASRock X570 Taichi (revision 1.06, BIOS/UEFI version P5.50) |
Cooling | EK-Quantum Velocity, EK-Quantum Reflection PC-O11, EK-CoolStream PE 360, XSPC TX360 |
Memory | Micron DDR4-3200 ECC Unbuffered Memory (4 sticks, 128GB, 18ASF4G72AZ-3G2F1) |
Video Card(s) | XFX Radeon RX 5700 & EK-Quantum Vector Radeon RX 5700 +XT & Backplate |
Storage | Samsung 2TB 980 PRO 2TB Gen4x4 NVMe, 2 x Samsung 2TB 970 EVO Plus Gen3x4 NVMe, AMD Radeon RAMDisk |
Display(s) | 2 x 4K LG 27UL600-W (and HUANUO Dual Monitor Mount) |
Case | Lian Li PC-O11 Dynamic Black (original model) |
Power Supply | Corsair RM750x |
Mouse | Logitech M575 |
Keyboard | Corsair Strafe RGB MK.2 |
Software | Windows 10 Professional (64bit) |
Benchmark Scores | Typical for non-overclocked CPU. |
Watch out for a known bug there - HWinfo reading the settings freezes the corsair service, and it locks into last known settings until the service is reset. Shutdowns don't fix it.
Easy to spot, because icue wont show voltage readings any more.
The easy fix is to disable the corsair/asetek setting in HWinfo, but that stops you reading those readings
From what I recall iCue and HWinfo (or any other vendor attempting to get the data) end up fighting each other over the telemetry data and the Corsair service locks up because of it. If you closed HWinfo you could restart the corsair service from iCue, then close iCue and reopen HWinfo. I never had a problem with HWinfo getting the data (temps and fans speeds) as long as I never had them running at the same time. (version 3.xx of iCue) I was operating like this for years right up until I killed my PC with PBO. Another thing with Corsair is their service had some stupid timer somewhere in their software that kept everyone's AMD CPU boosting all the time. There was a windows command to get the OS to report it but I don't recall what that command was.