3ds max 2017 viewport freezing and stopped working

[Anonymous]

Hello, i got some issues with my 3ds max. it always freezing when i click it and then the viewport turns black.

and sometimes it just showing and error and saved my file into backup folder.

i have i7-6700, GTX 970 and 16gb ram with windows 10 running.

please help.

[Alfred.DeFlaminis]

Hello @Anonymous,

Thank you for the update.  This is interesting news... a windows update causing these problems in Max.  Can I ask which updates were failing?  I wonder if it's affecting others in this thread the same way.  Thanks for any extra information.  

In a general sense the version of Vray that you are using will have an impact on how this question is answered.  I highly recommend asking on the Vray forums, but generally speaking there are only 2 areas that really matter with Vray 3.4.  The first is your Max AA subdivisions, and the second is your noise threshold in the bucket image sampler.  (Adaptive is now called bucket.)  I highly recommend the Chaosgroup forum thread titled:  "Cheatsheet: How to get a Cleaner image with SP3" by Lele.   If you don't mind, could you also post your post above here in your original thread so I can mark that thread with the solution?  Thank you so much @Anonymous.  We can tackle the Vray questions in there as well, happy to help!

To @all else, thank you for posting your information.  I will attach this thread to the relevant trackers.  

Best Regards,

[Anonymous]

Same problem with viewport crashes in DX11-mode.

Windows version:  Windows 10 Pro 64-bit, Version 1511

3ds Max and Service Pack version:  2017 SP3

Graphics card:  GTX 1070, Gainward Phoenix

Current NVDIA driver version:  376.19

In Max, no 3rd-party plugins.

[istan]

Dear Alfred,

just to demonstrate that it's not only win10 related:

3 different machines:

Windows version:  Windows 7x64

3ds Max version:  2017 Update1

Graphics cards:  GTX 6xx, GTX 7xx, GTX 9xx

Current NVDIA driver versions:  37x.xx (although using different versions, the same crash occurs)

..and again, all these three machines work with max2016 + nitrous!

[gregg_lagnese]

Per your request (my config):

Windows version: Windows 10 Pro v1607 OS Build 14393.576

3ds Max and Service Pack version:   19.51.835.0  (2017 with SP3 and 2017.0.1 Security Fix)

Graphics card:  Nvidia GeForce GTX 1060 (6GB)

Current NVDIA driver version: 376.33

Note that Max does not crash and offer to send a crash report when the viewport hangs, Max continues to run for a short while, then completely hangs and becomes unresponsive.  The thread inspection shows a DirectX draw call happening over and over.  The only option is to kill Max and restart it.

[darawork]

NVidia iRay Max forum is suspiciously quiet. Since iRay+ branch off. iRay will not be supported post 2015. Deadend compared to being a 3rd party paid Plugin with dedicated support. ADSK doesn't support Pascal, especially retrograde patches.

[darawork]

Although maybe, with all this noise.
10xx series cards are a big market.
People are ditching Quadro cards like rats on the Titanic.

[darawork]

Time for ADSK to milk the market IMHO.

[Alfred.DeFlaminis]

Thank you all for the information.  Knowing the manufacturer of the cards does help in the case that it's a problem with specific cards or Pascal (which I don't know much about.)

I know that it's been tough to repro these issues in house, my home computer (Supermicro X8DA3 and EVGA GTX 970) and my work laptop (M4800 with NVIDIA Quadro K2100M) haven't been able to repro these issues on W7 with DX11.  I wish I was able to, it would make it easier to log.

If you all don't mind listing your GPU manufacturers that would be great.  You can PM it to me and I'll edit your posts to add that info so it's all nice and organized.  At this point all I can do is make a master list here and send it to people who know more about dev and dx issues than I do.  Right now I believe you're all having issues but I have no solution other than to try to use DX9 display mode in the case there is a problem with DX11.

Thanks again for the information.

Best Regards,

[darawork]

W10 is a harsh mistress, like gravity.

https://www.youtube.com/shared?ci=R4mz9nCYK1Q

[darawork]

