Software Tuning, Performance Optimization & Platform Monitoring
Discussion regarding monitoring and software tuning methodologies, Performance Monitoring Unit (PMU) of Intel microprocessors, and platform updating.

Can't run the Intel Power Gadget

John_D_8
Débutant
8 702 Visites

I'm trying to run the Intel Power Gadget on a Win 8.1 x64 system with a Core i7-720QM.  The program and the MS Visual C++ 2010 redistributable library appear to install OK, but the tool will not start.  I try launching it, and nothing happens.  I attached windbg to the executable, but did not learn anything.  I also investigated it with Process Monitor and Dependency Walker, but couldn't get to the bottom of it.

The same utility runs fine on a different computer.  Curiously, I might have not installed the MSVC 2012 redistributable on that PC.  I don't see it listed in Programs and Features.  The power gadget runs just fine though.

Any ideas?

 

0 Compliments
1 Solution
Seung-Woo_K_Intel
8 702 Visites

I should put up a dialog box when it's not supported rather than quietly quitting. Another idea for the next release... :)

Voir la solution dans l'envoi d'origine

0 Compliments
11 Réponses
Bernard
Précieux contributeur I
8 702 Visites

Can you post screenshot of Dependency Walker and screenshot of windbg output? In your case Power Gadget can exhibit so called Silent Process Termination.

0 Compliments
John_D_8
Débutant
8 702 Visites

Attached are 4 files.  Two are screenshots from Dependency Walker and windbg, and two are text outputs from those utilities.

Thanks for thinking about it.

 

0 Compliments
Seung-Woo_K_Intel
8 702 Visites

I am the author of Intel Power Gadget. Can you tell me your machine's spec? Please run CPUZ utility and send me the report.

0 Compliments
John_D_8
Débutant
8 702 Visites

I also posted this on StackOverflow.  A user kindly analyzed the executable and came up with this conclusion:

i took a look at the offending exe it seems there is an integer division by zero exception in EnergyLib64.dll->Initialization Routine called by initterm (LdrpRunInitializeRoutine) when it checks for some processor specific functionality using cpuid the result of cpuid after some calculations is shifted right by 20 shr eax,20 which makes eax 0 and the divisor ebp is also 0 so div eax, ebp results in a divide by zero exception which leads to immediate termination. via msvcrt!exit at 0x......9e78

So, it seems that there's a bug which only affects systems with certain CPUs.

Can someone at Intel report this to the utility authors?  The authors appear to be: Seung-Woo Kim, Karthik Krishnan, Vardhan Dugar, Joseph Jin-Sung, and Jun De Vega.

Thanks.

 

0 Compliments
Seung-Woo_K_Intel
8 702 Visites

We are still using VS 2010 for backward compatibility, so the run time distributable that comes with the package should be enough. There must be something else going on.

 

0 Compliments
John_D_8
Débutant
8 702 Visites

Seung-Woo Kim (Intel) wrote:

I am the author of Intel Power Gadget. Can you tell me your machine's spec? Please run CPUZ utility and send me the report.

Attached is a screenshot from CPUZ.  Thanks for investigating.

 

0 Compliments
Seung-Woo_K_Intel
8 702 Visites

That's why I asked for CPU-Z report to get the exact CPU specification, which comes from cpuid :)

0 Compliments
John_D_8
Débutant
8 702 Visites

Seung-Woo Kim (Intel) wrote:

That's why I asked for CPU-Z report to get the exact CPU specification, which comes from cpuid :)

Attached is the full CPU-Z report as a text file in case you need more info than the screenshot I posted earlier.

 

0 Compliments
Seung-Woo_K_Intel
8 702 Visites

Yep, it's Clarksfield. Intel Power Gadget supports SandyBridge and later.

0 Compliments
Seung-Woo_K_Intel
8 703 Visites

I should put up a dialog box when it's not supported rather than quietly quitting. Another idea for the next release... :)

0 Compliments
John_D_8
Débutant
8 702 Visites

Seung-Woo Kim (Intel) wrote:

Yep, it's Clarksfield. Intel Power Gadget supports SandyBridge and later.

OK, thanks.  I read the System Requirements too quickly and thought that all Core CPUs were supported.

 

0 Compliments
Répondre