Problems due to leftover Nvidia drivers #108810
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
5 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#108810
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 11 Home
Graphics card: Intel Arc a770 16gb Limited Edition (latest drivers)
Blender Version
Broken: (Blender 3.3, 3.5 and 4.0) Trying to work out if it is just my GPU that is the issues
Blender 3.5.1 will not allow me to access editor preferences, and won't allow me to render in Cycles. CPU or GPU. Eevee works.
Blender 3.3 allows me to access editor preferences, but still won't allow me to render in Cycles. CPU or GPU. Eevee works.
Blender 4.0 allows for editor preferences, same issue with Cycles. Eevee works fine.
By not allowing me to access editor preferences or Cycles I mean it crashes.
I have tried to converse with Intel engineers with a video of the crashes but they seem incompetent with knowing how to enable GPU rendering in their own tests.
Please run file
blender_debug_log.cmdfrom 4.0 build and after crash upload created files.here you go.
Hmm it is interesting, that
blender_system_info.txtis empty. Can you click on Help > Save System Info and upload saved file?Let's add to the mystery. I did just did that and it's empty.
I think I have seen similar case, will try to find the report
I have found #108101 and #107419. In both cases they switched from nvidia GPU to AMD and produced empty system info. In both cases removing nvidia drivers fixed the issue. Please check those reports and let me know if you solved the issue. They weren't super detailed about the process.
Thank you so much for that, there were left over Nvidia drivers still installed in my system, everything works perfectly now.
Glad to hear. This is very strange behavior, that seems to be only reported recently. I would assume, that the issue is caused by nvidia drivers, but I can't be sure about that.
I will try to reproduce this on machine with AMD GPU, at least will check where system info process fails. Debugger should give some clue I guess.
Okay so I have recently upgraded my GPU to an Intel arc770. Ever since I have installed it, making sure to have latest drivers, I have not been able to ender anything in Cycles. Even with just my CPU.to Problems due to leftover Nvidia driversUnfortunately I wasn't able to force install nvidia driver and further investigate this issue.
@Jeroen-Bakker what do you think is likelyhood that issue is on our side, when swapping Nvidia for AMD card and not uninstalling drivers causes problems? I do have AMD card, just wanted to avoid HW swapping...
Imo this is an OS responsibility. Don’t think there is a way how we can control drivers in that way. Makes me guess that it would also happen on other applications. Perhaps they need a certain degree of gpu complexity
@Jeroen-Bakker I should have noted, that this has started to happen quite recently and there are at least 3 reports like this one, so that makes me doubt, that this could be issue on our side.
There are less new reports to triage compared to usual, so I will dust off the card and see what happens. it's GCN 4, but here it states that even CPU rendering fails. Now I realized this is cycles specific, so could have poked Brecht instead...
Confirming for now since we have already received multiple reports about this.
I have swapped GPU for RX550 without touching nvidia drivers and everything runs well. So there is probably some nuance in how this issue is triggered.
Would like to have good step by step guide how a system gets in this state so we can actually reproduce the issue and come to a solution for it. It is not clear if this is a driver issue (uninstalling leaves something behind), OS issue (OS loads incorrect driver) or Blender issue (Selecting CUDA as it is still present although not supported by the device).
@brecht do you have an idea how a system can get into this state?
We've encountered this issue in the past, where it's crashing in the driver. In one case for example there was a CUDA dll, but then some missing DLL that CUDA depends on. We have a workarounds for this in
device_cuda_safe_initbut it only helps in some cases. We also mentioning uninstalling existing drivers in the manual:https://docs.blender.org/manual/en/dev/troubleshooting/gpu/windows/intel.html#crash-on-startup
I don't think this is something we can fix in Blender. How exactly it gets into this state I don't know, I've never been able to reproduce it myself. It's not hard to imagine that between driver installers from Windows update, OEMs and GPU vendors there can be conflicts. If we have specific steps we could rmake a bug report to one of them, but otherwise I don't think there is much we can do here.