3ds Max error on close with ucrtbase.dll

cadgislabor · ‎01-16-2017

to keep you informed: I still have the same Problem with Windows 7 x64 Professional Clients on HP Workstations. Changing of Motherboards is not an option to me. I opened a supportcase and the problem is actually processed through the Autodesk development department.

Regards,

Alexander Koch

Alfred.DeFlaminis · ‎01-17-2017

Hello @cadgislabor,

Did you get a report #, case #, or defect # when you submitted this? Firmware and driver updates might be worth looking into, but I cannot suggest you flash anything in an official sense. That being said, if there are driver problems with the hardware there isn't much that can be done on this end. Do you have better luck with different hard drives? Thanks for any additional information.

Best Regards,

cadgislabor · ‎01-18-2017

Hello @Alfred.DeFlaminis,

yes, I got a case number. I send it to you by PM. I opened the case in last September. I know from a member in the german part of the forum (Tarek_K) that the case is being processed by the development department. At the moment, the solution of this problem is not time depending for me. I probably stay on 3ds max 2016 at least for the next half year. With that version I don't get the error on the same clients. The machines where the problem occured have been installed new with latest os and graphiccard updates. I didn't check what happens with different hard drives installed. I'll give this a try as soon as possible.

Regards,

Alexander Koch

Alfred.DeFlaminis · ‎01-18-2017

Thanks for the PM @cadgislabor,

Are you having a freeze on startup and/or disk utilization error in addition to the crash on close? I read over your case but there's no mention of the disk utilization or startup crashes there. It's no problem but I may split these past few posts out to a new thread since they don't seem to align 1:1. The good news is that I don't think your motherboard is the problem here, from what I'm reading in your case log.

I can see that there's no update to the case in the past couple months. My thinking is that I need to put more information in there. I did find your thread here. I wonder if I should relog this for you with a slightly different title. If there is any other relevant information that would be great, and after reading more about your case I don't think it's the same issue that @Anonymous was having. Please correct me if I'm wrong.

All that being said, the UCRTBASE.DLL issues were mostly limited to W10. It's strange to see them in W7. I did a search for other issues like this and apparently some applications may replace that .dll with other versions, which does seem to be related to some problems I'm seeing. Are there any other adverse effects other than the crash on close I should be aware of?

Best Regards,

cadgislabor · ‎01-19-2017

Hello @Alfred.DeFlaminis,

( @Tarek_K, @matthias.schindler & @tobias_wiesendanger ich verlink euch hier mal, geht um den ucrtbase.dll Fehler bei 3ds Max 2017)

I had only the appcrash error message on closure of 3ds Max 2017 using the German Language Version. There were no other problems. I took part of this thread because it was the only one I found, that also had a appcrash error caused by the module ucrtbase.dll. Meanwhile I also do think this it is related to some other issue than rayshawnpaul had.

A summary of the problem:

3ds Max 2017 x64 Installation on Windows 7 Professional x64 SP1 on HP Workstation, Graphiccard: NVIDIA Quadro 2000 (os and drivers using latest updates).

Installed as user "Administrator", starting the Application with administrative rights.

Using the German Language Version I get an appcrash error message at about 5 seconds after the program was closed.

Name der fehlerhaften Anwendung: 3dsmax.exe, Version 19.2.472.0

Name des fehlerhaften Moduls: ucrtbase.DLL, Version: 10.0.10586.9

Ausnahmecode: 0xc0000005

The error message doesn't appear using the french or english language pack (didn't try other ones).

Also i had no error message with 3ds Max 2016 on the same clients

Tried solutions (not working):

- Un- and reinstalling of all Visual C++ Redistributable Packages

- Renamed ucrtbase.dll in system32 and syswow64 and installed a update for Universal C Runtime https://support.microsoft.com/de-de/kb/2999226

- Replaced the VC++ and the U CRT Runtime files in my adminimage with downloads from microsoft

- Installation on Win 7 Prof x64 SP1 with no further updates, no other software, no virusscanner

- sfc /scannow

- Repairinstallation of all C++ Redist Packages

- Installed Visual Studio Community 2015 Package from visualstudio.com before 3ds Max 2017 (lead to appcrash messages from ucrtbase.dll and kernelbase.dll)

Tried solution (working!):

- changing the language settings in the taskbar from DE to EN

I am not the only one that could reproduce the error message on Windows 7 Clients. In the german part of the Board matthias.schindler reported the same error behavior on Windows 7 Professional SP1 (Post 19). tobias.wiesendanger reported the same error behavior on Windows 10 (Post 37) and got them also on Windows 7 (Post 57). Matthias.schindler had no error on Win 8.1 Professional.

Regards

Alexander Koch

cadgislabor · ‎01-19-2017

just found out, that you already dicussed about the issue in this thread: http://forums.autodesk.com/t5/3ds-max-forum/error-sound-when-closing-max-2016-win7/m-p/6027315/highl...

Alfred.DeFlaminis · ‎01-19-2017

Hello @cadgislabor,

Thank you for the detailed information. This helps a lot. I had to edit the titles of the posts to match the thread title so this thread was easier to find for other people and I moved the posts to this new thread first so that if a solution is found it could be marked. Thanks for your understanding there.

I do have a question, is your Windows in German or in English? I'm trying to see if the problem happens when there is a mismatch between the OS language and the Max language. Once I know this I will update all the relevant areas with this information. Thank you.

Best Regards,

cadgislabor · ‎01-19-2017

Hello @Alfred.DeFlaminis,

my Windows is in German language.

Regards,

Alexander Koch

Alfred.DeFlaminis · ‎01-20-2017

Thank you for the update @cadgislabor, I have updated the case information with a link to this thread. There was a theory this happened due to language mismatches, but you just confirmed that is likely not the problem here. Thank you for doing that.

