3ds Max 2017 Crashing

[Anonymous]

3ds max running very slow, freezes and crashes very often. I tried reinstalling windows, updated the latest drivers and rolled back to previous versions, I tried reinstalling 3ds max, changed the current video card Quadro K620 to GTX 1070 and still the same specially when on high quality viewport mode or while using other software like illustrator and Photoshop. Any ideas I tried everything. I don’t know what to do. Please Help

Brand new computer

I7 6700k

64 GB RAM

GPU GTX 1070

Windows 10

[Daf]

Hi,

I believe there are still issues with Windows 10.

Have you already checked the Windows 10 Support link to the right? http://autode.sk/1IY4C2X

Or done a google search: https://www.google.com/search?q=3ds+max++windows+10

Good luck!

Daf

[Alfred.DeFlaminis]

Hello @Anonymous,

Hardware issues can be notoriously difficult to solve.  @Daf has a point that some users (a minority) do have some serious issues with Windows 10, Max, and Titan/10X0 cards.  It's not an issue that can be reproduced by QA or by me despite spending many, many hours trying.  My first thought is to check that your power supply is sufficient for the 10X0 card, to do a clean uninstall of your old drivers (sometimes a 3rd party app to wipe all traces clean is needed) and then reinstall the drivers for the 10X0 card.  Check firmware updates for major hardware.  (I cannot officially suggest you flash your firmware, just a suggestion to see if they exist.)  

For most users the problem is limited to the 3D software, but if Photoshop and Illustrator are causing problems too you will want to double check that power supply and drivers.  I have seen weird things like a DVD drive using generic drivers cause all kinds of system problems in the past.  Sometimes the event viewer logs can help show what the problem is, so it might be worth checking out and posting if you're comfortable doing so.  I can't offer too much support on hardware because I am not a hardware expert at Autodesk, but these suggestions hopefully can help lead you in the right direction.  

You might also check that your motherboard uses the same PCI bus type as the new card, sometimes the motherboard will have to downgrade the PCIe for compatibility reasons, again it's very hard to diagnose without the details.  If you listed your motherboard, power supply, etc. it may help to solve this, but again it is not my specialty.  

Best Regards,

[Alfred.DeFlaminis]

Hello @Anonymous,

I just wanted to follow up here, any progress on this issue?

Best Regards,

[Anonymous]

HELLO Alfred.DeFlaminis

THANK YOU VERY MUCH FOR YOUR HELP.

OK SO I THINK MY POWER SUPPLY IS ENOUGH FOR THE GRAPHIC CARD, I DID A CLEAN INSTALLATION OF WINDOWS 10 AND UPDATED ALL DRIVERS AND FIRMWARE AND THE PROBLEM PERSISTS. I'VE BEEN SENDING THE INFORMATION TO AUTODESK EVERY TIME 3DS MAX CRASHES. I'M ALSO ATTACHING THE LOG FILES YOU ASKED.

IF YOU NEED ANY OTHER INFO PLEASE LET ME KNOW.

Intel Core i7-6700K CPU @4.00GHz
INSTALLED RAM 32.0GB
MOTHERBOARD GIGABYTE Z170X-Gaming 6
GRAPHIC CARD GYGABYTE GEFORCE GTX 107
POWER SUPPLY CORSAIR CX650M
CPU Cooler CORSAIR H80i v2
WINDOWS 10 PRO

THANKS IN ADVANCE

[Alfred.DeFlaminis]

Hello @Anonymous,

I checked your crash logs and two of your crashes are from bugs that were fixed in Sp1 and Sp2.  Which Service pack are you currently on?  This is the area I can help the most. 

Do you have more than one GPU in your system? (I.E.- are you using both the quadro and the 1070?)  If you are, you might be having power issues.  Both of those cards plus all the other hardware might be too much, but hard to say.  

There are some error messages in the event viewer logs that might point toward system problems but it's hard to tell with some of them because I am not much of a hardware fixit specialist.  I can list what I'm seeing though and maybe it can help you look further.  I have to admit harware isn't my specialty and I can't provide that much help on it, but I can list the problems I'm seeing.  I can't say for sure if these errors are important or not, just that they caught my eye.  You have quite a few errors related to the following:

Kernal PnP (plug and play).  Points toward a device on your system that isn't fully compatible with W10.  These driver issues can cause all sorts of weird problems, so I would look to find out what this is referring to.  If the Kingston reference is RAM, you might need to check your motherboard white paper to make sure they are compatible with this much RAM/chips in the current cofiguration.  I'm only seeing 2 kingston chips on there at all, so maybe a memory compatibility problem?)  

The driver \Driver\WudfRd failed to load for the device SWD\WPDBUSENUM\_??_USBSTOR#Disk&Ven_Kingston&Prod_DataTraveler_111&Rev_PMAP#070729EA32D7D043&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

The driver \Driver\WudfRd failed to load for the device USB\VID_05AC&PID_12A8\2021ac84b0158e901f4f1c76806c112421beee12.

Nvidia drivers and crashing or NVIDIA related;

Display driver nvlddmkm stopped responding and has successfully recovered.

NvAPI_GPU_GetBoardInfo error code=-1

The Nvidia Quadro driver detected high GPU memory usage. This will impact application performance.  (Is the quadro still in the machine?  Weird code.)

