Cannot start Blender 2.83 - Crashing on startup #77360
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
6 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#77360
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
Graphics card: NVIDIA GeForce 2080 Super
Blender Version
2.83 and 2.82
Short description of error
Blender 2.83 is crashing on startup, even with the previous version I had the same problem.
Attached is the logfile, Im having the same message for both versions of Blender.
blender_debug_output.txt
Added subscriber: @mathieuhevey
Added subscriber: @Alaska
The debug file lists video memory as the issue. Please try updating your GPU drivers: https://www.nvidia.com/Download/index.aspx
Another cause could be faulty hardware.
Also, as per the traige playbook , I'm have to close this report:
Thanks for the report, but unfortunately this can't be triaged as a complete bug report.
For the development team to be able to help, there needs to be either reproducible steps (start blender, press this, then that and crash) or at least a known regression (Blender version X worked, but not version Y).
Sadly, "Blender crashes on startup in every version I've tested" is not a set of reproducible steps. And because we don't have a comparison between a working and faultly version, this can't be considered a regression.
Changed status from 'Needs Triage' to: 'Archived'
Added subscriber: @ankitm
uhh crash at startup is a valid report: #72098
Only thing missing so far is system report. with some comments, that can be received too.
Changed status from 'Archived' to: 'Needs User Info'
@ankitm in the weekly report May 25 - 29 by Dalai Felinto (https://wiki.blender.org/wiki/User:Dfelinto/Reports/2020#May_25_-_29) it states:
Maybe I mis-understood this. If you, or Dalai Felinto would like to discuss this further, this report probably isn't the best place to do it. I can be found over on devtalk if you want to start a private conversation.
Added subscriber: @amy_aimei
I tried the Windows version of the 2.82a, it works. But I can't even get a debug log with 2.83.
I started it at Command Prompt:
C:\blender-2.83.0-windows64>blender
found bundled python: C:\blender-2.83.0-windows64\2.83\python
Error : EXCEPTION_ACCESS_VIOLATION
Address : 0x00007FF6D35FFFF4
Module : C:\blender-2.83.0-windows64\blender.exe
If you run Blender from the file
blender_debug_log.cmd
in the installation directory of Blender, it should open up a file explorer after crashing with two files. Please upload both of them here.All my drivers are up to date, my other softwares works perfectly when I render and they do not crash on startup (DAZ Studio, UE4), its only blender that struggle...
Here are both files attached, sorry I forgot to attach the system info doc.
blender_system_info.txt
blender_debug_output.txt
renderer: 'Intel(R) UHD Graphics 630'
vendor: 'Intel'
version: '4.5.0 - Build 26.20.100.7262'
Closed as duplicate of #72098
See https://developer.blender.org/T72098#938719
and https://developer.blender.org/T72098#906441
for workarounds.
Ah, the power saving trick works ! Thanks !
Added subscriber: @rjg
@mathieuhevey BTW you graphics driver is not up-to-date. The most recent driver for Intel UHD 630 is 27.20.100.8280
I did the update for the intel 630 right before using the power save trick.
Thanks !
Added subscriber: @B10essee
For anyone else still having issues with latest Blender 2.83 builds...below is what worked for me after having the same issues of the Blender cmd opening and then quickly closing.
Running Win 10 Pro 64
Intel i9-9900
32 GB of RAM
Two Quadro P1000 installed
1 Intel UHD Graphics 630
Switched to the Intel card (and made sure all graphics drivers were updated). Still had issues.
Ran Repair on the software and Blender opened with no issues.
I'm not completely IT savvy, but I think there were old user temp files from the 2.82a build I had loaded that were getting in the way. Hope this helps others.