Page MenuHome

invalid value in cuMemcpy
Closed, ArchivedPublic

Description

Was rendering ok (well, very slow for Cycles x, taking 5 minutes of pre-render calculations before starting the actual render) but I eventually got a "blender out of memory in cumemcpy" error. So I watched a tutorial on how to fix the issue by adding these keys to the registry:

(both keys have same value, although oddly I chose decimal and set it to 120, but after restarting they changed to hex and the number is 78). After this change I now get "invalid value" error.

In either scenario my scene won't render. It's quite heavy at render time with displacements and fog.

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

Blender Version
Broken: version: 3.0.0 Alpha, branch: cycles-x, commit date: 2021-09-10 16:35, hash: rB0a8a190c819a
Worked: (newest version of Blender that worked as expected)

Short description of error
Can't render using GPU

Exact steps for others to reproduce the error
When I render I get this error

Event Timeline

This sometimes happens to me as well (same error). From what I read, it happens when you go out of vram (my gpu has 6gb of vram).
I don't know how to avoid it, but when it happens to me i just close and re-open the .blend file and it solves the problem. Other thing you can do is to download the 3.0 alpha master branch (most recent).
I hope this helps you.

This sometimes happens to me as well (same error). From what I read, it happens when you go out of vram (my gpu has 6gb of vram).
I don't know how to avoid it, but when it happens to me i just close and re-open the .blend file and it solves the problem. Other thing you can do is to download the 3.0 alpha master branch (most recent).
I hope this helps you.

I found out it's when you use two graphics cards. Not ideal to just use one though as it slows down render time. Something that needs investigating though.

Evan Wilson (EAW) closed this task as Archived.Sep 15 2021, 2:59 AM

Thanks for the report. It appears that this is reporting on a feature branch.

Feature branches might include (partially) broken or missing functionality (which most of the time developers are already aware of). For this reason, bugs in feature branches are not handled on the bug tracker.

Please also test this on the master branch and if the issue is present there as well, please submit a new report for this.