topic Loading a capture in Frame Analyzer: BEGIN Event was not create in Intel® Graphics Performance Analyzers (Intel® GPA)

GPA 2012: Frame Analyzer crashes when loading frame capture file

Guay__Jean-Sébastien — Wed, 29 Feb 2012 18:28:58 GMT

Hello,

Intel GPA 4.3.160275
nVidia GTX 560ti
Intel Xeon W3550 (3.06GHz)
12GB RAM

I captured a frame in a DX11 application and am trying to load it in Frame Analyzer. The load seems to go fine, I start to see the timeline and job tree and can select a job, but then it starts slowing down the entire machine a lot, and eventually pops up a messagebox saying "BEGIN Event was not created." . Click ok on that and another one pops up saying "An unexpected error occurred." and Frame Analyzer crashes.

A colleague of mine has GPA 4.0.something, and can capture the same application and open it in Frame Analyzer fine.

Capturing a frame from DX SDK samples, even DX11 ones, doesn't cause this problem. Capturing the DX9 build of this same application also doesn't cause the problem. We use Compute Shader, however if that was the problem the DX SDK samples that use Compute Shader would also cause the same problem, and they don't.

I tried uninstalling and reinstalling 4.3.160275 but I still get the same results.

This is the XML report that it saves:

Intel GPA Error Report - Please report this error at http://www.intel.com/software/gpa

</p><p>An unexpected error occurred.</p><p>

BEGIN Event was not created.

magic_number: 1095780169

size_of_header: 296

file_revision: 3

entry_count: 27166

target_id: 00000000-0000-0000-0000-000000000000

file_id: c2d7b111-e6b3-443f-9aeb-9f2b79619283

frame: 1007

vendor_id: 4318

device_id: 4608

revision_id: 161

api_version: DX11

driver_version: 8.17.12.9573

sdk_version: 43

process_name: app_d3d11.exe

offset_to_index: 358992929

api_payload_version: 6

offset_to_ShortEntries: 356457939

size_of_ShortEntries: 2534990

number_of_ShortEntries: 6716

Windows 7, 64-bit DEP enabled

Num Processors: 8

Memory: 12279MB

System BIOS: LENOVO 60KT43AUS (04/08/2011)

Video BIOS: Version 70.24.2E.00.60 (09/26/11)

Driver 0:

Device: NVIDIA GeForce GTX 560 Ti

Provider: NVIDIA

Date: 2-9-2012

Version: 8.17.12.9573

VendorId: 10de

ProductId: 1200

Stepping: a1

No support for GPA Instrumentation

GPA install directory: C:\\Program Files\\Intel\\GPA\\4.3\\

GPA version: 4.3.160275

Current user is in Administrators group: YES

Windows 7, 64-bit DEP enabled

Num Processors: 8

Memory: 12279MB

System BIOS: LENOVO 60KT43AUS (04/08/2011)

Video BIOS: Version 70.24.2E.00.60 (09/26/11)

Driver 0:

Device: NVIDIA GeForce GTX 560 Ti

Provider: NVIDIA

Date: 2-9-2012

Version: 8.17.12.9573

VendorId: 10de

ProductId: 1200

Stepping: a1

No support for GPA Instrumentation

GPA install directory: C:\\Program Files\\Intel\\GPA\\4.3\\

GPA version: 4.3.160275

Current user is in Administrators group: YES

BEGIN Event was not created.

What can I do to fix this? Thanks in advance.

Loading a capture in Frame Analyzer: BEGIN Event was not create

Neal_Pierman — Wed, 29 Feb 2012 22:06:16 GMT

Hello,

Thanks for letting us know about the issue that you have found.

As you indicated, it sounds like this issue is isolated to the specific game/application that you are analyzing, since other DX11 apps don't have this issue (including those with the compute shader).

By the way, you mentioned that a colleague is able to run ok with the same app with another version of Intel GPA -- do you know what graphics device she or he is using? I'm trying to determine whether this is due to a specific version of Intel GPA (and it could be due to the file creation or file playback), or whether it's partly due to the graphics device that you are using.

Also, having access to a copy of the frame capture file would help, but your answer to a couple of the other questions might help us get more info up-front before needing the file.

Regards,

Neal

Loading a capture in Frame Analyzer: BEGIN Event was not create

Guay__Jean-Sébastien — Thu, 01 Mar 2012 19:34:47 GMT

Hello Neal, thanks for your reply.

I agree with your initial analysis. However this game runs clean with DX11 break on error enabled, so without better info about what is causing the problem it's hard for me to find what specifically could be wrong with it. The error message GPA gives is not exactly descriptive. And presumably GPA should be robust enough to be able to capture even games that misbehave, given that it's a debugging tool and profiler for graphics applications... :-)