Faulting application name: NVDisplay.Container.exe, version: 1.0.0.0, time stamp: 0x584d90c8
Faulting module name: NvXDCore.dll_unloaded, version: 8.17.13.7633, time stamp: 0x584d9d8d
Exception code: 0xc0000005
Fault offset: 0x000000000004b8c0
Faulting process id: 0x540
Faulting application start time: 0x01d25f0b46a45f6d
Faulting application path: C:\Program Files\NVIDIA Corporation\Display.NvContainer\NVDisplay.Container.exe
Faulting module path: NvXDCore.dll
Report Id: 06abf63f-42ac-40a7-85d3-b48e416572ec
Faulting package full name:
Faulting package-relative application ID:

Kernal Power: (lots of these, hard to say if it's important.)

The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

3ds Max: (Interesting that the faulting module and path is empty.)

The program 3dsmax.exe version 19.0.1072.0 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel.  (Can you please check this to see what it says?)
Process ID: 24f0
Start Time: 01d25a2a54778025
Termination Time: 17
Application Path: C:\Program Files\Autodesk\3ds Max 2017\3dsmax.exe
Report Id: 34d168d8-c622-11e6-b139-1c1b0d05e22b
Faulting package full name:
Faulting package-relative application ID:

Faulting application name: 3dsmax.exe, version: 19.3.533.0, time stamp: 0x57cf64b2
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000035f65ba0
Faulting process id: 0xebc
Faulting application start time: 0x01d25c258c5b5c81
Faulting application path: C:\Program Files\Autodesk\3ds Max 2017\3dsmax.exe
Faulting module path: unknown
Report Id: 0ed4d7f6-c70b-4461-a782-9e9e9e8169c4
Faulting package full name:
Faulting package-relative application ID:

Corsair Link 4: (Google indicates lots of problems with this, whatever it is.  It's crashing with .Net, which may point toward .Net problems?   I am unfamiliar.)

Application: CorsairLink4.Service.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException
at CPUIDSDK.Close()
at CorsairLink4.Module.Dram.DramComponent.Dispose()
at CorsairLink4.Service.Service.DevicesMonitor.Dispose()
at CorsairLink4.Service.WindowsService.Dispose(Boolean)
at System.ComponentModel.Component.Dispose()
at System.ServiceProcess.ServiceBase.Run(System.ServiceProcess.ServiceBase[])
at System.ServiceProcess.ServiceBase.Run(System.ServiceProcess.ServiceBase)
at CorsairLink4.Service.Program.Main(System.String[])

I cannot help much with the hardware and driver issues but I wanted to point out what I was seeing.  You might check if you have any firmware updates to your hardware, but I cannot officially recommend to anyone that they flash their devices.  This is about all I can do regarding hardware, but if you need any help with installing the Max service packs or anything I am happy to help.  I am interested to see what happens here.

Best Regards,

[istan]

Have you tried using DirectX instead of Nitrous?

Launch max with this commandline

  3dsmax.exe -h

and select DirectX.

All my NVidia crashes went away by using DirectX!

[Alfred.DeFlaminis]

The problem is that Direct X is Nitrous.  (DX11 vs. DX9.)  Did you mean legacy D3D? 

Best Regards,

[istan]

Hi Alfred,

yes, I meant the "Legacy Direct3D" driver. Sorry for the confusion.

Nitrous & NVidia simply don't work with Max2017.

In contrast Max2016 on the same machine works smoothly with Nitrous.

What I specifically recognized under Max2017 with Nitrous is, that the model is always displayed shortly with b&w uvw chessboard-material, when I change something in the viewport settings.

Istan

[tarmana10]

I can also confirm the above.

Nitrous using DX11 under 3DS Max 2017 does NOT WORK - (at least with my GTX 1080 under Win10 Anniversary Update)

Nitrous using DX11 under 3DS Max 2016 DOES WORK (using the same machine, GTX 1080, Win 10 Anniversary Update)

While I can use d3d 9 mode in Max 2017 and have been up until now, this problem has been ongoing for some time.

I have since reverted back to 3DS Max 2016 until Autodesk work out how they have broken Nitrous in Max 2017.

I appreciate you trying to help Alfred, but the "power supply / plugins / driver issues" suggestions are not the root problem for many of us effected with this issue..

Please fix Max 2017 DX11 Nitrous Autodesk!

[darawork]

I've pretty much the same system;

Max 2017 SP3

Windows 10 Anniversary Updated.

i7 6700k

32gb Corsair Ram

Asus z170x - Pro Gaming

Corsair Hydro 115i Water Cooler.

ASus Gtx 1080

Asus Gtx 980

Corsair HX 750i PSU. 

I was getting random viewport freeze-ups while using the WalkThrough tool, even with fairly simple scenes.

I went back to 2016. No Freeze-ups since.

The complexity of the Nitrous viewport did look very nice in 2017,but was ultimately unstable. Sometimes I had to really spin around fast with the Walkthough tool, deliberately trying to crash Max... but it always did crash in the end.

My Viewport-Freezes are exactly as explained in this post: http://forums.autodesk.com/t5/3ds-max-forum/3ds-max-2017-viewport-freezing-and-stopped-working/m-p/6... I can access the menu, save... everything but manipulate the viewports (Maximise / Miniminise etc..) Then it crashes.

[istan]

In my case, simply changing between different visual style settings sooner or later crashes max with just one simple mesh without any specific materials attached. And it happens on three different machines.

[Alfred.DeFlaminis]

Hello @all!

Ok.  I am seeing more and more posts about this and I'm going to go back through all my old threads about this issue and asking if the people involved in the thread can please post their information in this thread here.   I have a post there asking about specific information on each machine and I thought it would be best to have all this info in one place.  Thank you very much for doing so.  I had thought these were isolated cases but I'm seeing that is not true and I want to do whatever I can to collect info and get the info passed along.  

Best Regards,

[darawork]

Switching viewport styles also triggered it for me.