Your case in the tracker matches some other entries I seen in there, and I have updated them with a link to this thread. There has been some comments and activity in those reports so this issue is being looked at. For the time being however, the only workaround I could suggest is that you might try to install the script from this thread to see if it prevents the crash on Max close by shutting down it down before it gets a chance to crash. Thanks for trying that for me!

Best Regards,

wbeinart · ‎01-22-2017

I have the same problem on a new install of 2017 under Windows 7 Pro x64. I've updated Visual Studio C++ 2015 to sp3 reinstalled Max, repaired Max, repaired Visual studio and still get the error on closing.

Problem Event Name: APPCRASH
Application Name: 3dsmax.exe
Application Version: 19.3.533.0
Application Timestamp: 57cf64b2
Fault Module Name: ucrtbase.DLL
Fault Module Version: 10.0.10586.9
Fault Module Timestamp: 5642c48d
Exception Code: c0000005
Exception Offset: 0000000000068193
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Information 1: d840
Additional Information 2: d8403474ad0568eac8b5c2fc919e6905
Additional Information 3: d2e1
Additional Information 4: d2e1df167bad5d0e9081bc24d63b4d18

Been messing with this for some time and it's annoying the **** out of me. No error report generated to send to Autodesk just a windows error that max has stopped working. I built this computer and yes it is a few years old but everything else works no problem. Asus Sabertooth x79 mobo, 32g ram, K5000 quadro, intel 3930k processor. It happens every time after the first session after repair of Visual Studio.

cadgislabor · ‎01-23-2017

Hello @Alfred.DeFlaminis,

I actually don't have any Clients running 3ds Max 2017. After the appcrash errors ocurred on my testmachines we decided to stay on 3ds Max 2016. Time permitting I'll give this a try an tell you how it works.

@wbeinartdo you use the english language pack of 3ds Max 2017 on an english Windows? Till now I thougt this problem is only related to the german language pack of 3ds Max 2017 running on german OS. But I didn't try on an english os. I just noticed that the problem doesn't appear if I change the language setting in the taskbar from DE to EN.

Regards

Alexander Koch

wbeinart · ‎01-23-2017

Yes this happens in the English version also. If I could go back to the 2017 version I would but since I had to let my subscription lapse due to financial reasons shortly after 2017 Building Design Suite Premium that's what I'm stuck with.

This never happened to me with 2016 and prior versions all the way back to 2010. From my research and limited knowledge this appears to be a result from making the software Windows 10 compatible. Don't even get me going on that fiasco with Windows. If my computer hadn't locked on me after a windows update in Windows 7 which resulted in the "no os found" error I wouldn't even be in this mess. This is a fresh install and everything else appears to be functioning correctly. This includes zBrush4r7 and Adobe Production Suite Premium CS6: these all appear to function correctly. Even AutoCAD 2017 works correctly. Only 3dsMax throws this error. From my research and limited knowledge I think this all is caused by the C++ 2105 redistributable which was designed to allow Windows 10 compatibility for prior versions of Windows, If I repair the C++ 2015 x86 and x64 redistributable I can load up 3dsMax with simple geometry and it closes gracefully as it should but the next time I load up simple geometry and exit it throws the error; a WINDOWS error not an Autodesk error with the error report dialog. Looking at my Windows event viewer the error always has the same information.

I've tried reparsing the windows install through the command prompt and it always reports no errors. It doesn't matter if I reset the scene in 3dsMax prior to closing it still throws the error. I hope the error remains only at closing as it seems to function correctly while in use.

wbeinart · ‎01-23-2017

I meant rollback to the 2016 version not 2017; my error. If Autodesk would allow me to rollback my perpetual license back to 2016 I would do it in a heartbeat!

I should add that this is a standalone install and not a network install.

wbeinart · ‎01-23-2017

I just tried the max script Alfred and it appears to work!! Just installed it, loaded max geometry, shut down and no windows error but a graceful, quick shutdown. Tried it a few times with same results. I'll keep my fingers crossed and thank you.

cadgislabor · ‎01-23-2017

Sounds good. But if I got this right the script just kills the 3ds process before the message appears. It doesn't solve the problem.

I also don't have the problem with AutoCAD 2017, Civil 3D 2017 and Map 3D 2017 but 3ds Max 2017 shows the error message. It seems like the program is working fine but I didn't try to find out more. I thougt the problem is not related to the functionality of the software itself since I don't get the error message if I work with the english language pack, but I'm not sure about that. The lecture is in german language and I don't want to install 3ds Max 2017 in an educational environment with that error appearing as long as the professor is willing to teach the 2016 version. If the script prevents me from the error message, that would be fine, but I still would have doubts about if everything is working correctly.

Regards

Alexander Koch

Alfred.DeFlaminis · ‎01-23-2017

Hello @cadgislabor and @wbeinart,

Thanks for the updated information. This happens to me on Win7 in English as well with 2017, so it's not specifically a W10 thing, for what that's worth. The problem seems to be with a .NET update as mentioned by @wbeinart. Nothing about it should hurt your Max installation, so you don't have to worry about that. The script should prevent any settings corruptions as well, it has worked for me on this end for a couple months. I have this logged into the tracker and the script is the only workaround for the time being that I am aware of.

Best Regards,

cadgislabor · ‎01-24-2017

Hello @Alfred.DeFlaminis,

thanks for your support. I did some tests with the script and it seems like this works for me too. Didn't get the error messages again until now.

Best Regards

Alexander Koch

Alfred.DeFlaminis · ‎01-24-2017

Thank you for the update and confirmation @cadgislabor. I'm glad to hear it.

Best Regards,