Windows 10, Nvidia users
Posted: Thu Mar 21, 2019 2:08 pm
Has anybody had this happening and knows how to fix it?
Not sure if this is film opencl, my driver, or TDR delay 600 seconds or BiDirVM random with mesh emitter light source of 900 triangles.
Windows warning of low memory did not happen.
I think classic BiDir rendered longer, but i don't get how render image is updated in ui like everything is fine, then you turn off monitor go to sleep and when you come back the monitor won't find connection to PC.
I'm using LuxCore standalone version build 7ef5b9e
CPU rendering (BiDirVM random)
film.opencl.enable = 1
NV driver 419.35
Last render output auto saved is at 6.30 o clock, next auto save should have happened 9.30 o clock.
At 7 o clock i get:
At 7.16
At 8.46
At 14 o clock i can't wake up monitor, but computer is running. Had to restart PC.
Not sure if this is film opencl, my driver, or TDR delay 600 seconds or BiDirVM random with mesh emitter light source of 900 triangles.
Windows warning of low memory did not happen.
I think classic BiDir rendered longer, but i don't get how render image is updated in ui like everything is fine, then you turn off monitor go to sleep and when you come back the monitor won't find connection to PC.
I'm using LuxCore standalone version build 7ef5b9e
CPU rendering (BiDirVM random)
film.opencl.enable = 1
NV driver 419.35
Last render output auto saved is at 6.30 o clock, next auto save should have happened 9.30 o clock.
At 7 o clock i get:
Code: Select all
Faulting application name: luxcoreui.exe, version: 0.0.0.0, time stamp: 0x5c916fc6
Faulting module name: ucrtbase.dll, version: 10.0.17134.619, time stamp: 0xf74cf274
Exception code: 0xc0000409Code: Select all
Display driver nvlddmkm stopped responding and has successfully recovered.Code: Select all
Display driver nvlddmkm stopped responding and has successfully recovered