3dsMax 2024/2023 File crashing on a different pc

[tomuuchan]

Hello there. I was working on my external drive because I had to change of pc. Everything was working well on the old one (2023 version) but now that I have the new one with the 2024 version, I can open the scene sometimes (sometimes it's crashing with the following error), work in but everytime I want to save (or save as copy), it's crashing and makes me unnable to work on previous files. (Files because I have multiple copies of my file and every single ones are doomed.) Is there anything I can do to resolve this ? :/ Thanks in advance (All my drivers are updated)

People said that I should give you the Dump file so here it is.

Thanks for reading and for your help 😭

[darawork]

Hi,

I had a look through the dump file with Windows WinDbg, and it said this:

This dump file has an exception of interest stored in it.
The stored exception information can be accessed via .ecxr.
(3870.2ccc): Access violation - code c0000005 (first/second chance not available)
For analysis of this file, run !analyze -v
----------------------------------------------------------------------------
The user dump currently examined is a minidump. Consequently, only a subset
of sos.dll functionality will be available. If needed, attaching to the live
process or debugging a full dump will allow access to sos.dll's full feature
set.
To create a full user dump use the command: .dump /ma <filename>
----------------------------------------------------------------------------
ntdll!NtGetContextThread+0x14:
00007ffd`86d8ef04 c3              ret
0:000> !analyze -v
*******************************************************************************
*                                                                             *
*                        Exception Analysis                                   *
*                                                                             *
*******************************************************************************

Failed to request MethodData, not in JIT code range

KEY_VALUES_STRING: 1

    Key  : AV.Fault
    Value: Read

    Key  : Analysis.CPU.mSec
    Value: 3156

    Key  : Analysis.Elapsed.mSec
    Value: 53704

    Key  : Analysis.IO.Other.Mb
    Value: 117

    Key  : Analysis.IO.Read.Mb
    Value: 3

    Key  : Analysis.IO.Write.Mb
    Value: 254

    Key  : Analysis.Init.CPU.mSec
    Value: 1015

    Key  : Analysis.Init.Elapsed.mSec
    Value: 556111

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 336

    Key  : CLR.BuiltBy
    Value: NET48REL1LAST_B

    Key  : CLR.Engine
    Value: CLR

    Key  : CLR.Version
    Value: 4.8.4644.0

    Key  : Failure.Bucket
    Value: INVALID_POINTER_READ_c0000005_core.dll!Unknown

    Key  : Failure.Hash
    Value: {b20d8d78-4565-1d4c-3cab-439879508258}

    Key  : Timeline.Process.Start.DeltaSec
    Value: 112

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Version
    Value: 10.0.19041.1

    Key  : WER.Process.Version
    Value: 26.1.0.2270


FILE_IN_CAB:  3dsmax_minidump.dmp

NTGLOBALFLAG:  0

PROCESS_BAM_CURRENT_THROTTLED: 0

PROCESS_BAM_PREVIOUS_THROTTLED: 0

CONTEXT:  (.ecxr)
rax=00005db6ef0fdf00 rbx=0000009800000099 rcx=5dd72e96b91a0000
rdx=0000018191426c30 rsi=0000009800000099 rdi=0000000000000000
rip=00007ffd4c4cd6dc rsp=00000061c19966c0 rbp=00000061c1996761
 r8=000000000000003f  r9=0000000000010065 r10=00000181cbc8cb90
r11=00000181cddf2c10 r12=0000000000000001 r13=0000000000010065
r14=0000000000010065 r15=00000000fffffff0
iopl=0         nv up ei pl zr na po nc
cs=0033  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
core+0x42d6dc:
00007ffd`4c4cd6dc 488b06          mov     rax,qword ptr [rsi] ds:00000098`00000099=????????????????
Resetting default scope

EXCEPTION_RECORD:  (.exr -1)
ExceptionAddress: 00007ffd4c4cd6dc (core+0x000000000042d6dc)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000009800000099
Attempt to read from address 0000009800000099

PROCESS_NAME:  3dsmax.exe

READ_ADDRESS:  0000009800000099 

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

EXCEPTION_CODE_STR:  c0000005

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000009800000099

IP_ON_HEAP:  0000009800000099
The fault address in not in any loaded module, please check your build's rebase
log at <releasedir>\bin\build_logs\timebuild\ntrebase.log for module which may
contain the address if it were loaded.

FRAME_ONE_INVALID: 1

STACK_TEXT:  
00000061`c19966c0 00000098`00000099     : 00000182`db3cd850 00000181`891eba20 00007ffd`00010065 00000000`00000001 : core+0x42d6dc
00000061`c19966c8 00000182`db3cd850     : 00000181`891eba20 00007ffd`00010065 00000000`00000001 00000061`c1996780 : 0x00000098`00000099
00000061`c19966d0 00000181`891eba20     : 00007ffd`00010065 00000000`00000001 00000061`c1996780 00000181`cbbeea40 : 0x00000182`db3cd850
00000061`c19966d8 00007ffd`00010065     : 00000000`00000001 00000061`c1996780 00000181`cbbeea40 00000000`00000000 : 0x00000181`891eba20
00000061`c19966e0 00000000`00000001     : 00000061`c1996780 00000181`cbbeea40 00000000`00000000 00000000`00000000 : 0x00007ffd`00010065
00000061`c19966e8 00000061`c1996780     : 00000181`cbbeea40 00000000`00000000 00000000`00000000 00000000`00000001 : 0x1
00000061`c19966f0 00000181`cbbeea40     : 00000000`00000000 00000000`00000000 00000000`00000001 00000061`c1996820 : 0x00000061`c1996780
00000061`c19966f8 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00000181`cbbeea40


STACK_COMMAND:  ~0s; .ecxr ; kb

SYMBOL_NAME:  core+42d6dc

MODULE_NAME: core

IMAGE_NAME:  core.dll

FAILURE_BUCKET_ID:  INVALID_POINTER_READ_c0000005_core.dll!Unknown

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

IMAGE_VERSION:  26.1.0.2270

FAILURE_ID_HASH:  {b20d8d78-4565-1d4c-3cab-439879508258}

Followup:     MachineOwner

From that initial exception code, it led me to look at this Autodesk Knowlegebase Article:

https://www.autodesk.com/support/technical/article/caas/sfdcarticles/sfdcarticles/A-fatal-error-has-...

That's about as far as I got now.

Have you tried to merge the file into a new scene in 2024? To see if you can open it that way?

Regards,

[tomuuchan · Accepted solution]

Hello,
First, thanks for your fast reply. I merged back evey mesh one by one in a
new scene and it turns out that it's a mesh that is doomed (idk why). I can
redo it so everything looks fine. Thanks once again ! 🙂
Regards

[darawork]

Hi, cool. Good that you got it working. The mesh corruption might have been something to do with a previous plug in or script that created the problematic mesh that isn't present in the new max you're using. There are some visual basic errors and graphics errors in the log. But who knows? 

Sometimes the easiest solution is a step by step file merge, item by item if needs be. 7 times out of 10 it works all of the time. 

Regards,