Application Error (Max 2017)

#1

Hi. I have a problem that others seem to have had in the past.

When opening a max file, I get an application error. Max then has to close. Before anyone says it’s a corrupt file, it isn’t.

It’s an evermotion file… In fact, it can be any file. These files work fine on other systems in the office.

Now, to the really, really annoying bit.

I’ve had this problem for weeks. Eventually, for some random reason, it’d work fine. Then I’d get the problem again. it got to a point where it didn’t work at any time

Last week I was using Win7 but have since done a fresh install of my system and installed Win10.

Max has been fine until a couple of hours ago and I’m now getting this issue again. This means I can’t work and meet deadlines if I can’t even open a scene.

Please, can anyone help me?

Thanks,

Sean

#2

Difficult if its completely random.Maybe its a hardware related problem. Did you check for faulty RAM? Graphic Drivers up to date? Try a different graphics mode, like Direct3D or OpenGL.

Perhaps an installed plugin or script that interferes and is specific to your workstation?

Other suggestion is, to go to the AREA 3dsmax forum and ask Alfred.DeFlaminis to take a look at your crash dumps.In case you sent them and provided an email address.

#3

Thanks. The issue is frustrating enough but the complete randomness of it makes it worse.

I’ve just logged onto the office system and the scene has loaded.

Yet earlier I was showing people and 9/10 times it crashed.

This seems to be a known issue but no guaranteed fix.

I saw a video where someone seems to fix it by having max closed and renaming the ‘2017 - 64bit’ in:

AppData\Local\Autodesk\3dsMax

Max then makes a new one

I might give that a try.

RAM is testing fine, I updated my GFX card yesterday. I switched to Nitrous D3D 9 (from v11) earlier.

I’ll try the others too.

#4

Also, everyone has the same plugins, and same versions.

In fact, as I’ve done a clean OS install, I’m probably better off script wise than the rest. So don’t think that’s the cause.

#5

I’ve send Alfred a PM.

Thanks again

#6

Thank you for the reference Gernot, I appreciate it!

I am working with Sean here , in the case that a future user stumbles across this thread. I have traced the crash reports and they do seem to have been fixed in SP2, and I am communicating about this with Sean right now in the forums.

Thank you all and best regards,
Alfred

#7

Thanks for the help, Alfred!
Hope you guys can find a solution.

#8

Woah - Alfred , was not aware that you (Diffuse3d/Max Headroom avatar here and Alfred over at theArea) are one and the same person. Knew your Max Headroom Avatar for a long time here already

#9

Same here :slight_smile: Nice to see you here, Alfred, and thanks for your help over at the AREA.

The original problem sounds bad, hope you guys are able to sort it out.

#10

I do understand this kind of error can wreck your iPhone but you should be knowing about your iPhone and that application you are using right now, but first, you can know get IMEI number with iPhoneIMEI.net also many tips that should be following correctly incase you are in worried.