Access violation in vk_icdNegotiateLoaderICDInterfaceVersion when putting computer to sleep. #112146

Open
opened 2023-09-08 16:08:21 +02:00 by michael campbell · 12 comments

System Information
Operating system: Windows-10-10.0.19044-SP0 64 Bits
Graphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.99

Blender Version
Broken: version: 3.6.3 Release Candidate, branch: blender-v3.6-release, commit date: 2023-09-05 15:07, hash: d371c3c09fa8
Worked: (3.6.2)

Short description of error
access violation when putting computer to sleep. crash log is created immediately after clicking sleep.

Exact steps for others to reproduce the error

  1. launch blender.
  2. open a file
  3. save it
  4. put the computer to sleep

Edited steps because it just happened when blender was launched normally. Wasn't saved this time, and was a different blend file.

**System Information** Operating system: Windows-10-10.0.19044-SP0 64 Bits Graphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.99 **Blender Version** Broken: version: 3.6.3 Release Candidate, branch: blender-v3.6-release, commit date: 2023-09-05 15:07, hash: `d371c3c09fa8` Worked: (3.6.2) **Short description of error** access violation when putting computer to sleep. crash log is created immediately after clicking sleep. **Exact steps for others to reproduce the error** 1. launch blender. 2. open a file 3. save it 4. put the computer to sleep Edited steps because it just happened when blender was launched normally. Wasn't saved this time, and was a different blend file.
michael campbell added the
Priority
Normal
Type
Report
Status
Needs Triage
labels 2023-09-08 16:08:22 +02:00
michael campbell changed title from access violation when putting computer to sleep if blender started from VS code. to access violation when putting computer to sleep. 2023-09-08 18:58:42 +02:00
Member

Looks like it crashed in vk_icdNegotiateLoaderICDInterfaceVersion

Probably due to unstable system hardware status when this function is called or something.

Looks like it crashed in `vk_icdNegotiateLoaderICDInterfaceVersion` Probably due to unstable system hardware status when this function is called or something.
YimingWu changed title from access violation when putting computer to sleep. to Access violation in `vk_icdNegotiateLoaderICDInterfaceVersion` when putting computer to sleep. 2023-09-09 16:10:39 +02:00
YimingWu added the
Platform
Windows
Interest
Vulkan
Interest
OpenGL
labels 2023-09-09 16:10:57 +02:00

"Probably due to unstable system hardware status when this function is called or something."

Wouldn't a hardware issue cause it to happen with all versions of Blender?

"Probably due to unstable system hardware status when this function is called or something." Wouldn't a hardware issue cause it to happen with all versions of Blender?
Member

I can confirm the crash in 4.0 build
Crash has not occurred in 3.6 build so we can call it a regression (but crash log suggests the crash in NVIDIA driver)

I can confirm the crash in 4.0 build Crash has not occurred in 3.6 build so we can call it a regression (but crash log suggests the crash in NVIDIA driver)

I've just found something that might be related. If it doesn't crash when coming out of sleep mode, the wires in node editors dissapear. After closing Blender to try and get the wires back, Blender will no longer open. It just get's stuck on reading preferences, even if loading in Factory mode, manually killing the Blender process from Task Manager, attempting to start from VS Code, it still won't start.

The only way to fix was by restarting windows, and even then, the first time took much longer to start than usual, but was fast to start after that.

I've just found something that might be related. If it doesn't crash when coming out of sleep mode, the wires in node editors dissapear. After closing Blender to try and get the wires back, Blender will no longer open. It just get's stuck on reading preferences, even if loading in Factory mode, manually killing the Blender process from Task Manager, attempting to start from VS Code, it still won't start. The only way to fix was by restarting windows, and even then, the first time took much longer to start than usual, but was fast to start after that.
Miguel Pozo added
Module
EEVEE & Viewport
and removed
Module
Platforms, Builds & Tests
labels 2023-09-19 17:36:31 +02:00
Member

@Jeroen-Bakker Could you take a look at this?

@Jeroen-Bakker Could you take a look at this?
Jeroen Bakker self-assigned this 2023-09-19 19:29:37 +02:00
Member

Will try to reproduce and find the commit that altered the behavior. Perhaps that would lead to some clues.

Will try to reproduce and find the commit that altered the behavior. Perhaps that would lead to some clues.
Member

I am not able to reproduce the issue using

Operating system: Windows-10-10.0.19044-SP0 64 Bits
Graphics card: Quadro RTX 5000/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 537.34
Blender Version:
* version: 4.0.0 Alpha, branch: main, commit date: 2023-09-21 05:55, hash: `9cc4df8062af` (own build)
* version: 4.0.0 Alpha, branch: main, commit date: 2023-09-21 00:11, hash: `963c0ed5e7b0` (buildbot build)
Operating system: Windows-10-10.0.19044-SP0 64 Bits
Graphics card: NVIDIA GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 537.34
Blender Version:
* version: 4.0.0 Alpha, branch: main, commit date: 2023-09-21 05:55, hash: `9cc4df8062af` (own build)
* version: 4.0.0 Alpha, branch: main, commit date: 2023-09-21 00:11, hash: `963c0ed5e7b0` (buildbot build)

