Windows Troubleshooting

NAM Division 1.0.3 has seemed to fix Windows crashes for all but one person who reported a consistant crash on load. This page is to help in the rare event that you are also having problems.

Windows crash troubleshooting

If NAM Division closes immediately, or causes your DAW to close, please try the following steps in order.

1. Confirm the installed version

Make sure you are using the latest release and launching the installed application—not the installer.

Standalone application:

C:\Program Files\NAM Division\namdivision_x64.exe

VST3:

C:\Program Files\Common Files\VST3\namdivision.vst3

NAM Division currently supports 64-bit Windows 10 and Windows 11.

2. Check for an existing process

Open Task Manager and end any existing namdivision_x64.exe processes, then try launching the standalone again.

Restarting Windows will also clear any hidden or stuck instances.

3. Reset NAM Division's saved settings

1. Press Win+R.
2. Enter %LOCALAPPDATA%.
3. Find the folder named namdivision.
4. Rename it to namdivision-backup.
5. Try NAM Division again.

Renaming the folder is safe and preserves the old settings. This resets saved audio-device selections and model/IR library locations.

4. Select the high-performance GPU

NAM Division uses OpenGL for its interface. On systems with integrated and dedicated graphics:

1. Open Settings → System → Display → Graphics.
2. Add namdivision_x64.exe.
3. Select Options → High performance.
4. For the VST3, apply the same setting to your DAW executable.
5. Install the latest Intel, NVIDIA or AMD graphics driver.

Please mention if you are using Remote Desktop, a virtual machine, Parallels, or “Microsoft Basic Display Adapter”.

5. Test the VST3 in a blank project

Create a completely new DAW project and insert NAM Division without loading a model.

When reporting the problem, tell us exactly when it occurs:

• During the DAW's plugin scan
• When inserting NAM Division
• Only when opening the plugin window
• When loading a .nam file
• Only when reopening an existing project

6. Check for old plugin copies

Search your DAW's plugin locations for additional copies of namdivision.vst3.

The current copy should normally be located at:

C:\Program Files\Common Files\VST3\namdivision.vst3

Temporarily rename or move any older manually installed copies, then make the DAW rescan its plugins.

7. Check Windows security

NAM Division is free and currently distributed without a paid code-signing certificate. Check:

• Windows Security → Protection history
• Any third-party antivirus or endpoint-security history
• On Enterprise systems: Event Viewer → Applications and Services Logs → Microsoft → Windows → CodeIntegrity → Operational
• On Enterprise systems: Event Viewer → Applications and Services Logs → Microsoft → Windows → AppLocker → EXE and DLL

Please report any entry mentioning namdivision, the installer, or your DAW.

8. Collect crash information

Open Reliability Monitor by pressing Win+R and running:

perfmon /rel

Select the NAM Division or DAW failure and include its technical details.

You can also check:

Event Viewer → Windows Logs → Application

Please copy the following fields if available:

• Faulting application
• Faulting module
• Exception code
• Fault offset

Information to include in your report

Please include:

• NAM Division version
• Standalone, VST3, or both
• Exact point at which it crashes
• DAW name and version
• Windows edition and complete build number from winver
• Whether Windows Insider builds are enabled
• 64-bit x64 or Windows on ARM
• CPU
• GPU and graphics-driver version
• Audio interface and ASIO-driver version
• Whether resetting %LOCALAPPDATA%\namdivision helped
• Whether selecting the high-performance GPU helped
• Reliability Monitor or Event Viewer details

Please do not upload full crash dumps publicly, as they can contain local file paths and other personal information.