Page MenuHome

Blender 2.8 crashes on startup
Closed, ResolvedPublic

Description

System Information
Windows 7 Ultimate x64, Nvidia Geforce 8600 GT Fatality Edition (1 GB VRAM)

Blender Version
Broken: (blender-2.80.0-git.e856eb7-windows64)
Worked: (optional)

Short description of error
Blender 2.8 crashes on startup. The black terminal window opens, then the following text appears for a few seconds:


Then, a blank window appears:

After a few seconds, the window closes. If I start Blender again, it crashes again. My monitor resolution is 1680x1050. I don't know if the smaller resolution could cause these issues. My GPU supports OpenGL 3.3. I will attach a system information file generated from Blender 2.79

Exact steps for others to reproduce the error
Blender crashes when it starts. There is no way to provide a .blend file.

Event Timeline

Does Blender run if you start it with --debug-gpu?

Yes, it starts with this command

Can you try the last build from the buildbot and see if it's still an issue? there were some changes to the opengl context done.

If @Chris Marn (mahri726) is having the same issue that I've been having on my old laptop (and current dev machine), the problem currently looks like:

 	nvoglv64.dll!0000000076c5c300()	Unknown
 	nvoglv64.dll!0000000076c5c1e8()	Unknown
 	nvoglv64.dll!0000000076c5b4cc()	Unknown
>	blender.exe!immEnd() Line 415	C             <----  "glBindBuffer(GL_ARRAY_BUFFER, 0);"
 	blender.exe!region_draw_emboss(const ARegion * ar, const rcti * scirct, int sides) Line 140	C
 	blender.exe!ED_region_do_draw(bContext * C, ARegion * ar) Line 531	C
 	blender.exe!wm_draw_window_offscreen(bContext * C, wmWindow * win, bool stereo) Line 539	C
 	blender.exe!wm_draw_window(bContext * C, wmWindow * win) Line 667	C
 	blender.exe!wm_draw_update(bContext * C) Line 825	C
 	blender.exe!WM_main(bContext * C) Line 550	C
 	blender.exe!main(int argc, const unsigned char * * UNUSED_argv_c) Line 525	C

(Note: Tested with 16878072a499d1b328e8f2eb968e5fd4829d996b, via the greasepencil-object branch)

Pre-Code Quest, Blender used to crash much earlier (i.e. in Ghost, after window creation - see my comments on T51644). As a result, I currently run Blender via an stderr-filtering Rust wrapper, that runs Blender with the --debug-gpu flag, which is the only way to work around the driver problems on my Nvidia GeForce GT 740M.

given --debug-gpu works, i thought I might be some kind of race condition again, clement did some work with the context today/yesterday, if it's still an issue can you see if GHOST_TSuccess GHOST_ContextWGL::activateDrawingContext() ever returns false?

Hmm interesting... will test sometime today and let you know. Hopefully we can get to the bottom of this at last.

Yeah given i can't repro it, it's probably gonna be a lot of can you try X can you see if Y... sorry about that...

I tried the latest build, and the problem still persists

Coming from T56193 to this one (which seems to be similar). Exactly the same behaviour.
When starting blender with --factory-startup from the Windows 10 commandline (running as admin) I see the following in the command prompt after the crash:

Error : EXCEPTION_ACCESS_VIOLATION
Address : 0x000000006BA092D0
Module : C:\WINDOWS\SYSTEM32\nvoglv64.DLL

Starting with -d --debug-gpu it works but extremely slow, while 2.79b works fine.

Full texts of both scenarios attached as txt file, as well as system info.

To answer the questions from the other thread:

  • OS and drivers are fully up-to-date, drivers are from NVIDIA, not OS. Though the latest drivers which support my GPU are from 2016.
  • --factory-startup commandline option does nothing, still crashes.
  • Tweaking GPU driver settings (performance/quality) does not fix it.

Ok so making sense of the error messages:

Win32 Error# (3221692565): <no system message>
Win32 Error# (3221684237): <no system message>

Reading this it seems that the error code are in fact the lower 16 bits of the full DWORD.

3221692565 > 0xC0072095 > 0x2095 > ERROR_INVALID_VERSION_ARB
3221684237 > 0xC007000D > 0x000D > ERROR_INVALID_DATA

But I think those messages maybe ok because we test every higher versions of OpenGL before trying to get the minimum 3.3 context.

It might be nice if someone with a debug build could confirm it's the case.

Can someone (@Joshua Leung (aligorith) ?) please test this simple patch P766 and tell me if that changes anything?

@Clément Foucault (fclem) Yep, this solves the crash here. UI draws normally, and Spring files can be loaded.

Awesome, this fixed it for me (trying 77e1942e0e1).
Thanks a lot!