Blender freezes on startup
Closed, ArchivedPublic

Description

System Information
OS: Windows 10 build 1803
GPU: Radeon RX 480

Blender Version
Broken: 2.78b and newer
Worked: 2.78a and older

Short description of error
Blender freezes after the command line opens and the grey Blender window showed up, but before everything else.

Exact steps for others to reproduce the error
Opens Blender directly or via command line
Blender frozen (non-responsive), showing only grey inside the Blender window. (As attached screenshot)


Extra info
I've also ran various command line arguments, note that all these commands showed only output with 2.79b, but similar results were met when using with any version from 2.78b and above.

  • The first one is just blender by itself.
  • The second one with multiple arguments is the one where I combined all I think that might help
  • The third one is where I tried switching being multiple engines

R:\Program Files\Blender Foundation\Blender>blender
AL lib: (EE) UpdateDeviceParams: Failed to set 44100hz, got 96000hz instead
found bundled python: R:\Program Files\Blender Foundation\Blender\2.79\python

R:\Program Files\Blender Foundation\Blender>blender --verbose 9 -noaudio --debug-value 9 -con -Y -d --debug-gpu -noglsl -nojoystick
Switching to fully guarded memory allocator.
Blender 2.79 (sub 0)
Build: Thu 03/22/2018 09:59 AM Windows
argv[0] = blender
argv[1] = --verbose
argv[2] = 9
argv[3] = -noaudio
argv[4] = --debug-value
argv[5] = 9
argv[6] = -con
argv[7] = -Y
argv[8] = -d
argv[9] = --debug-gpu
argv[10] = -noglsl
argv[11] = -nojoystick
disabling nojoystick
read file
Version 272 sub 2 date unknown hash unknown

ordered
OBCube
OBLamp
OBCamera
Using OpenGL 4.3 debug facilities
GL application marker: Successfully hooked OpenGL debug callback.
GL_CONTEXT_PROFILE_MASK = 0x2 (compatibility profile)
found bundled python: R:\Program Files\Blender Foundation\Blender\2.79\python

R:\Program Files\Blender Foundation\Blender>blender -E BLENDER_RENDER/BLENDER_GAME/CYCLES
AL lib: (EE) UpdateDeviceParams: Failed to set 44100hz, got 96000hz instead
found bundled python: R:\Program Files\Blender Foundation\Blender\2.79\python

Details

Type
Bug
Philipp Oeser (lichtwerk) triaged this task as Incomplete priority.Thu, Jun 21, 12:19 PM

Total shot in the dark, but:

  • do you have any antivirus running (could you try disabling?) ?
  • does it also happen with --factory-startup?

Marking as incomplete until we have an answer on these two questions...

Total shot in the dark, but:

  • do you have any antivirus running (could you try disabling?) ?
  • does it also happen with --factory-startup?

    Marking as incomplete until we have an answer on these two questions...

Hi,

Thank you for the reply!

Beside Windows Defender, I only have Malwarebytes installed, disabling it still gives the same result.

When using --factory-startup, the same issue persist with this same output:
AL lib: (EE) UpdateDeviceParams: Failed to set 44100hz, got 96000hz instead
found bundled python: C:\Program Files\Blender Foundation\Blender\2.79\python

Could you try a new build from https://builder.blender.org/download?

If that still doesnt work, could you try dropping this dll in the folder where blender.exe resides and test again? (you can remove it after the test)

I've tried the latest 2.79 and 2.80 builds (both with and without New Compiler), the results are still the same.

When retesting using the provided opengl32.dll, 2.79 builds and 2.80 builds behaved differently.

On 2.79 builds, the same thing occurred, but the output from the console is slightly different:
AL lib: (EE) UpdateDeviceParams: Failed to set 44100hz, got 96000hz instead
Warning! Legacy WGL is unable to select between OpenGL versions.found bundled python: C:\Program Files\Blender Foundation\Blender\2.79\python

On 2.80 builds, an error dialogue appeared saying "Blender requires a graphics driver with at least OpenGL 3.3 support" and Blender didn't start, the console has the following output:
AL lib: (EE) UpdateDeviceParams: Failed to set 44100hz, got 96000hz instead
Win32 Error# (0): The operation completed successfully.
Win32 Error# (0): The operation completed successfully.
Win32 Error# (0): The operation completed successfully.
Win32 Error# (0): The operation completed successfully.
Win32 Error# (0): The operation completed successfully.
Win32 Error# (0): The operation completed successfully.
Win32 Error# (0): The operation completed successfully.

I hope that helped!

Bastien Montagne (mont29) closed this task as Archived.Thu, Jul 12, 4:26 PM
Bastien Montagne (mont29) claimed this task.

Yes, 2.8 won’t run with old software OpenGL am afraid…

The issue must be related to either your hardware, or your OS/driver though, pretty much impossible to help further without being able to investigate ourselves, so will archive the report for now.