Page MenuHome

runtime error R6034 on start
Closed, InvalidPublic


--- Operating System, Graphics card ---
os: windows 7 64 bit

--- Blender version with error, and version that worked ---
error: official versions (2.67 32bit & 64bit)
worked: self build since beta

--- Short description of error ---
when i download the official blender releases (zipped) and start them i get a runtime error R6034. blender still runs after i klick the error away.
this is nothing new, ive seen it on several systems and i think ive already seen this as far back as 2.49
i attached a screenshot of the error message that pops up.

--- Steps for others to reproduce the error (preferably based on attached .blend file) ---
1. download zip version of blender
2. unpack the zip
3. run the blender.exe
4. get the runtime error



Event Timeline

Can you think of anything particular on this Windows installation that might be influencing this? Some particular installed visual studio runtimes, service packs, .. ? Do the binaries give the same issue?

Obviously this is not happening on many installations or we would have had this reported already, and this is the first I've heard of this problem.

i actually cant think of a reason, my system is up to date with service packs and i have visual studio 2008 and 2010 professional edition or team edition installed which should have all the runtimes.
what i remember is that its a dll that i needed to put into the blender (2.49) folder itself for it to work.

i found a link where they aparently solved it for some other software
looks like its some PATH problem, as you can see in the attached screenshot, there are quite a few of these dll's on my system and the search was not finished. so no reason for blender not to find it.
the question for me is if the problem is on my (the user) side or on blenders side?

Could be some conflict between msvc redistributable installed into system and bundled into blender's archive. Can you please try removing this files from blender's folder and see whether it helps or not: msvcm90.dll msvcp90.dll, msvcr90.dll vcomp90.dll Microsoft.VC90.CRT.manifest Microsoft.VC90.OpenMP.manifest

ok i tried what you suggested.

the vcomp90.dll needs to be there, otherwise i get an other error, something about software not installed or something like that.

and i only get the runtime error when the "msvcr90.dll" is in the blender folder. it works fine with the other files.

This is likely some conflict between runtime libraries you've got in your system and bundled to blender's installation. Didn't happen for blender before and there's no useful information in the internet about what could be suggested to be tried.

Unfortunately, this is that kind of bugs which are really tricky to trobleshoot without having access to the buggy setup. Closing for until some other developer comes across with this same issue and would be able to fix. For now you at least do have workaround to make blender work :)

Hi !

I'm updating this issue because I've found the same problem but with a really easy way to reproduce it :
Open Blender and type the following in the python console :

import uuid

And the error will show up.

Hope it helps !

i get this again with the 2.68 RC so mazbe zou want to reopen this issue since its not solved?

Seems you need to remove msvcr90.dll from the installation folder.
I'm not sure whether it's fixable from blender side, it's more like something specific on your particular configuration. And so far no one was able to reproduce this exact issue.

the interesting thing is that i have it on at least 3 different systems... and i doubt im the only one with this im probably just the only one reporting it.

i just wanted to let you know that we tracked down the issue and it seems it is caused by a in-house addon. i will continue to investigate and report back if i know why the addon causes this.

finally got some time to track down this issue and it was caused by a
import uuid seems to be a legit python module so no idea why this happens.

I have the same issue with blender-2.70a-windows64

import uuid in the Python Console causes R6034 Runtime Error