After investigating this particular issue, it turns out that there are several different underlying causes that might be triggering this particular error code. Here’s a list of potential culprits that might be causing this error code with the legacy game Diablo II: Now that you have become familiar with every underlying cause that might be causing this issue, here’s a list of confirmed methods that other affected users have successfully used to resolve the ‘Error 25: A Critical error has occurred while initiating Direct3D’ when launching Diablo II:
Method 1: Running the Game in Windowed Mode
As it happens with a lot of legacy games that were originally built around a deprecated Direct3D version, you should be able to circumvent the apparition of the ‘Error 25: A Critical error has occurred while initiating Direct3D‘ by modifying the executable so that you force it to run in windowed mode. Several affected users have confirmed that this workaround has successfully allowed them to finally run Diablo II normally without issues. If you haven’t tried this fix yet, follow the instructions below to re-configure the properties screen of the game’s shortcut or main executable so that it’s forced to run in windowed mode: In case the same problem is still occurring, move down to the next potential fix below.
Method 2: Running the Game in Compatibility Mode (with admin access)
If running the game in windowed mode didn’t allow you to circumvent the issue, you should proceed by using the same Properties screen to run ensure that the legacy version of Diablo II runs in compatibility mode with Windows XP and that admin access is granted. This fix is confirmed to work by a lot of Diablo II players that were encountering this issue on Windows 10. For step by step instructions on configuring the game to be rendered in compatibility mode with Windows XP and grant admin access from the Diablo II shortcut, follow the instructions below: If the problem is still not fixed even when you run the game in compatibility mode, move down to the next potential fix below.
Method 3: Using a Wrapper for Direct3D
If the first 2 methods didn’t work in your case, you’ve pretty much eliminated every potential cause that might be causing the ‘Error 25: A Critical error has occurred while initiating Direct3D‘ that’s outside the scope of an outdated Direct3D version. Keep in mind that Direct3D (the technology used on Diablo II) is an old API that is deprecated by no and hardly supported by Windows 10. Fortunately, you can still use wrappers like dgVoodoo or Sven’s Glide Wrapper to convert legacy game graphics to Direct3D 11 or Direct3D 12 so that your GPU has no issues rendering the game. Note: You can also use wrappers like this to enable various overrides that will allow you to use 3rd party tools that can enhance or improve the gaming experience with legacy games on Windows 10. If you’re already familiar with a different wrapper, you can use that one instead. But if you never used a tool like this before, you can follow the instructions below to use the dgVooDoo wrapper to bypass the Error 25 with Diablo II and play the game at a higher resolution:
How to Fix Diablo 2 Error Code 1 - Unsupported Graphics on Windows 10Fix: Diablo 3 Error Code 1016How to Fix Error Code 300016 with Diablo 3?How to Fix Diablo 3 Crashing?
