“The program can’t start because nvrtc64_101_0.dll is missing from your computer.” The nvrtc64_101_0.dll error usually means that a CUDA-enabled application cannot find its NVIDIA NVRTC runtime files.
This is not a Windows system DLL. It belongs to NVIDIA CUDA Toolkit 10.1 and provides runtime compilation for CUDA device code. The safest fix is normally to repair the application that requested it, not to download the DLL and copy it into System32.
As an Amazon Associate I earn from qualifying purchases.
Which fix applies to you
Use this list to choose the shortest safe path:
- Only one game or program fails: Repair, reinstall, or verify that application first.
- The error appeared after antivirus cleanup: Check Windows Security Protection history and confirm whether a trusted application file was quarantined.
- Several CUDA applications fail: Repair the CUDA installation, inspect CUDA-related PATH entries, and check the NVIDIA driver.
- The application specifically requires CUDA 10.1: Install or repair the official CUDA Toolkit 10.1 package, including its NVRTC runtime.
- The file exists but Windows still reports a missing module: A dependency, DLL search path, architecture, or CUDA version may be wrong.
- Windows has other corruption symptoms: Run DISM followed by SFC, but do not expect those tools to restore a third-party CUDA file.
- The message says the file is not designed to run on Windows: Replace the file through the owning application or official CUDA installer. It may be corrupt, incompatible, or the wrong architecture.
What nvrtc64_101_0.dll is
The name identifies the file:
nvrtcmeans NVIDIA Runtime Compilation.64identifies the 64-bit runtime family.101identifies CUDA 10.1._0is part of NVIDIA’s CUDA 10.1 naming pattern.
CUDA applications use NVRTC to compile CUDA code while they run. Applications that may depend on it include machine-learning packages, scientific software, renderers, computer-vision programs, OptiX applications, and packaged Python environments.
NVIDIA’s CUDA 10.1 Windows layout normally places the runtime in:
#1 Best Overall
- Powered by the NVIDIA Blackwell architecture and DLSS 4. System Requirements: Minimum 850W PSU with 16-pin 12V-2x6 (12VHPWR) connector required. Verify before purchasing.
- Military-grade components deliver rock-solid power and longer lifespan for ultimate durability. Compatibility: 348mm (13.7") length, 3.6 slots, 4.3 lbs. Confirm case clearance and slot spacing. GPU bracket included.
- Protective PCB coating helps protect against short circuits caused by moisture, dust, or debris
- 3.6-slot design with massive fin array optimized for airflow from three Axial-tech fans
- Phase-change GPU thermal pad helps ensure optimal thermal performance and longevity, outlasting traditional thermal paste for graphics cards under heavy loads
C:Program FilesNVIDIA GPU Computing ToolkitCUDAv10.1bin
An application may also ship a private copy in its own installation directory or environment. That is why reinstalling the display driver alone may not restore this file.
The file is not normally supplied by Windows in C:WindowsSystem32 or C:WindowsSysWOW64. Do not treat it like a Windows component.
Fix 1: Repair the program that fails
This is the best first fix when one application refuses to start.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallFor a normal desktop application
- Press Windows + I to open Settings.
- Select Apps.
- Select Installed apps.
- Find the program that produced the error.
- Select the three-dot menu beside it.
- Choose Advanced options, if available.
- Select Repair.
- Start the application again.
If there is no Repair option, download the installer from the application’s official publisher and run it over the existing installation. Choose Repair if the installer offers that option. Otherwise, uninstall and reinstall the program using the publisher’s installer.
Do not delete the application folder first unless the publisher’s instructions require it. Some applications keep configuration, licenses, or private CUDA runtimes there.
For a Steam game
- Open Steam.
- Select Library.
- Right-click the affected game.
- Select Properties.
- Select Installed Files.
- Select Verify integrity of game files.
- Wait for Steam to complete the check.
- Launch the game again.
Verification replaces missing or damaged files from Steam’s official content source. If the error remains, check whether the game has a separate launcher repair option or a required runtime installer in its installation folder.
How to tell whether this worked
The application should launch without the nvrtc64_101_0.dll message. If the error changes to another missing CUDA file, such as nvrtc-builtins64_101.dll, the installation is still incomplete and should be repaired again rather than patched with an unrelated download.
Rank #2
- Chipset: NVIDIA GeForce GT 1030
- Video Memory: 4GB DDR4
- Boost Clock: 1430 MHz
- Memory Interface: 64-bit
- Output: DisplayPort x 1 (v1.4a) / HDMI 2.0b x 1
Fix 2: Check whether antivirus quarantined the file
Security software can remove or quarantine a CUDA DLL after an application update, cleanup, or scan.
- Open Windows Security from the Start menu.
- Select Virus & threat protection.
- Select Protection history.
- Review recent actions.
- Expand an entry associated with the affected application or CUDA runtime.
- Confirm the original file path and the application that installed it.
Only restore a file when you recognize the application, obtained it from a legitimate publisher, and the installation is trustworthy. If the file came from a random download site, do not restore it. Reinstall the parent application instead.
After restoring a trusted quarantined file, start the application. If Windows Security immediately quarantines it again, leave it blocked and reinstall the application from its official source.
Fix 3: Install matching CUDA 10.1 files
Install CUDA only when the affected program genuinely expects CUDA 10.1. A newer CUDA runtime with a different filename does not automatically satisfy a program requesting nvrtc64_101_0.dll.
Use NVIDIA’s official CUDA Toolkit archive and select the CUDA 10.1 Update 2 Windows x86_64 installer. During setup, retain the NVRTC runtime component. Do not install an isolated DLL from a file-download site.
Before installing, close CUDA applications and note whether the failing program is a self-contained application. If it ships its own CUDA files, installing the full toolkit may be unnecessary and can introduce conflicting versions.
After installation:
- Restart Windows.
- Launch the affected application.
- If it still fails, inspect whether the application is loading its own private CUDA directory.
- Repair or reinstall the application if its private
binorLibrarybinfolder is incomplete.
A 64-bit program requires the 64-bit runtime identified by this filename. Installing a 32-bit CUDA file, or copying a similarly named file from another CUDA release, will not resolve the problem.
Rank #3
- Powered by NVIDIA GeForce GT 730, 28nm GK208 chipset process with 902MHz core frequency, integrated with 4096MB DDR3 memory and 64-bit bus width
- More stable performance, compatible with Win11, can automatically install new driver
- Support NVIDIA Surround technology for 4 screens output by dual HDMI and VGA / DP. HDMI Max Resolution-2560x1600, VGA Max Resolution-2048x1536, DP Max Resolution-2560x1600
- Support DirectX 12, OpenGL 4.6, CUDA, OpenCL, DirectCompute and DirectML
- Original half height bracket matches with the low profile brackets make the Glorto GeForce GT 730 graphics card fit well with all PC tower, small form factor and HTPC(except micro form factor)
Fix 4: Check CUDA paths and conflicting installations
Several CUDA versions can coexist, but an incorrect PATH order can make an application load an unintended runtime.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →- Press Windows + R.
- Type
sysdm.cpland press Enter. - Open the Advanced tab.
- Select Environment Variables.
- Under both User variables and System variables, inspect
Path. - Look for CUDA entries such as a
CUDAv10.1bindirectory. - Remove entries that point to folders that no longer exist.
- Avoid placing an unrelated CUDA version ahead of the version required by the application.
- Select OK on each window.
- Restart the application.
Do not remove a PATH entry merely because it contains another CUDA version. Some programs need different versions. The goal is to prevent a generic system PATH entry from overriding an application’s private runtime.
If one application fails while others work, restore the application’s own files instead of changing global PATH settings.
Fix 5: Repair or update the NVIDIA driver
Although nvrtc64_101_0.dll is a CUDA/NVRTC runtime component rather than a normal Windows graphics-driver DLL, CUDA applications also require a compatible NVIDIA driver. A driver update can expose an existing toolkit or application installation problem, and a damaged driver can cause broader CUDA failures.
Check the driver in Device Manager
- Right-click the Start button.
- Select Device Manager.
- Expand Display adapters.
- Right-click the NVIDIA adapter.
- Select Properties.
- Open the Driver tab.
- Note the provider, date, and version.
- Select Update Driver.
- Choose Search automatically for drivers.
If the problem began immediately after a driver update:
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
- Return to the Driver tab.
- Select Roll Back Driver, if available.
- Restart Windows.
- Test the application again.
For a clean repair, obtain the driver from NVIDIA’s official driver page or your computer manufacturer. Select the correct Windows version and hardware model. A driver installer is not a replacement for the CUDA Toolkit when the missing file belongs to CUDA 10.1.
Manually hunting through multiple hardware-driver pages and guessing which package is stale can be time-consuming. Outbyte Driver Updater can scan for outdated drivers; its free scan identifies issues, while driver installation through the full version is optional, and reinstalling the affected CUDA application remains the definitive fix when its private files are missing.
Fix 6: Repair Windows components with DISM and SFC
Use these commands when the PC has wider corruption, such as repeated Windows component errors, failed updates, or several unrelated programs failing. They generally do not restore a third-party CUDA DLL.
Rank #4
- Memory Speed:19 Gbps.Digital Max Resolution: 3840 x 2160
- NVIDIA GeForce GT 730 GPU. 384 processor cores. 4GB DDR3. 64-bit memory bus. Engine clock: 902 MHz. Memory clock: 1600 MHz. PCI Express 2.0 (x8 lanes)
- Package contents : ZOTAC GeForce GT 730. 1 x Low-profile bracket [VGA]. 1 x Low-profile bracket [DVI + HDMI]. User manual.Driver disc
- 1 x DL-DVI-D. 1 x VGA. 1 x HDMI. Triple simultaneous display capable. HDCP compliant.
- 300-watt power supply recomillimeterended. 25-watt max power consumption
- Open the Start menu.
- Type Command Prompt.
- Right-click Command Prompt.
- Select Run as administrator.
- Select Yes at the User Account Control prompt.
- Run:
DISM.exe /Online /Cleanup-Image /RestoreHealth
Wait for DISM to finish. Then run:
sfc /scannow
Restart Windows after both commands complete and test the application.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Microsoft recommends running DISM before SFC because DISM can repair the component store that SFC uses. If SFC reports that it found and repaired corrupted files, test again. If it reports that it could not repair everything, repeat the application repair steps and review Windows Update health.
Repeating SFC and DISM without knowing whether Windows components changed can waste time. Outbyte PC Repair can scan for broader system issues; its free scan shows detected problems, while repair through the full version is optional, and it cannot replace reinstalling the application that owns this CUDA runtime.
Fix 7: Diagnose a file that exists but will not load
A message such as “The specified module could not be found” does not always mean the named DLL itself is absent. Windows may be unable to find a dependency required by NVRTC.
Check these possibilities:
- The application is 64-bit but received a 32-bit file.
- The file belongs to another CUDA release.
- A companion file such as
nvrtc-builtins64_101.dllis missing. - The application’s DLL search path does not include its private runtime directory.
- The file is damaged or blocked.
- Another CUDA installation is being loaded first.
- A required Microsoft runtime is separately missing.
Repair the owning application before copying anything manually. If the program vendor documents a private deployment, the exact matching runtime may be placed beside the application executable, but use the vendor’s installer or package manager whenever possible.
Free tools Windows power users keep installed
One-click scans. No signup required.
If the message says the file is not designed to run on Windows, suspect corruption, wrong architecture, wrong version, or a non-Windows file. Replace the complete application component rather than replacing only one DLL.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Why regsvr32 is not the fix
Do not normally run:
regsvr32 nvrtc64_101_0.dll
NVRTC is a runtime library, not a COM or ActiveX component intended for registry registration. regsvr32 works only with DLLs that provide the registration entry point. Running it against NVRTC will typically produce an error and will not repair the application.
Likewise, do not copy the file into System32 or SysWOW64. This can create version conflicts and does not repair the application’s dependency layout.
Best Value
- Designed for professional workflows, the PNY Nvidia RTX A400 is a single-slot, low-profile graphics card optimized for compact business systems and professional environments.
- Powered by Nvidia Ampere architecture and featuring 768 CUDA cores, it delivers exceptional compute power for AI, ray-tracing, and modelling tasks.
- Equipped with 4GB GDDR6 memory for high-speed data transfer and seamless multitasking across demanding applications like video production and 3D rendering.
- Supports PCI Express 4.0, providing enhanced bandwidth for next-gen connectivity in modern workstations and business systems.
- Offers four Mini DisplayPort 1.4a outputs for connecting multiple high-resolution displays (4x 5120 x 2880 @ 60 Hz), ideal for professional video editing and visualization workflows.
If several CUDA programs still fail
When multiple CUDA applications report related errors:
- Confirm the NVIDIA GPU appears normally in Device Manager.
- Check for a recent driver rollback or failed update.
- Inspect CUDA PATH entries.
- Repair the CUDA Toolkit version required by those programs.
- Check each application’s private CUDA folders.
- Reinstall packages into the correct 64-bit environment.
- Restart Windows and test each program separately.
If malware or file tampering is suspected, run a full Microsoft Defender scan or Microsoft Defender Offline scan, then reinstall the legitimate application.
FAQ
Is nvrtc64_101_0.dll part of Windows?
No. It is an NVIDIA CUDA 10.1 NVRTC runtime file and is not normally installed by Windows.
Can I download the DLL by itself?
Avoid random DLL download websites. The file may contain malware, have the wrong architecture, belong to another CUDA version, or leave the actual application problem unresolved. Use the affected application’s installer, its package manager, or NVIDIA’s official CUDA distribution.
Does installing the latest NVIDIA display driver fix it?
Not necessarily. The driver and CUDA Toolkit are related but separate components. The application may need CUDA 10.1 NVRTC files that a display-driver installation does not provide.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsWhat does 101 mean?
It identifies CUDA 10.1 in NVIDIA’s pre-11.3 NVRTC naming pattern.
Should I copy it to System32?
No. Keep the file in the application’s managed directory or the matching CUDA Toolkit bin directory.
What if only one game fails?
Verify or repair that game first. A single-program failure usually points to incomplete or damaged application files rather than Windows corruption.
When should I use System Restore?
Use it only as a last resort when the failure began immediately after a known installation or update and no application repair is available. It can remove later applications and settings.
Recommended Free Tools
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
