KERNELBASE.dll

292 views
Skip to first unread message

William Asperti

unread,
Oct 26, 2022, 2:18:01 AM10/26/22
to Royal Render Knights Tavern
hi,  last night I tried to send a render on 6 pc tonight
but 1 of these, after 6 layers, make this error in the job log:

R187| Stack trace:

R188| KERNELBASE.dll!RaiseException

R189| redshift-core-cuda-vc140.dll!RSStream::operator=

R190| redshift-core-cuda-vc140.dll!CGCCUDA_CompileLazyKernelFromFile

R191| redshift-core-vc140.dll!RSMaterial::~RSMaterial

R192| redshift-core-vc140.dll!RSMaterial::~RSMaterial

R193| redshift-core-vc140.dll!CGCRingBufferMemPointer::CheckStackBufferMemoryValidity

R194| redshift-core-vc140.dll!CGCRingBufferMemPointer::CheckStackBufferMemoryValidity

R195| redshift-core-vc140.dll!CGCRingBufferMemPointer::CheckStackBufferMemoryValidity

R196| redshift-core-vc140.dll!RSMaterial::~RSMaterial

R197| redshift-core-vc140.dll!RSMaterial::~RSMaterial

R198| redshift-core-vc140.dll!CGCRingBufferMemPointer::CheckStackBufferMemoryValidity

R199| redshift-core-vc140.dll!CGCRingBufferMemPointer::CheckStackBufferMemoryValidity

R200| redshift-core-vc140.dll!CGCRingBufferMemPointer::CheckStackBufferMemoryValidity

R201| redshift-core-vc140.dll!RSMaterial::~RSMaterial

R202| redshift-core-vc140.dll!RSMaterial::~RSMaterial

R203| redshift-core-vc140.dll!CGCRingBufferMemPointer::CheckStackBufferMemoryValidity

R204| redshift-core-vc140.dll!CGCRingBufferMemPointer::CheckStackBufferMemoryValidity

R205| redshift-core-vc140.dll!RS_Renderer_GetShaderDebuggingModeEnabled

R206| redshift-core-vc140.dll!RSUVTILETexture::~RSUVTILETexture

R207| redshift-core-vc140.dll!RS_Renderer_GetMaxNumActiveDevices

R208| ntdll.dll!RtlUserThreadStart

R209|

R210| 00007FFBADADF600

R211| >"C:\Program Files\RoyalRender\lc64\rrCheckexitcode.exe" 2 0 0 1

R212| ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

R213| ++ Oct 26. 01:23.38 Render executable closed ++++++++++++++++++++++++++++++++++++++++++++++++++++

R214| ++ Royal Render checks the return code of the executable or the OS +++++++++++++++++++++++++++++++

R215| ++ Executable returned 2 (0x2) as exit code for frame 1 (jobthread 0). +++++++++++++++++++++++++++

R216| ++ => Executable returned with an error code +++++++++++++++++++++++++++++++++++++++++++++++++++++

R217| ++ 8.3.05 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

R218| ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

R219| +++++++++++++++++++++++++ All commandlines executed +++++++++++++++++++++++++++++++++++

R220| +++++ Alpha rrClient 8.3.06c rrVer8.3.06 NoLVersion

R221| 1:23:38.25

R222| +++++ Job ID: {V26r}

R223| ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++



that not apper on the other layers rendered from  this pc

i must restart the pc and then work for some hours untile the error return

RR, Schoenberger

unread,
Oct 26, 2022, 9:53:21 AM10/26/22
to rrKn...@googlegroups.com

Hi

Kernelbase is not the issue.
It catches an issue and raises an exception.

The issue is Redshift:
    redshift-core-cuda-vc140.dll!CGCCUDA_CompileLazyKernelFromFile

    redshift-core-vc140.dll!RSMaterial::~RSMaterial

    redshift-core-vc140.dll!CGCRingBufferMemPointer::CheckStackBufferMemoryValidity



There is not you can do in Royal Render.

It is a Redshift bug.

The Redshift bug could be caused by a difference on this machine only.

It could be anything, GPU Hardware, driver version, …

CheckStackBufferMemoryValidity() could indicate that the GPU/Machine  has less RAM that your other machines.

 

Either you try to update the driver or contact MAXON.

 

 

regards,
Holger Schönberger

 

Please use the rrKnights Tavern
or our support system for new questions.

Reply all
Reply to author
Forward
0 new messages