Announcement

Collapse
No announcement yet.

CUDA error 700

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • CUDA error 700

    Error : C:\CI\cgrepo\vraysdk\samples\vray_plugins\rt_priva te\rt_opencl_(2884) : CUDA error 700

    after this error happens, i can't seem to close 3ds max, or rather it takes a while, or i will end-task it.

    it happens when i use IPR with Vray 6.0 GPU and make adjustments... the last time i was changing forestcolor tint amount on the forest object (it looks like it doesn't work on their presets). the time before, i was changing vray sun and vray sky options (intensity, clouds, the vray sky i had instanced the map into the material editor and was changing intensity etc.)

    funny how that directory doesn't seem to exist on my PC.

    i have not updated to the latest version (released within the last couple of days?), the version of 6.0 that i have is from about 10 days ago?

    my cards are 1080ti hybrids and driver versions are 511.65 studio drivers.

    i do have the latest version of forestpack and railclone (but i'm only using forest in this scene).

    i can't seem to upload an archive b/c the size of the zip file is 8.44mb. hm.

    any thoughts?



  • #2
    For starters, try installing the latest recommended GPU drivers. If the issue persists send the scene so we can take a look. Mention this thread in the message.
    Aleksandar Hadzhiev | chaos.com
    Chaos Support Representative | contact us

    Comment


    • #3
      ok i have updated to the latest version 6 release, i also updated the drivers, but they didn't work at all so reverted to the recommended driver version according to the error message in the log. still getting errors. so this happens while i try starting/stopping IPR - doing changes in the scene and then starting IPR again and it doesn't render. this time around, the 3ds max viewport wouldn't update if i say, zoomed in. or panned left/right/up/down. nice emoji's when i paste the errors hahaha

      [08:39:59.090] Error : C:\CI\cgrepo\vraysdk\samples\vray_plugins\rt_priva te\rt_opencl_(165 : CUDA error 700
      [08:39:59.093] Error : C:\CI\cgrepo\vraysdk\samples\vray_plugins\rt_priva te\rt_opencl_(165 : CUDA error 700

      Comment


      • #4
        Thanks for the provided scene. It doesn't seem to happen on my end (tested with V-Ray 6 hotfix 2), so it should be something on yours. Does it work with RTX? Maybe you can try a clean GPU driver uninstalling with Device Driver Uninstaller. Also, you may try locating the GPU that causes it (if you have multiple, obviously), through the Render Devices Select.
        Aleksandar Hadzhiev | chaos.com
        Chaos Support Representative | contact us

        Comment


        • #5
          well, the 3rd time my whole computer locked up to where i had to dead-restart, i remembered something that happened 4ish years ago. but first, the last time i updated the video card drivers i had no issues with this particular problem. that was about the time i switched over to VRAY 5.0 and figured well something must be different from my old render engine and maybe i was good to go. then i recently updated to the newest approved drivers last week and the problem started happening again.

          the act of updating the nvidia drivers cancels out the fix - this is why i rarely update drivers. but like i said for vray 5 and whatever version i used then, i didn't have the problem so that was probably just good luck.

          ok the problem is, missing a registry entry for MSISupported dword = 1

          i studied this a long time ago and it might just be specific to my 1080ti's or the MOBO, but having IRQ's as POSTIVE values, would crash the cards and the whole PC. it would render 1 or 2 times but then crash. i found the solution on the internet. here are some quick screen shots of the IRQ values before and after the fix to the registry i just implemented. also here are the 4 text files i created so that i can quickly import them into the reg (thankfully our local IT person popped up and enter admin credentials when he has the time)

          [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\P CI\VEN_10DE&DEV_1B06&SUBSYS_66983842&REV_A1\6&1f49 2daf&0&00400018\Device Parameters\Interrupt Management\MessageSignaledInterruptProperties]
          "MSISupported"=dword:00000001

          i just posted one, but this is done for all the cards i have on my machine.

          also, i don't think the exact number is needed as windows will assign whatever is available.

          so far no issues this afternoon!
          Attached Files
          Last edited by s_gru; 25-08-2022, 12:58 PM.

          Comment


          • #6
            well that did not solve the problem. although it hasn't happened since then until now. and now, what i was doing is using IPR with GPU and then switched from 1 camera to a different camera and that's when it happened. also, interestingly, it happened right after i create a forest object with their preset for layered lawn base 3. i hadn't happened before that.

            EDIT: i submitted an archive file of the scene with a new request. thanks. and referenced this thread.
            Last edited by s_gru; 06-09-2022, 02:02 PM.

            Comment


            • #7
              you know, in the scene i just submitted, it definitely happens when i have IPR going and switch from one viewport camera to another. interesting. i don't remember if i was doing that way back at the beginning of this thread.

              Comment


              • #8
                Hey s_gru

                Are you still running into this crash?
                What motherboard do you have?

                Best,
                Muhammed
                Muhammed Hamed
                V-Ray GPU product specialist


                chaos.com

                Comment


                • #9
                  Update, we are able to reproduce this crash on our side. We will have this solved ASAP

                  Best,
                  Muhammed
                  Muhammed Hamed
                  V-Ray GPU product specialist


                  chaos.com

                  Comment


                  • #10
                    Hi I was able to reproduce the issue using the scene we received through the support contact form.

                    The issue is logged under VGPU-5954 in our bug tracking system.
                    Vladimir Krastev | chaos.com
                    Chaos Support Representative | contact us

                    Comment


                    • #11
                      hello. did this get resolved in the latest release? i am still getting the crash, my ticket was closed - not sure if i will still get notified? thanks.

                      Comment

                      Working...
                      X