Maya crashes anytime (2024/25)

[david_novasg]

This happens usually while I'm working. No matter if I'm moddeling, rigging, sculpting,...

I've tryed uploading drivers, reinstalling maya,... nothing works.
This is the cash log:

//=====================================================

Maya Crash Report

//=====================================================

Exception code: C0000005: ACCESS_VIOLATION - illegal read at address 0x00000000

Fault address:  DA733963 in C:\WINDOWS\System32\DriverStore\FileRepository\nvmii.inf_amd64_add1b07f2161ca7f\nvwgf2umx.dll

0001:000E2963 Logical offset (see .map file for location)

Call stack:

Module:  C:\WINDOWS\System32\DriverStore\FileRepository\nvmii.inf_amd64_add1b07f2161ca7f\nvwgf2umx.dll (-exported-)

Location: nvwgf2umx.dllOpenAdapter10 + 16E4 bytes

Module:  C:\WINDOWS\SYSTEM32\d3d11.dll (-exported-)

Location: d3d11.dllCreateDirect3D11DeviceFromDXGIDevice + 3EA60 bytes

Module:  C:\WINDOWS\SYSTEM32\d3d11.dll (-exported-)

Location: d3d11.dllCreateDirect3D11DeviceFromDXGIDevice + 41BB6 bytes

Module:  C:\WINDOWS\SYSTEM32\d3d11.dll (-exported-)

Location: d3d11.dllD3D11CoreCreateLayeredDevice + 50E bytes

Module:  C:\WINDOWS\SYSTEM32\d3d11.dll (-exported-)

Location: d3d11.dllD3D11CoreCreateLayeredDevice + 4CC bytes

Module:  C:\WINDOWS\SYSTEM32\d3d11.dll (-exported-)

Location: d3d11.dllD3D11CoreCreateLayeredDevice + 45C bytes

Module:  C:\WINDOWS\SYSTEM32\d3d11.dll (-exported-)

Location: d3d11.dllD3DPerformance_GetStatus + 89A bytes

Module:  C:\WINDOWS\SYSTEM32\d3d11.dll (-exported-)

Location: d3d11.dllCreateDirect3D11DeviceFromDXGIDevice + 36ADC bytes

Module:  C:\WINDOWS\SYSTEM32\d3d11.dll (-exported-)

Location: d3d11.dllCreateDirect3D11DeviceFromDXGIDevice + 41CDF bytes

Module:  C:\WINDOWS\SYSTEM32\d3d11.dll (-exported-)

Location: d3d11.dllCreateDirect3D11DeviceFromDXGIDevice + 41ACA bytes

Module:  C:\WINDOWS\SYSTEM32\d3d11.dll (-exported-)

Location: d3d11.dllCreateDirect3D11DeviceFromDXGIDevice + 45F2D bytes

Module:  C:\WINDOWS\SYSTEM32\d3d11.dll (-exported-)

Location: d3d11.dllD3D11CreateDevice + 2229 bytes

Module:  C:\WINDOWS\SYSTEM32\d3d11.dll (-exported-)

Location: d3d11.dllD3D11CreateDevice + 21CF bytes

Module:  C:\WINDOWS\SYSTEM32\d3d11.dll (-exported-)

Location: d3d11.dllD3D11CreateDevice + 2184 bytes

Module:  C:\WINDOWS\SYSTEM32\d3d11.dll (-exported-)

Location: d3d11.dllD3D11CoreCreateLayeredDevice + 588 bytes

Module:  C:\WINDOWS\SYSTEM32\d3d11.dll (-exported-)

Location: d3d11.dllD3D11CoreCreateLayeredDevice + 10717 bytes

Module:  C:\WINDOWS\System32\DriverStore\FileRepository\nvmii.inf_amd64_add1b07f2161ca7f\nvoglv64.dll (-exported-)

Location: nvoglv64.dllDrvPresentBuffers + 532A bytes

Module:  C:\WINDOWS\System32\DriverStore\FileRepository\nvmii.inf_amd64_add1b07f2161ca7f\nvoglv64.dll (-exported-)

Location: nvoglv64.dllDrvPresentBuffers + 3642 bytes

Module:  C:\WINDOWS\System32\DriverStore\FileRepository\nvmii.inf_amd64_add1b07f2161ca7f\nvoglv64.dll (-exported-)

Location: nvoglv64.dllDrvPresentBuffers + 2FBF6 bytes

Module:  C:\WINDOWS\System32\DriverStore\FileRepository\nvmii.inf_amd64_add1b07f2161ca7f\nvoglv64.dll (-exported-)

Location: nvoglv64.dllDrvPresentBuffers + 32027 bytes

Module:  C:\WINDOWS\System32\DriverStore\FileRepository\nvmii.inf_amd64_add1b07f2161ca7f\nvoglv64.dll (-exported-)

Location: nvoglv64.dllDrvPresentBuffers + 30FB4 bytes

Module:  C:\WINDOWS\System32\DriverStore\FileRepository\nvmii.inf_amd64_add1b07f2161ca7f\nvoglv64.dll (-exported-)

