GPU Cycles Rendering Issues #89124
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
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#89124
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 64bit
MSI Tomahawk B450 MAX II Motherboard 32gig memory
Graphics card
2070 + 1070 Screenshot below
Blender Version
9.93 + 2.83
Short description of error
Exact steps for others to reproduce the error
Basic Cube Basic Shader nothing Fancy, in Cycles mode GPU, Compute as per screenshots below I get Error Cuda Errors Illegal address in cuCtxsynchroize()device_cuda_impl.ccp:2049)illegal address Image 1 or it just freezes and locks up for ages like image no 4,
No, I'm not a programmer, I do subscribe to support Blender but every time I ask for help I just get a load of tech jargon, please could i just have a simple answer to fix this as spent 3 days now un-installing blender, GPU drivers, Just tell me what I need to install or uninstall so I can get it working, please. the error is happening with 8.3 now so have no blender software to use at all
Thanks for your time
Kind regards
Dela
Added subscriber: @GavinWyatt
Added subscriber: @iss
Changed status from 'Needs Triage' to: 'Needs User Info'
I have seen reports with this error due to overclocked GPUs or due to TDR error see https://docs.substance3d.com/spdoc/gpu-drivers-crash-with-long-computations-128745489.html for guide on how to increase acceptable delay.
Does this happen when you choose only one of GPUs for rendering?
Over the past 3 days,
uninstalled Blender 9.3
uninstalled all drivers for GPU
Did a full Windows Repair
Reinstalled Nvidia Studio Drivers
Fresh Clean no addons for Blender 2.93
I have never ever overclocked my GPUs
I have Screenshot loads of the GPU Afterburner program to show the basic settings
Any other information id be happy to send, Thanks for reply
edited the Regedit file as you said "https://docs.substance3d.com/spdoc/gpu-drivers-crash-with-long-computations-128745489.html for guide on how to increase acceptable delay."
only one GPU picked being the 2070 super, just locking up no response
Changed status from 'Needs User Info' to: 'Needs Developer To Reproduce'
Well, I did all that I have been told to do, nothing working and no help?
Changed status from 'Needs Developer To Reproduce' to: 'Needs Triage'
Greetings all Developers, I have rebuilt the whole PC, and still no joy
Added subscriber: @lichtwerk
Changed status from 'Needs Triage' to: 'Needs User Info'
Does this work if only on GPU is check in Preferences?
Are the two cards using SLI?
Does it work if you remove one GPU from your computer entirely?
Sorry if this is a bit vague, just trying to get closer to a solution...
Changed status from 'Needs User Info' to: 'Needs Developer To Reproduce'
I have done everything you spoke of
I have cycles working with CPU only,
I took out the 1070 Card to no joy the 2070 same issues still
Did a full purge of every blender version complete clean install no addons
I have Googled answers from others and 100's are having the same Issues even with 3080 cards
https://blenderartists.org/t/blender-failed-to-load-kernel-indirect-background-in-2-9-cycles/1293923
https://blender.stackexchange.com/questions/224493/blender-2-93-cycles-render-does-not-work
https://blenderartists.org/t/failed-to-create-cuda-context-illegal-adress/1278322/2
as you can see i have tried everything i can think of :(
Thanks for you reply
Changed status from 'Needs Developer To Reproduce' to: 'Needs Triage'
Added subscriber: @PratikPB2123
Changed status from 'Needs Triage' to: 'Needs User Info'
Does this problem remain in latest blender versions?: https://builder.blender.org/download/daily/
Changed status from 'Needs User Info' to: 'Archived'
No activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed.
Thanks again for the report. If the problem persists please open a new report with the required information.