Every time I attempt to launch the game I log in then when I click "engage" I get "Fatal Error: Direct3D driver returned error code (E_OUTOFMEMORY) while creating D3D device.
So, I can say for certain I am not out of memory despite what it says. I've tried safemode on and off, I've tried 32 bit and 64 bit, I've tried both 32 and 64 bit with safemode toggled on and with safemode toggled off. I've also tried turning on-demand patching on and off with all previously listed configurations of said options.
And I've force-verified, as well. At this point I don't know what to do. There's no good reason for this issue as far as I can see.
Of course, I'm having a similar issue with Champions Online, so it seems to be a Cryptic-specific issue as no other non-cryptic game does this for me. In terms of Champions online it says something similar, pops up a window that says "Program Error" which reads "Couldn't create D3D device."
I have no idea what's wrong and any I would be thankful of any help that can be offered.
0
Comments
Using an AMD Ryzen 5 1500X Quad-Core Processor 3.5 GHz
16Gb Ram
NVidia GeForce GTX 1050Ti (397.31 Drivers)
Windows 10 Home
After restarting the PC, was able to get the game running. We'll see for how long...
Join Date: Tuesday, February 2, 2010
Before launching the game, I happened to notice that the latest drivers I thought I had installed through Geforce experience never actually installed so I took care of that.
I then did a force verify launch of the game, walked away and came back later. Played the game for a while with no trouble, exited the game and then saw the little pop up from Windows....even though I didn't tell it to, it seems that Windows ran the compatibility mode troubleshooter when I launched the game.
So, it could be any one of those actions, or a combination of two, or even all three that solved the problem, I don't know. Even though it was in forums for a few different games other than STO, setting the game to run as administrator was what solved the problems for people in those games. A side note, I had set the game to run as administrator in the past, however when I went in to check it this time, it was no longer set that way. I suspect that the patch, while sneakily introducing the 64 bit client, replaced both startrekonline.exe and gameclient.exe (along with adding even more instances of gameclient.exe in different folders) which would explain why it was no longer set to run as administrator.
I would suggest finding all instances of startrekonline.exe and gameclient.exe and setting the all to run as administrator first. If that doesn't work, check/update your video drivers, and as a last resort, run the compatibility mode troubleshooter.
BTW, if one of those solves the problem, please be sure and let everyone know which one did it so anyone else having this problem can hopefully go straight to the solution.
After my last post, I have had the D3D out of memory error again twice now. Both times when I open Geforce experience it tells me a game ready driver is available, the exact same driver I have already installed twice now, three times counting the installation that is going on while I'm typing this. The last time, allI did was (re) install the video drivers and that fixed it. In a few minutes I will know if it fixes it again.
Now, the reason I am posting this. At least for me, it seems the D3D out of memory error(s) is easily solved by just reloading the latest video drivers. If you are running Win10 and using Nvidia, you might want to check your drivers, they seem to revert back to MSofts "certified" drivers without warning.
I've come across these two threads, I'm not sure if they'll give us some insight here or not.
https://answers.microsoft.com/en-us/windows/forum/windows_10-hardware/windows-10-nvidiageforce-completely-disappeared/88bf2c79-9b9e-4634-b4c9-cbd6b4fba7c4
https://answers.microsoft.com/en-us/windows/forum/windows_xp-update/nvidia-display-driver-disappears-after-windows/b14d457a-1b6f-4d2d-a87f-468e5a0dcd80
I find it unusual that it started last week for several people there was an nvidia update last week, and I've also gotten this error in mediaplayer classic. Which leads me to believe that this is an nvidia/windows issue and not an STO issue
https://www.neowin.net/news/nvidia-says-new-drivers-coming-very-soon-to-replace-buggy-39731-release
I can confirm, downloaded and installed driver 397.55 and it appears to have fixed this problem.