I am working on an application which uses Boost.Python to embed the Python interpreter. This is used to run user-generated "scripts" which interact with the main program.
Unfortunately, one user is reporting runtime error R6034 when he tries to run a script. The main program starts up fine, but I think the problem may be occurring when python27.dll is loaded.
I am using Visual Studio 2005, Python 2.7, and Boost.Python 1.46.1. The problem occurs only on one user's machine. I've dealt with manifest issues before, and managed to resolve them, but in this case I'm at a bit of a loss.
Has anyone else run into a similar problem? Were you able to solve it? How?
(This might be better as a comment than a full answer, but my dusty SO acct. doesn't yet have enough rep for that.) 
Like the OP I was also using an embedded Python 2.7 and some other native assemblies.  
Complicating this nicely was the fact that my application was a med-large .Net solution running on top of 64-Bit IIS Express (VS2013).  
I tried Dependency Walker (great program, but too out of date to help with this), and Process Monitor (ProcMon -- which probably did find some hints, but even though I was using filters the problems were buried in thousands of unrelated operations, better filters may have helped).
However, MANY THANKS to Michael Cooper!  Your steps and Process Explorer (procexp) got me quickly to a solution that had been dodging me all day.  
I can add a couple of notes to Michael's excellent post.  

I ignored (i.e. left unchanged) not just the \WinSxS\... folder but also the \System32\... folder.  

Ultimately I found msvcr90.dll being pulled in from:

C:\Program Files (x86)\Intel\OpenCL SDK\2.0\bin\x64

Going through my Path I found the above and another, similar directory which seemed to contain 32-bit versions.  I removed both of these, restarted and... STILL had the problem.  
So, I followed Michael's steps once more, and, discovered another msvcr90.dll was now being loaded from: 

C:\Program Files\Intel\iCLS Client\

Going through my Path again, I found the above and an (x86) version of this directory as well.  So, I removed both of those, applied the changes, restarted VS2013 and...
No more R6034 Error! 
I can't help but feel frustrated with Intel for doing this.  I had actually found elsewhere online a tip about removing iCLS Client from the Path.  I tried that, but the symptom was the same, so, I thought that wasn't the problem.  Sadly iCLS Client and OpenCL SDK were tag-teaming my iisexpress.  If I was lucky enough to remove either one, the R6034 error remained.  I had to excise both of them in order to cure the problem.  
Thanks again to Michael Cooper and everyone else for your help!
Runtime error R6034 in embedded Python application