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

Frame capture fails with "Invalid Parameters"

j81
Beginner
754 Views

Hello,

I am having problems getting a frame capture with the version 2012 R3 (12.3.174307).

The HUD appears fine while the app is running but when I attempt a frame capture it says "Invalid Parameters" and "Capture Failed" underneath that. All of the tests (2x2 Texture, Simple Pixel Shader, etc) seem to work fine. Other applications seem to capture fine for me.

OS: Windows Server 2008 R2 SP1 64-bit

Video Card: Nvidia GeForce GTX 580 (8.17.13.142)

Thank you in advance for any help.

0 Kudos
7 Replies
Neal_Pierman
Valued Contributor I
754 Views
Hello,

Sorry that you're running into this problem -- let's see what we can do to help isolate and resolve the issue.

First of all, I'm assuming that your game runs correctly without Intel GPA, and that the error only occurs when using Intel GPA when capturing a frame.

I believe that what may be happening is that your game is accessing a texture or other resource that is unique to Nvidia -- that is, you are using an extension that is unique to this vendor's graphics card. While Intel GPA attempts to correctly work with the most common extensions, there still may be some that we don't handle correctly.

To help determine if this is the case, first of all right-click on the Intel GPA icon in the notification tray, then copy the "About..." info here, and if Intel GPA created an XML error file please copy that here as well.

Regards,

Neal

0 Kudos
j81
Beginner
754 Views
Hi Neal,

I'm not sure where I would find the XML error file generated. I looked in program files as well as the documents location. I found a monitorlog.txt but all it contained was one line: "2012-08-08 17:53:32 Frame cannot be captured.". If there is another place/file that would be helpful I will try to locate it.

Here is the information from the "About..." section:

Windows Server 2008 R2, 64-bit DEP enabled
Num Processors: 8
Memory: 24548MB
System BIOS: American Megatrends Inc. 1203 (05/24/2012)
Video BIOS: Version 70.10.34.00.84 (02/29/12)

Driver 0:
Device: NVIDIA GeForce GTX 580
Provider: NVIDIA
Date: 5-15-2012
Version: 8.17.13.142
VendorId: 10de
ProductId: 1080
Stepping: a1
No support for GPA Instrumentation

GPA install directory: C:\Program Files\Intel\GPA\2012 R3\
GPA version: 12.3.174307

Current user is in Administrators group: YES

Current GPA 2012 R3 (12.3.174307)

0 Kudos
Neal_Pierman
Valued Contributor I
754 Views
Hello,

1) One thing I do know is that we don't support Windows Server. Would you be able to try this on a non-server version of Windows in order to see if you still get the same error?

2) In parallel, if there is an XML error file created, it would probably be located somewhere in this directory:
C:\Users\\Documents\GPA_2012_R3\
So you probably don't have a error file created; is there any more info displayed on the screen when you get the error message?

3) See if running Intel GPA System Analyzer in the client/server mode (instead of the HUD) gives you different results (even if both the client and target are the same system).

thanks!

Neal
0 Kudos
j81
Beginner
754 Views
Hi Neal,

One thing to note that I just found out is when our application is loading (very simple rendering) it will capture correctly but when the application is past the loading section and doing interesting work, from that point forward it will get the capture failed messages when attempting to capture.

1) I was not aware of that and maybe that explains it. I will try to try down a different OS and try that and get back to you.

2) I double checked and didn't see any error type XML files in there. The info displayed on screen is only "invalid parameters" with "capture failure" below that.

3) I tried running the client/server mode and doing a capture from that but got the same error.

Thank you.
0 Kudos
Neal_Pierman
Valued Contributor I
754 Views
Hello,

Thanks for the quick reply. I'll do some more checking at this end in parallel with this info while you see if you can try a non-server version of the OS.

Regards,

Neal
0 Kudos
j81
Beginner
754 Views
Hi Neal, I finally was able to get this running on a different OS. I tried it on a Windows 7 64bit Service Pack 1 and still no luck (exact same error as before). This machine has the following info from dxdiag: Operating System: Windows 7 Ultimate 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.120503-2030) DirectX Version: DirectX 11 --------------- Display Devices --------------- Card name: NVIDIA GeForce GTX 670 Manufacturer: NVIDIA Chip type: GeForce GTX 670 DAC type: Integrated RAMDAC Device Key: Enum\PCI\VEN_10DE&DEV_1189&SUBSYS_26703842&REV_A1 Display Memory: 4042 MB Dedicated Memory: 1994 MB Shared Memory: 2047 MB Current Mode: 1280 x 1024 (32 bit) (60Hz) Monitor Name: Generic PnP Monitor Monitor Model: DELL 1800FP Monitor Id: DELE001 Native Mode: 1280 x 1024(p) (60.020Hz) Output Type: DVI Driver Name: nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um Driver File Version: 8.17.0013.0142 (English) Driver Version: 8.17.13.142 DDI Version: 11 Driver Model: WDDM 1.1 Driver Attributes: Final Retail Driver Date/Size: 5/15/2012 03:48:00, 18044224 bytes WHQL Logo'd: n/a WHQL Date Stamp: n/a Device Identifier: {D7B71E3E-52C9-11CF-7C5B-7D061FC2C535} Vendor ID: 0x10DE Device ID: 0x1189 SubSys ID: 0x26703842 Revision ID: 0x00A1 Driver Strong Name: oem3.inf:NVIDIA_SetA_Devices.NTamd64.6.1:Section033:8.17.13.142:pci\ven_10de&dev_1189 Rank Of Driver: 00E62001 Video Accel: ModeMPEG2_A ModeMPEG2_C ModeVC1_C ModeWMV9_C Please let me know if you have any more thoughts on things to try. I would really like to continue using this product. Also I'm not sure that I mentioned it before, but this is a DirectX 11 application.
0 Kudos
Neal_Pierman
Valued Contributor I
754 Views
Hello, Sorry to get back to you so late; the new system hasn't notified me of new activity on threads like the old system did (but I understand that this will be fixed soon). Since this is a different system and you are still seeing the same error, this sounds like an issue with this specific application. Is it possible to get a copy of the app to test? In parallel I'll look to see if there are other debugging hints that don't require the application. Regards, Neal
0 Kudos
Reply