The file I use for testing is https://download.blender.org/demo/cycles/monster_under_the_bed_sss_demo_by_metin_seven.blend

In order to continue a developer should be able to reproduce it and perhaps perform a bisect to find the commit that causes the change in behavior. As long as we don't have this information there isn't anything we can do about it at this moment.

Perhaps try to update to the latest drivers and see if the issue still occurs.

I am not able to reproduce the issue using ``` Operating system: Windows-10-10.0.19044-SP0 64 Bits Graphics card: Quadro RTX 5000/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 537.34 Blender Version: * version: 4.0.0 Alpha, branch: main, commit date: 2023-09-21 05:55, hash: `9cc4df8062af` (own build) * version: 4.0.0 Alpha, branch: main, commit date: 2023-09-21 00:11, hash: `963c0ed5e7b0` (buildbot build) ``` ``` Operating system: Windows-10-10.0.19044-SP0 64 Bits Graphics card: NVIDIA GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 537.34 Blender Version: * version: 4.0.0 Alpha, branch: main, commit date: 2023-09-21 05:55, hash: `9cc4df8062af` (own build) * version: 4.0.0 Alpha, branch: main, commit date: 2023-09-21 00:11, hash: `963c0ed5e7b0` (buildbot build) ``` The file I use for testing is https://download.blender.org/demo/cycles/monster_under_the_bed_sss_demo_by_metin_seven.blend In order to continue a developer should be able to reproduce it and perhaps perform a bisect to find the commit that causes the change in behavior. As long as we don't have this information there isn't anything we can do about it at this moment. Perhaps try to update to the latest drivers and see if the issue still occurs.
Jeroen Bakker added
Status
Needs Information from User
and removed
Status
Confirmed
labels 2023-09-21 11:14:13 +02:00
Member

BTW, I'm on RTX mobile GPU
For me (in 4.0), crash does not happen when laptop is connected to power supply (This may be irrelevant here)

**System Information**
Operating system: Windows-10-10.0.22000-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 3050 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 532.03
BTW, I'm on RTX mobile GPU For me (in 4.0), crash does not happen when laptop is connected to power supply (This may be irrelevant here) ``` **System Information** Operating system: Windows-10-10.0.22000-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 3050 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 532.03 ```
Member

I do have access to a laptop with Windows and GPU. But it doesn't have a development environment installed. Will try to reproduce it on that machine, if reproducable will try to install a development environment for bisecting.

I do have access to a laptop with Windows and GPU. But it doesn't have a development environment installed. Will try to reproduce it on that machine, if reproducable will try to install a development environment for bisecting.
Jeroen Bakker added
Status
Needs Info from Developers
and removed
Status
Needs Information from User
labels 2023-09-28 15:08:39 +02:00
Jeroen Bakker added
Priority
Normal
Type
Known Issue
and removed
Priority
High
Type
Report
labels 2023-10-23 14:26:08 +02:00
Member

I haven't been able to reproduce. But looking at the information provided this seems to originate from a driver bug/issue what we might have triggered by reorganizing some code somewhere. We need to be able to reproduce the issue, to locate the code that change this behavior.

For now I am lowering the priority and marking it as a known issue. If someone with a system that fails is able to perform a bi-sect we can continue investigating the issue.

I haven't been able to reproduce. But looking at the information provided this seems to originate from a driver bug/issue what we might have triggered by reorganizing some code somewhere. We need to be able to reproduce the issue, to locate the code that change this behavior. For now I am lowering the priority and marking it as a known issue. If someone with a system that fails is able to perform a bi-sect we can continue investigating the issue.
Jeroen Bakker added this to the EEVEE & Viewport project 2023-10-23 14:29:24 +02:00
Jeroen Bakker removed their assignment 2023-10-25 14:54:16 +02:00

I discovered this issue might be related to the BlenderKit add-on. In another bug report that I reported where Blender crashes, I discovered that enabling BlenderKit is a problem.

You can read my latest comment directly here: #120352 (comment)

I’m updating this bug report as my original report was marked closed as a duplicate of what appeared to be the same issue. You can see my original report here: #119748

Maybe it will provide new information if you investigate the BlenderKit issue.

I discovered this issue might be related to the BlenderKit add-on. In another bug report that I reported where Blender crashes, I discovered that enabling BlenderKit is a problem. You can read my latest comment directly here: https://projects.blender.org/blender/blender/issues/120352#issuecomment-1165408 I’m updating this bug report as my original report was marked closed as a duplicate of what appeared to be the same issue. You can see my original report here: https://projects.blender.org/blender/blender/issues/119748 Maybe it will provide new information if you investigate the BlenderKit issue.
Member

I was able to reproduce with factory defaults.

I was able to reproduce with factory defaults.
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 Assignees
6 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#112146
No description provided.