BugReport How to solve this problem?

Forums: BugReport How to solve this problem?
A public forum for discussing and asking questions about OctaneVR.

BugReport How to solve this problem?

Postby Dadz » Tue Feb 22, 2022 3:10 pm

Dadz Tue Feb 22, 2022 3:10 pm
Hello, I have an untimely crash of octane render, I can't solve the problem.

Help would be welcome :)

Here is the bugreport text file, I didn't manage to paste the whole text


https://mega.nz/file/JQ8RRaDS#AIBkYkCep ... Gqr3FwT8UM




CINEMA_4D_Crash_Report_WINDOWS
{
Call_Stacks
{
Call_Stack_Thread_11596
{
octane.dll: Octane::isGreyscalePass + 0x494851 (SP: 0x00000027705FD400, PC: 0x00007FFD51098BA1)
octane.dll: Octane::isGreyscalePass + 0x490183 (SP: 0x00000027705FD460, PC: 0x00007FFD510944D3)
octane.dll: Octane::ApiNode::create + 0xe2 (SP: 0x00000027705FD4E0, PC: 0x00007FFD50A6E922)
c4dOctane-R25.xdl64: 0x00007FFDB0D4B987 (SP: 0x00000027705FD5A0, PC: 0x00007FFDB0D4B987)
c4dOctane-R25.xdl64: 0x00007FFDB0D4B8CD (SP: 0x00000027705FD5E0, PC: 0x00007FFDB0D4B8CD)
c4dOctane-R25.xdl64: 0x00007FFDB0D5A917 (SP: 0x00000027705FD620, PC: 0x00007FFDB0D5A917)
c4dOctane-R25.xdl64: 0x00007FFDB0D4E37A (SP: 0x00000027705FEC20, PC: 0x00007FFDB0D4E37A)
c4dOctane-R25.xdl64: 0x00007FFDB0D556C0 (SP: 0x00000027705FF220, PC: 0x00007FFDB0D556C0)
c4dOctane-R25.xdl64: 0x00007FFDB0F26AC3 (SP: 0x00000027705FF400, PC: 0x00007FFDB0F26AC3)
c4dOctane-R25.xdl64: 0x00007FFDB0F21316 (SP: 0x00000027705FF640, PC: 0x00007FFDB0F21316)
c4dplugin.xdl64: Ordinal0 + 0x8ee215 (SP: 0x00000027705FF6B0, PC: 0x00007FFDC7CEE215)
c4d_viewport_render.xdl64: Ordinal0 + 0x1733bc (SP: 0x00000027705FF700, PC: 0x00007FFDB13333BC)
drawport_directx.module.xdl64: Ordinal0 + 0x79710 (SP: 0x00000027705FF7C0, PC: 0x00007FFDC3F69710)
drawport_directx.module.xdl64: Ordinal0 + 0x7d422 (SP: 0x00000027705FF8C0, PC: 0x00007FFDC3F6D422)
c4d_viewport_render.xdl64: Ordinal0 + 0x172711 (SP: 0x00000027705FF910, PC: 0x00007FFDB1332711)
c4d_viewport_render.xdl64: Ordinal0 + 0x173125 (SP: 0x00000027705FF9F0, PC: 0x00007FFDB1333125)
c4d_viewport_render.xdl64: Ordinal0 + 0x8d6ec (SP: 0x00000027705FFA50, PC: 0x00007FFDB124D6EC)
drawport_directx.module.xdl64: Ordinal0 + 0x1be924 (SP: 0x00000027705FFB10, PC: 0x00007FFDC40AE924)
drawport_directx.module.xdl64: Ordinal0 + 0x1c3add (SP: 0x00000027705FFBD0, PC: 0x00007FFDC40B3ADD)
c4d_viewport_render.xdl64: Ordinal0 + 0x88caf (SP: 0x00000027705FFC10, PC: 0x00007FFDB1248CAF)
c4d_viewport_render.xdl64: Ordinal0 + 0x8d10c (SP: 0x00000027705FFCC0, PC: 0x00007FFDB124D10C)
Cinema 4D.exe: MaxonDebugDumpThreadProfile + 0x46e1b9 (SP: 0x00000027705FFD10, PC: 0x00007FF69594FB19)
Cinema 4D.exe: MaxonDebugDumpThreadProfile + 0x47395b (SP: 0x00000027705FFD60, PC: 0x00007FF6959552BB)
Cinema 4D.exe: MaxonDebugDumpThreadProfile + 0x473e5a (SP: 0x00000027705FFDB0, PC: 0x00007FF6959557BA)
Cinema 4D.exe: MaxonDebugDumpThreadProfile + 0x47700c (SP: 0x00000027705FFE20, PC: 0x00007FF69595896C)
ucrtbase.dll: crt_at_quick_exit + 0xb9 (SP: 0x00000027705FFE80, PC: 0x00007FFDFE1CFC99)
KERNEL32.DLL: BaseThreadInitThunk + 0x10 (SP: 0x00000027705FFEB0, PC: 0x00007FFDFF9F54E0)
ntdll.dll: RtlUserThreadStart + 0x2b (SP: 0x00000027705FFEE0, PC: 0x00007FFE00C6485B)
Registers
{
rax: 0x00000027705fd4a0 rbx: 0x00000027705fd4b0 rcx: 0x0000019c566fd688 rdx: 0x00000027705fd4b0
rdi: 0x0000019c566fd688 rsi: 0x0000000000000000 rbp: 0x00007ffd53a5abf0 rsp: 0x00000027705fd400
r8: 0x00000027705fd4a0 r9: 0x0000000000000006 r10: 0x0000000000000000 r11: 0x0000019c418ef640
r12: 0x0000000000000003 r13: 0x0000019c0ae8a380 r14: 0x00000027705fd4a0 r15: 0xffffffffffffffff
eflags: 0x0000000000010206 rip: 0x00007ffd51098ba1 cs: 0x0000000000000033 ds: 0x000000000000002b
es: 0x000000000000002b fs: 0x0000000000000053 gs: 0x000000000000002b ss: 0x000000000000002b
ContextFlags: 0x000000000010005f MxCsr: 0x0000000000009fe0 dr0: 0x0000000000000000 dr1: 0x0000000000000000
dr2: 0x0000000000000000 dr3: 0x0000000000000000 dr6: 0x0000000000000000 dr7: 0x0000000000000000
xmm0: 0x00007ffd000000000000019c418ef460 xmm1: 0x00000000000000000000000000000000 xmm2: 0x6e6f697463656a6f7270205655206873 xmm3: 0x00000000000000000000000000000000
xmm4: 0x00000000000000000000000000000000 xmm5: 0x00000000000000000000000000000000 xmm6: 0x00000000000000004138600f90ded289 xmm7: 0x00000000000000003ff0000000000000
xmm8: 0x00000000000000000000000000000000 xmm9: 0x00000000000000003ff4cccccccccccd xmm10: 0x00000000000000000000000000000000 xmm11: 0x00000000000000000000000000000000
xmm12: 0x00000000000000003ff0000000000000 xmm13: 0x00000000000000003ff7333333333333 xmm14: 0x00000000000000000000000000000000 xmm15: 0x000000000000000041385cef3318fc51

}
Variables
{
ThreadName = unknown
}
}
Call_Stack_Thread_14364
{
ntdll.dll: NtWaitForAlertByThreadId + 0x14 (SP: 0x000000275C4FEF28, PC: 0x00007FFE00D072A4)
ntdll.dll: RtlSleepConditionVariableCS + 0x10a (SP: 0x000000275C4FEF30, PC: 0x00007FFE00CCA2DA)
KERNELBASE.dll: SleepConditionVariableCS + 0x29 (SP: 0x000000275C4FEFA0, PC: 0x00007FFDFE2CD449)
Cinema 4D.exe: MaxonDebugDumpThreadProfile + 0x4872de (SP: 0x000000275C4FEFD0, PC: 0x00007FF695968C3E)
Cinema 4D.exe: MaxonDebugDumpThreadProfile + 0x46d8b8 (SP: 0x000000275C4FF090, PC: 0x00007FF69594F218)
Cinema 4D.exe: MaxonDebugDumpThreadProfile + 0x3b64f2 (SP: 0x000000275C4FF150, PC: 0x00007FF695897E52)
c4d_viewport_render.xdl64: Ordinal0 + 0x8c6c8 (SP: 0x000000275C4FF1B0, PC: 0x00007FFDB124C6C8)
c4dplugin.xdl64: Ordinal0 + 0x8a2184 (SP: 0x000000275C4FF1E0, PC: 0x00007FFDC7CA2184)
c4dplugin.xdl64: Ordinal0 + 0x37f200 (SP: 0x000000275C4FF220, PC: 0x00007FFDC777F200)
c4dplugin.xdl64: Ordinal0 + 0x2fe791 (SP: 0x000000275C4FF2E0, PC: 0x00007FFDC76FE791)
c4dplugin.xdl64: Ordinal0 + 0xc57b27 (SP: 0x000000275C4FF330, PC: 0x00007FFDC8057B27)
c4dplugin.xdl64: Ordinal0 + 0x16ae54e (SP: 0x000000275C4FF4A0, PC: 0x00007FFDC8AAE54E)
c4dplugin.xdl64: Ordinal0 + 0x16aefd5 (SP: 0x000000275C4FF4D0, PC: 0x00007FFDC8AAEFD5)
c4dplugin.xdl64: Ordinal0 + 0x16aedf5 (SP: 0x000000275C4FF540, PC: 0x00007FFDC8AAEDF5)
c4dplugin.xdl64: Ordinal0 + 0x16aed4d (SP: 0x000000275C4FF5A0, PC: 0x00007FFDC8AAED4D)
Cinema 4D.exe: MaxonDebugDumpThreadProfile + 0x2e2bd4 (SP: 0x000000275C4FF600, PC: 0x00007FF6957C4534)
Cinema 4D.exe: MaxonDebugDumpThreadProfile + 0x2e2603 (SP: 0x000000275C4FF740, PC: 0x00007FF6957C3F63)
Cinema 4D.exe: MaxonDebugDumpThreadProfile + 0x2e0d83 (SP: 0x000000275C4FF770, PC: 0x00007FF6957C26E3)
Cinema 4D.exe: MaxonDebugDumpThreadProfile + 0x2de563 (SP: 0x000000275C4FF8A0, PC: 0x00007FF6957BFEC3)
Cinema 4D.exe: MaxonDebugDumpThreadProfile + 0x5d28 (SP: 0x000000275C4FF8D0, PC: 0x00007FF6954E7688)
Cinema 4D.exe: MaxonDebugDumpThreadProfile + 0x4d4 (SP: 0x000000275C4FF970, PC: 0x00007FF6954E1E34)
Cinema 4D.exe: MaxonDebugDumpThreadProfile + 0x1a8a (SP: 0x000000275C4FF9F0, PC: 0x00007FF6954E33EA)
Cinema 4D.exe: MaxonDebugDumpThreadProfile + 0x6e0d (SP: 0x000000275C4FFB00, PC: 0x00007FF6954E876D)
Cinema 4D.exe: MaxonDebugDumpThreadProfile + 0x2d39 (SP: 0x000000275C4FFB30, PC: 0x00007FF6954E4699)
Cinema 4D.exe: MaxonDebugDumpThreadProfile + 0x3430 (SP: 0x000000275C4FFC20, PC: 0x00007FF6954E4D90)
Cinema 4D.exe: MaxonDebugDumpThreadProfile + 0x49c01a (SP: 0x000000275C4FFE90, PC: 0x00007FF69597D97A)
KERNEL32.DLL: BaseThreadInitThunk + 0x10 (SP: 0x000000275C4FFED0, PC: 0x00007FFDFF9F54E0)
ntdll.dll: RtlUserThreadStart + 0x2b (SP: 0x000000275C4FFF00, PC: 0x00007FFE00C6485B)
Registers
{
Dadz
 
Posts: 5
Joined: Tue Nov 16, 2021 3:40 pm

Re: BugReport How to solve this problem?

Postby bepeg4d » Mon Feb 28, 2022 8:35 am

bepeg4d Mon Feb 28, 2022 8:35 am
Sorry c4d bugreport is not enough.

Please, open the scene, then go to c4doctane Settings/Log Output tab, and enable all the Log option checkboxes.
Then, load the scene in Live View, then in Picture Viewer, or until crash, then reopen c4d, navigate to c4doctane Settings/Log Output tab, press the Generate log report button, and share the resulting octanelog_report.zip file, thanks.
Image

ciao,
Beppe
User avatar
bepeg4d
Octane Guru
Octane Guru
 
Posts: 9959
Joined: Wed Jun 02, 2010 6:02 am
Location: Italy

Re: BugReport How to solve this problem?

Postby Dadz » Mon Feb 28, 2022 11:04 am

Dadz Mon Feb 28, 2022 11:04 am
Hello,
Thank you for your feedback,


here is the Bugreport from Octane.

This bug occurs every time I click on the ''Stop and reset render data'' button

Sometimes, clicking on ''pause'' before reset, does not cause an error.


https://mega.nz/folder/xQlgzRyK#oCdDiheY3xMy6r-UIhIDeQ
Dadz
 
Posts: 5
Joined: Tue Nov 16, 2021 3:40 pm

Re: BugReport How to solve this problem?

Postby bepeg4d » Tue Mar 01, 2022 8:09 am

bepeg4d Tue Mar 01, 2022 8:09 am
Hi,
thanks for sharing the log.

1. Please remove the installed c4doctane version and upgrade to 2021.1.3 new stable version.
You can find it by visiting your personal Downloads area:
https://render.otoy.com/account/download_archive.php
Please use 7zip to uncompress the .RAR archive, it is free:
https://www.7-zip.org/

2. The scene is to big for RTX 3080, and ~1.5GB of Out-of-core is already active.
Please disable the RTX 3080, and render only with RTX 3090 for this particular scene, or reduce the complexity of the scene to be able to fit it completely into ~9GB VRAM of RTX 3080.

ciao,
Beppe
User avatar
bepeg4d
Octane Guru
Octane Guru
 
Posts: 9959
Joined: Wed Jun 02, 2010 6:02 am
Location: Italy

Re: BugReport How to solve this problem?

Postby Dadz » Tue Mar 01, 2022 8:47 am

Dadz Tue Mar 01, 2022 8:47 am
Thank you for your advice. I'll go ahead and make the necessary arrangements.

David
Dadz
 
Posts: 5
Joined: Tue Nov 16, 2021 3:40 pm

Re: BugReport How to solve this problem?

Postby Dadz » Tue Mar 01, 2022 2:31 pm

Dadz Tue Mar 01, 2022 2:31 pm
Here I am again :roll: ,

I did update the octane plugin, I'm on another scene, I only had the 3090 activated. Even if the scene was less than 10Gb, I could have activated the 3080, but for the stability test, I prefer to leave only the 3090 for the moment.

I got an error message again, this time just running the octane renderer. I was zooming in on my scene at the same time.



https://mega.nz/folder/xQlgzRyK#oCdDiheY3xMy6r-UIhIDeQ

I'm running on winsows 11, it's all clean from a few days. My pc is not overclocked. I just changed my ram bar, not long ago, I went from 32GB to 128GB vaI had error messages before, but not as many as now.

David
Dadz
 
Posts: 5
Joined: Tue Nov 16, 2021 3:40 pm

Re: BugReport How to solve this problem?

Postby bepeg4d » Wed Mar 02, 2022 8:38 am

bepeg4d Wed Mar 02, 2022 8:38 am
Hi David,
ok, from what you have written, and from the logs, the issues seems not related to c4doctane, but to Nvidia driver.

Please, perform a clean installation of 472.84 Nvidia Studio driver:
https://www.nvidia.com/download/driverR ... 4240/en-us

If this version does not work, please try with the DCH version:
https://www.nvidia.com/download/driverR ... 4239/en-us

To perform a clean installation, please follow these steps:
Image

After reboot, please try to do the same steps and report back, thanks.

ciao,
Beppe
User avatar
bepeg4d
Octane Guru
Octane Guru
 
Posts: 9959
Joined: Wed Jun 02, 2010 6:02 am
Location: Italy

Re: BugReport How to solve this problem?

Postby Dadz » Wed Mar 02, 2022 8:43 am

Dadz Wed Mar 02, 2022 8:43 am
Hello,

That's right, I completely forgot to install these drivers in my new windows installation.

Thanks a lot.

David
Dadz
 
Posts: 5
Joined: Tue Nov 16, 2021 3:40 pm

Return to OctaneVR Questions & Discussion


Who is online

Users browsing this forum: No registered users and 21 guests

Sat Apr 27, 2024 11:04 am [ UTC ]