Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Maka

Pages: [1]
1
[Max] Bug Reporting / Re: Corona 11, 3ds max 2024 crash
« on: 2024-06-27, 17:50:46 »
Hi thank you for answering.
Can you please explain this more? I 'm not sure I know what you mean.
I have used "Render Overrides" before whenever I am sending clay renders to my client.
So I overwrite everything with some basic white Corona Physical Mat. and under Preserve I select: displacement, bump, light, opacity and glass material.
Is that what you had in mind?
Unfortunately when set up like that it still crashes...

2
[Max] Bug Reporting / Re: Corona 11, 3ds max 2024 crash
« on: 2024-06-26, 19:35:45 »
Hi

I have the same issue too.
did you find any solution or culprit for this error?


it is my error breif report


No, I haven't.

3
[Max] Bug Reporting / Re: Corona 11, 3ds max 2024 crash
« on: 2024-06-26, 19:34:03 »
I just did, so will see. I didn't archive those scenes. I wasn't sure if it was necessary.

4
[Max] Bug Reporting / Re: Corona 11, 3ds max 2024 crash
« on: 2024-06-17, 13:41:41 »
Hi,
Thank you so much for taking the time to help me.

I can try to crash it with a simple scene, and let you know.

when you say third party plugin do you also mean the Corona renderer? Right now I have Itoo forest pack and railclone latest versions availible installed. I also have Vray as well as Corona. I tried rendering with Vray scenes that crash with Corona and the same thing happens. I will paste the chat gpt break down of that crash dump file. I have to also say that I had the same problem with previos versions of 3dsmax and Corona.

here is the chat gpt break down of the Vray crash:

Based on the provided minidump analysis, here is a breakdown of the key details and insights regarding the crash:

Key Details from the Minidump Analysis
Exception Information:

Exception Code: c0000005 (Access Violation)
Exception Address: 00007ff855588b55 (within vray.dll)
Exception Description: Attempt to read from address 0000000000000000 (null pointer dereference)
Process and Module Information:

Process Name: 3dsmax.exe
Faulting Module: vray.dll
V-Ray Function: vray!VUtils::VRayCore::getTimeInFrames
Context Information:

Register Context:
rax=000002118760bb80
rbx=000000aa89c95210
rcx=0000000000000000 (null pointer causing the crash)
rdx=000000aa89c95250
rip=00007ff855588b55 (instruction pointer at the faulting address)
rsp=000000aa89c950b0 (stack pointer)
The rcx register being zero (null) when trying to dereference it caused the access violation.
Call Stack:

The call stack shows the sequence of function calls leading to the crash:
vray!VUtils::VRayCore::getTimeInFrames
vray!PluginManagerUtilsBase::writeDotDependencyGraph
vray!VUtils::VRayCore::traceRay
vrender2024!VUtils::SetupForTextureCaching::setup
vrender2024!isMaxMaterialSwitcher
and several other functions within vray.dll and vrender2024.dll.
Failure Bucket and Hash:

Failure Bucket: NULL_POINTER_READ_c0000005_vray.dll!Unknown
Failure Hash: {8164d52e-fc1f-edfe-9388-37eac0ba00a6}
Summary of the Analysis
The crash occurred due to a null pointer dereference within the vray.dll module, specifically in the VUtils::VRayCore::getTimeInFrames function. This happened while 3ds Max (3dsmax.exe) was running, and the V-Ray plugin was in use. The exception code c0000005 indicates an access violation, which is common in cases where the application attempts to read or write to an invalid memory address.

Potential Causes and Next Steps
Null Pointer Dereference:

Ensure that the code checks if pointers are valid (not null) before dereferencing them.
Add proper error handling and logging to identify when pointers become null unexpectedly.
V-Ray Plugin Issues:

The issue lies within the V-Ray plugin (vray.dll). Checking for updates or patches from the V-Ray developers might resolve this issue.
Consider contacting V-Ray support with the details of the crash, including the minidump analysis, for further assistance.
Environmental Factors:

Sometimes crashes can be influenced by specific scenes or configurations in 3ds Max. Try replicating the crash with different scenes or settings.
Check for any recent changes or updates to the system, 3ds Max, or V-Ray that might have introduced the issue.
Debugging and Logging:

Implement additional logging around the areas where the crash occurs to capture more context and potentially identify the root cause.
Use tools like WinDbg to perform a live debugging session if the issue persists and more detailed analysis is required.
By addressing these potential causes and taking the suggested next steps, you can work towards identifying and resolving the root cause of the crash.

5
[Max] Bug Reporting / Re: Corona 11, 3ds max 2024 crash
« on: 2024-06-16, 21:12:36 »
Hi
No, I have AMD Ryzen 9 3950X 16 core processor
It is Corona 11 HF 2

6
[Max] Bug Reporting / Corona 11, 3ds max 2024 crash
« on: 2024-06-16, 19:23:49 »
Hi
3ds max 2024 keeps crashing in the middle of rendering with Corona 11, the latest version right now. The crash is inconsistent and doesn't happen every time. It will render some scenes fine, others will crash 3ds max 9 out of 10 times. Sometimes within the same scene and file it will render 4 different cameras fine and then crash every time on the fifth camera. If I archive file and transfer it to my other pc, relink everything it will render fine. Some scenes alway crash, some scenes crash most of the times, some scenes don't crash at all. Even the same scenes and files that used to render fine a couple of months ago will now crash. Yesterday I completely reseted the OS. Windows 11 has wiped clean the drive it was on as well as all other softwares installed. I reinstalled everything from scratch and still the same thing. Lately it happens more and more often and it has come to a point that it works maybe in 5% cases. It is driving me crazy. Because of this inconsistency it has been impossible to identify the cause of the crash as well as reproducing it effectively. I have been sending crash reports to autodesk but now I have finally taken it upon myself to try and read the mini dump file myself. I even gave it to chat gpt to analyse it. this is what it said:

Let's break down the contents of the WinDbg analysis of the 3ds Max minidump crash report and discuss possible steps to fix the issue:

Key Elements from the Analysis:
1. Exception Information:
Exception Code: c0000005 (Access Violation)
Indicates that the program attempted to read or write to an invalid memory location.
Faulting Module: Corona_Release.dll
The crash occurred within the Corona render engine plugin for 3ds Max.
2. Exception Description:
Attempt to write to address 0000000000000000
A null pointer dereference. The program tried to write data to a null (invalid) memory address.
3. Call Stack:
The call stack shows the sequence of function calls leading to the crash. Here's the relevant part:

ruby
Kopiraj kod
Corona_Release!Legion::Corona::serializeToString+0x3e143:
00007ff8`7f24a323 410f1128 movups xmmword ptr [r8],xmm5 ds:00000000`00000000=?????????????????????????????????
Function Involved: Legion::Corona::serializeToString
This suggests that the issue occurred while the Corona renderer was trying to serialize data to a string.
4. Key Value Strings:
AV.Dereference: NullPtr
The dereferenced pointer was null.
AV.Fault: Write
The crash happened during a write operation.
Failure.Bucket: NULL_POINTER_WRITE_c0000005_Corona_Release.dll!Unknown
This categorizes the crash for easier identification and debugging.
Summary:
The crash is caused by the Corona render engine attempting to write data to a null pointer during a serialization operation. This is a clear indication of a bug in the Corona render engine code.

Pages: [1]