For reference, I can capture and examine the capture just fine in nVidia NSight. Sure they're not the same programs, but it shows that our game shouldn't be doing anything _grossly_ wrong...

I just tried with GPA 4.0 and the result is different - the capture loads and Frame Analyzer doesn't crash, but it never shows the render target previews or textures.

My colleague is using a GTX460. But I am using the most recent nvidia drivers (295.73) while he is using older ones (285 series I think).

As for the frame capture, I doubt I can send one to you. I can do some tests here if you have any ideas but I don't think it can do more.

Thanks.

Loading a capture in Frame Analyzer: BEGIN Event was not create

Neal_Pierman — Thu, 01 Mar 2012 19:48:40 GMT

Hello,

Thanks for the additional information. The part about your app running "clean" (with break on error enabled) is important, as this eliminates a key item that we've seen before (and yes, we are working to make the program more robust).

I realize that it's probably not easy for us to access your frame capture file.

Can you wait a couple of days? I may have another version of GPA that I can provide you for testing to see if this fixes the problem.

Regards,

Neal

Loading a capture in Frame Analyzer: BEGIN Event was not create

Guay__Jean-Sébastien — Fri, 02 Mar 2012 13:54:25 GMT

Hello Neal,

I can test a new version whenever it becomes available, sure.

J-S

Loading a capture in Frame Analyzer: BEGIN Event was not create

Neal_Pierman — Fri, 02 Mar 2012 17:23:21 GMT

Hello,

I've got a new version for you to check out -- goto the Intel GPA Home Page, then under the "downloads" section look for "2012 R1".

Please let me know whether this version helps.

Regards,

Neal

Loading a capture in Frame Analyzer: BEGIN Event was not create

Guay__Jean-Sébastien — Tue, 06 Mar 2012 19:38:45 GMT

Hello Neal,

Same result: "BEGIN Event was not created."

Sorry...

Loading a capture in Frame Analyzer: BEGIN Event was not create

Neal_Pierman — Tue, 06 Mar 2012 21:56:53 GMT

Hello,

I'm checking with the dev team for some more suggestions on how to proceed with tracking down the issue.

In the meantime, you mentioned that a colleague of yours is able to run your app ok on Intel GPA 4.0 (including both capturing the file and viewing it in Intel GPA Frame Analyzer). I believe that you said that when you run your app on your machine you can capture the file ok but not view it in Intel GPA Frame Analyzer (issues with textures and render target previews on 4.0, but a crash on 4.3 or 12.1).

Do you know whether your colleague has run your app OK on the 4.3 or 12.1 versions of Intel GPA? I guess I'm wondering whether the issue is somehow related to your specific device and/or driver version.

Regards,

Neal

Loading a capture in Frame Analyzer: BEGIN Event was not create

s33m3 — Fri, 16 Mar 2012 10:02:57 GMT

