CUDA Illegal address errors Windows #52572

New Issue

Danny Gonzalez · 2017-08-28T19:26:26+02:00

Danny Gonzalez commented

2017-08-28 19:26:26 +02:00

System Information
Windows 10, NVidia GTX 1060 6GB

Blender Version
Broken: 2.79 release candidate 2

Short description of error
Rendering or even going into rendered view yields "Cuda error: Illegal address in cuCTxSynchronize(), line 1372"

Exact steps for others to reproduce the error
It's as simple as place an object in, add material/add details, go into rendered view at 32 samples or render at 128 samples.

**System Information** Windows 10, NVidia GTX 1060 6GB **Blender Version** Broken: 2.79 release candidate 2 **Short description of error** Rendering or even going into rendered view yields "Cuda error: Illegal address in cuCTxSynchronize(), line 1372" **Exact steps for others to reproduce the error** It's as simple as place an object in, add material/add details, go into rendered view at 32 samples or render at 128 samples.

Danny Gonzalez commented

2017-08-28 19:26:26 +02:00

Changed status to: 'Open'

Danny Gonzalez commented

2017-08-28 19:26:26 +02:00

Added subscriber: @FlameoHotman

blender-admin commented

2017-08-28 19:26:26 +02:00

#52487 was marked as duplicate of this issue

blender-admin commented

2017-08-28 19:26:26 +02:00

#53075 was marked as duplicate of this issue

blender-admin commented

2017-08-28 19:26:26 +02:00

#53072 was marked as duplicate of this issue

Ray molenkamp commented

2017-08-28 19:29:12 +02:00

Added subscriber: @LazyDodo

Ray molenkamp commented

2017-08-28 19:29:12 +02:00

when you check the windows event log around the time you get this error are there any mentions of Event ID 4101 ( Display Driver Timeout ) ? Also is this branched path tracing by any chance?

Stefan Eisenreich commented

2017-08-29 15:41:56 +02:00

Added subscriber: @stefan.eisenreich98

Stefan Eisenreich commented

2017-08-29 15:54:09 +02:00

In #52572#455414, @LazyDodo wrote:
when you check the windows event log around the time you get this error are there any mentions of Event ID 4101 ( Display Driver Timeout ) ? Also is this branched path tracing by any chance?

Same GPU, same version of Blender, same error here.
Event ID is 1001, it's named "LiveKernelEvent".
I'm not using branched path tracing.

> In #52572#455414, @LazyDodo wrote: > when you check the windows event log around the time you get this error are there any mentions of Event ID 4101 ( Display Driver Timeout ) ? Also is this branched path tracing by any chance? Same GPU, same version of Blender, same error here. Event ID is 1001, it's named "LiveKernelEvent". I'm not using branched path tracing.

Bastien Montagne commented

2017-09-05 12:57:30 +02:00

Added subscriber: @mont29

Bastien Montagne commented

2017-09-05 12:57:30 +02:00

Please also check those points:

Give us your exact Blender, OS and GPU (including drivers) versions, as requested in the template!
Ensure both your OS and drivers are fully up-to-date (and use official GPU drivers, not those provided by windows or tablet/laptop maker).
Try to start Blender in factory settings (--factory-startup commandline option) (this will ensure whether this is a userpref or addon issue or not).
Launch Blender from the command line with --debug-cycles option and attach as text file here any error printed out in the console (do not paste it directly in comment).

Please also check those points: * Give us your exact Blender, OS and GPU (including drivers) versions, as requested in the template! * Ensure both your OS and drivers are fully up-to-date (and use official GPU drivers, not those provided by windows or tablet/laptop maker). * Try to start Blender in factory settings (`--factory-startup` commandline option) (this will ensure whether this is a userpref or addon issue or not). * Launch Blender from the command line with `--debug-cycles` option and **attach as text file** here any error printed out in the console (**do not** paste it directly in comment).

Stefan Eisenreich commented

2017-09-13 02:01:03 +02:00

