stasio Posted May 14, 2014 Share Posted May 14, 2014 Hi Fiery, just to let you know...latest AIDA64 Beta....perfect work...... GB Hardware Monitor (SIV) replaced ET..... http://i1105.photobucket.com/albums/h356/stasio1/2014-05-14_212908.png Take note that VCCIOA in GB SIV read offset +0.1V. Will check more this days..... Rgs, Stasio Quote Link to comment Share on other sites More sharing options...
Fiery Posted May 14, 2014 Share Posted May 14, 2014 Can you please check if VCCIOA is really an offset away from our value, or maybe it's a ratio that should be applied, like *1.09 ?Thanks, Fiery Quote Link to comment Share on other sites More sharing options...
stasio Posted May 14, 2014 Author Share Posted May 14, 2014 GTL display correctly...btw, Edit: Already reported to GB HQ. Quote Link to comment Share on other sites More sharing options...
stasio Posted May 15, 2014 Author Share Posted May 15, 2014 Hi Fiery, yea seems AIDA64 display VCCIOA voltage slightly (-) offset. Set in BIOS to 1.18V,please have a look pic bellow: Also,can you implement VRING voltage reading from ITE , as we have also for Z87 system. Thanks,rgs Stasio Quote Link to comment Share on other sites More sharing options...
Fiery Posted May 15, 2014 Share Posted May 15, 2014 I don't think VRING can be monitored by your motherboard As for VCCIOA, I'm confused. What is the actual offset AIDA64 should use? Quote Link to comment Share on other sites More sharing options...
stasio Posted May 15, 2014 Author Share Posted May 15, 2014 I think ~ +0.011V.... I will talk with Martin ,to see how he implement VRING in HWiNFO. Edit: HWMonitor also display..... Quote Link to comment Share on other sites More sharing options...
Fiery Posted May 16, 2014 Share Posted May 16, 2014 That VRING doesn't come from the motherboard or the motherboard sensor chip. It's not the VRING you've got used on GA-Z87 family motherboards. Those values that HWMonitor displays may come from calls to ICC. AIDA64 doesn't use ICC calls. Quote Link to comment Share on other sites More sharing options...
stasio Posted May 16, 2014 Author Share Posted May 16, 2014 I don't have all info about changes from Z87-OC.but maybe this can helped: Quote Link to comment Share on other sites More sharing options...
Fiery Posted May 16, 2014 Share Posted May 16, 2014 What I mean is... The fact that a GA-Z87 board could monitor VRING voltage in the UEFI Setup and via the Gigabyte monitoring software doesn't automatically mean the same voltage rail could be monitored with a successor board (GA-Z97). AFAIK VRING voltage measurement is missing from both the UEFI Setup or in Gigabyte monitoring software on GA-Z97 boards. Quote Link to comment Share on other sites More sharing options...
stasio Posted May 16, 2014 Author Share Posted May 16, 2014 OK Fiery. For Z87 board, ET didnn't display VRING voltage (just checked),instead is same as Z97. Just posted pic to Martin,as HWiNFO got some slightly offset (VCCIOA and VRING values): Gigabyte ET and GTL display correct values Edit: OK, I take multimeter and values are:VCCIOA....1.000VVRING.......1.077VVDIMM......1.500VVCORE.....1.032VVRIN..........1.782V AIDA64: Quote Link to comment Share on other sites More sharing options...
stasio Posted May 21, 2014 Author Share Posted May 21, 2014 Hi Fiery, beta 2954 Vcore change (VID voltage?).......in beta 2946 ..OK. The rest remain same (no change)....VCCIOA offset - 0.012V Going back to beta 2946. Vcore Beta 2946....Beta 2954 Vcore HWMonitor....Beta 2946....HWiNFO VCCIOA VCCIOA measured by digital multimeter......1.1805V Edit: No chance for VRING reading? HWiNFO and SIV use same method from Z87 system (with slightly offset)...and is working well. Quote Link to comment Share on other sites More sharing options...
Fiery Posted May 21, 2014 Share Posted May 21, 2014 1) We've replaced Vcore reading with VID because Vcore reading shows very low values when the CPU enters C1E. VID shows a more realistic value for a CPU core voltage than the actual Vcore reading. 2) We'll add the +0.012V offset for the VCCIOA voltage in the next AIDA64 beta release. 3) As I've explained above, your Z97 motherboard doesn't seem to be able to monitor VRING voltage. Quote Link to comment Share on other sites More sharing options...
stasio Posted May 21, 2014 Author Share Posted May 21, 2014 I still prefer previous Vcore reading. If I set all power saving to disable,Vcore display max.value (which is different then VID value). With C3 and C6/7 state enabled....voltage drop (together with temperatures) what is normal for me. I will check now with C1E enabled...will edit post.... This new beta remain me of CPU-Z (max.VID voltage always)......which also affect BCLK reading and core speed. Edit: Enabled C1E,C3 and C6/7 state....for me nothing wrong in beta 2946..pic: Vcore (fluctuate)....0.0360V Latest CPU-Z: Vcore.....max.VID (always).....(as latest AIDA64 beta 2954) Core speed....should be 4600 MHz Bus speed......should be 100 MHZ Quote Link to comment Share on other sites More sharing options...
Fiery Posted May 21, 2014 Share Posted May 21, 2014 0.036V doesn't seem like valid value for CPU core voltage, especially if you consider the VID value when the CPU is idle. That's what I meant above, that's why we've replaced Vcore reading with VID. As for CPU-Z, please note that we are not the authors of CPU-Z, so we cannot fix any bugs you may find in that software. Quote Link to comment Share on other sites More sharing options...
stasio Posted May 21, 2014 Author Share Posted May 21, 2014 So,now Core voltage is VID? VID voltage already displayed in AIDA64 Sidebar Gadget readings and Overclock page. Official Gigabyte SIV: Quote Link to comment Share on other sites More sharing options...
Fiery Posted May 21, 2014 Share Posted May 21, 2014 On certain Gigabyte and MSI motherboards we use VID as Vcore, yes. And we're aware of the fact that Gigabyte and MSI software displays the same very low Vcore values, but those values in AIDA64 caused user confusions and several users approached to us complaining about them. Not easy to make a proper sensor measurement solution when the values are suspicious in the first place... Quote Link to comment Share on other sites More sharing options...
stasio Posted May 21, 2014 Author Share Posted May 21, 2014 Haha,this confused users probably don't know what is Vcore and VID. I'll stay with beta 2946 and advice any Gigabyte user to use this version. Thanks Fiery. Quote Link to comment Share on other sites More sharing options...
stasio Posted May 23, 2014 Author Share Posted May 23, 2014 Hi Fiery, Gigabyte HQ send me today updated version of Hardware Monitor (GB SIV).Please, adjust CPU Core Voltage reading and VCCIOA voltage offset as per pics (and GB monitoring software): Thanks,rgs, Stasio Quote Link to comment Share on other sites More sharing options...
Fiery Posted May 26, 2014 Share Posted May 26, 2014 Please upgrade to the latest beta version of AIDA64 Extreme available at: http://www.aida64.com/downloads/aida64extremebuild2959jb7mpx9kzfzip In this build we've reverted back to the native Vcore measurement (on both Gigabyte 8-series and 9-series boards, as well as on MSI 8-series boards), in order to provide power-users with a more accurate Vcore measurement when the CPU is under load. For the rest of the AIDA64 users base we'll explain the issue of very low Vcore at idle when it's necessary We've also implemented the requested offset for VCCIOA. Quote Link to comment Share on other sites More sharing options...
stasio Posted May 26, 2014 Author Share Posted May 26, 2014 Thanks Fiery, everything OK now......!!!! Quote Link to comment Share on other sites More sharing options...
Fiery Posted May 27, 2014 Share Posted May 27, 2014 Thank you for the feedback Quote Link to comment Share on other sites More sharing options...
stasio Posted June 2, 2014 Author Share Posted June 2, 2014 Hi Fiery, Just lunched new GA-Z97X-SOC Force LN2 motherboard. Uploaded files: https://www.mediafire.com/?pjj7dranonaxch0 Thanks. Quote Link to comment Share on other sites More sharing options...
stasio Posted June 2, 2014 Author Share Posted June 2, 2014 Thanks Fiery, with Beta 3006 seems to be all OK. Rgs, stasio Quote Link to comment Share on other sites More sharing options...
Fiery Posted June 2, 2014 Share Posted June 2, 2014 Thank you for the feedback Quote Link to comment Share on other sites More sharing options...
stasio Posted June 2, 2014 Author Share Posted June 2, 2014 Fiery, maybe just about memory.......they are in slot 1 and 2. Also XMP profile ...to be 2933. Same will be for SOC Force. Thanks. 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.