I have the same error, in my managed project (I'm using SharpDX DirectX11 wrapper).

I managed to track down "THE" line that make this error occurs for me :

context.CopyResource(_engine.BackBufferTex, _solidBackBuffer);

Where I simply do a copy of the BackBuffer texture resource into another similar texture.

Without this line, the error is not raised.

Don't know If it can help.

Regard.

Loading a capture in Frame Analyzer: BEGIN Event was not create

Neal_Pierman — Fri, 16 Mar 2012 14:23:23 GMT

Hello,

Thanks for the info.

Could you please include your configuration information by right-clicking the Intel GPA Monitor icon in the notification tray and selecting "About..."?

Also, are you running with "break on error"? If so, could you run without this option and let us know if you see a difference?

thanks!

Neal

Loading a capture in Frame Analyzer: BEGIN Event was not create

Neal_Pierman — Fri, 16 Mar 2012 15:23:40 GMT

Hello,

We've not been able to reproduce this issue internally... a frame capture file from you would be very helpful!

Regards,

Neal

Loading a capture in Frame Analyzer: BEGIN Event was not create

s33m3 — Fri, 16 Mar 2012 18:36:52 GMT

For sure, here is the Info about my system first (this machine is really low end one) :

Windows 7, 32-bit DEP enabled

Num Processors: 2

Memory: 3583MB

System BIOS: American Megatrends Inc. 0401 (07/14/2009)

Video BIOS: Version 62.98.42.00.00 (02/04/09)

(Display driver information not available)

GPA install directory: C:\Program Files\Intel\GPA\2012 R1\

GPA version: 12.1.166792

Current user is in Administrators group: YES

Current GPA 2012 R1 (12.1.166792)

Windows 7, 32-bit DEP enabledNum Processors: 2Memory: 3583MBSystem BIOS: American Megatrends Inc. 0401 (07/14/2009)Video BIOS: Version 62.98.42.00.00 (02/04/09)(Display driver information not available)GPA install directory: C:\Program Files\Intel\GPA\2012 R1\GPA version: 12.1.166792Current user is in Administrators group: YESCurrent GPA 2012 R1 (12.1.166792)

I have uploaded the frame causing probleme here :http://www.sendspace.com/file/z2rcz5

Regards.

Loading a capture in Frame Analyzer: BEGIN Event was not create

Neal_Pierman — Fri, 16 Mar 2012 19:45:11 GMT

Hello,

Thanks for the file... I've copied it for analysis by the development team. I'll let you know as soon as I hear back from them.

Regards,

Neal

Loading a capture in Frame Analyzer: BEGIN Event was not create

s33m3 — Fri, 16 Mar 2012 20:03:38 GMT

Tx you. One remark, maybe important. I tried to replay this from another computer, without any problem.

The "big" difference I see, is that the problem is occuring from a Dual-monitor configuration.

Will try on another dual screen configuratin, and keep you informed.

Loading a capture in Frame Analyzer: BEGIN Event was not create

Neal_Pierman — Tue, 20 Mar 2012 21:16:23 GMT

Hello,

The Development Team has been able to duplicate this problem and provide a workaround.

The error seems to occur only when you are using the D3D control panel to enable "break settings" for errors in your code. If you disable this feature, Intel GPA should properly create, read, and process the frame capture file.

Therefore, as a quick fix please disable any "break" settings, and let me know if this workaround resolves your issue.

Regards,

Neal

Loading a capture in Frame Analyzer: BEGIN Event was not create

s33m3 — Wed, 21 Mar 2012 16:31:12 GMT

Hello,

I'm sorry to tell you that the D3D control panel, "Break settings" is empty. And that this error is still occuring when the DirectX device is created without "Debug flag".

It clearly seems to be linked to computer, as the same program can be debugged easily on another hardware.

Regards.

Loading a capture in Frame Analyzer: BEGIN Event was not create

Neal_Pierman — Tue, 27 Mar 2012 19:35:21 GMT

Hello,

It appears that we may have multiple issues here.

On one of our internal systems we did see the same error with the capture file you provided, and it ended up being due to the D3D control panel settings. It's been fixed internally, and is planned for the next release.

We also saw that this bug could occur when the NVIDIA driver is reloaded by Windows 7* -- this occured when using trivial shaders with some versions of the NVIDIA driver, and only on some h/w configurations, and we are actively looking at this situation as well. This may be why the workaround we suggested didn't work (that is, don't use "break on error").

You also mentioned that you were going to test on another dual-monitor configuration -- did this configuration work ok?

And one final question -- how critical is a fix for this bug to you? Is the workaround of using another system sufficient for you, or is this seriously affecting your analysis/optimization tasks?

Also,

Loading a capture in Frame Analyzer: BEGIN Event was not create

Neal_Pierman — Thu, 29 Mar 2012 14:51:38 GMT

Hello,

As I mentioned the development team has been doing additional testing of this issue, and we have found what we believe is the root cause of this problem.

Our testing shows that the latest NVidia driver (296.10) causes memory leaks if a D3D application uses UpdateSubresource D3D call in some situations. The Intel GPA playback library uses this call, and thats why we see crash in playback when opening this frame in Intel GPA Frame Analyzer.

We do not see this problem with the NVidia 266.58 driver -- this seems to work ok and do not have the problem with Intel GPA Frame Analyzer.

As we create a workaround for this in our code, would you be able to test with the 266 driver, and see if the problem still occurs? Your testing will help us verify that we are on the right track in getting Intel GPA to work correctly.

thanks!

Neal

I know this is an old post,

Jason_K_3 — Tue, 02 Jun 2015 00:21:30 GMT

I know this is an old post, but I'm getting this issue with Graphics Frame Analyzer for DirectX 15.1.244099. When I use the ID3D11DeviceContext::CopyResource and Map/Unmap (to access the subresource data) methods, I get the unexpected error. If I comment them out then I don't have a problem. Additionally, I'm copying from a render target with the D3D11_RESOURCE_MISC_GDI_COMPATIBLE flag. My NVidia driver is 352.86.

Please advise.

Hi Jason,

Seth_S_Intel — Tue, 02 Jun 2015 16:27:35 GMT

Hi Jason,

Sorry that you are having this issue with Frame Analyzer.

When your Frame Analyzer crashes, does it give you the option to save the error report? Additionally, if you could post the copied output from "right click task bar GPA Monitor -> about -> copy", it will better help solve this problem.

Seth