[SOLVED] Blender Crashes on program load

[zeffii]

This could be many things, but i'll ignore that and try to get you to use a builder.blender.org version (it will be slightly newer and have some bugfixes over the official 2.73a, it may also have new and exciting bugs...)

• go to builder.blender.org
• obtain the archive suitable for your Operating System (careful 32bit or 64bit)
• create folder (if you have permission) called blender_trunk somewhere on your machine:
  • I have a folder called blender_trunk directly inside C:\ , so C:\blender_trunk
• unpack the file, then go into the folder which will read something like : blender-2.73-8cd106f-win32
• inside this folder you will see a 2.7x folder and a whole bunch of blender files.
• then drag over the content of that entire that folder into C:\blender_trunk, so the content looks like

what happens if you click on that blender.exe ?

If it still crashes, it may be worth trying to launch blender from a command prompt / terminal, to see if there are any error messages.

[MonZop]

With the help of a colleague, we did just that, plus area more attempts. the result is invariably that blender starts and crashes immediately. in the blender report there is no help,either...

[zeffii]

ok.. all is not lost yet!

C:\Users\your_user_name\AppData\Roaming\Blender Foundation\Blender\2.73

delete all content in that folder

[zeffii]

When you start blender from a command prompt, what does it say?

[zeffii]

reading through the bug tracker of blender.org, there's a scenario which appears much like the one you describe. It involves something called a (forgive the caps) PYTHONPATH.

in a console/terminal type: SET or set and windows will spit out a bunch of environmental variables.

If PYTHONPATH is among those, and it points to a 2.6 or 2.7 version of Python, this may indicate the problem and a solution

[MonZop]

Path=C:\ProgramData\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windo ws\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Python27;C:\Pyth on27\Scripts

There is not a specific PYTHONPATH; Python is mentioned in the lines copied above

[zeffii]

hmm, nope that's not it then.. i'll do some more digging

[MonZop]

Following another clue (http://blenderartists.org/forum/showthread.php?359439-Blender-2-73-Crashes-at-Startup) , I updated Windows to the latest ; unfortunately the result is the same: immediate crash of Blender (maybe this is an issue for the BF developers?)

[zeffii]

it's win7 64bit? Do you have admin rights, can you freely install stuff. Uni computers tend to come with certain restrictions, and sometimes background monitoring processes that close programs which are not in some white-list of allowed executables.

i'd be interested to know a few more things, before doing a bug report to BF developers.

• what happens if you start blender from blender-app.exe
• what happens if you start blender from command-line using blender.exe --debug-all (this might spit out a bunch of data but it should stay on screen so you can read the last few lines -- the last lines tend to be informative in these scenarios)

[MonZop]

Yeas, I do have full control on the pc. It is a Windows7, 64 bits (I even tried to install the 32 bit, but it crashes).

With blender-app.exe same result

[MonZop]

with blender.exe --debug-all I get what you said. How do I paste here the copy of command window? However the last lines are: (....) ED_screen_refresh: set screen ghost_event_proc: ghost redraw 1 ghost_event_proc: ghost redraw 1 GL error: enumeratore non valido Writing: C:\Users\Monica\AppData\Local\Temp\blender.crash.txt

The file crash.txt says

# Blender 2.73 (sub 0), Commit date: 2015-01-20 18:16, Hash bbf09d9
bpy.ops.wm.splash()  # Operator

# backtrace

[MonZop]

Ops, sorry about the size: i have no control of it

[MonZop]

The line fomr the black window that says: GL error:enumeratore non valido means invalid enumerator might this be the problem?

[MonZop]

[zeffii]

no, GL_errors are most probably false positives. The --debug-all is like a fishing net which also catches the occasional octopus.

[zeffii]

The first thing the guys in Blender's bug tracker will ask is to try with a latest builder-bot version too. The error you pasted (not the image) shows the last blender.crash.txt was generated by a blender.exe which was created 2015-1-20 (two weeks ago).

At this point you have several 64bit versions of 2.73 on your machine, but the most interesting feedback will be if you do a debug from one of the builder-bot versions. (the zips, like: blender-2.73-280ed32-win64, where 280ed32 is the hash / unique identifier.

literally:

• create a folder on C called blender_trunk
• drag one of the builder-bot builds into that
• start blender.exe from there with the debug flag,
  • it would be C\blender_trunk\blender.exe --debug-all .
  • or something like
  • C:\blender_trunk\blender-2.73-280ed32-win64\blender.exe --debug-all

This is a real pain. The solution should be torturously simple.

[MonZop]

Done:

[MonZop]

repeated without mistake (space between --debug and -all)

[zeffii]

Cool! i'll ask around. At this point it beyond what I know how to fix

[MonZop]

Thanks (in the meanwhile, I have to remove all 2.73, and re-install 2.70, if I want to do some work!)

[zeffii]

you can have multiple blender installations on the same machine, you can set up shortcuts to each of the executables..

[zeffii]

<mont29> zeffii: Please:

• Ensure both your OS and drivers are fully up-to-date.
• Ensure your GPU driver supports at least OpenGL 1.4.
• Ensure you have installed MSVC2013 redistributable package (http://www.microsoft.com/en-us/download/details.aspx?id=40784).
• Try to disable any running antivirus.
• Ensure you have no python executable available in your %path% envvar.
• Try to re-download and re-install Blender.
• Try to start Blender in factory settings (--factory-startup commandline option).
• Try to place this dll next to your blender.exe (software OGL, will be slow, but will show whether this is a driver issue or not).

[MonZop]

I'll need a day only to understand all of this! ;-) But will try OS fully updated, already done...

[MonZop]

BINGO!! I updated the NVIDIA driver. I thought that all updates were done automatically, but clearly this was not the case. Inow have Blebder 273, and can start checking BioBledner Jumps up and down!!

[zeffii]

AWESOME/.

now we ROK ON!

[zeffii]

still, advice is to use the latest builder bot version or 2.73a (I tend to use the builder bot because it fixes tonnes of bugs in-between the major releases)

[mernstackman]

I got the same problem, and after I tried to run from command prompt, I found that it was trying to open a file named quit.blend located on my Temp directory.

C:/Users/My Username/AppData/Local/Temp/quit.blend

I deleted that file and blender launched normally.