EXCEPTION_ACCESS_VIOLATION Blender 2.79
Open, IncompletePublic

Description

System Information
Using Win10 64bit
Gigabyte GeForce® GTX 1050 Ti

Blender Version
Broken: 2.79
Worked: 2.78c

Short description of error
Closes on boot when running normally regardless of run as admin
Throws error "EXCEPTION_ACCESS_VIOLATION" when running from cmd
Only 2.79 is broken for me, every other version i've tried works like a glove

Details

Type
Bug
Philipp Oeser (lichtwerk) triaged this task as Incomplete priority.Mon, May 7, 10:13 AM

Please:

  • Ensure both your OS and drivers are fully up-to-date (and use official GPU drivers, not those provided by windows or tablet/laptop maker).
  • Try to disable any running antivirus.
  • Try the latest build from our buildbot.
  • Try to start Blender in factory settings (--factory-startup commandline option) (this will ensure whether this is a userpref or addon issue or not).
  • Try to tweak your GPU driver settings (e.g. try different values between 'performance' and 'quality' if you have such slider, etc.
  • Launch Blender from the command line with -d option and attach as text file here any error printed out in the console (do not paste it directly in comment).
  • Try to run Blender through Software OpenGL, this will be much slower however, if everything works then it means that the bug is spefic for your GPU/Driver and you should report the bug to your GPU vendor instead. On MS-Windows: Download this dll and copying it so its located in the same directory as 'blender.exe' and run Blender normally.

Marking as incomplete until we have this tried.

Same problem here, Windows 10 Pro 64bit, build 1709 (not fully up to date, Windows Update broken for unknown reasons) and an Nvidia Geforce GTX 970 with latest drivers.

If I remember correctly, 2.78 was initially installed and worked, but that could be months ago. Just updated with the official installer to 2.79b, but still crashes despite the following:

  • No 3rd party antivirus, only Windows Defender
  • Command line parameter --factory-startup
  • Using opengl32.dll
  • Reinstallation of VC redist 2013
  • Running as administrator
  • Changed Python related things in environment variables to some non-existing paths (e.g. C:\tools\python2 --> C:\tools\piiithon2)

The following build bot builds start without problems however:

  • blender-2.79-4461be1-win64.zip (VC12)
  • blender-2.79-4461be1-win64-vc14.zip
  • blender-2.80-34c98e3-win64-vc14.zip

Seems highly unlikely that a change to the driver settings would make the official 2.79b work that otherwise crashes, whereas above builds start up just fine without a change to the driver settings.

I can't update Windows at the moment, because something is terrible broken there since 2 weeks. It might have started when I tried to install the Hyper-V feature, which is currently enabled.

Running the crashing 2.79b with -d option:

C:\Program Files\Blender Foundation\Blender>blender --factory-startup -d
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] = --factory-startup
argv[2] = -d
read file
  Version 272 sub 2 date unknown hash unknown

ordered
 OBCube
 OBLamp
 OBCamera
AL lib: (EE) UpdateDeviceParams: Failed to set 44100hz, got 48000hz instead
found bundled python: C:\Program Files\Blender Foundation\Blender\2.79\python
Error: EXCEPTION_ACCESS_VIOLATION

Doing the same with one of the working builds:

C:\Users\CodeManX\Downloads\blender-2.79.0-git.4461be1-windows64-vc12>blender -d
Switching to fully guarded memory allocator.
Blender 2.79 (sub 4)
Build: Wed 05/16/2018 04:27 AM Windows Release
argv[0] = blender
argv[1] = -d
read file
  Version 272 sub 2 date unknown hash unknown

ordered
 OBCube
 OBLamp
 OBCamera
AL lib: (EE) UpdateDeviceParams: Failed to set 44100hz, got 48000hz instead
found bundled python: C:\Users\Simran\Downloads\blender-2.79.0-git.4461be1-windows64-vc12\2.79\python
Cycles OpenCL: driver crashed, continuing without OpenCL.

The last line seems relevant. OpenCL crashed apparently, but Blender doesn't seem to care. Is it possible that the older official version doesn't catch this error and crashes?

I've got the same problem on 2.79, I've installed VC Redist 2013, updated graphics drivers from AMD, and tried running both as admin, and with the software OpenGL dll. I've also tried running with --factory-startup, but this is the first run of the program on a new machine, so there are no existing user settings.

  • Windows 10 Pro 64-bit (10.0, Build 16299)
  • Intel Core i5-7500
  • 16GB RAM
  • AMD FirePro W2100
    • Driver date: 2018-4-25
C:\Program Files\Blender Foundation\Blender> ./blender.exe -d
Switching to fully guarded memory allocator.
Blender 2.79 (sub 0)
Build: Thu 03/22/2018 09:59 AM Windows
argv[0] = C:\Program Files\Blender Foundation\Blender\blender.exe
argv[1] = -d
read file
  Version 272 sub 2 date unknown hash unknown

ordered
 OBCube
 OBLamp
 OBCamera
AL lib: (EE) UpdateDeviceParams: Failed to set 44100hz, got 48000hz instead
found bundled python: C:\Program Files\Blender Foundation\Blender\2.79\python
Error: EXCEPTION_ACCESS_VIOLATION