Intel® Graphics Performance Analyzers (Intel® GPA)
Improve your game's performance by quickly specifying problem areas
488 Discussions

Intel GPA Monitor crashes on start using Nvidia graphics (GPA 2013 R2/R3)

Renaud_B_
Beginner
2,586 Views

Hi,

The latest version of Intel GPA (13.2_release_20083) crashes when starting the Monitor app. Older versions worked fine on my setup but I'm unsure whether it's an issue with newer graphics drivers, or me updating to the latest GPA version.
I can see the icon appearing in the taskbar with its notification pop-up with the IP address it's monitoring, and when I hover the icon it disappears. The application itself only stays alive for a second or two, then the process kills itself.

I've attached my DxDiag information, I'd attach a crash log but I'm not sure where that would be. The Windows Event Viewer does not report any application crash.

Let me know if I can provide more details!

Thanks,
Renaud 

0 Kudos
12 Replies
Renaud_B_
Beginner
2,586 Views

Installing GeForce Experience 1.6 with my 326.41 nVidia drivers fixed the crash!
I initially did not install it because it interferes with our asset compilation pipeline, but looks like GPA needs it for some reason?

0 Kudos
Renaud_B_
Beginner
2,586 Views

...and with the latest GeForce Exprience which is 1.6.1, it crashes on start again.

0 Kudos
EDUARDO_R___Intel_
2,586 Views

Hello Renaud,

Thank you for reporting the issue. We'll investigate this immediatly. I'll keep you posted as we get more details.

-Eddy

0 Kudos
STANISLAV_V_Intel
2,586 Views

Hello Renaud,

We investigated the issue and there is some collision between GPA and some NVidia process in the register entries.
I would assume that it's GeForce Experience. Could you try to uninstall it and check if it helps?

0 Kudos
Tomas_B_
Beginner
2,586 Views

Hello,

I have the same problem on MacBook Pro Retina and Win 7 64bit. Uninstallation didn't help. Killing a process called nvxdsync.exe, described as "NVIDIA User Experience Driver Component" didn't help either. Then I fully reinstalled the driver 326.41 together with the GeForce Experience 1.6 and prevented the upgrade to 1.61 so the GPA Monitor works fine again.

Regards,
Tomas

0 Kudos
Renaud_B_
Beginner
2,586 Views

Hi Stanislav,

Uninstalling GeForce Experience does work, as does using GeForce Experience 1.6 exclusively. But I'd rather be able to use GeForce Experience, in fact 1.6.1 is required for my work. Can we expect a proper fix in Intel GPA itself?

0 Kudos
STANISLAV_V_Intel
2,586 Views

Hi,
In fact, we already fixed the issue. This fix will be a part of 2013 R4 release which will be available in aproximately 3 months.
-Stas 

0 Kudos
STANISLAV_V_Intel
2,586 Views

The following thing should help you:
Please modify the following values in the register:
    LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Windows\AppInit_DLLs
    LOCAL_MACHINE\Software\Wow6432Node\Microsoft\Windows NT\CurrentVersion\Windows\AppInit_DLLs
by adding some letter or random string to make it non-empty. For example add 'A'. 

 

0 Kudos
davidlee80
Beginner
2,586 Views

The latest version of Intel GPA (13.3_release_207307)  has the same issue with the nv GeForce Experience 1.6.1, but with Stanislav's solution(modify the register), my gpa monitor works fine again, my os is win 8 pro x64, and  GeForce Experience 1.6.1.  nv gtx460 and the driver is 320.49.

Thank you

0 Kudos
jhp_b_
Beginner
2,586 Views

Installing the Analyzer 2013 R3 tools 

It gives an error on installation: "Theinstaller failed to enable GPA autorun."

  • Machine was rebooted before install
  • Installation was run with administrator rights.

When trying to run the monitor, it will crash (almost) immediately.

  • Disabled firewall - did not fix the issuye
  • Uninstalled NVidia driver experience 1.7.1 - did not fix the issue 
  • Changing the two registry-key, as described above, fixes the issue

System: NVidia driver: 331.64 with a GTX 570

 

 

0 Kudos
Neal_Pierman
Valued Contributor I
2,586 Views

Hello,

Thanks for letting us know that the registry key workaround fixes the issue.

Regards,

Neal

0 Kudos
Reply