Blender does not open 2.82a #76042

Closed
opened 2020-04-24 09:48:12 +02:00 by edson · 13 comments

blender_system_info.txt

System Information
Operating system: Windows 10
Graphics card: Intel(R) HD Graphics 630

Short description of error
Just uninstalled and installed the new version of blender (2.82a). Updated my drivers to the latest and when I double-click on the blender app, a few milliseconds of pop-up appeared and blender does not execute. Using blender_debug_output, the message is as follows:


Switching to fully guarded memory allocator.
Blender 2.82 (sub 7)
Build: 2020-03-12 15:41:08 Windows Release
argv[0] = blender
argv[1] = --debug
argv[2] = --debug-gpu
argv[3] = --python-expr
argv[4] = import bpy; bpy.ops.wm.sysinfo(filepath=r'C:\Users\***\AppData\Local\Temp\blender\debug_logs\blender_system_info.txt')
read file 
  Version 280 sub 39 date unknown hash unknown
Error   : EXCEPTION_ACCESS_VIOLATION
Address : 0x0000000000000000

Exact steps for others to reproduce the error
Double-clicking on blender.exe

[blender_system_info.txt](https://archive.blender.org/developer/F8492209/blender_system_info.txt) **System Information** Operating system: Windows 10 Graphics card: Intel(R) HD Graphics 630 **Short description of error** Just uninstalled and installed the new version of blender (2.82a). Updated my drivers to the latest and when I double-click on the blender app, a few milliseconds of pop-up appeared and blender does not execute. Using blender_debug_output, the message is as follows: ``` Switching to fully guarded memory allocator. Blender 2.82 (sub 7) Build: 2020-03-12 15:41:08 Windows Release argv[0] = blender argv[1] = --debug argv[2] = --debug-gpu argv[3] = --python-expr argv[4] = import bpy; bpy.ops.wm.sysinfo(filepath=r'C:\Users\***\AppData\Local\Temp\blender\debug_logs\blender_system_info.txt') read file Version 280 sub 39 date unknown hash unknown Error : EXCEPTION_ACCESS_VIOLATION Address : 0x0000000000000000 ``` **Exact steps for others to reproduce the error** Double-clicking on blender.exe
Author

Added subscriber: @weic1253

Added subscriber: @weic1253
Member

Closed as duplicate of #72098

Closed as duplicate of #72098
Member

Added subscriber: @ankitm

Added subscriber: @ankitm
Member
Try this: https://developer.blender.org/T72098#906441
Author

Hi, I tried but it doesn't work. It gives the same error.

Hi, I tried but it doesn't work. It gives the same error.
Author
@ankitm
Member

You're using driver released in Dec 2019. Try updating it. https://downloadcenter.intel.com/product/98909/Intel-HD-Graphics-630

You're using driver released in Dec 2019. Try updating it. https://downloadcenter.intel.com/product/98909/Intel-HD-Graphics-630
Author

@ankitm
I updated my drivers and checked the configuration of my workstation as follows:

Report Date: Tuesday, 28 April 2020
Report Time [hh:mm:ss]: 09:08:00 PM
Operating System: NA
Language: en-US
Physical Memory: NA
Current Resolution: 1920x1080

Processor: NA
Processor Speed: 3801 MHz MHz
GFX Driver Name: Intel(R) HD Graphics 630
Shader Version: 5.1
OpenCL* Version: 2.1

* Microsoft DirectX* *
Runtime Version: 12
Hardware-Supported Version: 12
Vulkan* Version: 1.2.135
Vendor ID: 
Device ID: 
Device Revision: 04
GFX Driver Version: 26.20.100.8141 (this is the current version, see https://downloadcenter.intel.com/download/29530/Intel-Graphics-Windows-10-DCH-Drivers?product=98909)
GFX Vulcan: 1.2.135
GFX Video BIOS: 1046

GFX Driver Name: NVIDIA GeForce GTX 1060 6GB
Shader Version: NA
OpenCL* Version: NA
* Microsoft DirectX* *
Runtime Version: NA
Hardware-Supported Version: NA
Vulkan* Version: NA
Vendor ID: NA
Device ID: NA
Device Revision: NA
GFX Driver Version: 26.21.14.4587
GFX Vulcan: 

* Devices connected to the Graphics Accelerator *
Active Displays: 1

* Digital Display 1 *
Display Name: 
Display Type: 
Serial Number:             
DDC2 Protocol: Supported
Gamma: 2.2
Connector Type: HDMI

I tried to investigate and it seems that my monitor is not attached to NVIDIA GPU? image.png

However, clicking on blender still reveals similar error, but with a slight difference as follows:

Switching to fully guarded memory allocator.
Blender 2.82 (sub 7)
Build: **2020-03-12 15:41:08 Windows Release**
argv[0] = blender
argv[1] = --debug
argv[2] = --debug-gpu
argv[3] = --python-expr
argv[4] = import bpy; bpy.ops.wm.sysinfo(filepath=r'C:\Users\XXX\AppData\Local\Temp\blender\debug_logs\blender_system_info.txt')
read file 
  Version 280 sub 39 date unknown hash unknown
Error   : EXCEPTION_ACCESS_VIOLATION
Address : 0x0000000000000000

@ankitm **I updated my drivers and checked the configuration of my workstation as follows:** ``` Report Date: Tuesday, 28 April 2020 Report Time [hh:mm:ss]: 09:08:00 PM Operating System: NA Language: en-US Physical Memory: NA Current Resolution: 1920x1080 Processor: NA Processor Speed: 3801 MHz MHz GFX Driver Name: Intel(R) HD Graphics 630 Shader Version: 5.1 OpenCL* Version: 2.1 * Microsoft DirectX* * Runtime Version: 12 Hardware-Supported Version: 12 Vulkan* Version: 1.2.135 Vendor ID: Device ID: Device Revision: 04 GFX Driver Version: 26.20.100.8141 (this is the current version, see https://downloadcenter.intel.com/download/29530/Intel-Graphics-Windows-10-DCH-Drivers?product=98909) GFX Vulcan: 1.2.135 GFX Video BIOS: 1046 GFX Driver Name: NVIDIA GeForce GTX 1060 6GB Shader Version: NA OpenCL* Version: NA * Microsoft DirectX* * Runtime Version: NA Hardware-Supported Version: NA Vulkan* Version: NA Vendor ID: NA Device ID: NA Device Revision: NA GFX Driver Version: 26.21.14.4587 GFX Vulcan: * Devices connected to the Graphics Accelerator * Active Displays: 1 * Digital Display 1 * Display Name: Display Type: Serial Number: DDC2 Protocol: Supported Gamma: 2.2 Connector Type: HDMI ``` I tried to investigate and it seems that my monitor is not attached to NVIDIA GPU? ![image.png](https://archive.blender.org/developer/F8499132/image.png) **However, clicking on blender still reveals similar error, but with a slight difference as follows:** ``` Switching to fully guarded memory allocator. Blender 2.82 (sub 7) Build: **2020-03-12 15:41:08 Windows Release** argv[0] = blender argv[1] = --debug argv[2] = --debug-gpu argv[3] = --python-expr argv[4] = import bpy; bpy.ops.wm.sysinfo(filepath=r'C:\Users\XXX\AppData\Local\Temp\blender\debug_logs\blender_system_info.txt') read file Version 280 sub 39 date unknown hash unknown Error : EXCEPTION_ACCESS_VIOLATION Address : 0x0000000000000000 ```
Member

going over some old reports, I see some suggestions:

  • Change GPU settings to force Blender to use Nvidia card, not intel. As you can see in system info under " OpenGL" .. "renderer". Since I don't use windows, you'd have to lookup some guides.
  • Run blender_debug_gpu_glitchworkaround.cmd & upload the files it mentions.

But as of now, the task #72098 is the tracker for errors in dual GPU Intel HD 5xx-6xx machines. So when that gets fixed, & your system still doesnt work, let us know & we can reopen this report.

going over some old reports, I see some suggestions: - Change GPU settings to force Blender to use Nvidia card, not intel. As you can see in system info under " OpenGL" .. "renderer". Since I don't use windows, you'd have to lookup some guides. - Run blender_debug_gpu_glitchworkaround.cmd & upload the files it mentions. But as of now, the task #72098 is the tracker for errors in dual GPU Intel HD 5xx-6xx machines. So when that gets fixed, & your system still doesnt work, let us know & we can reopen this report.
Author

Thank you for your prompt response. @ankitm

image.png I tried the first method and changed the GPU settings to NVIDIA such that blender opens with NVIDIA, but the same still happens.

I tried to investigate further and it seems that I can't access NVIDIA's Control Panel because my workstation is not attached to NVIDIA GPU. image.png

Running blender_debug_gpu_glitchworkaround.cmd produces the same thing but there is no blender_system_info file, so here is the code. I have attached the file here as well.

blender_debug_output.txt

Switching to fully guarded memory allocator.
Blender 2.82 (sub 7)
Build: 2020-03-12 15:41:08 Windows Release
argv[0] = blender
argv[1] = --debug
argv[2] = --debug-gpu
argv[3] = --debug-gpu-force-workarounds
argv[4] = --python-expr
argv[5] = import bpy; bpy.ops.wm.sysinfo(filepath=r'C:\Users\XXX\AppData\Local\Temp\blender\debug_logs\blender_system_info.txt')
read file 
  Version 280 sub 39 date unknown hash unknown
Error   : EXCEPTION_ACCESS_VIOLATION
Address : 0x0000000000000000
Thank you for your prompt response. @ankitm ![image.png](https://archive.blender.org/developer/F8499142/image.png) I tried the first method and changed the GPU settings to NVIDIA such that blender opens with NVIDIA, but the same still happens. I tried to investigate further and it seems that I can't access NVIDIA's Control Panel because my workstation is not attached to NVIDIA GPU. ![image.png](https://archive.blender.org/developer/F8499146/image.png) Running blender_debug_gpu_glitchworkaround.cmd produces the same thing but there is no blender_system_info file, so here is the code. I have attached the file here as well. [blender_debug_output.txt](https://archive.blender.org/developer/F8499149/blender_debug_output.txt) ``` Switching to fully guarded memory allocator. Blender 2.82 (sub 7) Build: 2020-03-12 15:41:08 Windows Release argv[0] = blender argv[1] = --debug argv[2] = --debug-gpu argv[3] = --debug-gpu-force-workarounds argv[4] = --python-expr argv[5] = import bpy; bpy.ops.wm.sysinfo(filepath=r'C:\Users\XXX\AppData\Local\Temp\blender\debug_logs\blender_system_info.txt') read file Version 280 sub 39 date unknown hash unknown Error : EXCEPTION_ACCESS_VIOLATION Address : 0x0000000000000000 ```
Member

So I'm going to go out on a limb here and say that you have Onboard video and you have the monitor cable plugged into the wrong port on
the back of your computer.....
Edit*** make sure the monitor cable (hdmi, DVI, ect) is plugged into the video card and not into a port in the i/o panel up by the usb ports

source

For me, the reason was simply that I didn't plug my screen cable to the right plug on my desktop computer. It was plugged on the motherboard instead of being plugged on the graphic card. The computer was therefore using the processor instead of the graphic card for all the graphic stuff, so everything was working fine except in games where I had a FPS of 5 to 15 instead of 60.

source

>So I'm going to go out on a limb here and say that you have Onboard video and you have the monitor cable plugged into the wrong port on >the back of your computer..... > Edit*** make sure the monitor cable (hdmi, DVI, ect) is plugged into the video card and not into a port in the i/o panel up by the usb ports [source](https://www.reddit.com/r/nvidia/comments/5g9w4j/you_are_not_currently_using_a_display_attached_to/) > For me, the reason was simply that I didn't plug my screen cable to the right plug on my desktop computer. It was plugged on the motherboard instead of being plugged on the graphic card. The computer was therefore using the processor instead of the graphic card for all the graphic stuff, so everything was working fine except in games where I had a FPS of 5 to 15 instead of 60. [source](https://steamcommunity.com/discussions/forum/11/558752356793395263/)

Added subscriber: @Apollo_001

Added subscriber: @Apollo_001

Setting the Graphics settings to the intel card (power savings) fixed the problem for me, thx!

In #76042#919274, @weic1253 wrote:
Thank you for your prompt response. @ankitm

image.png I tried the first method and changed the GPU settings to NVIDIA such that blender opens with NVIDIA, but the same still happens.

I tried to investigate further and it seems that I can't access NVIDIA's Control Panel because my workstation is not attached to NVIDIA GPU. image.png

Running blender_debug_gpu_glitchworkaround.cmd produces the same thing but there is no blender_system_info file, so here is the code. I have attached the file here as well.

blender_debug_output.txt

Switching to fully guarded memory allocator.
Blender 2.82 (sub 7)
Build: 2020-03-12 15:41:08 Windows Release
argv- [x] = blender
argv- [x] = --debug
argv- [x] = --debug-gpu
argv- [x] = --debug-gpu-force-workarounds
argv- [x] = --python-expr
argv- [x] = import bpy; bpy.ops.wm.sysinfo(filepath=r'C:\Users\XXX\AppData\Local\Temp\blender\debug_logs\blender_system_info.txt')
read file 
  Version 280 sub 39 date unknown hash unknown
Error   : EXCEPTION_ACCESS_VIOLATION
Address : 0x0000000000000000

In #76042#919274, @weic1253 wrote:
Thank you for your prompt response. @ankitm

image.png I tried the first method and changed the GPU settings to NVIDIA such that blender opens with NVIDIA, but the same still happens.

I tried to investigate further and it seems that I can't access NVIDIA's Control Panel because my workstation is not attached to NVIDIA GPU. image.png

Running blender_debug_gpu_glitchworkaround.cmd produces the same thing but there is no blender_system_info file, so here is the code. I have attached the file here as well.

blender_debug_output.txt

Switching to fully guarded memory allocator.
Blender 2.82 (sub 7)
Build: 2020-03-12 15:41:08 Windows Release
argv- [x] = blender
argv- [x] = --debug
argv- [x] = --debug-gpu
argv- [x] = --debug-gpu-force-workarounds
argv- [x] = --python-expr
argv- [x] = import bpy; bpy.ops.wm.sysinfo(filepath=r'C:\Users\XXX\AppData\Local\Temp\blender\debug_logs\blender_system_info.txt')
read file 
  Version 280 sub 39 date unknown hash unknown
Error   : EXCEPTION_ACCESS_VIOLATION
Address : 0x0000000000000000
Setting the Graphics settings to the intel card (power savings) fixed the problem for me, thx! > In #76042#919274, @weic1253 wrote: > Thank you for your prompt response. @ankitm > > ![image.png](https://archive.blender.org/developer/F8499142/image.png) I tried the first method and changed the GPU settings to NVIDIA such that blender opens with NVIDIA, but the same still happens. > > > I tried to investigate further and it seems that I can't access NVIDIA's Control Panel because my workstation is not attached to NVIDIA GPU. ![image.png](https://archive.blender.org/developer/F8499146/image.png) > > > Running blender_debug_gpu_glitchworkaround.cmd produces the same thing but there is no blender_system_info file, so here is the code. I have attached the file here as well. > > [blender_debug_output.txt](https://archive.blender.org/developer/F8499149/blender_debug_output.txt) > ``` > Switching to fully guarded memory allocator. > Blender 2.82 (sub 7) > Build: 2020-03-12 15:41:08 Windows Release > argv- [x] = blender > argv- [x] = --debug > argv- [x] = --debug-gpu > argv- [x] = --debug-gpu-force-workarounds > argv- [x] = --python-expr > argv- [x] = import bpy; bpy.ops.wm.sysinfo(filepath=r'C:\Users\XXX\AppData\Local\Temp\blender\debug_logs\blender_system_info.txt') > read file > Version 280 sub 39 date unknown hash unknown > Error : EXCEPTION_ACCESS_VIOLATION > Address : 0x0000000000000000 > ``` > In #76042#919274, @weic1253 wrote: > Thank you for your prompt response. @ankitm > > ![image.png](https://archive.blender.org/developer/F8499142/image.png) I tried the first method and changed the GPU settings to NVIDIA such that blender opens with NVIDIA, but the same still happens. > > > I tried to investigate further and it seems that I can't access NVIDIA's Control Panel because my workstation is not attached to NVIDIA GPU. ![image.png](https://archive.blender.org/developer/F8499146/image.png) > > > Running blender_debug_gpu_glitchworkaround.cmd produces the same thing but there is no blender_system_info file, so here is the code. I have attached the file here as well. > > [blender_debug_output.txt](https://archive.blender.org/developer/F8499149/blender_debug_output.txt) > ``` > Switching to fully guarded memory allocator. > Blender 2.82 (sub 7) > Build: 2020-03-12 15:41:08 Windows Release > argv- [x] = blender > argv- [x] = --debug > argv- [x] = --debug-gpu > argv- [x] = --debug-gpu-force-workarounds > argv- [x] = --python-expr > argv- [x] = import bpy; bpy.ops.wm.sysinfo(filepath=r'C:\Users\XXX\AppData\Local\Temp\blender\debug_logs\blender_system_info.txt') > read file > Version 280 sub 39 date unknown hash unknown > Error : EXCEPTION_ACCESS_VIOLATION > Address : 0x0000000000000000 > ```
Sign in to join this conversation.
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
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#76042
No description provided.