Jump to content

Intel Power Gadget 3.7.0


SavageAUS
 Share

51 posts in this topic

Recommended Posts

So some get instant reboot ( install OK, but first use of the app = reboot) some not... a bit ??

I use Clover & his P/C States generation + Intel CPU Monitor (from Slice).

May be MacModel dependency? I am using iMac17,1. Fine.

Link to comment
Share on other sites

can be. But it seems that ix-3xxx (me, MacModel iMac13,2) and ix-2xxx cpus (here) have this problem.

Got some with that 2 or 3 gen ix that new gadet to work / no reboot if used? And if yes what MacModel do you use? 

Intel claims that it intended from 2nd Generation up to 7th Generation Intel® Core™ processors. Intel's bug?

Or may be it requires Intel GPU presents?

Link to comment
Share on other sites

Yep, i think its a bug (seems only 4. gen ix CPU work) or they forgot  to tell its for 4. gen + CPUs only (before version 2. gen+) ?

And yes, known probs (in their text) tells some IGPU related probs with the graph (iGPU needed?) - but not the reason for reboot.

But doesn't matter if older versions work for those use it - i dont use, i use only slice Intel CPU Monitor - always working :)

Link to comment
Share on other sites

Version 3.5.1 works on Sandy and Ivy?

Should. Last days i wrote about problem in the Intel comments - now they tell ist fixed. fast :)  Will try later.

 

(me) Michalak, Andreas said on Jan 15,2018

Mac Version 3.5.0 : Mac reboots if gadget is started on System with  Sandy or Ivy CPU Types.  ix-2..... and ix-3.....  4. gen CPU and above works. 

Patrick Konsor (Intel) said on Jan 16,2018

We've posted Power Gadget for Mac 3.5.1, which resolves the issue with 3.5.0 that caused crashes on 2nd and 3rd generation Core products.
  • Like 2
Link to comment
Share on other sites

no

during some testing I noticed graphical IPG values are influenced (in bad way) by ie KernelXCPM clover flag in my case

also power wattage are influence from cpu SVID parameter on bios (auto/enabled produce different results)

so you have Dram, hmmm... you xmp in the bios enabled?

Link to comment
Share on other sites

enabled

in auto you should have also wattage wrong display

I don't know if 3.50 3.51 IPG release have fixed this

wattage visualization was a problem also in windows if auto was set in cpu svid

 

hmm i have my bios patched.

 

for cpu SVID, is yours set to enable, or auto?


msr 0xE2 patch should not be related to your problem

Link to comment
Share on other sites

this is with cpu SVID in auto

 

enabled

in auto you should have also wattage wrong display

I don't know if 3.50 3.51 IPG release have fixed this

wattage visualization was a problem also in windows if auto was set in cpu svid

 


msr 0xE2 patch should not be related to your problem

post-468967-0-12622700-1516214029_thumb.png

Link to comment
Share on other sites

 Share

×
×
  • Create New...