Jump to content
Bearbite

TTRGB Plus is not read system temp !!PWM not working!! (Riing trio fans with AMD Ryzen Threadripper 2950X)

Recommended Posts

Hi,

I have a system with 23 Riing trio radiator fans, but the TT RGB plus software can't read my system / processor temperature.
The 6 controllers working good. I can set the color and the speed manually. But i woluld like to set PWM with auto fan speed...

Motherboard: Asus zenith extreme
Processor: AMD Ryzen Threadripper 2950X
OS: Windows 10 Pro 64
TT RGB PLUS version: 1.3.3

I had run the TTRGB PLUS by system admin.

HWINFO output (I see my processor temperature in the HWINFO):

------------HWi32_GetSensorName:System = 6.95148e-310----------------------
------------HWi32_GetSensorName:CPU [#0]: AMD Ryzen Threadripper 2950X = 0----------------------
HWi32_GetVoltage:Core 0 VID = 1.3125
HWi32_GetClock:Core 0 Clock = 4116.08
HWi32_GetUsage:Core 0 T0 Usage = 20
HWi32_GetVoltage:Core 1 VID = 1.425
HWi32_GetClock:Core 1 Clock = 4116.08
HWi32_GetVoltage:Core 2 VID = 1.425
HWi32_GetClock:Core 2 Clock = 4190.92
HWi32_GetUsage:Core 1 T0 Usage = 10
HWi32_GetVoltage:Core 3 VID = 1.3875
HWi32_GetClock:Core 3 Clock = 4190.92
HWi32_GetVoltage:Core 4 VID = 1.38125
HWi32_GetClock:Core 4 Clock = 4091.14
HWi32_GetUsage:Core 2 T0 Usage = 10
HWi32_GetVoltage:Core 5 VID = 1.43125
HWi32_GetClock:Core 5 Clock = 4091.14
HWi32_GetVoltage:Core 6 VID = 1.43125
HWi32_GetClock:Core 6 Clock = 4165.97
HWi32_GetVoltage:Core 7 VID = 1.44375
HWi32_GetClock:Core 7 Clock = 4116.08
HWi32_GetVoltage:Core 8 VID = 1.45
HWi32_GetClock:Core 8 Clock = 2993.51
HWi32_GetVoltage:Core 9 VID = 1.44375
HWi32_GetClock:Core 9 Clock = 2993.51
HWi32_GetVoltage:Core 10 VID = 1.46875
HWi32_GetClock:Core 10 Clock = 2744.05
HWi32_GetVoltage:Core 11 VID = 1.45
HWi32_GetClock:Core 11 Clock = 4116.08
HWi32_GetVoltage:Core 12 VID = 1.45
HWi32_GetClock:Core 12 Clock = 2993.51
HWi32_GetUsage:Core 6 T0 Usage = 40
HWi32_GetVoltage:Core 13 VID = 1.45
HWi32_GetClock:Core 13 Clock = 4116.08
HWi32_GetVoltage:Core 14 VID = 1.44375
HWi32_GetClock:Core 14 Clock = 2760.68
HWi32_GetVoltage:Core 15 VID = 1.4375
HWi32_GetClock:Core 15 Clock = 4116.08
HWi32_GetUsage:Core 7 T1 Usage = 10
HWi32_GetClock:Bus Clock = 99.7838
HWi32_GetUsage:Core 9 T1 Usage = 10
HWi32_GetUsage:Core 10 T0 Usage = 10
HWi32_GetUsage:Core 11 T0 Usage = 10
HWi32_GetClock:Core 0 T0 Effective Clock = 266.646
HWi32_GetUsage:Core 13 T0 Usage = 30
HWi32_GetClock:Core 0 T1 Effective Clock = 79.6988
HWi32_GetClock:Core 1 T0 Effective Clock = 191.631
HWi32_GetClock:Core 1 T1 Effective Clock = 176.67
HWi32_GetClock:Core 2 T0 Effective Clock = 392.364
HWi32_GetClock:Core 2 T1 Effective Clock = 27.7474
HWi32_GetClock:Core 3 T0 Effective Clock = 292.171
HWi32_GetUsage:Max CPU/Thread Usage = 40
HWi32_GetClock:Core 3 T1 Effective Clock = 65.7851
HWi32_GetUsage:Total CPU Usage = 4.6875
HWi32_GetClock:Core 4 T0 Effective Clock = 141.335
HWi32_GetClock:Core 4 T1 Effective Clock = 20.2848
HWi32_GetClock:Core 5 T0 Effective Clock = 90.5325
HWi32_GetClock:Core 5 T1 Effective Clock = 30.0429
HWi32_GetClock:Core 6 T0 Effective Clock = 1576.87
HWi32_GetClock:Core 6 T1 Effective Clock = 12.7494
HWi32_GetClock:Core 7 T0 Effective Clock = 69.497
HWi32_GetClock:Core 7 T1 Effective Clock = 113.659
HWi32_GetClock:Core 8 T0 Effective Clock = 24.9393
HWi32_GetClock:Core 8 T1 Effective Clock = 1.50633
HWi32_GetClock:Core 9 T0 Effective Clock = 47.9095
HWi32_GetClock:Core 9 T1 Effective Clock = 52.4736
HWi32_GetClock:Core 10 T0 Effective Clock = 31.8203
HWi32_GetClock:Core 10 T1 Effective Clock = 1.93067
HWi32_GetClock:Core 11 T0 Effective Clock = 40.53
HWi32_GetClock:Core 11 T1 Effective Clock = 55.027
HWi32_GetClock:Core 12 T0 Effective Clock = 66.4707
HWi32_GetClock:Core 12 T1 Effective Clock = 23.3705
HWi32_GetClock:Core 13 T0 Effective Clock = 1739.25
HWi32_GetClock:Core 13 T1 Effective Clock = 7.21509
HWi32_GetClock:Core 14 T0 Effective Clock = 340.901
HWi32_GetClock:Core 14 T1 Effective Clock = 8.69661
HWi32_GetClock:Core 15 T0 Effective Clock = 50.3515
HWi32_GetClock:Core 15 T1 Effective Clock = 22.9879
HWi32_GetClock:Average Effective Clock = 189.471
------------HWi32_GetSensorName:Memory Timings = 0----------------------
HWi32_GetClock:Memory Clock = 1064.36
------------HWi32_GetSensorName:CPU [#0] Node #0: AMD Ryzen Threadripper 2950X: Enhanced = 0----------------------
HWi32_GetTemperature:CPU (Tctl) = 59.375
HWi32_GetTemperature:CPU (Tdie) = 32.375
HWi32_GetVoltage:SoC Voltage (SVI2 TFN) = 0.825
HWi32_GetCurrent:SoC Current (SVI2 TFN) = 15.851
HWi32_GetPower:SoC Power (SVI2 TFN) = 13.0771
------------HWi32_GetSensorName:CPU [#0] Node #1: AMD Ryzen Threadripper 2950X: Enhanced = 0----------------------
HWi32_GetTemperature:CPU (Tctl) = 59.375
HWi32_GetVoltage:CPU Core Voltage (SVI2 TFN) = 1.29375
HWi32_GetCurrent:CPU Core Current (SVI2 TFN) = 33.0667
HWi32_GetPower:CPU Package Power (SMU) = 47.0834
HWi32_GetTemperature:CPU (Tdie) = 32.375
HWi32_GetPower:Core 0 Power (SMU) = 1.53457
HWi32_GetClock:Memory Controller Clock (UCLK) = 1064.36
HWi32_GetPower:Core 1 Power (SMU) = 1.92335
HWi32_GetPower:Core 2 Power (SMU) = 1.65709
HWi32_GetPower:Core 3 Power (SMU) = 1.5879
HWi32_GetPower:Core 4 Power (SMU) = 0.758437
HWi32_GetPower:Core 5 Power (SMU) = 0.61
HWi32_GetPower:Core 6 Power (SMU) = 2.86871
HWi32_GetPower:Core 7 Power (SMU) = 0.747103
HWi32_GetPower:Core 8 Power (SMU) = 0.258131
HWi32_GetPower:Core 9 Power (SMU) = 0.731898
HWi32_GetPower:Core 10 Power (SMU) = 0.265751
HWi32_GetPower:Core 11 Power (SMU) = 0.7372
HWi32_GetPower:Core 12 Power (SMU) = 0.674353
HWi32_GetPower:Core 13 Power (SMU) = 4.27411
HWi32_GetPower:Core 14 Power (SMU) = 0.837431
HWi32_GetPower:Core 15 Power (SMU) = 0.546986
HWi32_GetPower:CPU Core Power (SVI2 TFN) = 42.78
------------HWi32_GetSensorName:ASUS WMI = 0----------------------
HWi32_GetTemperature:CPU Temperature = 27
HWi32_GetVoltage:CPU Core Voltage = 1.4388
HWi32_GetCurrent:CPU VRM Output Current = 14
HWi32_GetPower:CPU Power = 18.396
HWi32_GetTemperature:CPU Socket Temperature = 28
HWi32_GetVoltage:CPU SOC Voltage = 0.872
HWi32_GetTemperature:Motherboard Temperature = 30
HWi32_GetVoltage:DRAM AB Voltage = 1.2208
HWi32_GetTemperature:Chipset Temperature = 52
HWi32_GetVoltage:DRAM CD Voltage = 1.2208
HWi32_GetVoltage:1.8V PLL Voltage = 1.8312
HWi32_GetFan:Water Pump 1 = 2636
HWi32_GetTemperature:CPU VRM Temperature = 36
HWi32_GetVoltage:+12V Voltage = 12.099
HWi32_GetTemperature:Water In = 25
HWi32_GetVoltage:+5V Voltage = 4.93225
HWi32_GetTemperature:Water Out = 25
HWi32_GetVoltage:3VSB Voltage = 3.3354
HWi32_GetVoltage:VBAT Voltage = 3.0302
HWi32_GetVoltage:AVCC3 Voltage = 3.3572
HWi32_GetVoltage:SB 1.05V Voltage = 1.04375
HWi32_GetVoltage:CPU Core Voltage (VRM) = 1.314
HWi32_GetVoltage:CPU SOC Voltage (VRM) = 0.824
HWi32_GetVoltage:DRAM AB Voltage (VRM) = 1.2
HWi32_GetVoltage:DRAM CD Voltage (VRM) = 1.2
------------HWi32_GetSensorName:DIMM Temperature Sensor = 0----------------------
HWi32_GetTemperature:DIMM[0] Temperature = 35.5
HWi32_GetTemperature:DIMM[1] Temperature = 37
HWi32_GetTemperature:DIMM[2] Temperature = 38
HWi32_GetTemperature:DIMM[3] Temperature = 38
HWi32_GetTemperature:DIMM[4] Temperature = 33.75
HWi32_GetTemperature:DIMM[5] Temperature = 35.25
HWi32_GetTemperature:DIMM[6] Temperature = 36.25
HWi32_GetTemperature:DIMM[7] Temperature = 36.25
------------HWi32_GetSensorName:S.M.A.R.T.: Samsung SSD 970 PRO 1TB (S462NF0M316868X) = 0----------------------
HWi32_GetTemperature:Drive Temperature = 41
HWi32_GetUsage:Drive Remaining Life = 100
HWi32_GetTemperature:Drive Temperature 2 = 50
------------HWi32_GetSensorName:S.M.A.R.T.: Samsung SSD 970 PRO 1TB (S462NF0M800553P) = 0----------------------
HWi32_GetTemperature:Drive Temperature = 38
HWi32_GetUsage:Drive Remaining Life = 100
HWi32_GetTemperature:Drive Temperature 2 = 42
------------HWi32_GetSensorName:S.M.A.R.T.: Samsung SSD 970 PRO 1TB (S462NF0M316898Z) = 0----------------------
HWi32_GetTemperature:Drive Temperature = 36
HWi32_GetUsage:Drive Remaining Life = 100
HWi32_GetTemperature:Drive Temperature 2 = 39
------------HWi32_GetSensorName:Drive: Samsung SSD 970 PRO 1TB (S462NF0M316868X) = 0----------------------
HWi32_GetUsage:Write Activity = 0.16
HWi32_GetUsage:Total Activity = 0.16
------------HWi32_GetSensorName:Drive: Samsung SSD 970 PRO 1TB (S462NF0M800553P) = 0----------------------
------------HWi32_GetSensorName:Drive: Samsung SSD 970 PRO 1TB (S462NF0M316898Z) = 0----------------------
------------HWi32_GetSensorName:GPU [#0]: NVIDIA GeForce RTX 2080 Ti:  = 0----------------------
HWi32_GetTemperature:GPU Temperature = 28
HWi32_GetVoltage:GPU Core Voltage = 0.725
HWi32_GetPower:GPU Power = 55.011
HWi32_GetClock:GPU Clock = 1140
HWi32_GetUsage:GPU Core Load = 1
HWi32_GetUsage:GPU Memory Controller Load = 1
HWi32_GetClock:GPU Memory Clock = 7000
HWi32_GetClock:GPU Video Clock = 1050
HWi32_GetUsage:GPU Memory Usage = 11.0349
HWi32_GetUsage:GPU D3D Usage = 0.3268
------------HWi32_GetSensorName:GPU [#1]: NVIDIA GeForce RTX 2080 Ti:  = 0----------------------
HWi32_GetTemperature:GPU Temperature = 27
HWi32_GetVoltage:GPU Core Voltage = 0.725
HWi32_GetPower:GPU Power = 21.511
HWi32_GetClock:GPU Clock = 300
HWi32_GetClock:GPU Memory Clock = 405
HWi32_GetClock:GPU Video Clock = 540
HWi32_GetUsage:GPU Memory Usage = 1.90874
------------HWi32_GetSensorName:Network: Atheros/Qualcomm QCA6174 802.11ac Wireless Network Adapter = 0----------------------
------------HWi32_GetSensorName:Network: Intel I211AT Copper (Pearsonville) Network Adapter = 0----------------------
------------HWi32_GetSensorName:Windows Hardware Errors (WHEA) = 0----------------------

Please help me, how can i use this software with PWM function?!
Why the software can't see the temp if it is in the HWINFO???

Thank you,

P

 


 

2020-02-23_LI.jpg

Share this post


Link to post
Share on other sites

Have the same problem with Threadripper 1950X, please help,

 

HWINFO output:

 

------------HWi32_GetSensorName:System = 6.95151e-310----------------------

------------HWi32_GetSensorName:CPU [#0]: AMD Ryzen Threadripper 1950X = 0----------------------

HWi32_GetVoltage:Core 0 VID = 1.39375

HWi32_GetClock:Core 0 Clock = 3899.01

HWi32_GetUsage:Core 0 T0 Usage = 21.4

HWi32_GetVoltage:Core 1 VID = 1.39375

HWi32_GetClock:Core 1 Clock = 3899.01

HWi32_GetUsage:Core 0 T1 Usage = 2.1

HWi32_GetVoltage:Core 2 VID = 1.39375

HWi32_GetClock:Core 2 Clock = 3899.01

HWi32_GetUsage:Core 1 T0 Usage = 6.1

HWi32_GetVoltage:Core 3 VID = 1.39375

HWi32_GetClock:Core 3 Clock = 3899.01

HWi32_GetVoltage:Core 4 VID = 1.4

HWi32_GetClock:Core 4 Clock = 3899.01

HWi32_GetUsage:Core 2 T0 Usage = 2.1

HWi32_GetVoltage:Core 5 VID = 1.4

HWi32_GetClock:Core 5 Clock = 3899.01

HWi32_GetUsage:Core 2 T1 Usage = 1.3

HWi32_GetVoltage:Core 6 VID = 1.4

HWi32_GetClock:Core 6 Clock = 3899.01

HWi32_GetUsage:Core 3 T0 Usage = 3

HWi32_GetVoltage:Core 7 VID = 1.39375

HWi32_GetClock:Core 7 Clock = 3899.01

HWi32_GetUsage:Core 3 T1 Usage = 2.1

HWi32_GetVoltage:Core 8 VID = 1.4

HWi32_GetClock:Core 8 Clock = 3899.01

HWi32_GetUsage:Core 4 T0 Usage = 1.7

HWi32_GetVoltage:Core 9 VID = 1.4

HWi32_GetClock:Core 9 Clock = 3899.01

HWi32_GetVoltage:Core 10 VID = 1.39375

HWi32_GetClock:Core 10 Clock = 3899.01

HWi32_GetUsage:Core 5 T0 Usage = 3

HWi32_GetVoltage:Core 11 VID = 1.39375

HWi32_GetClock:Core 11 Clock = 3899.01

HWi32_GetUsage:Core 5 T1 Usage = 0.8

HWi32_GetVoltage:Core 12 VID = 1.39375

HWi32_GetClock:Core 12 Clock = 3899.01

HWi32_GetUsage:Core 6 T0 Usage = 5.2

HWi32_GetVoltage:Core 13 VID = 1.4

HWi32_GetClock:Core 13 Clock = 3899.01

HWi32_GetVoltage:Core 14 VID = 1.4

HWi32_GetClock:Core 14 Clock = 3899.01

HWi32_GetUsage:Core 7 T0 Usage = 15.7

HWi32_GetVoltage:Core 15 VID = 1.4

HWi32_GetClock:Core 15 Clock = 3899.01

HWi32_GetUsage:Core 7 T1 Usage = 4.8

HWi32_GetClock:Bus Clock = 99.9745

HWi32_GetUsage:Core 8 T0 Usage = 6.1

HWi32_GetUsage:Core 8 T1 Usage = 3.5

HWi32_GetUsage:Core 9 T0 Usage = 25.4

HWi32_GetUsage:Core 9 T1 Usage = 2.1

HWi32_GetUsage:Core 10 T0 Usage = 10.5

HWi32_GetUsage:Core 10 T1 Usage = 3.5

HWi32_GetUsage:Core 11 T0 Usage = 5.2

HWi32_GetUsage:Core 11 T1 Usage = 3.5

HWi32_GetUsage:Core 12 T0 Usage = 3.9

HWi32_GetClock:Core 0 T0 Effective Clock = 984.43

HWi32_GetUsage:Core 13 T0 Usage = 1.7

HWi32_GetClock:Core 0 T1 Effective Clock = 113.725

HWi32_GetClock:Core 1 T0 Effective Clock = 659.108

HWi32_GetUsage:Core 14 T0 Usage = 4.3

HWi32_GetClock:Core 1 T1 Effective Clock = 128.431

HWi32_GetUsage:Core 14 T1 Usage = 1.3

HWi32_GetClock:Core 2 T0 Effective Clock = 267.895

HWi32_GetUsage:Core 15 T0 Usage = 0.8

HWi32_GetClock:Core 2 T1 Effective Clock = 161.632

HWi32_GetUsage:Core 15 T1 Usage = 2.1

HWi32_GetClock:Core 3 T0 Effective Clock = 291.459

HWi32_GetUsage:Max CPU/Thread Usage = 25.4

HWi32_GetClock:Core 3 T1 Effective Clock = 132.222

HWi32_GetUsage:Total CPU Usage = 4.475

HWi32_GetClock:Core 4 T0 Effective Clock = 248.701

HWi32_GetClock:Core 4 T1 Effective Clock = 79.3609

HWi32_GetClock:Core 5 T0 Effective Clock = 245.698

HWi32_GetClock:Core 5 T1 Effective Clock = 102.637

HWi32_GetClock:Core 6 T0 Effective Clock = 451.763

HWi32_GetClock:Core 6 T1 Effective Clock = 69.3373

HWi32_GetClock:Core 7 T0 Effective Clock = 707.906

HWi32_GetClock:Core 7 T1 Effective Clock = 333.562

HWi32_GetClock:Core 8 T0 Effective Clock = 441.108

HWi32_GetClock:Core 8 T1 Effective Clock = 175.604

HWi32_GetClock:Core 9 T0 Effective Clock = 1123.85

HWi32_GetClock:Core 9 T1 Effective Clock = 98.2497

HWi32_GetClock:Core 10 T0 Effective Clock = 497.029

HWi32_GetClock:Core 10 T1 Effective Clock = 169.595

HWi32_GetClock:Core 11 T0 Effective Clock = 446.989

HWi32_GetClock:Core 11 T1 Effective Clock = 174.471

HWi32_GetClock:Core 12 T0 Effective Clock = 301.529

HWi32_GetClock:Core 12 T1 Effective Clock = 73.7967

HWi32_GetClock:Core 13 T0 Effective Clock = 168.218

HWi32_GetClock:Core 13 T1 Effective Clock = 77.0482

HWi32_GetClock:Core 14 T0 Effective Clock = 291.403

HWi32_GetClock:Core 14 T1 Effective Clock = 129.217

HWi32_GetClock:Core 15 T0 Effective Clock = 122.176

HWi32_GetClock:Core 15 T1 Effective Clock = 187.081

HWi32_GetClock:Average Effective Clock = 295.476

------------HWi32_GetSensorName:Memory Timings = 0----------------------

HWi32_GetClock:Memory Clock = 1466.29

------------HWi32_GetSensorName:CPU [#0] Node #0: AMD Ryzen Threadripper 1950X: Enhanced = 0----------------------

HWi32_GetTemperature:CPU (Tctl) = 61.5

HWi32_GetTemperature:CPU (Tdie) = 34.5

HWi32_GetVoltage:SoC Voltage (SVI2 TFN) = 1.20625

HWi32_GetCurrent:SoC Current (SVI2 TFN) = 27.2784

HWi32_GetPower:SoC Power (SVI2 TFN) = 32.9046

------------HWi32_GetSensorName:CPU [#0] Node #1: AMD Ryzen Threadripper 1950X: Enhanced = 0----------------------

HWi32_GetTemperature:CPU (Tctl) = 59.875

HWi32_GetVoltage:CPU Core Voltage (SVI2 TFN) = 1.39375

HWi32_GetCurrent:CPU Core Current (SVI2 TFN) = 23.4667

HWi32_GetPower:CPU Package Power (SMU) = 79.1145

HWi32_GetTemperature:CPU (Tdie) = 32.875

HWi32_GetPower:Core 0 Power (SMU) = 2.8905

HWi32_GetClock:Memory Controller Clock (UCLK) = 1466.29

HWi32_GetPower:Core 1 Power (SMU) = 2.40015

HWi32_GetPower:Core 2 Power (SMU) = 1.76809

HWi32_GetPower:Core 3 Power (SMU) = 1.82056

HWi32_GetPower:Core 4 Power (SMU) = 1.73351

HWi32_GetPower:Core 5 Power (SMU) = 1.86697

HWi32_GetPower:Core 6 Power (SMU) = 2.20278

HWi32_GetPower:Core 7 Power (SMU) = 3.24391

HWi32_GetPower:Core 8 Power (SMU) = 1.89575

HWi32_GetPower:Core 9 Power (SMU) = 2.62342

HWi32_GetPower:Core 10 Power (SMU) = 2.02445

HWi32_GetPower:Core 11 Power (SMU) = 2.02938

HWi32_GetPower:Core 12 Power (SMU) = 1.6738

HWi32_GetPower:Core 13 Power (SMU) = 1.52264

HWi32_GetPower:Core 14 Power (SMU) = 1.85092

HWi32_GetPower:Core 15 Power (SMU) = 1.77616

HWi32_GetPower:CPU Core Power (SVI2 TFN) = 32.7067

------------HWi32_GetSensorName:ASUS WMI = 0----------------------

HWi32_GetTemperature:CPU Temperature = 34

HWi32_GetVoltage:CPU Core Voltage = 1.417

HWi32_GetCurrent:CPU VRM Output Current = 21

HWi32_GetPower:CPU Power = 29.106

HWi32_GetTemperature:CPU Socket Temperature = 33

HWi32_GetVoltage:CPU SOC Voltage = 1.2426

HWi32_GetTemperature:Motherboard Temperature = 33

HWi32_GetVoltage:DRAM AB Voltage = 1.3734

HWi32_GetTemperature:Chipset Temperature = 55

HWi32_GetVoltage:DRAM CD Voltage = 1.3516

HWi32_GetVoltage:1.8V PLL Voltage = 1.7876

HWi32_GetTemperature:CPU VRM Temperature = 41

HWi32_GetVoltage:+12V Voltage = 11.9028

HWi32_GetVoltage:+5V Voltage = 5.014

HWi32_GetVoltage:3VSB Voltage = 3.3354

HWi32_GetVoltage:VBAT Voltage = 3.0956

HWi32_GetVoltage:AVCC3 Voltage = 3.3354

HWi32_GetVoltage:SB 1.05V Voltage = 1.05

HWi32_GetVoltage:CPU Core Voltage (VRM) = 1.386

HWi32_GetVoltage:CPU SOC Voltage (VRM) = 1.207

HWi32_GetVoltage:DRAM AB Voltage (VRM) = 1.35

HWi32_GetVoltage:DRAM CD Voltage (VRM) = 1.35

 

 

tt.JPG

Share this post


Link to post
Share on other sites

Ok, "good to hear" i'm not alone with this problem...  So please Thermaltake create a solution to this problem! Anybody? We have same problem with AMD Threadripper processors. Please help us!

Share this post


Link to post
Share on other sites

Hello Thermaltake,

Why don't we get an answer? I'm very disappointed! This was the last time I bought Thermaltake!!!
I wrote emails, I wrote forum messages, and with no answer! This is SHAME THERMALTAKE!!! This is the worst product with the worst support with highest price!!!

I hope Thermalte you read this! 

 

 

Share this post


Link to post
Share on other sites

I just recently bought ring quad fans and noticed that on my thread ripper system PWM is kinda broken. While looking at the fans connectors I did notice that the fans are PWM, but the fans are pulling the temps from software. How does this software know where the fans are located? Does it use my cpu temp for all fans? I have 2 loops 1 for cpu and 1 for 2 gpus in sli. Now I don't like modding stuff that don't need to be modded, but the fan design is broken or not meant for dual loop systems. So what I have figured out is to make a splitter from their 9 pin header plug to 9 pin header and PMW output fan plug. It's going cost me under 30$ to do all 12 of my fans. Since this is an adapter this won't void warranty. I have already depinned a 140mm Ring Quad and actually had the PWM function working on my mother board so I know it's going to work. I'm using the SIV software from Gigabyte to control fans speeds and pump speeds. Once all the stuff from Amazon gets here I'll post my final design, hope it will help you guys.

Share this post


Link to post
Share on other sites

Hello Thermaltake,

what about the problem will give a solution
have to say, support from Thermaltake is a disaster :-(((

that with the temperature used to work, why not now ????????????

v1.3.503   =     Temp:0°C / 32°F

Share this post


Link to post
Share on other sites
On 5/3/2020 at 12:12 PM, Chris Welch said:

I just recently bought ring quad fans and noticed that on my thread ripper system PWM is kinda broken. While looking at the fans connectors I did notice that the fans are PWM, but the fans are pulling the temps from software. How does this software know where the fans are located? Does it use my cpu temp for all fans? I have 2 loops 1 for cpu and 1 for 2 gpus in sli. Now I don't like modding stuff that don't need to be modded, but the fan design is broken or not meant for dual loop systems. So what I have figured out is to make a splitter from their 9 pin header plug to 9 pin header and PMW output fan plug. It's going cost me under 30$ to do all 12 of my fans. Since this is an adapter this won't void warranty. I have already depinned a 140mm Ring Quad and actually had the PWM function working on my mother board so I know it's going to work. I'm using the SIV software from Gigabyte to control fans speeds and pump speeds. Once all the stuff from Amazon gets here I'll post my final design, hope it will help you guys.

Hello Chris,

Nice idea :) Can you link the adapter and share a photo how do you solve this problem?

Thanks

 

Share this post


Link to post
Share on other sites

I will be making my own adapter, but isolating the fan from the usb header plug into two plugs, one pwm fan plug and another usb header plug and chaining the tach wire to both plugs. I have to make 12 of these, it's a shame TT won't split the plug, one for rgb and one for PWM, like CM fans.

Share this post


Link to post
Share on other sites

Also experiencing this issue, but immediately after doing a BIOS update. Getting 0 reading on my temps only on this program so it stay low. Now I forced to just leave the fans on max to keep things safe. Would really like to see a response from TT on this whats going with an update maybe.  

EDIT: Just as an note, they were working perfectly before my BIOS update, But no other program is having issues reading temps right now except TT

Share this post


Link to post
Share on other sites

Made one prototype using a pwm extension cutting the male end off, and crimping new male pins. I made 4 short length wires with new pins male, female with 2 new usb header connectors. Used yellow as my signal wire even though green is the signal wires from the fan. Notice that the signal wire is split from the male connector to the new usb connector and the pwm connector. It's working TT software shows rpms speeds but doesn't control pwm at all now. PWM is now controlled by the motherboard fan curve software and uses the actual temps from the motherboard. Hope it helps, it's alot of work for me (12 fans) but its worth it to me. 

20200513_183455.jpg

20200513_183502.jpg

Share this post


Link to post
Share on other sites

Here's my two cents. I have an AMD 2700x, i also have temps being reported as 0/32 which is absolutely not correct. I've been surfing thru any potential fixes and have come across a forum linked here (https://community.thermaltake.com/index.php?/topic/64805-fix-for-riing-plus-software-116-wrong-temperature-read-outs-ryzen-incl-threadripper/) This was back in 2018. The post links an older version of the TT RGB Plus software (1.1.6 x86) that version reads the temps rather accurate but the fix that it explains does nothing and only installing the new version is useless as the problem is still there. I have a feeling it might have to do with the fact that one is a 32-bit version and the other is a 64-bit version. might be solely software at this point I can only assume lol. we shouldn't be needing to mod, make adapters or run an old version of the software. Hopefully someone reaches out, till then TT fans and products seem like a waste of money (atleast to me). 

Share this post


Link to post
Share on other sites

TT software should stick to just RGB 99% of newer motherboards have built in fan control with temp headers that work better. I really don't want TT controlling my fans hence the adapters.

Share this post


Link to post
Share on other sites
2 hours ago, Chris Welch said:

TT software should stick to just RGB 99% of newer motherboards have built in fan control with temp headers that work better. I really don't want TT controlling my fans hence the adapters.

Ditto, it would be cool if they would give us the option to use Asus aura headers (or similar) and the fan headers for control, like other devices offer.

Share this post


Link to post
Share on other sites

Yes, the TT software and a controller is a buggy #### :( 

I have a problem with the controllers, too. The TT RGB Plus always lose the controller hubs randomly. I have 5 hubs with correct settings (connected with bridge cable), and working ~2-3 days,.. Then the software lost the connection with the 2nd and 3rd hub but the 1st and the 5th is still working... (Windows still recognize the Common USB hubs) When I have restarted the PC the still have the problem. BUT If I shut down the PC and wait 10 min and restart it, the software can recognize the controllers again.. 

 

Does anyone else have this problem?

Share this post


Link to post
Share on other sites

I'm wondering if the amount of stuff I have connected via USB has any effect on the controllers? I have alot connected with usb and sometimes i can get them to reinitialize by disconnecting one of my hubs. Then again I might be crazy.

Share this post


Link to post
Share on other sites

Maybe someone got their wish when not wanting TT software to be messing with their fan speeds via using the 'Temp' light mode.

Untitled.jpg

Share this post


Link to post
Share on other sites

Don't try getting Chroma to sync these either, controllers lag out loose connection and fail to work. I have 3 controllers, sometimes they work sometimes they don't. TT needs to revise these #### things asap. 

Share this post


Link to post
Share on other sites

I have written 2 messages via TT support central, (https://my.thermaltake.com/csTech.aspx) but nobody answered me. Annoying... I think I will send back these buggy overpriced #### to the seller. 🤬

Share this post


Link to post
Share on other sites

Update:

Weirdest crap happens when you least expect it, So I received 2 new controllers from TT. Same issues lag out cannot, will not work. So I decide to buy a new PS, I had a 850 EvGA pulling 650 ish from the wall. Against my better judgement and considering every #### PS was over priced as ####, amazon had a iRGB 1200w for 260$ I bought the thing. The same day I swapped them out, I get a software update from TT.  Now I had some issues that vanished! So I am like O.K the old PW was shot, put the ol voltage meter on it everything checks out. hmm... something's up but can't figure out what's the problem. Put the old PS back in the system started having problems, Voltages check out.. still pulling 650ish at the wall under load. At this point IDGAD anymore. Put the new PS back in and everything works fine, for once. Now under load with a threadripper , I barely break 500w!  What VooDoo you pulling here TT?!   Oh and BTW fix Chroma sync dammit! (at least now it doesn't lock up on rainbow puke lol)

Share this post


Link to post
Share on other sites

I also encounter the same problem, 1950X after the use of TT software version 1.3.0 will encounter this situation, so who has 1.2.7 this version of the file can send me one?

Share this post


Link to post
Share on other sites

Goood news here guys :D TT fixed this problem in the latest update of the TT RGB plus.

PWM working! I REPEAT, PWM Working with threadripper 2950x :D :D This is best day on my life LOL :D :D 

TTRGB plus version: 1.3.7 

 

 

Share this post


Link to post
Share on other sites

Just found this thread.

A while ago I was using TT RGB Plus 1.3.1 or 3.2 (not sure which) with no problems. I then updated my motherboard bios. I am using the ASUS ROG Zenith Extreme(original). I believe I upgraded from BIOS ver 1701 to 2001. 

In the change log for the bios on ASUS's website it says

ROG ZENITH EXTREME BIOS 1901
Improve hardware monitoring compatibility with 3rd party applications.
Fixed a boot issue when using a Quadro K6000 GPU.
" Before running the USB BIOS Flashback tool, please rename the BIOS file (ZE.CAP) using BIOSRenamer.''

Ver 2001 would have the same improvements + more.

Ever since updating, every version of TT RGB Plus from 1.2.8 (64 bit update) onward i have been getting a 0°C reading on TT RGB plus on my Threadripper system. Version 1.2.7 still works for me and I have been using that since, hoping a future update would help.

This bios update also changed my other system monitoring software, in particular interest HWINFO64, which I believe TT RGB Plus uses a plugin to get temps from. HWINFO64 continued to work, however the reporting of ASUS MB values had changed title to asus wmi, along with other changes, like readouts being renamed, e.g EXT Tsensor1 changed to Tsensor 1 Temperature. There may have been more changes, I don't know. Im guessing a name change or something similar is the problem.

Today I tried TT RGB Plus 1.3.7 because something caught my eye 2.Fixed AMD CPU temperature issue.

Something different has happened. I got a temperature other than 0°C. 😀The problem is it is the Tctl temp and not the tdie temp.🙁 Which of course means ttrgb thinks my cpu temp is 65°C instead of it's actual 40°C, so my fans are going close to full speed now. At least they are cooling the system, 0°C put them on idle🤔

I'll add a couple pictures which are hopefully straight forward, basically just diferent TT RGB versions and what the plugin is reading and what the program is reading on my PC. CPU is generally around 40°C idle.

I do now believe this problem is fixable but possibly only through a software update. I'm basically reaching out to any TTstaff that could possibly help. I know that a bios downgrade might work, but the new versions do have a few QOL improvements eg. mem stability etc. so would prefer not to.

If anyone else has any ideas as to what else could be the cause please let me know. I have been thinking this will probably never be fixed but this new update has given me hope. Any help from anyone would be much appreciated. Thanks😀

ttrgb1.3.7.png

ttrgb1.3.6.png

ttrgb1.2.8.png

ttrgb1.2.7.png

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • Create New...