ycodryn Posted August 17, 2017 Share Posted August 17, 2017 Using LatencyMon to check my system I saw values like 600-900 (current measured interrupt to process latency). I`m also using Logitech G13 to monitor cpu,gpu,fans etc. I closed AIDA and tried hwinfo for first time and had same latency. When I opened second time hwinfo it told me that if I enable some sensor system could hang, increase latency etc. I choose now to disable those and I had no more latency (40-70). In AIDA I can`t disable those even in stability tab. Is something named ASUS EC in hwinfo. In AIDA stability tab low-level sensor operations is giving that latency. Quote Link to comment Share on other sites More sharing options...
Fiery Posted August 18, 2017 Share Posted August 18, 2017 Without EC (Embedded Controller) support, you'd lose some of the sensor readings you may have places on your LCD layout. So it's not a good idea to disable EC support as long as you'd prefer to have all sensor readings. Quote Link to comment Share on other sites More sharing options...
ycodryn Posted August 18, 2017 Author Share Posted August 18, 2017 Hi. Checking Ec sensors in HWinfo I`m loosing only pch, vccst_a, pll, vccmp, cpu_opt fan. But is worth loosing some sensor and not having >800 latency. Quote Link to comment Share on other sites More sharing options...
Fiery Posted August 22, 2017 Share Posted August 22, 2017 On 2017. 08. 18. at 4:44 PM, ycodryn said: Hi. Checking Ec sensors in HWinfo I`m loosing only pch, vccst_a, pll, vccmp, cpu_opt fan. But is worth loosing some sensor and not having >800 latency. The basic issue is that even with EC traffic, such high latency is not supposed to occur. Other users with Asus motherboards having an EC chip do not see such anomalies. So it must be something about your computer IMHO. Maybe you've got another software running in the background that collides with the EC register readout activity of AIDA64? Quote Link to comment Share on other sites More sharing options...
ycodryn Posted August 28, 2017 Author Share Posted August 28, 2017 I made a fresh windows 10 install. I have nothing installed from ASUS besides drivers. What I found is that I have that high latency when I have something enabled from LCD tab. Either is Logitech or Odospace I have same big latency. I know that is AIDA`s fault because I have tried 4 (free) monitoring programs and none of them gives me high latency when rendering to tablet or logitech lcd. Nice thing about AIDA that makes me not to regret that I bought it is the lcd items layout and lcd supported drivers. Compared to hwinfo, AIDA does not have correction for every sensor (gpu memory clock multiply by 8 gives the correct result) , gpu Watts usage and sensors individual management (enable/disable). But maybe is just me, I bought aida for sensor monitoring only and not for other nice features. Should I try the AIDA64 Engineer trial? edit: I use only a hardware monitoring at a time. Quote Link to comment Share on other sites More sharing options...
Fiery Posted August 29, 2017 Share Posted August 29, 2017 19 hours ago, ycodryn said: I made a fresh windows 10 install. I have nothing installed from ASUS besides drivers. What I found is that I have that high latency when I have something enabled from LCD tab. Either is Logitech or Odospace I have same big latency. I know that is AIDA`s fault because I have tried 4 (free) monitoring programs and none of them gives me high latency when rendering to tablet or logitech lcd. Nice thing about AIDA that makes me not to regret that I bought it is the lcd items layout and lcd supported drivers. Compared to hwinfo, AIDA does not have correction for every sensor (gpu memory clock multiply by 8 gives the correct result) , gpu Watts usage and sensors individual management (enable/disable). But maybe is just me, I bought aida for sensor monitoring only and not for other nice features. Should I try the AIDA64 Engineer trial? edit: I use only a hardware monitoring at a time. It's easy to check whether the sensor module or the LCD module causes the high latency: simply just try turning off all LCD modules, and try to enable the SensorPanel. Please let me know how it changes the latency. Note that we've seen latency issues caused by the Logitech LCD API in the past. There's a chance the whole thing isn't rooted in AIDA64 at all. As for the missing features, we'll work on them GPU clock correction should come first, it's relatively easy. GPU Watts usage, I'm not sure about, since it should be supported by AIDA64 already. What video card do you have? As for sensors individual enabling/disabling: we haven't really dealt with that on the basis that the Computer / Sensor page was designed to provide just a quick glance on all the readings. If you want to further customize it, then you can go OSD Panel, where you can pick the items you want to have displayed. And, if you want to go one more step further, then there's SensorPanel and LCD, where you can not only pick which item to show, but also the visual representation of those items. About sensors AIDA64 Engineer will behave similarly to AIDA64 Extreme, so it doesn't make much sense to deal with it. Quote Link to comment Share on other sites More sharing options...
Fiery Posted August 29, 2017 Share Posted August 29, 2017 Meanwhile, we've rolled out a new AIDA64 beta build: https://www.aida64.com/downloads/latesta64xebeta In this build we've added a new option to the Preferences / Stability page to let you disable EC (Embedded Controller) polling. That way you would lose a few sensor readings, but maybe it helps to get around the latency issues. Also, in this build we've added GPU clocks as Correction items Quote Link to comment Share on other sites More sharing options...
ycodryn Posted August 29, 2017 Author Share Posted August 29, 2017 Hello. I have tried OSD, sensor panel, sensor icons separately and all of them gave me high latency. It seems that is not the lcd, is all of them. For GPU sensor aida only has TDP that comes close to watts but is not the same. It tells you only % from power range of card capability. I have a Asus Maximus 9 Formula mb and Evga GTX 1080 Hybrid card. edit: disable EC did the trick. I have all my sensor displayed on tabled and a nice latency. Thank you for that. Quote Link to comment Share on other sites More sharing options...
Fiery Posted August 29, 2017 Share Posted August 29, 2017 4 minutes ago, ycodryn said: Hello. I have tried OSD, sensor panel, sensor icons separately and all of them gave me high latency. It seems that is not the lcd, is all of them. For GPU sensor aida only has TDP that comes close to watts but is not the same. It tells you only % from power range of card capability. I have a Asus Maximus 9 Formula mb and Evga GTX 1080 Hybrid card. Can you please post a picture of how HWiNFO displays GPU power draw in Watts? Quote Link to comment Share on other sites More sharing options...
ycodryn Posted August 29, 2017 Author Share Posted August 29, 2017 Quote Link to comment Share on other sites More sharing options...
Fiery Posted August 29, 2017 Share Posted August 29, 2017 Thank you. Please right-click on the bottom status bar of AIDA64 main window --> Video Debug --> nVIDIA GPU Registers. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. You may need to enable status bar in AIDA64 / main menu / View first. Also right-click on the bottom status bar of AIDA64 main window --> Video Debug --> nVIDIA SMBus Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Quote Link to comment Share on other sites More sharing options...
ycodryn Posted August 29, 2017 Author Share Posted August 29, 2017 ------[ Versions ]------ Program Version : AIDA64 Extreme v5.92.4341 Beta BenchDLL Version: 4.3.759-x64 Windows Version : Microsoft Windows 10 Pro 10.0.15063.540 (64-bit) ------[ Video Adapters ]------ EVGA e-GeForce GTX 1080 [10DE-1B80 / 3842-6288] ------[ Video Driver ]------ nvapi.dll: 22.21.13.8528 C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_9ab613610b40aa98\nvldumdx.dll|||C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_9ab613610b40aa98\nvldumdx.dll|||C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_9ab613610b40aa98\nvldumdx.dll|||C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_9ab613610b40aa98\nvldumdx.dll|||C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_9ab613610b40aa98\nvldumd.dll|||C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_9ab613610b40aa98\nvldumd.dll|||C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_9ab613610b40aa98\nvldumd.dll|||C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_9ab613610b40aa98\nvldumd.dll C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_9ab613610b40aa98\nvldumdx.dll|||C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_9ab613610b40aa98\nvldumdx.dll|||C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_9ab613610b40aa98\nvldumdx.dll|||C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_9ab613610b40aa98\nvldumdx.dll|||C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_9ab613610b40aa98\nvldumd.dll|||C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_9ab613610b40aa98\nvldumd.dll|||C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_9ab613610b40aa98\nvldumd.dll|||C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_9ab613610b40aa98\nvldumd.dll C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_9ab613610b40aa98\nvldumdx.dll|||C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_9ab613610b40aa98\nvldumdx.dll|||C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_9ab613610b40aa98\nvldumdx.dll|||C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_9ab613610b40aa98\nvldumdx.dll|||C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_9ab613610b40aa98\nvldumd.dll|||C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_9ab613610b40aa98\nvldumd.dll|||C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_9ab613610b40aa98\nvldumd.dll|||C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_9ab613610b40aa98\nvldumd.dll C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_9ab613610b40aa98\nvldumdx.dll|||C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_9ab613610b40aa98\nvldumdx.dll|||C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_9ab613610b40aa98\nvldumdx.dll|||C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_9ab613610b40aa98\nvldumdx.dll|||C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_9ab613610b40aa98\nvldumd.dll|||C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_9ab613610b40aa98\nvldumd.dll|||C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_9ab613610b40aa98\nvldumd.dll|||C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_9ab613610b40aa98\nvldumd.dll ------[ nVIDIA GPU #1 @ mem DE000000 ]------ GPU Clocks = 1721 / 0 / 0 MHz Memory Clock = 5005 MHz GPU Base Clock = 27000 kHz Shader Base Clock = 27000 kHz Memory Base Clock = 27000 kHz nvidia-000000 = 134000A1 [GP104] nvidia-001538 = 800003FF nvidia-001704 = 801FFFE1 nvidia-001714 = C01FFFE2 nvidia-00E114 = 0000021C nvidia-00E118 = 0000021C nvidia-00E11C = 00000001 nvidia-00E120 = 00000000 nvidia-00E728 = 00000000 nvidia-00E820 = 02020015 nvidia-00E8A0 = 02000012 nvidia-020008 = 00002CF7 nvidia-020014 = 0209019F nvidia-0200C4 = 000000D8 nvidia-0200C8 = 00000000 nvidia-0200D8 = 010000D8 nvidia-0200DC = 00000000 nvidia-020340 = 000000A0 nvidia-020344 = 0000004F nvidia-020348 = 000000A0 nvidia-020400 = 0000001B nvidia-021000 = C0040000 nvidia-0214A8 = BADF510C nvidia-022400 = 00000000 nvidia-022430 = 00000004 nvidia-022434 = 00000005 nvidia-022438 = 00000004 nvidia-02243C = 00000004 nvidia-022440 = 00000004 nvidia-088000 = 1B8010DE [GP104] nvidia-08A000 = 10F010DE nvidia-100714 = 00001817 nvidia-101000 = 00400080 nvidia-10100C = 02013000 nvidia-120070 = 00000001 nvidia-120074 = 00000004 nvidia-120078 = 00000004 nvidia-122634 = 00000000 nvidia-300000 = EB78AA55 nvidia-310000 = 4E4658FF nvidia-700000 = 00000000 nvidia-7E0000 = 00000000 ------[ nVIDIA GPU #1 / ForceWare Properties ]------ Memory Type = 10 (GDDR5X) Memory Vendor = 10 (Micron) Memory Bank Count = 1 Memory Bus Width = 256-bit GPU / MC / VE / BI Load = 2 / 1 / 0 / 0 VPE Count = 0 Shader Pipe Count = 4 Shader SubPipe Count = 20 Total SP Count = <unknown> Total TPC Count = 0 Total SM Count = <unknown> Core Count = 2560 ROP Count = 64 Partition Count = 4 (mask: 0000000F) Fan RPM = 1202 RPM Fan Duty Cycle = 56 % Core Voltage = <unknown> Core Rail Voltage = 793750 uV Current Pstate = 0 PerfCap Reason = 16 (Utilization) Ventura State = 0 (unsupported) Physical Frame Buffer Size = 8388416 KB Virtual Frame Buffer Size = 8388608 KB Total / Free Video Memory = 8388608 KB / 8039668 KB ------[ nVIDIA GPU #1 / ForceWare Clocks (old) ]------ Perf. Levels = 4 Active Profile = 3 curr-core/shader/mem-0 = 607 MHz / 0 MHz / 405 MHz curr-core/shader/mem-1 = 569 MHz / 0 MHz / 810 MHz curr-core/shader/mem-2 = 683 MHz / 0 MHz / 4513 MHz curr-core/shader/mem-3 = 683 MHz / 0 MHz / 5005 MHz [Active] orig-core/shader/mem-0 = 607 MHz / 0 MHz / 405 MHz orig-core/shader/mem-1 = 569 MHz / 0 MHz / 810 MHz orig-core/shader/mem-2 = 683 MHz / 0 MHz / 4513 MHz orig-core/shader/mem-3 = 683 MHz / 0 MHz / 5005 MHz [Active] ------[ nVIDIA GPU #1 / BIOS Info ]------ BIOS Version = 86.04.3B.01.80 Signon Message = GP104 PG413 SKU 0 VGA BIOS Bootup Core Clock = 0 MHz Bootup Shader Clock = 1006739 MHz Bootup Mem Clock = 84215 MHz Ref. Clock 4000 = 0 kHz = 0 MHz *4 Ref. Clock 4008 = 0 kHz = 0 MHz *4 [Memory] Ref. Clock 4010 = 0 kHz = 0 MHz *4 Ref. Clock 4018 = 0 kHz = 0 MHz *4 Ref. Clock 4020 = 0 kHz = 0 MHz *4 [Shader] Ref. Clock 4028 = 0 kHz = 0 MHz *4 [GPU] Ref. Clock 4030 = 0 kHz = 0 MHz *4 Ref. Clock 4038 = 0 kHz = 0 MHz *4 Diode Gain Mul = 0 Diode Gain Div = 0 Diode Offset Mul = 0 Diode Offset Div = 0 Diode Offset Bin Mul = 0 Diode Offset Bin Div = 1 Temp Compensation Mul = 0 Temp Compensation Div = 1 Max Div = 0 Measured Temp Threshold (Raw) = 0 Measured Temp Threshold (Int) = 0 Celsius Measured Temp Threshold (Float) = 0 Celsius BIOS Temp Threshold = 125 Celsius Measured Diode Temp (Raw) = 0 Measured Diode Temp (Int) = 0 Celsius Measured Diode Temp (Float) = 0 Celsius Diode Temp by ForceWare = 27 Celsius ------[ NVAPI GPU Handles ]------ GPU Count = 1 GPU #1 = 00000100 ------[ nVIDIA GPU #1 / Thermal Settings V2 ]------ Sensor Count = 1 Sensor #0 / Controller = GPU Internal Sensor #0 / Target = GPU Core Sensor #0 / Current Temp = 27 Celsius ------[ nVIDIA GPU #1 / Thermal Settings V1 ]------ Sensor Count = 1 Sensor #0 / Controller = GPU Internal Sensor #0 / Target = GPU Core Sensor #0 / Current Temp = 27 Celsius Quote Link to comment Share on other sites More sharing options...
ycodryn Posted August 29, 2017 Author Share Posted August 29, 2017 ------[ Versions ]------ Program Version : AIDA64 Extreme v5.92.4341 Beta BenchDLL Version: 4.3.759-x64 Windows Version : Microsoft Windows 10 Pro 10.0.15063.540 (64-bit) ------[ Video Adapters ]------ EVGA e-GeForce GTX 1080 [10DE-1B80 / 3842-6288] ------[ Video Driver ]------ nvapi.dll: 22.21.13.8528 C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_9ab613610b40aa98\nvldumdx.dll|||C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_9ab613610b40aa98\nvldumdx.dll|||C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_9ab613610b40aa98\nvldumdx.dll|||C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_9ab613610b40aa98\nvldumdx.dll|||C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_9ab613610b40aa98\nvldumd.dll|||C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_9ab613610b40aa98\nvldumd.dll|||C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_9ab613610b40aa98\nvldumd.dll|||C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_9ab613610b40aa98\nvldumd.dll C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_9ab613610b40aa98\nvldumdx.dll|||C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_9ab613610b40aa98\nvldumdx.dll|||C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_9ab613610b40aa98\nvldumdx.dll|||C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_9ab613610b40aa98\nvldumdx.dll|||C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_9ab613610b40aa98\nvldumd.dll|||C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_9ab613610b40aa98\nvldumd.dll|||C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_9ab613610b40aa98\nvldumd.dll|||C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_9ab613610b40aa98\nvldumd.dll C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_9ab613610b40aa98\nvldumdx.dll|||C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_9ab613610b40aa98\nvldumdx.dll|||C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_9ab613610b40aa98\nvldumdx.dll|||C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_9ab613610b40aa98\nvldumdx.dll|||C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_9ab613610b40aa98\nvldumd.dll|||C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_9ab613610b40aa98\nvldumd.dll|||C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_9ab613610b40aa98\nvldumd.dll|||C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_9ab613610b40aa98\nvldumd.dll C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_9ab613610b40aa98\nvldumdx.dll|||C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_9ab613610b40aa98\nvldumdx.dll|||C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_9ab613610b40aa98\nvldumdx.dll|||C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_9ab613610b40aa98\nvldumdx.dll|||C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_9ab613610b40aa98\nvldumd.dll|||C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_9ab613610b40aa98\nvldumd.dll|||C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_9ab613610b40aa98\nvldumd.dll|||C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_9ab613610b40aa98\nvldumd.dll ------[ nVIDIA GPU #1 / B00-CR1F = 00 ]------ ------[ nVIDIA GPU #1 / B00-CR49 = 00 ]------ ------[ nVIDIA GPU #1 / B01-CR1F = 00 ]------ ------[ nVIDIA GPU #1 / B01-CR49 = 00 ]------ ------[ nVIDIA GPU #1 / B02-CR1F = 00 ]------ ------[ nVIDIA GPU #1 / B02-CR49 = 00 ]------ ------[ nVIDIA GPU #1 / B03-CR1F = 00 ]------ ------[ nVIDIA GPU #1 / B03-CR49 = 00 ]------ ------[ nVIDIA GPU #1 / B04-CR1F = 00 ]------ ------[ nVIDIA GPU #1 / B04-CR49 = 00 ]------ ------[ nVIDIA I2C Device GPU #1 / B04-D49 ]------ 0000 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................ 0010 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................ 0020 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................ 0030 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................ 0040 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................ 0050 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................ 0060 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................ 0070 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................ 0080 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................ 0090 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................ 00A0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................ 00B0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................ 00C0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................ 00D0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................ 00E0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................ 00F0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ................ ------[ nVIDIA I2C Device GPU #1 / B04-D49 ]------ 0000 0000 0101 4444 FEFE 0A0A 0000 0101 0000 0202 FFFF 0000 0000 0505 0000 0000 0000 0010 0000 0000 0000 0000 0000 0000 0000 0000 0000 0404 0000 0000 0000 0000 0000 0000 0020 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0030 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0040 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0050 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0060 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0070 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0080 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0090 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 00A0 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 00B0 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 00C0 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 00D0 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 00E0 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 00F0 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 ------[ Chips Found ]------ GPU1-B04-D49: ***** Unknown Device ***** Total : 14.8 sec GPU1-B00: 3.0 sec GPU1-B01: 3.3 sec GPU1-B02: 3.2 sec GPU1-B03: 3.5 sec GPU1-B04: 0.8 sec Quote Link to comment Share on other sites More sharing options...
ycodryn Posted September 17, 2017 Author Share Posted September 17, 2017 If it helps this is the vendor link: https://www.evga.com/products/product.aspx?pn=08g-p4-6288-kr Quote Link to comment Share on other sites More sharing options...
Fiery Posted September 18, 2017 Share Posted September 18, 2017 Thank you for the data. The measurements comes via the NVML API, which is difficult to utilize from our software. We will need to work more on it, and implement special tricks to use NVML. Quote Link to comment Share on other sites More sharing options...
ycodryn Posted July 27, 2018 Author Share Posted July 27, 2018 Hello. Any news about gpu power (watts) values? Thank you. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.