Blender crash on start-up, EXCEPTION_ACCESS_VIOLATION, OpenGL.3.3 or higher required #79229
Labels
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#79229
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
System Information
Operating system: Windows 10
Intel Core i7-6700k CPU @ 4.00 GHz
Graphics card:
Blender Version
Broken: All, tested 2.78, 2.79, 2.8, 2.81, latest version on steam, which i assume is 2.83, and the 2.9 beta with the blender_debug_gpu.
Worked: N/A
Short description of error
Program shuts down immediatly after starting up. If starting though cmd i get the exception_access_violation error, if adding opengl32.dll to the directory the error is instead that the graphics card needs to support 3.3 or higher while the version on the pc is 4.6. All drivers are up-to-date. PC has been fully reset in hopes to solve the issue to no avail.
Exact steps for others to reproduce the error
Images of cmd: https:*imgur.com/akjPlBh / https:*imgur.com/PS6oKF0
blender_debug_output.txt Blender_debug_output
blender_debug_output (added opengl32.dll).txt Blender_debug_output (added opengl32.dll)
blender.crash.txt Blender.crash.txt
Added subscriber: @Juliavo
Added subscriber: @rjg
Changed status from 'Needs Triage' to: 'Needs User Info'
The fact the crash occurs that early and affects even the old versions of Blender, is not a good sign. Have you been experiencing similar issues with other software?
I haven't had this issue with any other software really. This has only been happening with Blender, which is weird because it used to work just fine on the same computer before.
In order to rule out an issue like #72098, please try the following:
Select the energy mode that uses the integrated Intel GPU and save.
If this doesn't change anything, select the Nvidia GPU instead and check if that makes any difference.
I cannot seem to find an option that only uses the Intel GPU. All three of the options show the same graphic cards for both power saving and high performance, i cannot click on them to change them either. I have tried starting the program with all three options but the problem sadly still remains.
Are you able to start Blender in background mode with the factory default settings?
blender.exeis located).blender.exe --factory-startup --backgroundWhen starting Blender in background mode, the errors that appear on the cmd say it's not able to create directories for thumbnails. A screenshot of the console is added below.
It does start Blender though. The creation of the directory may require elevated permissions. Have you tried starting it as administrator (this should only be done for testing purposes, in general it is not recommended)?
The big question is why OpenGL rendering doesn't work properly. Please run the following command in Blender's installation directory to create a system info file.
blender.exe --factory-startup --background --python-expr "import bpy; bpy.ops.wm.sysinfo(filepath=r'%temp%\blender\debug_logs\blender_system_info.txt')" > "%temp%\blender\debug_logs\blender_debug_output.txt" 2>&1The files should then be located in
C:\Users\julia\AppData\Local\Temp\blender\debug_logsRan the command, added the console down below. Not sure if it has anything to do with it, but as soon as i ran the command i got a notification from windows defender asking to scan the file? Clicking on it brought me to a website from Microsoft about 'Blocking at first sight'. https://docs.microsoft.com/en-us/windows/security/threat-protection/microsoft-defender-antivirus/configure-block-at-first-sight-microsoft-defender-antivirus
Edit: Forgot to say but ran Blender as Administrator as well, but it didn't really change anything.
blender_system_info.txt
blender_debug_output.txt
@Juliavo In this specific case it could be because you're using a development build of Blender, combined with the inline Python script that creates a file, which looks suspicious to Windows Defender. It would be interesting though if Windows Defender interferes with Blender on your system in general, because that can also result in a crash (e.g. quarantining files that Blender needs or stopping the process).
The system info file looks fine as far as I can tell, both GPUs get recognized by Blender. However, there are the following two error messages in the debug log:
@Juliavo Can you check if Defender has quarantined any of Blender's files (see "Restore quarantined files" )?
Just tried to start Blender with Windows Defender off, not much changed. It says it's an app that is allowed to go through the Firewall too, i'm not really sure if Defender and Firewall would be the cause of the problem. It probably was indeed just because it's a beta build like you mentioned earlier, figured it was worth a try just in case haha.
No files are shown in the protection history, so i suppose Defender didn't quarantine any of Blender's files.
@Juliavo That rules out the Windows Defender as cause. The firewall wouldn't stop Blender from starting, since it doesn't require any internet connection.
Could you please check if enabling the compatibility mode allows Blender to start with a GUI:
blender.exeand open the PropertiesThis time instead of a quick flash it showed a fullscreen, white window opening that did close after again, but it did show more than it did before.
Could you please run
blender_debug_gpu.cmdfor 2.90 again, with compatibility mode enabled and uploaded the created files, including the crash log inC:\Users\julia\AppData\Local\Temp.Ran the command, these are the files that were created.
blender_debug_output.txt With OpenGL32.dll
blender_debug_output (without opengl32.dll).txt Without the .dll
blender.crash.txt Blender.crash.txt
Compatibility mode doesn't seem to have any effect, you can deactivate it.
I would suggest that you install any pending Microsoft updates and then run DISM and SFC to detect and fix potentially broken system files as described in this guide by Microsoft .
Just finished the DISM and SFC, it seems the scans could not find any missing or corrupted files.
I was sure i installed all updates, but suddenly it shows an update for Microsoft defender which quickly disappears after a few seconds as well, again saying i'm fully up-to-date. The update appears and disappears again when i check for updates again. Does that mean my updater is broken?
@Juliavo Since DISM and SFC didn't find any issues, it's probably fine. You'd have to check the update history to see if/why a particular update failed. Since you've already tested with Microsoft Defender disabled, this is unlikely related to the Blender issue.
Unfortunately, I can't see a clear source of the problem with the currently available information. Perhaps somebody else has an idea what the issue might be.
Ah alright. It's such a shame, i was hoping to keep learning and using this program for work. Thank you for taking the time to help me though!
@Juliavo You're welcome.
My general impression, based on the current hardware you're using and the wide range of affected Blender versions, is that this is most likely caused by something on the side of the operating system or drivers.
Changed status from 'Needs User Info' to: 'Needs Triage'
I have tried running Ccleaner in the hopes that that maybe would get rid of files that could be interfering with Blender, but it doesn't really seem to have done much to help Blender run properly.
@Juliavo I would generally advise against running clean-up / tune-up utilities of any sort. At best they don't break anything. CCleaner in particular has a bad track record.
Ah alright. I've uninstalled it immediatly.
Added subscriber: @iss
Changed status from 'Needs Triage' to: 'Archived'
If you are unable to run even Blender 2.79, and you say that you was able to run it in the past, it is very unlikely the issue is bug in Blender. My personal advice would be to reinstall OS, if that is possible. if that is not possibility, you can try asking for help on one of the community websites: https://www.blender.org/community/
This tracker is only for reporting reproducible problems, so I will close this report. If you find root of the problem, and you think it is bug in Blender, please open new report.
I have fully deleted all partitions and reinstalled Windows again through a usb, which seemed to do the trick! I hope it stays this way haha. Thank you for the help!
Thanks for letting us know.