I have been using 2.55 for a couple of months. I am new to Blender but not new to 3D. I had no problems with 2.55 but thought I should upgrade to 2.56a last night. The first download was a little flaky, so I deleted and downloaded again. Everything worked fine on the second try last night; I worked for about an hour. When I try to load 2.56 today, I see no lines of code in the python window followed by a windows error that says “blender.exe stopped working.” I have deleted and redownloaded. I have tried to run from the unzipped folder and have installed. Can’t get 2.56 to work. Blender 2.55 continues to load by clicking on the exe.
Using a 6-month old HP laptop; Windows 7; 64 bit; NVidia Quado vid card.
I have read the suggestion to update the video driver. I went to the NVidia site and got the newest driver, but still no luck. Lightwave, 3D Studio Max, and Blender 2.55 run fine; no openGL issues.
Problem signature:
Problem Event Name: BEX64
Application Name: blender.exe
Application Version: 0.0.0.0
Application Timestamp: 4d239388
Fault Module Name: StackHash_b1f5
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 00000000
Exception Offset: 0000000080009a20
Exception Code: c0000005
Exception Data: 0000000000000008
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 1033
Additional Information 1: b1f5
Additional Information 2: b1f5e70a508effb096f057c68f67e59e
Additional Information 3: 1df3
Additional Information 4: 1df328be98d90083569e1a2ad52e7ea3
How are you determining that it’s a Python issue? Is it happening when you try a specific add-on? Are you running any special scripts? Do you change any of the User Preferences?
As a test, try finding and deleting your startup.blend… then try to run Blender and see what happens.
When I start Blender 2.55, the command window opens and I get code that says: “found blundled python” along with the path to the python directory inside the blender directory. When I start Blender 2.56, the command window opens but no code appears. The Blender window opens but it is just a big gray rectangle. A windows message opens that says “blender.exe has stopped working.” This is why I think it is a python issue.
When it did work, I don’t rememeber adding any special add-ons or running any special scripts. I think the only change I made in the User Prefs was to add a .x export.
I deleted the startup.blend file that was in my user/appdata directory but Blender 2.56 still refuses to open.
And did you download Blender 2.56a beta from blender.org or are you using a build from graphicall.org? Did you download the version with the installer or the version in the zip file? And, are you sure you downloaded the 64-bit version for Windows and not the 32-bit version?
(my apologies for the barrage of stupid questions, but it’s best to get the low-hanging fruit out of the way before determining if it’s a bigger problem)
I download from blender.org. I am sure I pulled down the 64-bit version. I tried the zip file first and it worked fine. When it stopped working the next day, I dowloaded the installer to see if that would work. It wouldn’t open either. I decided to delete the zip folder and am currently trying to open the one that installed in my “programs” directory. Should I try to download from graphicall.org?
This is very unusual… Is there anything that you did on your computer (non-Blender-related) between when Blender worked and when it didn’t? You may want to try getting 2.55 again and seeing if that still works on your machine. If it still works, then we know it’s something that happened between 2.55 and 2.56a. If it, too, doesn’t work, then perhaps the issue isn’t directly related to Blender at all.
No, I didn’t do anything to the machine between the time when 2.56a worked and the next day when it quit working. Blender 2.55 is still on the machine and is working fine. It is off the zip folder; not installed. I am not having this issue on my desktop machine; only my laptop. Perhaps 2.56a doesn’t like the video card on the laptop - NVidia Quadro FX 880M.
Alrighty… in that case, let’s try using a recent build from graphicall.org. This is starting to sound a bit like a graphics bug, but there’ve been so many commits since 2.55 that I can’t recall off the top of my head which commit may have introduced this problem (or if a fix was put in). There’s a chance that the problem is solved in a more recent build. If it isn’t, then it may be time to submit a bug report.
I went to graphicall.org and downloaded “Blender 2.56 Trunk SVN r35583 Windows x64.” Had exactly the same problem. Python does not open. Windows says its a StackHash error.
It keeps getting stranger. I clicked on the shortcut for Blender 2.56a and it started working again. And the two I downloaded from graphicsall.com now work. Hmmm???
Well, Blender 2.56a worked for about an hour. When I closed and reopened, it crashed again. I really have no idea how to read a crash report, but here it is:
Version=1
EventType=BEX64
EventTime=129452395687604681
ReportType=2
Consent=1
ReportIdentifier=d9ed7abf-5437-11e0-bdd8-70f395a114f9
IntegratorReportIdentifier=d9ed7abe-5437-11e0-bdd8-70f395a114f9
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=blender.exe
Sig[1].Name=Application Version
Sig[1].Value=0.0.0.0
Sig[2].Name=Application Timestamp
Sig[2].Value=4d239388
Sig[3].Name=Fault Module Name
Sig[3].Value=StackHash_a313
Sig[4].Name=Fault Module Version
Sig[4].Value=0.0.0.0
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=00000000
Sig[6].Name=Exception Offset
Sig[6].Value=0000000080009a20
Sig[7].Name=Exception Code
Sig[7].Value=c0000005
Sig[8].Name=Exception Data
Sig[8].Value=0000000000000008
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7600.2.0.0.256.48
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=a313
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=a313a129d8b99afd3a61afb3e4716dd6
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=6d41
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=6d411a19412e8069d77f92a6e36d92e8
UI[2]=C:\Program Files (x86)\blender-2.56a-beta-windows64\blender.exe
UI[3]=blender.exe has stopped working
UI[4]=Windows can check online for a solution to the problem.
UI[5]=Check online for a solution and close the program
UI[6]=Check online for a solution later and close the program
UI[7]=Close the program
LoadedModule[0]=C:\Program Files (x86)\blender-2.56a-beta-
windows64\blender.exe
LoadedModule[1]=C:\windows\SYSTEM32
tdll.dll
LoadedModule[2]=C:\windows\system32\kernel32.dll
LoadedModule[3]=C:\windows\system32\KERNELBASE.dll
LoadedModule[4]=C:\Program Files (x86)\blender-2.56a-beta-
windows64\python31.dll
LoadedModule[5]=C:\windows\system32\USER32.dll
LoadedModule[6]=C:\windows\system32\GDI32.dll
LoadedModule[7]=C:\windows\system32\LPK.dll
LoadedModule[8]=C:\windows\system32\USP10.dll
LoadedModule[9]=C:\windows\system32\msvcrt.dll
LoadedModule[10]=C:\windows\system32\ADVAPI32.dll
LoadedModule[11]=C:\windows\SYSTEM32\sechost.dll
LoadedModule[12]=C:\windows\system32\RPCRT4.dll
LoadedModule[13]=C:\windows\system32\SHELL32.dll
LoadedModule[14]=C:\windows\system32\SHLWAPI.dll
LoadedModule[15]=C:\windows\WinSxS
\amd64_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.4926_none_08e1a05ba83
fe554\MSVCR90.dll
LoadedModule[16]=C:\Program Files (x86)\blender-2.56a-beta-
windows64\wrap_oal.dll
LoadedModule[17]=C:\windows\system32\WINMM.dll
LoadedModule[18]=C:\windows\system32\ole32.dll
LoadedModule[19]=C:\Program Files (x86)\blender-2.56a-beta-
windows64\VCOMP90.DLL
LoadedModule[20]=C:\Program Files (x86)\blender-2.56a-beta-
windows64\zlib.dll
LoadedModule[21]=C:\Program Files (x86)\blender-2.56a-beta-
windows64\avformat-52.dll
LoadedModule[22]=C:\Program Files (x86)\blender-2.56a-beta-
windows64\avcodec-52.dll
LoadedModule[23]=C:\Program Files (x86)\blender-2.56a-beta-
windows64\avutil-50.dll
LoadedModule[24]=C:\windows\system32\AVIFIL32.dll
LoadedModule[25]=C:\windows\system32\MSACM32.dll
LoadedModule[26]=C:\windows\system32\MSVFW32.dll
LoadedModule[27]=C:\windows\WinSxS\amd64_microsoft.windows.common-
controls_6595b64144ccf1df_5.82.7600.16661_none_a44e1fc257f685f6\COMCTL32.d
ll
LoadedModule[28]=C:\windows\system32\WS2_32.dll
LoadedModule[29]=C:\windows\system32\NSI.dll
LoadedModule[30]=C:\Program Files (x86)\blender-2.56a-beta-
windows64\avdevice-52.dll
LoadedModule[31]=C:\windows\system32\AVICAP32.dll
LoadedModule[32]=C:\windows\system32\VERSION.dll
LoadedModule[33]=C:\Program Files (x86)\blender-2.56a-beta-
windows64\swscale-0.dll
LoadedModule[34]=C:\Program Files (x86)\blender-2.56a-beta-
windows64\libsndfile-1.dll
LoadedModule[35]=C:\windows\system32\OPENGL32.dll
LoadedModule[36]=C:\windows\system32\GLU32.dll
LoadedModule[37]=C:\windows\system32\DDRAW.dll
LoadedModule[38]=C:\windows\system32\DCIMAN32.dll
LoadedModule[39]=C:\windows\system32\SETUPAPI.dll
LoadedModule[40]=C:\windows\system32\CFGMGR32.dll
LoadedModule[41]=C:\windows\system32\OLEAUT32.dll
LoadedModule[42]=C:\windows\system32\DEVOBJ.dll
LoadedModule[43]=C:\windows\system32\dwmapi.dll
LoadedModule[44]=C:\windows\system32\SHFOLDER.dll
LoadedModule[45]=C:\windows\system32\IMM32.DLL
LoadedModule[46]=C:\windows\system32\MSCTF.dll
LoadedModule[47]=C:\windows\system32\uxtheme.dll
LoadedModule[48]=C:\windows\system32\CRYPTBASE.dll
LoadedModule[49]=C:\windows\system32\profapi.dll
LoadedModule[50]=C:\windows\system32
voglv64.DLL
LoadedModule[51]=C:\windows\system32\WINTRUST.dll
LoadedModule[52]=C:\windows\system32\CRYPT32.dll
LoadedModule[53]=C:\windows\system32\MSASN1.dll
LoadedModule[54]=C:\Program Files\WIDCOMM\Bluetooth Software\btmmhook.dll
LoadedModule[55]=C:\windows\system32\PSAPI.DLL
LoadedModule[56]=C:\windows\system32\CLBCatQ.DLL
LoadedModule[57]=C:\windows\System32\dsound.dll
LoadedModule[58]=C:\windows\System32\POWRPROF.dll
LoadedModule[59]=C:\windows\System32\MMDevApi.dll
LoadedModule[60]=C:\windows\System32\PROPSYS.dll
LoadedModule[61]=C:\windows\system32\AUDIOSES.DLL
LoadedModule[62]=C:\windows\system32\wdmaud.drv
LoadedModule[63]=C:\windows\system32\ksuser.dll
LoadedModule[64]=C:\windows\system32\AVRT.dll
LoadedModule[65]=C:\windows\system32\msacm32.drv
LoadedModule[66]=C:\windows\system32\midimap.dll
FriendlyEventName=Stopped working
ConsentKey=BEX64
AppName=blender.exe
AppPath=C:\Program Files (x86)\blender-2.56a-beta-windows64\blender.exe
How are you quitting Blender? Are you using the X button in the window border or are you using Ctrl+Q or File->Quit?
The next time you run Blender and it works, it may be helpful to generate a system-info.txt to get the particulars on your machine. You can do that by going to Help->System Info from within Blender. This creates a text file called system-info.txt which you can see from Blender’s Text Editor. Save that file and upload it to a site like pasteall.org and share the link here.
When I quit Blender, I click on the X button in the upper right-hand corner. I have never used ctrl+Q or file>quit.
So far today, no luck getting 2.56a to open on the laptop. It works fine on the desktop. Maybe it will kick back in tonight.
I did run a system info report on the 2.55 that runs on the laptop. I don’t know if that info would help. I posted on my website: http://cce.lisd.net/blender/. I created an Adobe Acrobat PDF for the 2.55 system report.