OSError: [WinError 10014] on daemon start: Blender Not responding when opened with Blender Kit

[0lpha]

Describe the bug

Hello, I recently got blender kit and while trying to use blender kit, within 3 seconds of opening blender, my blender tab says Not Responding. I have waited a hour and more but it still doesnt fix. I have all the requirements to run blender and this addon but it just doesnt seem to work. I tried to trouble shooting with the blender trouble shooter and when loading and after leaving i get this log - Rasterization usage warning: Blending is enabled, but is not supported for integer framebuffers. Could you help me out and tell me the solution please, thanks.

Expected behavior

No response

Screenshots/video

Logs

No response

Environment

• BlenderKit version:
• Blender version:
• Operating system:
• additional specifics?

Additional information

No response

[agajdosi]

Hi @0lpha, thank you for the report. It seems that the add-on could be blocked by OS or antivirus, to get more information it would help us, if you could start the Blender from PowerShell and then paste here what Blender printed to the PowerShell. From that we will have more detailed information about the problem. It would be also nice if you could paste a log from C://Users/<your-username>/blenderkit_data/blenderkit-daemon-62485.log.

[0lpha]

Daemon log

(Press CTRL+C to quit)
Accept failed on a socket
socket: <asyncio.TransportSocket fd=524, family=AddressFamily.AF_INET, type=SocketKind.SOCK_STREAM, proto=6, laddr=('127.0.0.1', 62485)>
Traceback (most recent call last):
File "C:\Program Files\Blender Foundation\Blender 3.1\3.1\python\lib\asyncio\proactor_events.py", line 820, in loop
conn, addr = f.result()
File "C:\Program Files\Blender Foundation\Blender 3.1\3.1\python\lib\asyncio\windows_events.py", line 817, in _poll
value = callback(transferred, key, ov)
File "C:\Program Files\Blender Foundation\Blender 3.1\3.1\python\lib\asyncio\windows_events.py", line 566, in finish_accept
return conn, conn.getpeername()
OSError: [WinError 10014] The system detected an invalid pointer address in attempting to use a pointer argument in a call
Task exception was never retrieved
future: <Task finished name='Task-4' coro=<IocpProactor.accept..accept_coro() done, defined at C:\Program Files\Blender Foundation\Blender 3.1\3.1\python\lib\asyncio\windows_events.py:568> exception=OSError(10014, 'The system detected an invalid pointer address in attempting to use a pointer argument in a call', None, 10014, None)>
Traceback (most recent call last):
File "C:\Program Files\Blender Foundation\Blender 3.1\3.1\python\lib\asyncio\windows_events.py", line 571, in accept_coro
await future
File "C:\Program Files\Blender Foundation\Blender 3.1\3.1\python\lib\asyncio\proactor_events.py", line 820, in loop
conn, addr = f.result()
File "C:\Program Files\Blender Foundation\Blender 3.1\3.1\python\lib\asyncio\windows_events.py", line 817, in _poll
value = callback(transferred, key, ov)
File "C:\Program Files\Blender Foundation\Blender 3.1\3.1\python\lib\asyncio\windows_events.py", line 566, in finish_accept
return conn, conn.getpeername()
OSError: [WinError 10014] The system detected an invalid pointer address in attempting to use a pointer argument in a call

I am not sure how to open blender with powershell as it doesnt show for me on my blender open with section. I do not have a "open file with" section when right clicked on blender. Hopefully this is enough or you can tell me how

[0lpha]

Blender debug gpu-

INFO (gpu.debug): Notification : Successfully hooked OpenGL debug callback using OpenGL 4.3
INFO (gpu.debug): Notification : Successfully hooked OpenGL debug callback using OpenGL 4.3
I0921 00:21:23.571852 10968 device.cpp:45] CUEW initialization succeeded
I0921 00:21:23.572852 10968 device.cpp:47] Found precompiled kernels
I0921 00:21:23.585852 10968 device.cpp:68] HIPEW initialization failed: Error opening HIP dynamic library
INFO (gpu.debug): Notification : Texture state usage warning: The texture object (0) bound to texture image unit 0 does not have a defined base level and cannot be used for texture mapping.
INFO (gpu.debug): Notification : Texture state usage warning: The texture object (0) bound to texture image unit 0 does not have a defined base level and cannot be used for texture mapping.
INFO (gpu.debug): Notification : Texture state usage warning: The texture object (0) bound to texture image unit 0 does not have a defined base level and cannot be used for texture mapping.
INFO (gpu.debug): Notification : Texture state usage warning: The texture object (0) bound to texture image unit 0 does not have a defined base level and cannot be used for texture mapping.
INFO (gpu.debug): Notification : Texture state usage warning: The texture object (0) bound to texture image unit 0 does not have a defined base level and cannot be used for texture mapping.
INFO (gpu.debug): Notification : Texture state usage warning: The texture object (0) bound to texture image unit 0 does not have a defined base level and cannot be used for texture mapping.
INFO (gpu.debug): Notification : Texture state usage warning: The texture object (0) bound to texture image unit 0 does not have a defined base level and cannot be used for texture mapping.
INFO (gpu.debug): Notification : Texture state usage warning: The texture object (0) bound to texture image unit 0 does not have a defined base level and cannot be used for texture mapping.
WARN (gpu.debug): : Program/shader state performance warning: Vertex shader in program 207 is being recompiled based on GL state.
WARN (gpu.debug): : Program/shader state performance warning: Vertex shader in program 207 is being recompiled based on GL state, and was not found in the disk cache
INFO (gpu.debug): Notification : Texture state usage warning: The texture object (0) bound to texture image unit 0 does not have a defined base level and cannot be used for texture mapping.
INFO (gpu.debug): Notification : Texture state usage warning: The texture object (0) bound to texture image unit 0 does not have a defined base level and cannot be used for texture mapping.
INFO (gpu.debug): Notification : Texture state usage warning: The texture object (0) bound to texture image unit 0 does not have a defined base level and cannot be used for texture mapping.
WARN (gpu.debug): Workbench : Program/shader state performance warning: Vertex shader in program 207 is being recompiled based on GL state.
WARN (gpu.debug): Workbench : Program/shader state performance warning: Vertex shader in program 207 is being recompiled based on GL state, and was not found in the disk cache
WARN (gpu.debug): Workbench > psl->opaque_ps : Program/shader state performance warning: Vertex shader in program 34 is being recompiled based on GL state.
WARN (gpu.debug): Workbench > psl->opaque_ps : Program/shader state performance warning: Vertex shader in program 34 is being recompiled based on GL state, and was not found in the disk cache
INFO (gpu.debug): Notification : Rasterization usage warning: Blending is enabled, but is not supported for integer framebuffers.
WARN (gpu.debug): Overlay > Outlines : Program/shader state performance warning: Vertex shader in program 149 is being recompiled based on GL state.
WARN (gpu.debug): Overlay > Outlines > psl->outlines_prepass_ps : Program/shader state performance warning: Vertex shader in program 189 is being recompiled based on GL state.
WARN (gpu.debug): Overlay > Outlines > psl->outlines_prepass_ps : Program/shader state performance warning: Vertex shader in program 189 is being recompiled based on GL state, and was not found in the disk cache
WARN (gpu.debug): : Program/shader state performance warning: Geometry shader in program 210 is being recompiled based on GL state, and was not found in the disk cache
INFO (gpu.debug): Notification : Texture state usage warning: The texture object (0) bound to texture image unit 0 does not have a defined base level and cannot be used for texture mapping.