Location: nvoglv64.dllDrvPresentBuffers + 160DB bytes

Module:  C:\WINDOWS\System32\DriverStore\FileRepository\nvmii.inf_amd64_add1b07f2161ca7f\nvoglv64.dll (-exported-)

Location: nvoglv64.dllDrvPresentBuffers + 33458 bytes

Module:  C:\WINDOWS\System32\DriverStore\FileRepository\nvmii.inf_amd64_add1b07f2161ca7f\nvoglv64.dll (-exported-)

Location: nvoglv64.dllDrvPresentBuffers + 136775 bytes

Module:  C:\WINDOWS\System32\DriverStore\FileRepository\nvmii.inf_amd64_add1b07f2161ca7f\nvoglv64.dll (-exported-)

Location: nvoglv64.dllDrvPresentBuffers + 14426D bytes

Module:  C:\WINDOWS\System32\DriverStore\FileRepository\nvmii.inf_amd64_add1b07f2161ca7f\nvoglv64.dll (-exported-)

Location: nvoglv64.dllDrvPresentBuffers + 15BBC9 bytes

Module:  C:\WINDOWS\System32\DriverStore\FileRepository\nvmii.inf_amd64_add1b07f2161ca7f\nvoglv64.dll (-exported-)

Location: nvoglv64.dllDrvValidateVersion + 6F36 bytes

Module:  C:\WINDOWS\System32\DriverStore\FileRepository\nvmii.inf_amd64_add1b07f2161ca7f\nvoglv64.dll (-exported-)

Location: nvoglv64.dllDrvPresentBuffers + 11E131 bytes

Module:  C:\WINDOWS\System32\DriverStore\FileRepository\nvmii.inf_amd64_add1b07f2161ca7f\nvoglv64.dll (-exported-)

Location: nvoglv64.dllDrvPresentBuffers + FA122 bytes

Module:  C:\WINDOWS\System32\DriverStore\FileRepository\nvmii.inf_amd64_add1b07f2161ca7f\nvoglv64.dll (-exported-)

Location: nvoglv64.dllDrvPresentBuffers + F97E9 bytes

Module:  C:\WINDOWS\System32\DriverStore\FileRepository\nvmii.inf_amd64_add1b07f2161ca7f\nvoglv64.dll (-exported-)

Location: nvoglv64.dllDllMain + 5D19 bytes

Module:  C:\WINDOWS\System32\DriverStore\FileRepository\nvmii.inf_amd64_add1b07f2161ca7f\nvoglv64.dll (-exported-)

Location: nvoglv64.dllDllMain + 5E98 bytes

Module:  C:\WINDOWS\System32\DriverStore\FileRepository\nvmii.inf_amd64_add1b07f2161ca7f\nvoglv64.dll (-exported-)

Location: nvoglv64.dllDllMain + 5C6E bytes

Module:  C:\WINDOWS\System32\DriverStore\FileRepository\nvmii.inf_amd64_add1b07f2161ca7f\nvoglv64.dll (-exported-)

Location: nvoglv64.dllDllMain + 55DF bytes

Module:  C:\WINDOWS\System32\DriverStore\FileRepository\nvmii.inf_amd64_add1b07f2161ca7f\nvoglv64.dll (-exported-)

Location: nvoglv64.dllDrvSwapLayerBuffers + 2B5 bytes

Module:  C:\WINDOWS\System32\DriverStore\FileRepository\nvmii.inf_amd64_add1b07f2161ca7f\nvoglv64.dll (-exported-)

Location: nvoglv64.dllDllMain + 8746 bytes

Module:  C:\WINDOWS\System32\DriverStore\FileRepository\nvmii.inf_amd64_add1b07f2161ca7f\nvoglv64.dll (-exported-)

Location: nvoglv64.dll<7FFD2393942F>

Decl:  ?? 

Module:  C:\WINDOWS\System32\DriverStore\FileRepository\nvmii.inf_amd64_add1b07f2161ca7f\nvoglv64.dll (-exported-)

Location: nvoglv64.dll<7FFD2393910E>

Decl:  ?? 

Module:  C:\WINDOWS\System32\DriverStore\FileRepository\nvmii.inf_amd64_add1b07f2161ca7f\nvoglv64.dll (-exported-)

Location: nvoglv64.dllDrvValidateVersion + DF08 bytes

Module:  C:\WINDOWS\System32\KERNEL32.DLL (-exported-)

Location: KERNEL32.DLLBaseThreadInitThunk + 17 bytes

Module:  C:\WINDOWS\SYSTEM32\ntdll.dll (-exported-)

Location: ntdll.dllRtlUserThreadStart + 2C bytes

End of stack

//crash log file name = C:\Users\David\AppData\Local\Temp\MayaCrashLog250303.1745.log

//version     = 24.2.0.1186

//cut            =  10/18/2023, 202310181224

//current scene = unDisclosed

//command history (most recent last):

//====================================================

//last tool: sculptMeshCacheContext

//====================================================

//panel with focus: modelPanel4

//visible panels:

