The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →“The program can’t start because cudart64_42_9.dll is missing from your computer.” You may also see “cudart64_42_9.dll was not found,” “Error loading cudart64_42_9.dll,” or “The specified module could not be found.”
The 60-second answer
cudart64_42_9.dll is a 64-bit NVIDIA CUDA runtime library associated with the CUDA 4.2 generation. It is not a Windows system file, and Windows 11 or Windows 10 does not normally install it.
As an Amazon Associate I earn from qualifying purchases.
The clearest documented source is an old Emgu CV 2.4 GPU-enabled installation, which deployed this file alongside cvextern.dll, npp64_42_9.dll, and matching OpenCV native libraries. Other older CUDA applications may also have privately distributed the runtime.
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 minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11The safest fix is to identify the application showing the error, then repair or reinstall that application from its official installer. Do not download the DLL from a random DLL website, copy it into System32, or run regsvr32 against it.
#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
What causes the error
The filename alone cannot identify the exact program that needs the file. Common causes include:
- An old Emgu CV or OpenCV GPU deployment is missing native files.
- The application was copied without its complete native dependency folder.
- A 32-bit process is trying to load a 64-bit library.
- Another DLL required by the CUDA or OpenCV files is missing.
- The required Microsoft Visual C++ runtime is absent.
- Antivirus software quarantined the file.
- An application update replaced or removed part of its previous installation.
- A CUDA-capable application needs a compatible NVIDIA driver or supported GPU.
A current CUDA Toolkit or NVIDIA display driver may not install this exact, versioned filename. Replacing it with a newer file such as another cudart64 version is not a safe substitution.
Fix 1: Identify and repair the parent application
Start with the program that displays the message. Note its name, installation folder, and whether the problem began after an update, migration, or antivirus alert.
Recommended Free Tools
Use the application’s repair option
- Press Windows key + I to open Settings.
- Select Apps, then Installed apps.
- Find the application that fails.
- Select the three-dot menu beside it.
- Choose Advanced options, if available.
- Select Repair and wait for Windows to finish.
- Start the application again.
If there is no Repair option, open the application’s own installer or launcher and look for Repair, Verify files, or Scan and repair.
If the error remains:
- Return to Settings > Apps > Installed apps.
- Select the application.
- Choose Uninstall.
- Restart Windows.
- Download the installer from the application developer or organization that supplied the program.
- Install it again using its complete native dependency package.
- Start the application before copying back custom files or plugins.
For an Emgu CV 2.4 GPU project, reinstall or redeploy the complete matching native set. That normally includes cudart64_42_9.dll, cvextern.dll, npp64_42_9.dll, the matching OpenCV libraries, and the required Visual C++ runtime. Restoring only cudart64_42_9.dll can simply expose the next missing dependency.
Run the installer as administrator if it cannot write to its application directory. Right-click the official installer, select Show more options, choose Run as administrator, and approve the User Account Control prompt.
Confirm the application folder
The application-owned copy should normally be beside the executable or in the exact native subdirectory expected by the framework.
- Right-click the application shortcut.
- Select Properties.
- Open the Shortcut tab and select Open File Location.
- Locate the application’s executable and native folders.
- Check whether the complete dependency bundle is present.
Do not move the DLL to a system folder to compensate for an incomplete installation. Windows normally searches the application directory during DLL loading, and Microsoft warns that changing DLL search locations can create security problems.
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 x86 and x64 architecture
The 64 in cudart64_42_9.dll indicates a 64-bit Windows DLL naming convention. A 32-bit application cannot load it, even when Windows itself is 64-bit.
For a Visual Studio project:
- Open the solution in Visual Studio.
- Select Project > Properties.
- Select Build.
- Check Platform target.
- Match the target to the native files you deploy.
- Avoid leaving the project on Any CPU until the native layout is confirmed.
- Rebuild the project.
- Check
binDebugorbinReleasefor the expected x64 native folder and files.
Use the x64 dependency set only when the running process is 64-bit. If the application is 32-bit, use the framework’s matching x86 package instead of forcing the 64-bit CUDA runtime into the folder.
You can also check a process while it is running:
- Press Ctrl + Shift + Esc to open Task Manager.
- Select Details.
- Right-click a column heading and choose Select columns.
- Enable Platform, if that column is available.
- Check the failing application’s architecture.
A wrong-architecture error may appear as “not designed to run on Windows,” “bad image,” or a generic application startup failure rather than a clear x86/x64 explanation.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Fix 3: Find the missing dependent DLL
“Specified module could not be found” does not always mean cudart64_42_9.dll itself is absent. The named file may be present while one of its dependencies cannot be loaded.
For an Emgu CV application, check the surrounding native files, especially:
cvextern.dllnpp64_42_9.dll- The matching OpenCV libraries
- The correct x86 or x64 native folder
- The Microsoft Visual C++ runtime
Use a reputable dependency-analysis utility from a trusted source to inspect the application executable and native DLL tree. Look for dependencies marked missing, incompatible, or loaded from an unexpected directory.
If the tool reports a missing dependency, restore it through the parent application’s official installer. Do not replace individual files with similarly named DLLs from an unrelated CUDA release.
Fix 4: Install the required Visual C++ runtime
Legacy Emgu CV 2.4 OpenCV binaries were built with Visual Studio 2010 and may require the Microsoft Visual C++ 2010 SP1 runtime. The runtime architecture must match the application: x86 for a 32-bit process and x64 for a 64-bit process.
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)
Use Microsoft’s official redistributable package or the prerequisite included with the application. Then:
- Close the failing program.
- Install the appropriate redistributable.
- Restart Windows.
- Start the application again.
- If it still fails, install the other architecture only when another 32-bit or 64-bit component in the application requires it.
Do not assume that the newest Visual C++ package is interchangeable with every legacy build. The application’s documentation or installer is the best guide.
Fix 5: Check antivirus quarantine
An old third-party binary may have been quarantined, or an unofficial replacement may genuinely be unsafe. Check the security history before restoring anything.
In Windows Security:
- Open Start and search for Windows Security.
- Select Virus & threat protection.
- Select Protection history.
- Open the event involving the application or DLL.
- Review the detected file path and threat details.
- Restore or allow it only when the file came from a trusted official installer and its provenance is clear.
- Repair or reinstall the application afterward.
Do not disable antivirus protection just to make an unknown DLL load. If the file came from a random download site, remove it and reinstall the parent application from its official source instead.
Fix 6: Check the NVIDIA driver and GPU separately
The CUDA runtime DLL and the NVIDIA display driver are different components. A driver may provide the driver-side CUDA interface, but that does not guarantee that it supplies this old, application-versioned runtime file.
Check the hardware and driver:
- Right-click Start and select Device Manager.
- Expand Display adapters.
- Confirm that the expected NVIDIA adapter is listed.
- Right-click it and select Properties.
- Open the General tab and check Device status.
- Open the Driver tab to review the provider and driver date.
- Select Update Driver if an appropriate update is available.
- Restart Windows and test the application.
If Device Manager shows a warning icon, an unknown device, or no supported NVIDIA adapter, consult the application’s hardware requirements. Install a driver from NVIDIA’s official support channel that matches the GPU and Windows version.
Outbyte Driver Updater can reduce the manual work of hunting through device entries and guessing which driver is stale; its free scan identifies issues, while driver installation through the full version is optional. For this DLL, repairing the application that owns the runtime remains the definitive fix.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsA current driver still may not recreate cudart64_42_9.dll. If the error names this exact file, return to the parent application’s installer and native dependency bundle.
Fix 7: Repair Windows components only when Windows is damaged
SFC and DISM repair Windows component corruption. They usually do not restore an application-private CUDA runtime, so use them when other Windows features are also failing or system files appear damaged.
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 Start.
- Search for Command Prompt.
- Right-click it and select Run as administrator.
- Run:
DISM.exe /Online /Cleanup-Image /RestoreHealth
- Wait for it to complete.
- Then run:
sfc /scannow
- Restart Windows.
- Test the application again.
Microsoft recommends running DISM before SFC. If both commands report that they repaired files, test the application after restarting. If they report no problems, reinstalling the parent application is more relevant than repeating the commands.
Outbyte PC Repair can make the manual process of checking system issues less repetitive by showing what its scan finds; repairs are performed through the full version and are not required for this DLL. When the file belongs to a particular application, that application’s official reinstall remains the authoritative repair.
Free tools Windows power users keep installed
One-click scans. No signup required.
Do not use Windows Features for this file
cudart64_42_9.dll is not a Windows optional feature. You can inspect Windows Features by opening Control Panel > Programs > Turn Windows features on or off, but enabling unrelated features will not install this CUDA runtime.
Do not enable random legacy components as a DLL fix. Only enable a feature when the parent application’s documentation explicitly requires it.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Why regsvr32 does not fix this error
regsvr32 is intended for DLLs that expose registration entry points such as DllRegisterServer, commonly COM or ActiveX components. A CUDA runtime library is normally a runtime dependency, not a self-registering COM server.
Running this command is therefore not an appropriate repair:
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 →regsvr32 cudart64_42_9.dll
It may produce an error saying that DllRegisterServer was not found. That result does not mean the DLL needs a different registration command. Restore the correct application files instead.
Avoid random DLL download sites
Do not obtain cudart64_42_9.dll from an unofficial DLL index or copy supplied by an unknown person. The file may have the wrong CUDA generation, wrong architecture, altered contents, or malware. Even a genuine-looking copy may not include the dependent OpenCV, CUDA, or Visual C++ files that the application needs.
Use the original application developer’s installer, the organization’s official repair or update channel, and Microsoft’s official runtime packages. For legacy CUDA software, the application’s own deployment package is usually safer and more compatible than installing a current toolkit.
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.
FAQ
Is cudart64_42_9.dll part of Windows?
No. Treat it as third-party application software associated with NVIDIA CUDA-era programs.
Does the filename prove that I need an NVIDIA GPU?
No. The file is a CUDA runtime library, but the exact application may use it differently. A GPU-enabled program may require a supported NVIDIA GPU and driver, while the missing-file error itself usually indicates an incomplete application deployment.
Should I copy it to System32 or SysWOW64?
No. Keep the matching application-owned file beside the executable or in the framework’s expected native folder. System32 is the native system directory on 64-bit Windows, not simply the 32-bit DLL folder.
Can I replace it with a newer CUDA runtime?
No. Versioned CUDA runtime files are not guaranteed to be compatible. Restore the version required by the application.
What if the file exists but the error continues?
Check x86/x64 architecture and inspect dependent DLLs. “Specified module could not be found” can identify a missing dependency rather than the named file itself.
When should I use System Restore?
Use it only as a last resort when the failure began after a known system change and a clean application repair or reinstall is unavailable. It is not a DLL-specific repair.
What information should I collect for further troubleshooting?
Record the exact executable name, application and framework version, complete error text, process architecture, installation path, antivirus action, and any missing dependency reported by a trusted dependency checker.
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.