blender debug log-

I0921 00:22:36.876852 17584 device.cpp:45] CUEW initialization succeeded
I0921 00:22:36.877852 17584 device.cpp:47] Found precompiled kernels
I0921 00:22:36.896852 17584 device.cpp:68] HIPEW initialization failed: Error opening HIP dynamic library

[0lpha]

More daemon logs-

(Press CTRL+C to quit)
16:57:58.157 ERROR: Accept failed on a socket
socket: <asyncio.TransportSocket fd=548, family=AddressFamily.AF_INET, type=SocketKind.SOCK_STREAM, proto=6, laddr=('127.0.0.1', 62485)> [base_events.py:1729]
Traceback (most recent call last):
File "C:\Program Files\Blender Foundation\Blender 3.1\3.1\python\lib\asyncio\proactor_events.py", line 820, in loop
conn, addr = f.result()
File "C:\Program Files\Blender Foundation\Blender 3.1\3.1\python\lib\asyncio\windows_events.py", line 817, in _poll
value = callback(transferred, key, ov)
File "C:\Program Files\Blender Foundation\Blender 3.1\3.1\python\lib\asyncio\windows_events.py", line 566, in finish_accept
return conn, conn.getpeername()
OSError: [WinError 10014] The system detected an invalid pointer address in attempting to use a pointer argument in a call
16:57:58.160 ERROR: Task exception was never retrieved
future: <Task finished name='Task-9' coro=<IocpProactor.accept..accept_coro() done, defined at C:\Program Files\Blender Foundation\Blender 3.1\3.1\python\lib\asyncio\windows_events.py:568> exception=OSError(10014, 'The system detected an invalid pointer address in attempting to use a pointer argument in a call', None, 10014, None)> [base_events.py:1729]
Traceback (most recent call last):
File "C:\Program Files\Blender Foundation\Blender 3.1\3.1\python\lib\asyncio\windows_events.py", line 571, in accept_coro
await future
File "C:\Program Files\Blender Foundation\Blender 3.1\3.1\python\lib\asyncio\proactor_events.py", line 820, in loop
conn, addr = f.result()
File "C:\Program Files\Blender Foundation\Blender 3.1\3.1\python\lib\asyncio\windows_events.py", line 817, in _poll
value = callback(transferred, key, ov)
File "C:\Program Files\Blender Foundation\Blender 3.1\3.1\python\lib\asyncio\windows_events.py", line 566, in finish_accept
return conn, conn.getpeername()
OSError: [WinError 10014] The system detected an invalid pointer address in attempting to use a pointer argument in a call

[agajdosi]

Hi @0lpha, thank you for the reports. The OSError: [WinError 10014] could be caused by the fact that port BlenderKit wants to open is already used by another process (info from here: https://stackoverflow.com/questions/51709854/oserror-winerror-10013-an-attempt-was-made-to-access-a-socket-in-a-way-forbid). Please try to select different port in the add-on preferences, it should help. Let me know how it went.

We will cover this error with informative message to the GUI if the change of the port helps.

[0lpha]

Hey, i am unsure how to select a different port. I do not know what a port is or how i can select a different one. If you could help me out with that, it would be great. Thanks

[agajdosi]

Hi @0lpha, sorry for late reply, was on holiday. You can find it in the add-on preferences:

[0lpha]

Hey man, i found where i can change the port, however I cannot change it due to blender not responding instantly whenever i try and turn on the addon. Because of that i cannot click the settings in blender or use blender to change anything while the addon is on. With the addon removed or turned off from deleting it, i cannot access the menu because those settings dont occur when its active. I havent used blenderkit and my subscription is about to end so im very clueless on what to do with this problem.

[0lpha]

Is there a way i can change the port from directory?