Access violation in
vk_icdNegotiateLoaderICDInterfaceVersion when putting computer to sleep. #112146
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
Broken: version: 3.6.3 Release Candidate, branch: blender-v3.6-release, commit date: 2023-09-05 15:07, hash:
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
- launch blender.
- open a file
- save it
- 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.
Looks like it crashed in
Probably due to unstable system hardware status when this function is called or something.
"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?
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.
Will try to reproduce and find the commit that altered the behavior. Perhaps that would lead to some clues.
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.
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
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 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.
No due date set.
No dependencies set.
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?