Gta Sa D3d9.dll Not Working
Ezilda Newnam
I have tried every fix on New Vegas Nexus and NOTHING is working. I have about 1 FPS constant, regardless of resolution, view distance, indoors, outdoors, NPC's or no NPC's, or quality settings. If I stand still for about 5 minutes, the game smooths out until I start to walk, then it promptly returns to 1 FPS. I have tried the D3D9.dll fix, tried many fixes with Falloutprefs. I need help, I can run Crysis on ultra so there's no excuse for this to be happening. Any ideas or suggestions?
Kind of an old thread, but I just found out why mine didn't work. Apparently the d3d9.dll in the folder with the MassEffect3.exe was actually just an alias, and it wasn't pointing to anything. It was pointing to where it thought the Fxaa Tool folder was, with it's own d3d9.dll . So I fixed the alias, not sure if others have this same problem, but that fixed my game...
Yes...
The only issue I found is to change the compatibility mode of the game for Windows XP, and then reboot the pc, and cancel the compatibility mode. After this, the game launch one time, but when I leave the game, and retry to launch the game, the error message apears, so I must reboot again and again...
Some games require additional files, if the above doesnt work, search the game driectory for other files containing d3d9.dll, replace their content like above.Note:Some games wont still not work this way, Avatar for example.
BTW Ghost Recon should be DX8, only D3d8.dll that you need to put in the games folder where the games exe is located and use the vorpx DGVoodoo2 base profile.If that doesnt work, try other DGVoodoo2 profiles.
I'm unable to play Fallout 3 and New Vegas. I can't even load a save or start a new game. Instant crash to desktop and removing all the mods, tweaks, INI settings or having the game in its vanilla state doesn't seem to have any effect. Rolling back to previous version solves the problem but I don't plan to stick with older drivers just to play a 13 years old game. Any solution to this problem in the next release would be appreciated. I have a 6750 XT. I'm enjoying to overall experience but these minor things adds up.
Is this really the AMD experience: breaking a 14-year-old game, then just radio silence? This is embarrassing. I never had this issue with Nvidia, and if I ever did, it would be fixed in days not months!
Probably. I changed my old fx 8350 that runned every game in my collection, for a new intel 13th gen that runs only a few of my games and I had to undervolt the cpu to play at least half of my collection.
Same issue.
I got the game a long time ago and with the show i finally want to give it a try but as you can see the intro runs but in the first loading screen game close.
I think i will try fallout 4 instead until AMD save us, keep sending them reports in their support, maybe they notice us
I registered just to post here that I am having the same issue. Wanted to play some New Vegas after the Fallout series and crash on vanilla install when starting a new game and the Doc Mitchell scene should load. 7900XT here. 24.3.1 Driver. Great showing by AMD when people enjoy the Fallout Amazon series, get the itch to play, and can't. Fantastic.
Small Update. I did try the suggested DXVK solution just to see, and the game at least starts this way. I haven't dug too deep to see how I get it to Windowed/Borderless yet, but it is a start. You need to run it windowed for better performance.
Just update for 24.3.1 for i have 24.1.1 before and its off my card in device manager, and have issues with games, that why update your drivers for the newest, i use RX 6600 and have similar problem before.
There's certain steps you have to take for DXVK on AMD. You have to force windowed in native resolution or it will lag. Also install script extender and some of the optimization mods and you'll be golden. Most people get more FPS on DXVK than DX9 from what I've seen online comparing before and after.
Was thinking of giving fallout 3 and new vegas another go with the release of the fallout tv series, but it is sad to see that months after this was reported the game still crashes after loading a new game. 24.3.1 drivers on a 7900xt.
I think the problem is game seem to detect your advance GPU hardware and freak out because a very high perfomance inout, so you have to fool the game hardware detection that your hardware is old model.
Made an account to come post a solution I came across online. Not sure if it will work for everyone, but it did for me. I have an AMD 5700 XT, Windows 10, AMD 24.3.1. I was having issues launching the game. Launcher menu would appear but after pressing Play the game would crash. There is a mod on Nexus Mods called "Intel HD graphics Bypass package". I don't want to post links because I'm new and not sure what all the posting rules are. Do a search for it and you should find it pretty quick
Once you find the mod you can download it manually and put the d3d9.dll file in your Fallout3 main folder and then place the INI file in your Documents/MyGames/Fallout3 folder and replace the current INI file with the one from the mod. This basically tricks the game into thinking you have a Nvidia card and bypasses whatever issues I was having. Hope it helps!
AMD needs to fix this; rolling back the driver isn't acceptable and while the dxvk and other crafty homebrew workarounds to convince the game that you are using some other non-amd GPU work for some, it doesn't work for all.
Everyone new or coming back to this thread also be sure to submit bug reports, I don't know how reliably they check these forum threads but clogging up their report log with enough issues is bound to get someone to notice eventually.
I had this same issue with Fallout 3 in a 6600 on Windows 11. After trying several fixes by modifying the core file games and messing with settings, the only one that helped was to fool Fallout into thinking I had an NVIDIA GeForce 7900 GS via the mod found in NexusMod "Intel HD graphics Bypass package".
This was after also using the unofficial patcher in Fallout and doing a ton of other modifications that come with it, so your mileage may vary, but you may want to try this workaround (didn't see any downsides in performance), while AMD gets their stuff together.
It's a system issue, (if you're interested, take a look at -D3D9.dll @ 0x0010EA8F, as you can see no MTA calls are involved in the crash) what I advise is to update your GPU driver, and repair a potentially corrupt D3D9.dll:
.. As per the last post in this topic, it turned out to be Windows OS / system file / d3d9.dll (either in system32 or the affected software's installation folder) corruption or non-original file problem
Also after running DISM (Vista's replacement) didn't you forget to run the other command, sfc /scannow in cmd? That was part of the instructions, and it's vital to repair a possibly corrupt d3d9.dll, which is an OS file. Besides that, be aware it's better to just leave Vista behind, as ancient it is.
Still, devices such as your GPU, CPU etc aren't queryable by MTADiag (Windows API) so there's some sort of persistent corruption within your OS, but we already knew that. I noticed that you didn't allow MTADiag to make system changes, please do that with pressing ''y'' when it first asks (and let that process complete..)
I previously told you that if nothing tried here solves the problem, you could try using a clean GTA installation. If that is also to no avail, then the corruption is buried too deeply within your OS, the last thing you can try in that case is using DDU (download from: -details/display-driver-uninstaller-download.html) to completely uninstall the Intel GPU driver without traces left, and then re-install it with the earlier downloaded driver.
Errors related to d3d9.dll can arise for a few different different reasons. For instance, a faulty application, d3d9.dll has been deleted or misplaced, corrupted by malicious software present on your PC or a damaged Windows registry.
In the vast majority of cases, the solution is to properly reinstall d3d9.dll on your PC, to the Windows system folder. Alternatively, some programs, notably PC games, require that the DLL file is placed in the game/application installation folder.
Do you have information that we do not?
Did our advice help or did we miss something?
Our Forum is where you can get help from both qualified tech specialists and the community at large. Sign up, post your questions, and get updates straight to your inbox.
So what I tried was, I diassemble the d3d9.dll and through diassembling take out the offset of createcontextcb function. Than through listdll I looked for the address of d3d9.dll so that i can add the offset of createcontext into that address and by this I can set
the the breakpoint at that address. But I failed to find d3d9.dll in listdll application. I think d3d9.dll must be there if aero is working.
Is this the right approach to set debugpoint or is there any other approach.
Thanks and regards
Prashant