ucrtbase.dll error causing Solidworks to crash constantly- Windows 11 Home

Question

ucrtbase.dll error causing Solidworks to crash constantly- Windows 11 Home

Alex Kroll 0

I am running Solidworks 2022 SP5.0 on a Windows 11 Home edition. It is consistently crashing even doing simple tasks. I have been in touch with my reseller for support to guide me through troubleshooting. I have tried reinstalling Solidworks, reinstalling the x64 and x86 C++ redistributables, rebuilding the Solidworks registries, running Windows SFC/DISM, and it is still crashing. Typically, whenever I go to close out a file, the entire software will crash but does not give a normal crash report. I have also had Fusion 360 crash although I cannot be sure at this time that it is related. Every time Solidworks does crash, Event Viewer blames ucrtbase.dll. When I ran SFC it claimed that there were corrupted files and they have been repaired, but even after restarting my system, the crashing persists. I am up to date on Windows updates.

I have included the log generated after I ran SFC. sfcdetails.txt

0 comments

1 answer

Your answer

Answer 1

Francisco Montilla 30,620 Independent Advisor

Hello,

Since you already reinstalled Solidworks, rebuilt registries, ran SFC, and even reinstalled the C++ redistributables, the issue probably is not the ucrtbase.dll file itself or Solidworks being corrupted. Usually when ucrtbase.dll causes both Solidworks and Fusion 360 to crash during specific actions like closing a file, it means another background program, driver, or service is improperly hooking into your CAD software and bringing it down.

To help me figure out exactly what is causing the interference, I need you to check a few things for me.

First, can you open up Event Viewer, go to Windows Logs then Application, find one of those recent Solidworks crash events, and let me know the Exception Code? It will usually look something like 0xc0000409 or 0xc0000005.

Second, what brand is your PC or motherboard? Built in audio overlays or utilities that come preinstalled on systems like ASUS, MSI, or Alienware are heavily known for injecting into CAD UI elements and forcing ucrtbase.dll to fault when rendering changes.

Lastly, check if it still crashes when closing a file if you run Solidworks in Software OpenGL mode. You can open the Solidworks RX tool and launch it in safe mode to bypass the graphics card. This will immediately tell us if the graphics driver or hardware acceleration is the main issue.

Let me know what you find out and we can move forward from there.

Alex Kroll 0 Reputation points

2026-05-14T19:44:01.3566667+00:00

The exception code is: 0xc0000409

The brand is ASUS. Specifically, a ProArt Studiobook 16 H7600ZX.

I have run it in OpenGL mode and updated the graphics drivers before, and it still crashes.
Francisco Montilla 30,620 Reputation points Independent Advisor

2026-05-14T19:51:36.6166667+00:00

I see, I took a closer look at the diagnostic data. It shows this specific stack buffer overrun crash is notoriously caused by ASUS Sonic Studio or the Nahimic audio service that comes preinstalled on ASUS machines. These audio utilities try to inject sound overlays into 3D applications, which trips up that dll file.

Press the Windows key, type Services, and hit Enter. Scroll through the list and look for anything named Nahimic service or ASUS Sonic Studio. Right click the service, select Properties, change the Startup type to Disabled, and click the Stop button to kill the process. Click Apply and OK.

Next, open your Task Manager, navigate to the Startup apps section, and disable any Nahimic or Sonic Studio entries so they stop loading when you boot up.

Restart your computer and test Solidworks again, let me know how that goes.
Alex Kroll 0 Reputation points

2026-05-14T20:00:21.83+00:00

I'm not seeing either of those in the services list, nor do they come up when I go to startup apps or search for them in the taskbar.
Francisco Montilla 30,620 Reputation points Independent Advisor

2026-05-15T08:28:11.59+00:00

Okay, time to dig then.

Please do a clean boot to completely isolate if any third-party background service is causing this crash. Press the Windows key, type msconfig, and press Enter to open System Configuration. Go to the Services tab, check the box at the bottom that says Hide all Microsoft services, and then click the Disable all button.

After that, go to the Startup tab, click Open Task Manager, and disable every startup item listed there. Restart your laptop and try using Solidworks again.

Does it still crash when you close a file?
Alex Kroll 0 Reputation points

2026-05-15T15:33:14.2733333+00:00

That seems to have worked, thank you so much. What do I need to do in order to figure out what specifically caused this? Simply turn on the background services one at a time until the issue returns?
Alex Kroll 0 Reputation points

2026-05-15T15:49:08.6766667+00:00

Of course, as soon as I say that it starts crashing again, just in a different way. Now event viewer is saying this:

Although this seems to only happen when I go to open one file (that I hadnt tried to open before) in particular so I think this specific file may just be corrupted.
Francisco Montilla 30,620 Reputation points Independent Advisor

2026-05-16T05:53:03.9133333+00:00

You're right about the background services. You just enable half of them at a time and restart until the crashing comes back to pinpoint the exact one causing the conflict.

Regarding the new error in the image, the 0xc0000005 exception code means access violation. Solidworks is trying to read a piece of system memory it is not allowed to reach. Since it only happens with that one specific document and faults on the sldappu.dll module, your guess is correct. The file itself or a specific feature inside it is corrupted and causing the program to trip over itself.

Do you have access to a different machine where you can try opening that exact file just to be absolutely sure it is permanently broken?

Share via

ucrtbase.dll error causing Solidworks to crash constantly- Windows 11 Home

1 answer

Your answer