Okay, so I waited for the release to test this again.
It's still there. I'll try to find all the points:
Blender version 2.79 (I don't know if there's more to it, it's the full release from today).
Windows 10 Version 1607 (Build 14393.1715)
Nvidia GeForce GTX 1060 6GB (Asus ROG STRIX-GTX1060-O6G-GAMING to be precise) with driver version 385.41
GPU drivers are the official ones. They're up-to date, OS as well.
Starting in factory settings (well, plus activating CUDA in user preferences) still brings about this error.
Attached is the error log from the console (I only included the stuff that said "error").
Blender Error.txt

Okay, so I waited for the release to test this again. It's still there. I'll try to find all the points: Blender version 2.79 (I don't know if there's more to it, it's the full release from today). Windows 10 Version 1607 (Build 14393.1715) Nvidia GeForce GTX 1060 6GB (Asus ROG STRIX-GTX1060-O6G-GAMING to be precise) with driver version 385.41 GPU drivers are the official ones. They're up-to date, OS as well. Starting in factory settings (well, plus activating CUDA in user preferences) still brings about this error. Attached is the error log from the console (I only included the stuff that said "error"). [Blender Error.txt](https://archive.blender.org/developer/F793450/Blender_Error.txt)

Bastien Montagne commented

2017-09-13 08:11:50 +02:00

Thanks, let's see what our Cycles experts have to say here.

Sergey Sharybin was assigned by Bastien Montagne

2017-09-13 08:13:12 +02:00

Bastien Montagne commented

2017-09-13 08:13:12 +02:00

Added subscribers: @Sergey, @brecht

Sergey Sharybin commented

2017-09-13 09:27:53 +02:00

Please attach simple .blend file which demonstrates the issue. From the log i can see it's trying to use denoising, which is definitely not enabled by default and is lacking any mention in steps to reproduce the error.

Stefan Eisenreich commented

2017-09-15 17:00:32 +02:00

Sorry, my bad. I tested out the denoiser and forgot to turn it off for the error log. The error was 100% reproducable both with denoiser on and off but I tested again today and I couldn't reproduce it a single time. I made no updates to my Windows version, drivers or Blender version so I don't really understand why this is gone. I attached the .blend file anyway.
Clouds.blend

Sorry, my bad. I tested out the denoiser and forgot to turn it off for the error log. The error was 100% reproducable both with denoiser on and off but I tested again today and I couldn't reproduce it a single time. I made no updates to my Windows version, drivers or Blender version so I don't really understand why this is gone. I attached the .blend file anyway. [Clouds.blend](https://archive.blender.org/developer/F803116/Clouds.blend)

Stefan Eisenreich commented

2017-09-15 19:08:53 +02:00

Update:
I tried to get to the bottom of this since it seemed very strange that this issue suddenly vanished.
Now, since I use this PC mainly for gaming I have routinely overclocked my GPU as far as I could. I have of course tested the stability of this in games so my setup should be stable at all times. When I made the tests earlier this day I hadn't noticed that msi Afterburner had reset my overclocking settings.
Testing out further I found that only the core clock offset seemed to cause this issue, when I raised only the memory clock it rendered just fine.
So there, that's propably where the problem comes from.
I did all my testing with the .blend file from the previous post (denoiser disabled).

Update: I tried to get to the bottom of this since it seemed very strange that this issue suddenly vanished. Now, since I use this PC mainly for gaming I have routinely overclocked my GPU as far as I could. I have of course tested the stability of this in games so my setup should be stable at all times. When I made the tests earlier this day I hadn't noticed that msi Afterburner had reset my overclocking settings. Testing out further I found that only the core clock offset seemed to cause this issue, when I raised only the memory clock it rendered just fine. So there, that's propably where the problem comes from. I did all my testing with the .blend file from the previous post (denoiser disabled).

Maeldor commented

2017-09-17 20:03:10 +02:00

Added subscriber: @Maeldor

Maeldor commented

2017-09-17 20:03:10 +02:00

I am also getting the CUDA error: Illegal address in cuCtxSynchronize(), line 1372 error on the majority scenes I attempt to render via GPU (e.g. BMW Benchmark, Racing Car, etc.). Unfortunately, it's making GPU rendering unusable for me, as I can't tell from one render to another if it's going to crash, and it requires a complete restart of Blender to be able to attempt rendering again.

My setup:

Blender 2.79 (also happens on 2.78c)
Windows 10 Pro (64-bit) v1703 (build 15063.608)
MSI GTX 1080 TI SEA HAWK X (11 GB) - Driver version 385.41

It seems to happen more often with higher tile sizes and resolutions (still happens even as low as 128x128 tile size and lower, though) in sufficiently complex scenes, such as the demo files mentioned above. It also happens regardless of overclocking, no overclocking, or even underclocking of both core clock and memory clock (so no luck compared to Stefan's latest comment above). Various games and burn tests, and overall system, are completely stable. I have even underclocked the core clock by as much as -400 MHz and memory clock by -500 MHz (lowest I can take them) and it still happens. I could not replicate with the above Clouds.blend file, however, regardless of tile size and resolution.

Here is the complete output debug log for the BMW Benchmark (bmw27_gpu.blend, with no settings changed whatsoever) with "--factory-startup --debug-cycles" (seems very similar to Stefan's): cycles-debug.txt

Event logs under System for nvlddmkm with ID of 13 at time of above error:

\Device\UVMLiteProcess12
Graphics SM Warp Exception on (GPC 1, TPC 0): Out Of Range Address

\Device\UVMLiteProcess12
Graphics Exception: ESR 0x50c648=0x100000e 0x50c650=0x0 0x50c644=0xd3eff2 0x50c64c=0x17f

I have tried with and without TDR on (TdrDelay set higher, and also TdrLevel set to 0) with no difference.

Here are some other event logs I've had for other scenes earlier today:

\Device\UVMLiteProcess4
NVRM: Graphics TEX Exception on (GPC 4, TPC 0): TEX NACK / Page Fault

\Device\UVMLiteProcess4
Variable String too Large

\Device\UVMLiteProcess4
Graphics Exception: ESR 0x524224=0x80000000 0x524228=0x0 0x52422c=0x0 0x524234=0x0

\Device\UVMLiteProcess4
NVRM: Graphics TEX Exception on (GPC 5, TPC 2): TEX NACK / Page Fault

Help would be greatly appreciated as I am at a complete loss with what to do about GPU rendering. Please let me know if I can provide any more info or if I should create a separate issue.

I am also getting the **CUDA error: Illegal address in cuCtxSynchronize(), line 1372** error on the majority scenes I attempt to render via GPU (e.g. BMW Benchmark, Racing Car, etc.). Unfortunately, it's making GPU rendering unusable for me, as I can't tell from one render to another if it's going to crash, and it requires a complete restart of Blender to be able to attempt rendering again. My setup: > Blender 2.79 (also happens on 2.78c) > Windows 10 Pro (64-bit) v1703 (build 15063.608) > MSI GTX 1080 TI SEA HAWK X (11 GB) - Driver version 385.41 It seems to happen more often with higher tile sizes and resolutions (still happens even as low as 128x128 tile size and lower, though) in sufficiently complex scenes, such as the demo files mentioned above. It also happens regardless of overclocking, no overclocking, or even underclocking of both core clock and memory clock (so no luck compared to Stefan's latest comment above). Various games and burn tests, and overall system, are completely stable. I have even underclocked the core clock by as much as -400 MHz and memory clock by -500 MHz (lowest I can take them) and it still happens. I could not replicate with the above **Clouds.blend** file, however, regardless of tile size and resolution. Here is the complete output debug log for the BMW Benchmark (**bmw27_gpu.blend**, with no settings changed whatsoever) with *"--factory-startup --debug-cycles"* (seems very similar to Stefan's): [cycles-debug.txt](https://archive.blender.org/developer/F807864/cycles-debug.txt) Event logs under System for **nvlddmkm** with ID of 13 at time of above error: > \Device\UVMLiteProcess12 > Graphics SM Warp Exception on (GPC 1, TPC 0): Out Of Range Address > \Device\UVMLiteProcess12 > Graphics Exception: ESR 0x50c648=0x100000e 0x50c650=0x0 0x50c644=0xd3eff2 0x50c64c=0x17f I have tried with and without [TDR ](https://docs.microsoft.com/en-us/windows-hardware/drivers/display/tdr-registry-keys) on (**TdrDelay** set higher, and also **TdrLevel** set to 0) with no difference. Here are some other event logs I've had for other scenes earlier today: > \Device\UVMLiteProcess4 > NVRM: Graphics TEX Exception on (GPC 4, TPC 0): TEX NACK / Page Fault > \Device\UVMLiteProcess4 > Variable String too Large > \Device\UVMLiteProcess4 > Graphics Exception: ESR 0x524224=0x80000000 0x524228=0x0 0x52422c=0x0 0x524234=0x0 > \Device\UVMLiteProcess4 > NVRM: Graphics TEX Exception on (GPC 5, TPC 2): TEX NACK / Page Fault Help would be greatly appreciated as I am at a complete loss with what to do about GPU rendering. Please let me know if I can provide any more info or if I should create a separate issue.

Sergey Sharybin commented

2017-09-18 08:27:55 +02:00

@stefan.eisenreich98, we can not guarantee Blender to work on overclocked GPUs. There is a good reason why vendors didn't use higher frequencies to begin with. Fact that games are stable doesn't really mean much here, CUDA program will stress GPU much more than OpenGL/DirectX.

@Maeldor, did you try rendering default cube on GPU? Did you try installing driver downloaded directly from nvidia.com ?

@brecht, i'm away from my main desktop currently. Did you happen to have Pascal+Windows configuration handy? :)

@stefan.eisenreich98, we can not guarantee Blender to work on overclocked GPUs. There is a good reason why vendors didn't use higher frequencies to begin with. Fact that games are stable doesn't really mean much here, CUDA program will stress GPU much more than OpenGL/DirectX. @Maeldor, did you try rendering default cube on GPU? Did you try installing driver downloaded directly from nvidia.com ? @brecht, i'm away from my main desktop currently. Did you happen to have Pascal+Windows configuration handy? :)

Maeldor commented

2017-09-18 14:36:46 +02:00

Thanks for your quick reply!

In #52572#460489, @Sergey wrote:>
@Maeldor, did you try rendering default cube on GPU? Did you try installing driver downloaded directly from nvidia.com ?

I can typically render simple things without issue (so the default cube scene is likely to never cause a problem), but as I mentioned:

It seems to happen more often with higher tile sizes and resolutions (still happens even as low as 128x128 tile size and lower, though) in sufficiently complex scenes

Such a scene being the BMW Benchmark. I've often been able to successfully render it fully at 720p with a tile size of 128x128, but not always guaranteed. The moment I put the tile size or resolution higher, however, it almost guarantees a crash. Other scenes, like the Racing Car , will crash even at settings that low or lower.

Drivers are installed via Geforce Experience, which are latest (385.41).

In #52572#460489, @Sergey wrote:
@stefan.eisenreich98, we can not guarantee Blender to work on overclocked GPUs. There is a good reason why vendors didn't use higher frequencies to begin with. Fact that games are stable doesn't really mean much here, CUDA program will stress GPU much more than OpenGL/DirectX.

This worries me immensely; as I have mentioned, I've tested even with underclocking, but the issue persists while everything else is perfectly stable. Could this suggest a hardware fault? I was hoping it was a bug rather than a problem with my system. I don't even overclock my GPU whatsoever; everything is stock, and despite this, my attempts with underclocks well below stock levels (-400 MHz) still produce the exact same problem.

Are there any Windows utilities that you know of that would let me specifically test the stability of CUDA? I've ran several general GPU stability testers and benchmarks (FurMark, 3DMark, Heaven, Superposition, etc.), for extended periods and they are all perfectly fine, but if you suggest CUDA is different, it would be good to be able to test this specifically.

Thanks!

Thanks for your quick reply! > In #52572#460489, @Sergey wrote:> > @Maeldor, did you try rendering default cube on GPU? Did you try installing driver downloaded directly from nvidia.com ? I can typically render simple things without issue (so the default cube scene is likely to never cause a problem), but as I mentioned: > It seems to happen more often with higher tile sizes and resolutions (still happens even as low as 128x128 tile size and lower, though) **in sufficiently complex scenes** Such a scene being the BMW Benchmark. I've often been able to successfully render it fully at 720p with a tile size of 128x128, but not always guaranteed. The moment I put the tile size or resolution higher, however, it almost guarantees a crash. Other scenes, like the [Racing Car ](https://download.blender.org/demo/test/splash-pokedstudio.blend.zip), will crash even at settings that low or lower. Drivers are installed via Geforce Experience, which are latest (385.41). > In #52572#460489, @Sergey wrote: > @stefan.eisenreich98, we can not guarantee Blender to work on overclocked GPUs. There is a good reason why vendors didn't use higher frequencies to begin with. Fact that games are stable doesn't really mean much here, CUDA program will stress GPU much more than OpenGL/DirectX. This worries me immensely; as I have mentioned, I've tested even with underclocking, but the issue persists while everything else is perfectly stable. Could this suggest a hardware fault? I was hoping it was a bug rather than a problem with my system. I don't even overclock my GPU whatsoever; everything is stock, and despite this, my attempts with underclocks well below stock levels (-400 MHz) still produce the exact same problem. Are there any Windows utilities that you know of that would let me specifically test the stability of CUDA? I've ran several general GPU stability testers and benchmarks (FurMark, 3DMark, Heaven, Superposition, etc.), for extended periods and they are all perfectly fine, but if you suggest CUDA is different, it would be good to be able to test this specifically. Thanks!

Sergey Sharybin commented

2017-09-18 14:43:42 +02:00

@Maeldor, if you don't overclock, then things should be working stable. Root of your issue might be different from @Stef1309.

There is one more thing you can try: render file from console (cmd.exe), something like:

path\to\blender.exe --debug-cycles --factory-startup -y -b path\to\bmw27_cpu.blend -f 1

and see if that works and whether log gives any clues.

@Maeldor, if you don't overclock, then things should be working stable. Root of your issue might be different from @Stef1309. There is one more thing you can try: render file from console (cmd.exe), something like: ``` path\to\blender.exe --debug-cycles --factory-startup -y -b path\to\bmw27_cpu.blend -f 1 ``` and see if that works and whether log gives any clues.

Maeldor commented

2017-09-18 14:48:18 +02:00

In #52572#460567, @Sergey wrote:
@Maeldor, if you don't overclock, then things should be working stable. Root of your issue might be different from @Stef1309.

There is one more thing you can try: render file from console (cmd.exe), something like:

path\to\blender.exe --debug-cycles --factory-startup -y -b path\to\bmw27_cpu.blend -f 1

and see if that works and whether log gives any clues.

Thanks very much! I'll try that when I get home.

I see you've specified the bmw27_cpu.blend file. Is that meant to be CPU or GPU? And I expect --factory-startup will prevent the GPU being picked as the compute device.

> In #52572#460567, @Sergey wrote: > @Maeldor, if you don't overclock, then things should be working stable. Root of your issue might be different from @Stef1309. > > There is one more thing you can try: render file from console (cmd.exe), something like: > > path\to\blender.exe --debug-cycles --factory-startup -y -b path\to\bmw27_cpu.blend -f 1 > > and see if that works and whether log gives any clues. Thanks very much! I'll try that when I get home. I see you've specified the bmw27_**cpu**.blend file. Is that meant to be CPU or GPU? And I expect **--factory-startup** will prevent the GPU being picked as the compute device.

YAFU commented

2017-09-18 14:59:09 +02:00

Added subscriber: @YAFU

YAFU commented

2017-09-18 14:59:09 +02:00

Hi.
I have read before that the mere fact of having installed some GPU overclocking application can bring conflicts with Blender, even for CPU render. I say this because I read above about MSI Afterburner. So just in case to do reliable tests, if you have any of them installed (MSI Afterburner, ASUS GPU Tweak, etc.), completely remove the application.

Hi. I have read before that the mere fact of having installed some GPU overclocking application can bring conflicts with Blender, even for CPU render. I say this because I read above about MSI Afterburner. So just in case to do reliable tests, if you have any of them installed (MSI Afterburner, ASUS GPU Tweak, etc.), completely remove the application.

Sergey Sharybin commented

2017-09-18 15:02:16 +02:00

@Maeldor, yes, should be bmw27_gpu. And you're right about --factory-startup. Let's do this way then: backup your settings, load factory startup, enable CUDA and then try rendering from terminal.

Testing without overlocking/tweaking software will indeed be really handy. I was never able to reproduce any render problems on Windows and NVidia's GTX 1080..

@Maeldor, yes, should be `bmw27_gpu`. And you're right about --factory-startup. Let's do this way then: backup your settings, load factory startup, enable CUDA and then try rendering from terminal. Testing without overlocking/tweaking software will indeed be really handy. I was never able to reproduce any render problems on Windows and NVidia's GTX 1080..

Emmanuel LORANT commented

2017-09-18 15:07:09 +02:00

Added subscriber: @EmmanuelLORANT

Emmanuel LORANT commented

2017-09-18 15:07:09 +02:00

Hi, I have this too.

Specs : Windows 10 Pro x64, Blender 2.79 x64 Official Release, GPU for rendering : GTX 1080 Ti 11 Gb (no overclocking or anything at all) with 385.28 drivers version.

For now, it just does me on a scene with 5 large trees (about 8.8 millions tris). It start the rendered mod but stop at 2/32 samples. Once it failed, I cannot relauch a render, I have to close Blender. I also tried to delete 4 of the 5 trees before lauching the rendered mode but it failed too (even if I save the file with only one tree and reopen Blender).
If I append the tree in a new scene, it works. If I append the 5 trees, the rendered mode stops at 11/32 samples.

I don't know if it can help but I made screeshots of console log :

Hi, I have this too. Specs : Windows 10 Pro x64, Blender 2.79 x64 Official Release, GPU for rendering : GTX 1080 Ti 11 Gb (no overclocking or anything at all) with 385.28 drivers version. For now, it just does me on a scene with 5 large trees (about 8.8 millions tris). It start the rendered mod but stop at 2/32 samples. Once it failed, I cannot relauch a render, I have to close Blender. I also tried to delete 4 of the 5 trees before lauching the rendered mode but it failed too (even if I save the file with only one tree and reopen Blender). If I append the tree in a new scene, it works. If I append the 5 trees, the rendered mode stops at 11/32 samples. I don't know if it can help but I made screeshots of console log : ![Capture.JPG](https://archive.blender.org/developer/F812172/Capture.JPG) ![Capture2.JPG](https://archive.blender.org/developer/F812177/Capture2.JPG)

Kayran Schmidt commented

2017-09-21 14:40:35 +02:00

Added subscriber: @Winnetou

Kayran Schmidt commented

2017-09-21 14:40:35 +02:00

hi, I can confirm this error too.
win 10 64 bit
gtx 1080 Overclocked at ~2100MHz when rendering with overclocked VRAM
blender 2.79

(all rendering referred to as being rendered with cycles and gpu)

but when rendering the bmw benchmark even on 1440p with 300 samples and 256x256 tiles (without denoise) I have no crash whatsoever

I reproduce the crash when rendering these two scenes, even with the samples at 50, resolution at 50%:
from https:*www.blender.org/download/demo-files/

production benchmark:
https:*www.blender.org/download/demo-files/

splash of 2.79 (agent 327), here with brached and normal path tracing; with/without denoise
https:*cloud.blender.org/p/gallery/59819ee681191741ad07d283

too complex scenes do not render, even at low settings.
the crash occurs after some tiles rendered.
after the first crash, all rendering crashes immediately at the first tile. restarting blender allowes to render different files again.

hope this helps---

hi, I can confirm this error too. win 10 64 bit gtx 1080 Overclocked at ~2100MHz when rendering with overclocked VRAM blender 2.79 (all rendering referred to as being rendered with cycles and gpu) but when rendering the bmw benchmark even on 1440p with 300 samples and 256x256 tiles (without denoise) I have no crash whatsoever I reproduce the crash when rendering these two scenes, even with the samples at 50, resolution at 50%: from [https:*www.blender.org/download/demo-files/ ](https:*www.blender.org/download/demo-files/) production benchmark: [https:*www.blender.org/download/demo-files/ ](https:*www.blender.org/download/demo-files/) splash of 2.79 (agent 327), here with brached and normal path tracing; with/without denoise [https:*cloud.blender.org/p/gallery/59819ee681191741ad07d283 ](https:*cloud.blender.org/p/gallery/59819ee681191741ad07d283) too complex scenes do not render, even at low settings. the crash occurs after some tiles rendered. after the first crash, all rendering crashes immediately at the first tile. restarting blender allowes to render different files again. hope this helps---

Kayran Schmidt commented

2017-09-22 14:40:59 +02:00

UPDATE:
Yesterday I installed the newest Nvidia Driver: 385.69
this seemed to fix the crash.
agent 327 renders fine on gpu even with larger tile sizes (though 256x256 lead to blender crashing completely -> other topic)

UPDATE: Yesterday I installed the newest Nvidia Driver: 385.69 this seemed to fix the crash. agent 327 renders fine on gpu even with larger tile sizes (though 256x256 lead to blender crashing completely -> other topic)

Maeldor commented

2017-09-22 18:18:06 +02:00

In #52572#461882, @Winnetou wrote:
UPDATE:
Yesterday I installed the newest Nvidia Driver: 385.69
this seemed to fix the crash.
agent 327 renders fine on gpu even with larger tile sizes (though 256x256 lead to blender crashing completely -> other topic)

Was hopeful at reading this, but unfortunately it has made absolutely no difference for me. I even used DDU to reinstall from scratch to be safe, but I'm still having the exact same problem, so I guess you're lucky if you're not having the problem anymore!

In #52572#460567, @Sergey wrote:
@Maeldor, if you don't overclock, then things should be working stable. Root of your issue might be different from @Stef1309.

There is one more thing you can try: render file from console (cmd.exe), something like:

path\to\blender.exe --debug-cycles --factory-startup -y -b path\to\bmw27_cpu.blend -f 1

and see if that works and whether log gives any clues.

Ended up giving this many tries but got the exact same error(s) as before from the previous log. Do you still want an output?

I have also been doing tests all week to try and replicate the issue outside of Blender and have had no luck. I've tried various benchmarks for CUDA that I could find for Windows (Arion Benchmark, Octane Benchmark, NiceHashMiner, etc.) and they all had absolutely no problems. They all stressed the GPU to its limits via CUDA (particularly the hash miner) and none of them had a single error or crash. If you can suggest any other CUDA applications I can try, I'll be happy to also check those (any video transcoders?).

I also did a completely clean reinstall of Windows onto a separate hard drive to be able to start from scratch without any software installed. I installed Blender 2.79, did nothing but set the GPU as the compute device and the tiles to 512x512. I got the error after just a few seconds on the first tile, so it seems it's not related to my installed software.

This problem definitely seems to be specific to Blender only. Any ideas where to go from here?

Thanks!

> In #52572#461882, @Winnetou wrote: > UPDATE: > Yesterday I installed the newest Nvidia Driver: 385.69 > this seemed to fix the crash. > agent 327 renders fine on gpu even with larger tile sizes (though 256x256 lead to blender crashing completely -> other topic) Was hopeful at reading this, but unfortunately it has made absolutely no difference for me. I even used DDU to reinstall from scratch to be safe, but I'm still having the exact same problem, so I guess you're lucky if you're not having the problem anymore! > In #52572#460567, @Sergey wrote: > @Maeldor, if you don't overclock, then things should be working stable. Root of your issue might be different from @Stef1309. > > There is one more thing you can try: render file from console (cmd.exe), something like: > > path\to\blender.exe --debug-cycles --factory-startup -y -b path\to\bmw27_cpu.blend -f 1 > > and see if that works and whether log gives any clues. Ended up giving this many tries but got the exact same error(s) as before from the previous log. Do you still want an output? I have also been doing tests all week to try and replicate the issue outside of Blender and have had no luck. I've tried various benchmarks for CUDA that I could find for Windows (Arion Benchmark, Octane Benchmark, NiceHashMiner, etc.) and they all had absolutely no problems. They all stressed the GPU to its limits via CUDA (particularly the hash miner) and none of them had a single error or crash. If you can suggest any other CUDA applications I can try, I'll be happy to also check those (any video transcoders?). I also did a completely clean reinstall of Windows onto a separate hard drive to be able to start from scratch without any software installed. I installed Blender 2.79, did nothing but set the GPU as the compute device and the tiles to 512x512. I got the error after just a few seconds on the first tile, so it seems it's not related to my installed software. This problem definitely seems to be specific to Blender only. Any ideas where to go from here? Thanks!

Emmanuel LORANT commented

2017-09-22 18:31:34 +02:00

For me, it still even worse with 385.69 NVidia drivers. Blender crashes instead of giving the error and a file that worked with previous version of drivers crashes now :(.

Emmanuel LORANT commented

2017-09-22 19:03:37 +02:00

Well, I got a clue : in my scene, I use Principled BSDF with Subsurface at 1.000. By turning down the Subsurface at 0, it works.

To add precision :

there are 5 trees with for each one one trunk material and 3 leaves material (so 5 x 3 = 15 leaves materials). Leaves material use Subsurface at 1.000. In rendered mode, I raise one by one the subsurface from 0 to 1 and when I raise the 7th, it crashes.
but in another scene with only one tree (so 3 leaves material), only one subsurface at 1 makes Blender crashes. I noticed that the zoom had an importance : if I'm far, it doesn't crash even with 3 subsurfaces at 1.

Hope it helps.

Well, I got a clue : in my scene, I use Principled BSDF with Subsurface at 1.000. By turning down the Subsurface at 0, it works. To add precision : - there are 5 trees with for each one one trunk material and 3 leaves material (so 5 x 3 = 15 leaves materials). Leaves material use Subsurface at 1.000. In rendered mode, I raise one by one the subsurface from 0 to 1 and when I raise the 7th, it crashes. - but in another scene with only one tree (so 3 leaves material), only one subsurface at 1 makes Blender crashes. I noticed that the zoom had an importance : if I'm far, it doesn't crash even with 3 subsurfaces at 1. Hope it helps.

Kayran Schmidt commented

2017-09-23 00:46:05 +02:00

Update:
after some more intensive testing with the other file (production benchmark) I have to withdraw my initial fix report.
the production benchmark is not renderable on the gpu, even with 16x16 tiles, giving the initial error again.
But if the tiles get too big, the error changes to the "not enough memory" error.
however i was able to render the agent327 sucessfully with 128x128 tiles (at 100% of original res) which was impossible before.
sorry

Update: after some more intensive testing with the other file (production benchmark) I have to withdraw my initial fix report. the production benchmark is not renderable on the gpu, even with 16x16 tiles, giving the initial error again. But if the tiles get too big, the error changes to the "not enough memory" error. however i was able to render the agent327 sucessfully with 128x128 tiles (at 100% of original res) which was impossible before. sorry

Brecht Van Lommel commented

2017-09-29 23:47:08 +02:00

I could reproduce some rather random crashes with the official 2.79 release, a GTX 1080 and driver version 385.69 on Windows 10, for example in classroom_gpu.blend. Most of the time it works, but sometimes it crashes almost immediately.

Rendering the "Production Benchmark" (Victor scene) never works here, due to running out of memory. But it didn't work in earlier Blender versions for me either, 8 GB might just not be enough memory to render this scene.

I haven't been able to repro any crash with the latest daily build (97eefc1) so far, but that might be a coincidence since this crash is quite random for me. Can anyone else confirm if there is still a crash in the latest builds?
https://builder.blender.org/download/

I could reproduce some rather random crashes with the official 2.79 release, a GTX 1080 and driver version 385.69 on Windows 10, for example in `classroom_gpu.blend`. Most of the time it works, but sometimes it crashes almost immediately. Rendering the "Production Benchmark" (Victor scene) never works here, due to running out of memory. But it didn't work in earlier Blender versions for me either, 8 GB might just not be enough memory to render this scene. I haven't been able to repro any crash with the latest daily build (97eefc1) so far, but that might be a coincidence since this crash is quite random for me. Can anyone else confirm if there is still a crash in the latest builds? https://builder.blender.org/download/

Maeldor commented

2017-09-30 12:52:58 +02:00

In #52572#463326, @brecht wrote:
I could reproduce some rather random crashes with the official 2.79 release, a GTX 1080 and driver version 385.69 on Windows 10, for example in classroom_gpu.blend. Most of the time it works, but sometimes it crashes almost immediately.

Rendering the "Production Benchmark" (Victor scene) never works here, due to running out of memory. But it didn't work in earlier Blender versions for me either, 8 GB might just not be enough memory to render this scene.

I haven't been able to repro any crash with the latest daily build (97eefc1) so far, but that might be a coincidence since this crash is quite random for me. Can anyone else confirm if there is still a crash in the latest builds?
https://builder.blender.org/download/

Thanks for confirming this, Brecht. I was getting worried it wouldn't be reproduced.

Unfortunately, I have had no luck with the latest build v2.79 e3546a5 (I couldn't find a download link for 97eefc1 specifically). It crashed consistently on the first tile (though typically at a different samples number) in classroom_gpu.blend with my tests: #52572-2017-09-30-v2.79-e3546a5-classroom_gpu.txt

I also thought I'd try v2.8 (e3fe812) just to compare, but no luck there either. With classroom_gpu.blend it crashes without even needing to click render because it automatically renders in the viewport: #52572-2017-09-30-v2.8-e3fe812-classroom_gpu.txt

> In #52572#463326, @brecht wrote: > I could reproduce some rather random crashes with the official 2.79 release, a GTX 1080 and driver version 385.69 on Windows 10, for example in `classroom_gpu.blend`. Most of the time it works, but sometimes it crashes almost immediately. > > Rendering the "Production Benchmark" (Victor scene) never works here, due to running out of memory. But it didn't work in earlier Blender versions for me either, 8 GB might just not be enough memory to render this scene. > > I haven't been able to repro any crash with the latest daily build (97eefc1) so far, but that might be a coincidence since this crash is quite random for me. Can anyone else confirm if there is still a crash in the latest builds? > https://builder.blender.org/download/ Thanks for confirming this, Brecht. I was getting worried it wouldn't be reproduced. Unfortunately, I have had no luck with the latest build v2.79 e3546a5 (I couldn't find a download link for 97eefc1 specifically). It crashed consistently on the first tile (though typically at a different samples number) in `classroom_gpu.blend` with my tests: [#52572-2017-09-30-v2.79-e3546a5-classroom_gpu.txt](https://archive.blender.org/developer/F918228/T52572-2017-09-30-v2.79-e3546a5-classroom_gpu.txt) I also thought I'd try v2.8 (e3fe812) just to compare, but no luck there either. With `classroom_gpu.blend` it crashes without even needing to click render because it automatically renders in the viewport: [#52572-2017-09-30-v2.8-e3fe812-classroom_gpu.txt](https://archive.blender.org/developer/F918229/T52572-2017-09-30-v2.8-e3fe812-classroom_gpu.txt)

Brecht Van Lommel commented

2017-10-16 13:10:59 +02:00

We've now had a couple of similar reports, but currently none of the developers can reproduce this issue. I've tried different scenes, different driver versions, different Windows 10 versions, reinstalling Windows, etc. It all seems stable now, for some reason. It's unclear why there is a problem for some users, while most users seem to have no problem (as evidenced by threads like these ).

There's a few possible causes:

Bug in Cycles that causes it to access invalid memory, either in the kernel itself or in preparing data for the kernel. So far I have found nothing inspecting the code and running tools like valgrind and cuda-memcheck.
Different Nvidia graphics settings. Checking the "clean install" option when installing Nvidia drivers may help.
Corrupted Nvidia graphics installation. We've seen a few cases where Blender and any other application using CUDA crashes due to this, but not this type of error.
Differences in Windows versions or hardware. So far no pattern is visible here.

For now, all I can suggest is to do a totally clean driver install:

Uninstall any NVidia, AMD or Intel graphics drivers
Download latest driver from nvidia.com
Install, with clean install option checked
Reboot computer

Perhaps upgrading to Windows 10 Creators Update (or Fall Creators Update) may indirectly help as well.

We've now had a couple of similar reports, but currently none of the developers can reproduce this issue. I've tried different scenes, different driver versions, different Windows 10 versions, reinstalling Windows, etc. It all seems stable now, for some reason. It's unclear why there is a problem for some users, while most users seem to have no problem (as evidenced by [threads like these ](https://blenderartists.org/forum/showthread.php?439394-The-new-Cycles-GPU-2-79-Benchmark)). There's a few possible causes: * Bug in Cycles that causes it to access invalid memory, either in the kernel itself or in preparing data for the kernel. So far I have found nothing inspecting the code and running tools like valgrind and cuda-memcheck. * Different Nvidia graphics settings. Checking the "clean install" option when installing Nvidia drivers may help. * Corrupted Nvidia graphics installation. We've seen a few cases where Blender and any other application using CUDA crashes due to this, but not this type of error. * Differences in Windows versions or hardware. So far no pattern is visible here. For now, all I can suggest is to do a totally clean driver install: * Uninstall any NVidia, AMD or Intel graphics drivers * Download latest driver from nvidia.com * Install, with clean install option checked * Reboot computer Perhaps upgrading to Windows 10 Creators Update (or Fall Creators Update) may indirectly help as well.

Brecht Van Lommel changed title from ~~CUDA Error~~ to CUDA Illegal address errors Windows

2017-10-17 12:19:31 +02:00

Brecht Van Lommel commented

2017-10-17 12:19:40 +02:00

Added subscribers: @polly2carpets, @moth3r

Maeldor commented

2017-10-20 17:41:27 +02:00

I can confirm that the Fall Creators Update (with clean install of latest drivers, 387.92) has unfortunately not helped the issue, nor any of the recommendations by Brecht in the previous post.

Kayran Schmidt commented

2017-10-20 17:44:51 +02:00

Removed subscriber: @Winnetou

Brecht Van Lommel commented

2017-10-24 11:37:44 +02:00

One more thing to try would be to disabling NVidia Game Overlay in Geforce Experience (if it's enabled), or uninstall Geforce Experience (while keeping the driver).

Brecht Van Lommel commented

2017-11-06 18:10:04 +01:00

Has anyone tested disabling the Game Overlay? We're working with NVidia to resolve an issue with that, but we don't know yet if it's related to this specific crash.

We've also been making quite a few changes to the CUDA implementation in the last month, so latest daily builds may also help:
https://builder.blender.org/download/

Has anyone tested disabling the Game Overlay? We're working with NVidia to resolve an issue with that, but we don't know yet if it's related to this specific crash. We've also been making quite a few changes to the CUDA implementation in the last month, so latest daily builds may also help: https://builder.blender.org/download/

Simon Pollard commented

2017-11-06 21:26:56 +01:00

I've disabled that and still get errors. In fact I've bought a new SSD and installed Windows 10 fresh and with nothing else installed except Blender and the latest nVidia drivers I still get errors.

Brecht Van Lommel commented

2017-11-07 03:42:41 +01:00

Added subscriber: @knutL

Brecht Van Lommel commented

2017-11-07 03:44:26 +01:00

Added subscribers: @Pr3cast, @PsychoFisch

knut lagies commented

2017-11-07 11:37:54 +01:00

on my machine the problem just disappeared without any (known:)) changes from my side.
I did thousands of renderings with cycles on the gpu and everything worked fine now..
Very strange, keep my fingers crossed.

on my machine the problem just disappeared without any (known:)) changes from my side. I did thousands of renderings with cycles on the gpu and everything worked fine now.. Very strange, keep my fingers crossed.

Maeldor commented

2017-11-07 19:20:13 +01:00

Have tried some thorough testing of the benchmarks with the Game Overlay disabled, but it hasn't helped. Using drivers 388.13.

Latest tests over the past couple of days have been with blender-2.79.0-git.8a72be7-windows64 (2017-11-06) and initial results seemed promising. I was able to render bmw27_gpu and pavillon_barcelone_gpu yesterday, and fishy_cat_gpu today, but then failed about just over half way through classroom_gpu straight after :( Unfortunately such inconsistency has been typical the past few weeks. I've been able to successfully render all the benchmarks at one point or another, but not consistently, which rules out actual development and production use.

Error with the above version is now line 1507: CUDA error: Illegal address in cuCtxSynchronize(), line 1507

I can try again with debug via CLI and provide a report if you wish.

Have tried some thorough testing of the benchmarks with the Game Overlay disabled, but it hasn't helped. Using drivers **388.13**. Latest tests over the past couple of days have been with blender-2.79.0-git.8a72be7-windows64 (2017-11-06) and initial results seemed promising. I was able to render `bmw27_gpu` and `pavillon_barcelone_gpu` yesterday, and `fishy_cat_gpu` today, but then failed about just over half way through `classroom_gpu` straight after :( Unfortunately such inconsistency has been typical the past few weeks. I've been able to successfully render all the benchmarks at one point or another, but not consistently, which rules out actual development and production use. Error with the above version is now line **1507:** `CUDA error: Illegal address in cuCtxSynchronize(), line 1507` I can try again with debug via CLI and provide a report if you wish.

Sergey Sharybin removed their assignment 2018-02-07 17:36:06 +01:00

Brecht Van Lommel was assigned by Sergey Sharybin

2018-02-07 17:36:06 +01:00

Sergey Sharybin commented

2018-02-07 17:36:06 +01:00

@brecht, i can not reproduce the error on neither of my machines. If you can look into the issue, that'd be great (AFAIR, you managed to redo the issue). Otherwise, afraid this report should go to hardware related tracker.

Brecht Van Lommel commented

2018-02-07 17:41:43 +01:00

I can't redo this issue anymore, and I never was able to redo it with a more recent build after 2.79. There's also been lots CUDA changes in the meantime, related to using host memory for rendering.

If this is something that is still happening to many users with latest drivers and latest builds, I think it's worth keeping open, but otherwise it can indeed go to the other tracker.

I can't redo this issue anymore, and I never was able to redo it with a more recent build after 2.79. There's also been lots CUDA changes in the meantime, related to using host memory for rendering. If this is something that is still happening to many users with latest drivers and latest builds, I think it's worth keeping open, but otherwise it can indeed go to the other tracker.

Sergey Sharybin commented

2018-02-07 17:48:23 +01:00

@brecht, it doesn't help having reports in main tracker which we can not even reproduce. Also if we can not reproduce issue, we can not fix it, not in reasonable amount of time at least. Someone from the community with a technical skills need to reproduce the issue and provide crucial information or even a patch...

Brecht Van Lommel commented

2018-02-07 17:56:20 +01:00

Well, even if we can't reproduce right now, there's always more things we can try and code we can inspect. But in this case it seems we are mostly out of ideas for now .. so if you want to move it go ahead.

Roy commented

2018-03-31 15:22:09 +02:00

Added subscriber: @RoryOConnor

Roy commented

2018-03-31 15:22:09 +02:00

Hi, I had the same issue for months. It made me crazy and I could not do anything. You might try this solution. Its easy to do and undo.

One day I had a thought that it was possible that the "Nvidia Experience" software might be the culprit, so I un-installed it. and all my crashes in Cuda and memory errors went away!!

Now for me, Blender works perfect! You might try it.

Hi, I had the same issue for months. It made me crazy and I could not do anything. You might try this solution. Its easy to do and undo. One day I had a thought that it was possible that the "Nvidia Experience" software might be the culprit, so I un-installed it. and all my crashes in Cuda and memory errors went away!! Now for me, Blender works perfect! You might try it.

Ralf Maaßen commented

2018-06-18 11:57:17 +02:00

Added subscriber: @RalfMaassen

Ralf Maaßen commented

2018-06-18 11:57:17 +02:00

Uninstalling „Nvidia Experience“ does not fix the problem to me.
Cuda Error in line 1712 still occurs in complex scenes.
I `m using a Zotac GTX1080TI, Windows 7, latest Nvidia driver and all Blender versions (nightly builds, RC and Release versions. Modifying the reg keys does not help also.
Im sure that I did never had this issue with my older graphic card GTX 1080 (without TI)
It seems that some code is not able to get or copy/clean the content into/from the vram which is higher than 8GB (for me the main different to the older card).

Uninstalling „Nvidia Experience“ does not fix the problem to me. Cuda Error in line 1712 still occurs in complex scenes. I `m using a Zotac GTX1080TI, Windows 7, latest Nvidia driver and all Blender versions (nightly builds, RC and Release versions. Modifying the reg keys does not help also. Im sure that I did never had this issue with my older graphic card GTX 1080 (without TI) It seems that some code is not able to get or copy/clean the content into/from the vram which is higher than 8GB (for me the main different to the older card).

Ralf Maaßen commented

2018-06-19 15:49:32 +02:00

Awesome News Brecht!!!!!

The Problem seems fixed for me. I contacted the Zotac Support to get some help.
They answered me that I should try to reduce the clock speed by 50 MHz.
It worked for me. Currently we are analyzing the root cause for the issue. It seems that the power supply is not able to transport enough stable power to the graphiccard which may cause the driver to shutdown and clean the memory which results to the Blender error.

Awesome News Brecht!!!!! The Problem seems fixed for me. I contacted the Zotac Support to get some help. They answered me that I should try to reduce the clock speed by 50 MHz. It worked for me. Currently we are analyzing the root cause for the issue. It seems that the power supply is not able to transport enough stable power to the graphiccard which may cause the driver to shutdown and clean the memory which results to the Blender error.

Riccardo Giovanetti commented

2018-06-20 10:51:52 +02:00

Added subscriber: @Harvester

Riccardo Giovanetti commented

2018-06-20 10:51:52 +02:00

I started experiencing such an issue after I updated one week ago my Win10 Pro 64bit OS from Build 1511 to 1803 on an ASUS G752VS notebook (NVIDIA GeForce 1070), and then I updated the Nvidia Graphics drivers to the latest version. Reinstalling the graphics drivers (398.11) with a clean install didn't fix the issue. The error appears randomly when switching the 3D View to Rendered mode; closing and restarting blender and re-opening the same .blend project file sometimes it allows the GPU to render without errors.
The Blender version is 2.79b 64bit official portable release; the same issue appears on the latest buildbot releases 2.79.4.
The following are screenshots of the issue appearing after switching the 3D View to Rendered mode inboth Blender 2.79b and 2.79.4:

In the latter screenshot I first did a full render successfully then I tried to switch the 3D View to Rendered and the error was triggered. Hope this helps.

Testing several scenes of mine more or less complex, where I never ever had a single issue with Cycles, now the problem occurs randomly at render time and even more frequently when switching to Rendered 3D View mode.

Windows' System log messages show an issue with the NVLDDMKM video driver that had to be restarted, and in the Applications log I found those related to Blender.exe referring to module nvoglv64.dll. The error just before the latter is due to NVIDIA OpenGL Driver caused by a TDR detected and the application closed.

Any suggestions apart from the those above mentioned? Applying factory settings doesn't fix the issue.

I started experiencing such an issue after I updated one week ago my Win10 Pro 64bit OS from Build 1511 to 1803 on an ASUS G752VS notebook (NVIDIA GeForce 1070), and then I updated the Nvidia Graphics drivers to the latest version. Reinstalling the graphics drivers (398.11) with a clean install didn't fix the issue. The error appears randomly when switching the 3D View to Rendered mode; closing and restarting blender and re-opening the same .blend project file sometimes it allows the GPU to render without errors. The Blender version is 2.79b 64bit official portable release; the same issue appears on the latest buildbot releases 2.79.4. The following are screenshots of the issue appearing after switching the 3D View to Rendered mode inboth Blender 2.79b and 2.79.4: ![CudaError_279.jpg](https://archive.blender.org/developer/F3745657/CudaError_279.jpg) ![CudaError_279_4.jpg](https://archive.blender.org/developer/F3745799/CudaError_279_4.jpg) In the latter screenshot I first did a full render successfully then I tried to switch the 3D View to Rendered and the error was triggered. Hope this helps. Testing several scenes of mine more or less complex, where I never ever had a single issue with Cycles, now the problem occurs randomly at render time and even more frequently when switching to Rendered 3D View mode. Windows' System log messages show an issue with the NVLDDMKM video driver that had to be restarted, and in the Applications log I found those related to Blender.exe referring to module nvoglv64.dll. The error just before the latter is due to NVIDIA OpenGL Driver caused by a TDR detected and the application closed. Any suggestions apart from the those above mentioned? Applying factory settings doesn't fix the issue.

Riccardo Giovanetti commented

2018-06-20 17:56:55 +02:00

After further research I found this article: Preventing Cycles Crash after CUDA timeout

So, I duly modified the registry in Win10 adding that value (TdrDelay, it was not there) set at 8 (decimal) then rebooted and ... I tested again all those scenes/projects that previously raised the issue, without getting a single Cycles/CUDA error in the Blender's console. Not sure it can be extended also to others but here it is how I (hopefully) solved my problem. I will continue to test both rendering and viewport render mode with more projects (the biggest one being the Piper's Alley scene with more than 300 textures and approx 6GB of VRAM usage which rendered successfully).

After further research I found this article: [Preventing Cycles Crash after CUDA timeout ](http://artificialflight.org/blog/2013/cycles-crash-cuda-tdr-error/) So, I duly modified the registry in Win10 adding that value (TdrDelay, it was not there) set at 8 (decimal) then rebooted and ... I tested again all those scenes/projects that previously raised the issue, without getting a single Cycles/CUDA error in the Blender's console. Not sure it can be extended also to others but here it is how I (hopefully) solved my problem. I will continue to test both rendering and viewport render mode with more projects (the biggest one being the [Piper's Alley ](http://forums.cgsociety.org/showthread.php?f=185&t=1309021) scene with more than 300 textures and approx 6GB of VRAM usage which rendered successfully).

Brecht Van Lommel commented

2019-05-14 01:08:36 +02:00

Changed status from 'Open' to: 'Archived'

Brecht Van Lommel closed this issue

2019-05-14 01:08:36 +02:00

Brecht Van Lommel commented

2019-05-14 01:08:36 +02:00

It's been a while since we've had reports like this. Assuming it's fixed now due to either updated drivers, newer CUDA compiler or fixes in the kernel.

David Phipps commented

2020-06-05 02:35:44 +02:00

Added subscriber: @DavidPhipps

David Phipps commented

2020-06-05 02:35:44 +02:00

I'm currently experiencing this with Afterburner on a GTX 1080 using MSI Afterburner.

Blender 2.83
OS:10.0.18362 N/A Build 18362
Nvidia Driver 446.14

I'd be happy to provide sys info as needed.

Problem only persists with core clock increased with afterburner as noted above. As a work around I have separate profiles for gaming and rendering.

I'm currently experiencing this with Afterburner on a GTX 1080 using MSI Afterburner. Blender 2.83 OS:10.0.18362 N/A Build 18362 Nvidia Driver 446.14 I'd be happy to provide sys info as needed. Problem only persists with core clock increased with afterburner as noted above. As a work around I have separate profiles for gaming and rendering.

Diana David commented

2020-07-25 15:08:57 +02:00

Added subscriber: @DianaDavid

Diana David commented

2020-07-25 15:08:57 +02:00

Hello.
I'm having the same error here.

Blender 2.83.3
OS:Win7

Nvidia GeForce GTX980
:(

Hello. I'm having the same error here. Blender 2.83.3 OS:Win7 Nvidia GeForce GTX980 :(

Camille commented

2021-01-15 17:26:56 +01:00

Added subscriber: @Ekiwnox

Camille commented

2021-01-15 17:26:56 +01:00

Same error here with the new RTX 3080 from EVGA ...
So what's the deal?

Same error here with the new RTX 3080 from EVGA ... So what's the deal?

Harrison Baillie commented

2021-05-31 15:19:38 +02:00

Added subscriber: @harrisonbaillie

Harrison Baillie commented

2021-05-31 15:19:38 +02:00

Been having this exact problem for just over two weeks, and has seriously affected my workflow. I've deployed every fix mentioned in this thread to no avail, across multiple stable and experimental builds of Blender.

Urgently need a fix that actually works.

Been having this exact problem for just over two weeks, and has seriously affected my workflow. I've deployed every fix mentioned in this thread to no avail, across multiple stable and experimental builds of Blender. Urgently need a fix that actually works.

Sarah commented

2021-06-19 20:10:35 +02:00

Added subscriber: @shbadr

Sarah commented

2021-06-19 20:10:35 +02:00

I have this problem too, on both 2.93 and 2.92. It's wildly inconsistent, as the same exact frame can render or lead to crash.
Using an RTX 3070 from Gigabyte, all drivers up-to-date. Only other observation is that power usage appears very high in task manager.
Really frustrating that no fix seems to have worked so far.

I have this problem too, on both 2.93 and 2.92. It's wildly inconsistent, as the same exact frame can render or lead to crash. Using an RTX 3070 from Gigabyte, all drivers up-to-date. Only other observation is that power usage appears very high in task manager. Really frustrating that no fix seems to have worked so far.

Sarah commented

2021-06-19 21:40:42 +02:00

Update: Looks like it's working okay on 3.0 alpha, fingers crossed.