I've a 1080 in my DIY build that work paid for. I'd love to ask for a raise, being early January. And I wanna buy a Ford Cortina MKIII. There goes my pay rise for this year.

[alexnode]

I had random freezes after the latest update with a dual xeon 2660v3, Titan X (maxwell) , tried an old titan too, Wacom tablet, Dual Samsung SSDs 32GB ram. I also transferred max in my slave machine with dual xeon 2670 v4 and a titan card and i had the same problem. 

Note that i use 3 monitors in both scenarios 

 I know this is an old thread but good to add the specs all in one place.  

[Alfred.DeFlaminis]

kmh237462 posted his specs as listed below.  

Windows version: Windows 10

3ds Max and Service Pack version:   2017 (need update for SP)

Graphics card: Nvidia Quadro P5000

Current NVDIA driver version: Unknown

----

As @istan has pointed out, this isn't OS specific.  The only thing all of you seem to have in common is NVIDIA cards.  Is there anyone having these issues with ATI cards?

Best Regards,

[dave.tyner]

Same same here. 

1080 GTX - 376.33 driver

Always freezes on scene with DX materials. The latest iteration of this problem allows me to open the scene successfully. Then if I click anywhere, frozen.

[jacek.jerzy.maj]

@dave.tyner hey Dave, probably the same issue as mine:

forums.autodesk.com/t5/3ds-max-forum/3ds-max-2017-directx-shader-crash/td-p/6606625

[Alfred.DeFlaminis]

Hello @dave.tyner,

Thank you for the information, and I agree it seems the same issue that Jacek is having.  Are you on W10?

Best Regards,

[dave.tyner]

@Alfred.DeFlaminis 

Yes sir, Win 10. One machine has the Anniversary update, this machine's Windows build is 14393.576.

Same behavior on both.

Thanks!

[Damyanov_3dkad]

the same problem now with gtx 1080 and before with nvidiia quadro K5000. 

Win10 x64 and 3ds max 2017 is just not a good option. 

3ds max 2016 is working perfect!

[Anonymous]

This is happening to me as well, but a bit differently (might add a new perspective to the problem):

It happens only with ONE of my files. When opening the file max crashes sometimes, other times it opens normally but crashes after a few clicks and/or camera movements. And sometimes THIS problem happens, Max does not crash but the viewport problems start, just like everyone said, it freezes, turns black, but can still select objects and save and things like that...

I think it's the geometry. At one point, when it didn't crash, I converted to poly and exported and fbx of some of the parts. When re-importing them in a empty and clean new Max window, the problem persisted. I can't 'merge' all the shapes into a new scene since it'll crash or glitch the viewport as well, some objects can be merged tough.

Don't know if I can share this file so you can test it out but here it is: https://we.tl/sL66OiQCQT

Windows 10

GTX 1060 3gb (Gigabyte)

3ds Max 2017 SP3 (I started making that file in 2016, the problem was there so I tried changing  to 2017 to see if that fixed it)

[Alfred.DeFlaminis]

Thank you for the information @dave.tyner and @Damyanov_3dkad.

I appreciate the file @Anonymous, I am also seeing these crash issues.  I can't even open the file.  Did anything strange go on here with the UV  or texture maps or are you using a 3rd party plugin for UV or texture map generation?  I also tried merging and it crashed, so I think there is a corrupted object in here.  After some time, I've discovered it's the object named Plane073.  If you merge all the objects except that one, it seems to solve the problem.  I don't think it's the same issue as others in the thread, but I do thank you anyway for providing a scene file to test on.  There's something weird about the UV's on that one object, from the crash log.  (I was the only reporter of this crash in history, pointing toward corrupted geo uv's.)  

Best Regards,

[Anonymous]

To add to the discussion above:

Linking from Revit 17.1 to Max 17 is super slow, and/or sometimes just doesn't work ( freezes). Left my computer (max 17) overnight to do the linking, took hours to process, whereas Max 16 does it under 10 minutes. 

Tested both on Max 17 on win 7, and win 10 two different machines. 

The problem is with RVT and FBX files.