/Qparallel switch causing 0xc000007b errors on Windows 7 x64 release

[japrice3]

I have been using Parallel Studio on a project with Vista x64 and just installed Windows 7 Ultimate x64 (release version) as a second operating system on my development machine. I have migrated Visual Studio 2008 SP1, Parallel Studio(ParallelComposer Update 3) and my project to Windows 7. My project successfully builds on Windows 7, but I get error - "This application failed to initialize properly (0xc000007b). Click on OK to terminate the application." with the /Qparallel switch on.

I have built several sample apps just to test the problem, and found that any app compiled on Windows 7 with the /Qparallel switch produces the same error on launch.

I have even moved a couple of apps that were built on Vista x64, and run without error on Vista, to Windows 7 and get the same error on Windows 7. The error is so bad that if I put a break point at the very beginning of the "main" routine to attempt to step to the cause of the problem, I get the error before the debugger can even start.

Turning off /Qparallel allows the app to run without any further error. I have dual Xeon X5482 processors on an Intel D5400XS motherboard. Please advise.

Thank you,

John Price

[Brandon_H_Intel]

Quoting - japrice3

I have been using Parallel Studio on a project with Vista x64 and just installed Windows 7 Ultimate x64 (release version) as a second operating system on my development machine. I have migrated Visual Studio 2008 SP1, Parallel Studio(ParallelComposer Update 3) and my project to Windows 7. My project successfully builds on Windows 7, but I get error - "This application failed to initialize properly (0xc000007b). Click on OK to terminate the application." with the /Qparallel switch on.

I have built several sample apps just to test the problem, and found that any app compiled on Windows 7 with the /Qparallel switch produces the same error on launch.

I have even moved a couple of apps that were built on Vista x64, and run without error on Vista, to Windows 7 and get the same error on Windows 7. The error is so bad that if I put a break point at the very beginning of the "main" routine to attempt to step to the cause of the problem, I get the error before the debugger can even start.

Turning off /Qparallel allows the app to run without any further error. I have dual Xeon X5482 processors on an Intel D5400XS motherboard. Please advise.

Thank you,

John Price

Hi John,

The first thing I would like to know is if you see the same crash using /Qopenmp instead of /Qparallel. I've tried reproducing this problem myself both with a hello, world example and with the default MFC project in release mode, but both run ok with /Qparallel.

You could try using Dependency Walker (a Microsoft utility) to see which dll being loaded is causing the crash.

Also, if you can provide a test case that demonstrates the problem, I'd be happy to take a look.

[japrice3]

Quoting - Brandon Hewitt (Intel)

Hi John,

The first thing I would like to know is if you see the same crash using /Qopenmp instead of /Qparallel. I've tried reproducing this problem myself both with a hello, world example and with the default MFC project in release mode, but both run ok with /Qparallel.

You could try using Dependency Walker (a Microsoft utility) to see which dll being loaded is causing the crash.

Also, if you can provide a test case that demonstrates the problem, I'd be happy to take a look.

Hi Brandon,

After your post explaining that you had no problem with /Qparallel, I tried installing the composer_update3_redist_intel64 file. Everything works fine now. I never had to install the redistributal files on Win XP or Vista, but somehow this was the fix in this case.

I got a hint about this from a Google search on 0xc000007b errors that indicated that they were related to bad drive, directory, or path specifications. The post didn't say "bad path", but close enough. In any case, I'm up and running. Thanks for taking the time to confirm that there was no problem on Windows 7, it did help to solve the problem.

Regards,

John Price