Start with this diagnostic checklist
Recommended Free Tools
Before replacing anything, identify the application that displays the error.
- Which program or game fails: note its exact name and launcher.
- When it fails: during launch, after an update, after moving the game, or after security software reported a problem.
- Application architecture: a 32-bit program needs a 32-bit DLL, even when Windows itself is 64-bit.
- Likely owner: an older PhysX-based game, an application built with NVIDIA CUDA 6.5, or software that bundled its own runtime.
- Expected location: the file may need to sit beside the affected executable rather than in a Windows system folder.
The error may say:
- “The program can’t start because cudart32_65.dll is missing from your computer.”
- “cudart32_65.dll was not found.”
- “Cannot find cudart32_65.dll.”
- “The code execution cannot proceed because cudart32_65.dll was not found.”
- An older game may instead stop with “General Protection Fault.”
cudart32_65.dll is the 32-bit Windows CUDA Runtime DLL associated with NVIDIA CUDA Toolkit 6.5. It is not a Windows component. It can also be present in NVIDIA PhysX packages and older games, so the correct repair depends on the application that is failing.
Fix 1: Repair the affected game or application
This is the safest and most likely fix. A missing application-local DLL usually means the installation is incomplete, damaged, moved, or missing one of its optional runtime components.
EA App
- Open the EA app.
- Select Library.
- Find the affected game.
- Select its three-dot menu.
- Choose Repair.
- Wait for the scan and replacement process to finish.
- Start the game again from the EA app.
A successful repair restores the files expected by the game and allows it to launch without the DLL message. If the error remains, restart Windows and repeat the launch once before moving to a reinstall.
#1 Best Overall
- AI Performance: 767 AI TOPS
- OC mode: 2632 MHz (OC mode)/ 2602 MHz (Default mode)
- Powered by the NVIDIA Blackwell architecture and DLSS 4
- Axial-tech fan design features a smaller fan hub that facilitates longer blades and a barrier ring that increases downward air pressure
- A 2.5-slot design maximizes compatibility and cooling efficiency for superior performance in small chassis
Steam
- Open Steam.
- Select Library.
- Right-click the affected game and choose Properties.
- Select Installed Files.
- Choose Verify integrity of game files.
- Allow Steam to replace missing or damaged files.
- Launch the game from Steam.
If Steam reports that files were replaced but the same error returns, check whether antivirus software is removing the file again. Also consider uninstalling and reinstalling the game to its original library location.
Other launchers and standalone applications
Look for a menu named Repair, Verify, Scan, or Validate. If no repair option exists:
- Close the program.
- Back up saved games or application data if necessary.
- Uninstall the application from Settings → Apps → Installed apps.
- Restart Windows.
- Download the installer from the application publisher or launcher.
- Install the program again.
- Test it before adding unofficial files or compatibility tweaks.
This approach is preferable because the program may require a particular build of several related files, not just cudart32_65.dll.
Fix 2: Repair or reinstall NVIDIA PhysX
Older games may obtain this DLL from NVIDIA PhysX rather than from a separately installed CUDA development environment. A failed PhysX installation, launcher migration, driver cleanup, or manual deletion can leave the game without its private runtime files.
NVIDIA PhysX installations commonly contain files under:
C:Program Files (x86)NVIDIA CorporationPhysXCommon
First, check whether that folder exists. Do not copy files from it yet unless you have confirmed that the affected game is one that uses PhysX.
Rank #2
- Powered by the NVIDIA Blackwell architecture and DLSS 4
- Powered by GeForce RTX 5070 Ti
- Integrated with 16GB GDDR7 256bit memory interface
- PCIe 5.0
- WINDFORCE cooling system
- Open Settings → Apps → Installed apps.
- Search for NVIDIA PhysX System Software.
- If it is present, select the three-dot menu and choose Uninstall.
- Restart Windows.
- Install the appropriate PhysX System Software package from NVIDIA.
- For particularly old PhysX games, use NVIDIA’s Legacy PhysX System Software package.
- Start the game again.
If the game came from EA, EA has documented an application-folder workaround for certain older titles, including Medal of Honor, Mass Effect 1, and Battlefield 3. In that narrow situation, copy cudart32_65.dll from the verified PhysX Common directory into the folder containing the affected game executable.
Microsoft’s DLL search-order documentation explains why this can work: Windows normally checks the application directory as part of resolving a DLL dependency. This is an application-specific compatibility workaround, not a general Windows installation method.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC 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 & 11If the game uses a different executable than expected, check its launcher shortcut or installation folder before copying. Place the file beside the executable that produces the error, not in C:WindowsSystem32.
Fix 3: Install the matching CUDA 6.5 32-bit runtime
Use this path when the failing application is explicitly a CUDA application or its documentation identifies CUDA Toolkit 6.5.
NVIDIA’s CUDA 6.5 archive provides separate Windows packages, including:
cuda_6.5.19_windows_general_32.exe
cuda_6.5.19_windows_general_64.exe
cudart32_65.dll is a 32-bit file, so an application that requires this exact name needs the 32-bit CUDA package. Windows being 64-bit does not change that requirement. The architecture of the application determines which DLL architecture it can load.
Rank #3
- 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
- Confirm that the application is the one that requires CUDA 6.5.
- Obtain the CUDA 6.5 installer from NVIDIA’s official archive or use the application’s original installer.
- Choose the Windows 32-bit package when the affected program is 32-bit and specifically requires
cudart32_65.dll. - Run the installer with administrator approval.
- Restart Windows if the installer requests it.
- Launch the application again.
Installing the newest CUDA toolkit is not guaranteed to provide this legacy filename or to be binary-compatible with software built against CUDA 6.5. If the application bundled its own runtime, reinstalling that application is usually more reliable than installing a system-wide toolkit.
Fix 4: Check antivirus quarantine
Security software may quarantine a legitimate runtime after a game update or reinstall.
- Open Windows Security.
- Select Virus & threat protection.
- Choose Protection history.
- Look for an event involving
cudart32_65.dllor the affected application. - Confirm that the file came from the original game installation or a trusted NVIDIA installer.
- Restore it only when its provenance is clear.
- Reinstall or repair the application if the file cannot be verified.
Do not disable antivirus protection globally. If the file is repeatedly quarantined, use the original installer and inspect the file’s digital signature and location before considering an exception.
Fix 5: Confirm the application and DLL architecture
A 64-bit replacement such as cudart64_65.dll cannot substitute for cudart32_65.dll. Similarly, a similarly named DLL from another CUDA release may not satisfy an older application.
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 →To investigate the architecture:
- Right-click the application executable and choose Properties.
- Open the Details and Compatibility tabs for available information.
- Check the launcher’s metadata or documentation.
- In Task Manager, start the program if possible and inspect whether Windows labels it as a 32-bit process.
- Look in the application’s installation folder for other runtime files and their naming pattern.
If a corrected file produces an error stating that the program is “not designed to run on Windows,” or returns status code 0xc000012f, stop replacing files. The DLL may be corrupt, incompatible, or the wrong architecture. Repair or reinstall the owning package instead.
Fix 6: Check drivers, but do not treat this as a driver DLL
NVIDIA graphics drivers can be involved in the history of an older game installation, but cudart32_65.dll is not normally repaired by placing a graphics-driver file in a system folder. A driver cleanup may also have removed a PhysX component that the game expected.
Rank #4
- Powered by the NVIDIA Blackwell architecture and DLSS 4
- Powered by GeForce RTX 5060
- Integrated with 8GB GDDR7 128bit memory interface
- PCIe 5.0
- WINDFORCE cooling system
To inspect the installed driver:
- Right-click Start and open Device Manager.
- Expand Display adapters.
- Right-click the NVIDIA adapter and select Properties.
- Open the Driver tab.
- Note the provider, date, and version.
- Use Update driver only when a suitable official driver is available.
- Restart Windows and retest the application.
Manually hunting through multiple driver packages can make it difficult to know which component changed. Outbyte Driver Updater can scan for outdated drivers; its free scan identifies issues, while driver installation is handled by the full version. Reinstalling the affected game or its PhysX runtime remains the definitive fix when that program owns the missing DLL.
Fix 7: Run Windows integrity checks only for broader corruption
Windows repair commands generally do not recreate a third-party CUDA or PhysX DLL. Use them when other Windows components are also failing, updates are damaged, or system corruption is suspected.
Free tools Windows power users keep installed
One-click scans. No signup required.
- Open Start.
- Type 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.
- Repair or reinstall the affected application again.
Microsoft recommends running DISM before SFC. DISM repairs the Windows image, while SFC checks protected Windows system files. Neither command should be expected to restore an application-owned cudart32_65.dll.
Repeating these commands without knowing what changed makes troubleshooting harder. Outbyte PC Repair can scan and show system issues; the free scan identifies problems, while repair is handled by the full version. If this DLL belongs to a specific game or application, reinstalling that program is still the definitive repair.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Do not use regsvr32 or random DLL websites
cudart32_65.dll is a runtime library, not a typical COM component. Running:
regsvr32 cudart32_65.dll
is inappropriate. The expected result is an error such as:
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →The module was loaded but the entry-point DllRegisterServer was not found.
That does not mean registration is missing. It means this DLL does not provide the registration entry point that regsvr32 expects.
Best Value
- Powered by the NVIDIA Blackwell architecture and DLSS 4 OC mode: 2640MHz/Default mode: 2610MHz (Boost Clock)
- Military-grade components deliver rock-solid power and longer lifespan for ultimate durability
- Protective PCB coating helps protect against short circuits caused by moisture, dust, or debris
- 3.125-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
Avoid downloading an isolated copy from an unaffiliated DLL repository. The file may contain malware, belong to a different CUDA release, have the wrong architecture, or fail to match other files required by the application. Do not place random copies in C:WindowsSystem32 or C:WindowsSysWOW64. Windows may continue loading a private application copy, and a system-folder copy can introduce unrelated version conflicts.
Use the original game installer, the official launcher repair process, a verified NVIDIA PhysX package, or the official CUDA 6.5 archive instead.
If the error still returns
Check these items in order:
- Confirm that you are repairing the executable that actually fails.
- Check the launcher cache and verify the game files again.
- Inspect antivirus Protection History after each repair.
- Check file permissions on the game directory.
- Look for disk errors if files repeatedly disappear.
- Remove manually copied DLLs and reinstall the owning package.
- Check whether multiple CUDA versions or
PATHentries cause the application to load an unintended copy. - Use System Restore only if the problem began immediately after a known installation or update.
System Restore can revert system settings and installed programs, but it does not normally remove personal files. It is a recovery option, not a substitute for identifying the application that owns the DLL.
FAQ
Does cudart32_65.dll belong to Windows?
No. It is third-party NVIDIA runtime software associated with CUDA 6.5 and, in some installations, PhysX or an older game.
Why does a 32-bit DLL appear on 64-bit Windows?
A 32-bit application must load 32-bit dependencies. The operating system’s architecture does not determine the architecture of every application installed on it.
Will installing Visual C++ Redistributable, DirectX, or .NET fix it?
Usually not. Those packages may be required by the same game, but they do not normally restore this specific CUDA or PhysX DLL.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesCan I copy the file from the PhysX folder?
Only when the affected game is known to use that PhysX runtime and the source installation is trusted. Copy it beside the affected executable, following the documented compatibility workaround. Do not treat this as a universal Windows fix.
Should I install both 32-bit and 64-bit CUDA?
No. Install the package required by the application. A 64-bit CUDA runtime cannot replace cudart32_65.dll, and a newer release may not satisfy an application built for CUDA 6.5.
Why does the error appear after moving a game to another launcher?
The migration may omit bundled PhysX or application-local runtime files. Repairing or verifying the game through the new launcher is the correct first step.
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.
