EXCEPTION_ACCESS_VIOLATION Error code when using OPTIX #121191
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
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#121191
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
Windows 64
RTX 4090
19-14900K
Blender Version
BLENDER 4.0
BLENDER 4.02
Short description of error
When compositing, using Optix I get an error code EXCEPTION_ACCESS_VIOLATION and blender seems to crash. Happens in pretty much all files.
Exact steps for others to reproduce the error
Open file, hit render animation, gets a few frames in and then crashes.
Reinstalled GPU drivers from scratch today, all windows updates completed.
System does not run out of VRAM ( 3gb scene) 4090 has 24.
Running CUDA seems to fix issues
Logs attached from 4.02
A blender file which crashed on frame 14
Hi, thanks for the report. Unable to confirm the crash in 4.1
Can you check again in 4.1/4.2 build: https://builder.blender.org/download/daily/
Morning Pratik, thanks for the reply. I will try to recreate the issue today when I have a moment.
I did have another crash yesterday ( Blender 4.1 ) which seems to say EXCEPTION_ACCESS_VIOLATION in the error code as well, but this time I was using CUDA, so I guess it must be another issue? There are so many topics referring to this code all with different reasons so I'm not sure what it could be. I've attached that Crash file and will update if I get an optix one as well. Thank you.
EDIT - Nevermind got it straight away on OPTIX, updated the files below.
After some more browsing, I've found a few similar cases that suggest that its CPU related and limiting the clock speed / threads can help?
Would anyone know if that is something that would work in my case?
Thanks. Initially crash was specified with OptiX acceleration but it could be related to CPU 14900K, yes.
You can try undervolt/underclock the CPU-GPU, it might avoid the crash. See: #117368
Hi Pratik, I've been rendering a bit over the last few days and no crashes.
My solution was to disable Intel's boost on the CPU, so instead of CPU trying to pull 4000 watts its now only pulling 350.
Not sure if this has 'fixed' it permanently but I've been rendering 100+ 4k frames with no crashes in OPTIX.
Comparatively to that other post you mentioned, I haven't reduced the CPU ratio as of yet, this boost removal seems good so far.
Thanks for the updates. I think we can close this report for now. Feel free to reopen if you hit the crash again 🙂