// modelPanel1 modelPanel2 modelPanel3 modelPanel4 outlinerPanel1 

//====================================================

//Memory usage:

// 5386.824 Mb Free Memory

// 12220.539 Mb Free Swap

// 1791.434 Mb Current

//====================================================

[andrewsilke]

Yes, two of us have the same access violation error on startup here. 

We are very experienced Maya users and TDs, which stumped us both. And we are not on the same company or network. 

See our two attached files from different machines on different networks; we chatted and realised we had the same issue.  Usual clean prefs, no plugins, and no fix. 

We thought it was a corrupted Python install, but we reinstalled Maya, and it's still happening.  Also, it happens in both 2024 and 2025.  

Maya will randomly startup, usually crashing say 1 in 4 times on startup, so the crash isn't reliable but it also crashes all the time with pyQt errors which seem to be basic python corruption issues.  

Also, at least on my machine, I have noticed that chrome is having access violations. For example, watching Vimeo videos and Chrome, Spotify, and Discord restarting randomly.  This has all started happening in the last week.  Perhaps this is not AD?

We thought it might be i9-related as both our CPUs are i9s, but it looks like you are on AMD. 

I think AD will find there are many people with this issue, it would be great to know what it is and a fix, as Maya is constantly crashing making it almost unusable.  

We think it could be related to a Windows update. Maybe? We are stumped. 

[Daniel.S.Lima]

Just a shot in the dark here. Does it change anything if you change the rendering engine of the viewport 2.0? Give it a try to go in Preferences>Display>Viewport2.0  to change to OpenGl, and if it's already in OpenGl, change that to DirectX.

[andrewsilke]

I haven’t tried this but my friend has 

“I tried OpenGL and directx, still crashes”

“I have added `MAYA_DISABLE_OPENCL=1` to the maya.env as noted in that page you linked too”

[millermaneo]

What we know about this is that is persists across versions of maya once this occurs. 
there is multiple error codes that seem unrelated but are likely in fact not. 
this includes the currently observed erroneous packages:
In maya directory:
python{insert version}.dll
bifrost AminoPrivateDM_2_11_0.dll
null pointer read @ shiboken6.abi3.dll

external to maya:

nvwgf2umx.dll

I also think because of the nature of mayas start up with out attaching a debugger we cant tell at what point this is actually failing as it seems there is a problem.

What we have tried:
Changing memory, incase the access violation was related to the hardware. 
Moved environment across to a different working machine to test and see if this was related to the prefs. it is not. as maya continued working as normal.
Re installations of maya also didnt work. and problem if it exists will persist over different versions,
Checked for updates that could potentially interfere (there were none that were obvious or at all.)

Hardware on tow of the systems contained an i9 -> this is a specific note as there is evidence to show this could be an issue. 
There is also preexisting evidence of a series of windows updates preventing autocad from working at all. this may be relevant.
and finally. there are other electron based apps and video playback that seem to be having some minor issues at the present time on one of these systems that started at the exact same time these issues began. (discord, youtube, vimeo etc). 

Simply put this here for troubleshooting as the issue is not resolved on this end. 

This isn't being exhibited on Linux as far as i can tell, (cannot test mac) and is present on 2 windows machines.

[andrewsilke]

Yes this matches. Multiple ways that maya can crash, including bifrost errors and qt, sometimes on startup. 

[Daniel.S.Lima]

The fact that it crashes not every time and also that it's happening in separated machines in different networks...  quite puzzling.  Can you make sure you're running Maya vanilla installation and not bootstrapped? If it's not, I would take a look at any other python installation you might have in Windows, that somehow it's taking  priority over mayapy from Maya somehow(Which is not suppose to happen regardless).  

These would be my steps to find a solution:

1 - Make sure you running Maya vanilla, and not from a company bootstraped setup, which could be forcing you to load different version of pyqt, or python at start.

2 - I would also make sure that in the windows environment settings, there is no python path forcing an specific version of Python. In fact, I would uninstall all external Python version from the PC for this test.

3 - I know it might sound helpless, but make sure you running the latest stable version of your graphics card.

I know how frustrating this can be, so I'm literally just recommending what I would do at this point.

Good luck

[david.ljungstedtN52BD]

It´s crashing almost every time I open Maya. It also has corrupted files so it won't open at all. This is the worst version of Maya and I have been using it since 2004. Time to move over to Blender I guess.

[andrewsilke]

I was able to get to the bottom of the problem on my machine.  It was indeed a bad cpu core on my i9. 

I was able to fix the issue by disabling cores in windows 11 task manager with set affinity.  See the video here. 
https://youtu.be/W6DlJxAcnTw?si=exNXmZBEeKjhsNBL

It turned out it was my cpu 12 out of 32.  Disabling that single thread solved my issue in Maya. 

Im yet to hear back from my other friend and the user MillerMilano was just summarising from our discord chat. 

This may be unrelated to other users.  If also might be a microcode release that affected multiple intel CPUs.  I’m not sure. The OP may have a intel cpu as the amd64 error log is unrelated to amd processors.