"Failed to initialize renderer. No D3D Device found" error message, after installing NVHR mod

[jeminfinity]

Hi everyone

I really hope somebody can help me, please. I recently downloaded the NVHR (New Vegas Heap Replacer) Mod and installed it a few nights ago. I was initially quite chuffed because it did seem to make a noticeable difference and it had been playing fine, until I went to launch it again and now my game won't start at all, either from FNV mod manager or even just launched directly.

 

It keeps coming up with an error "Failed to initialize renderer. No D3D Device found"

 

As I figured the NVHR extension was the problem, I came back onto Nexus to look up any reported issues and causes/solutions, only to see it's been hidden and says it's broken, with no info to help me. So I thought it best to initially contact the mod author directly. It's been a couple of days but I still haven't had any response unfortunately, so I thought this forum should be my next avenue. Any advice anyone can give me to help fix this and get my game running again would be deeply appreciated.

I deleted the two mod files d3dx9_38.dll and tbbmalloc.dll from the root folder, but it has made no difference and just keeps coming up with the same error when I attempt to launch. Is there some other way I'm supposed get rid of it from my game?

 

I'm ok at working things out myself usually, but this is a bit above my pay grade for now and I can't find any solutions via net search engines that make it clear what I should do to fix it. My hubby is a tech nerd and would usually help me to fix it, but he's away at the moment, so I need to try figure out how to restore my game to normal myself. I wasn't having any issues until I used the NVHR so it's obviously the problem as it's directly related to whatever D3D is? I'm still learning about all these more complex things, so am a bit of a noob in this area, sorry ;-)

 

I saw another similar mod called “Alternate D3D9 fix for ATI plus D3D9Gen” , is that something similar that would help? I have the 4gb mod on my game and some other basic performance enhancers, including tick fix (which I thought was ok to use with this), and the game was working well until suddenly it wasn't, so I don't know if it's something else it clashed with and broke it?

 

Anyway, I've never messaged on this site before or had any issues I couldn't work out myself until now and I hate to impose on others, but as the mod author isn't able to get back to me yet it seems, I would be so grateful for any help. I don't want to have to reinstall my game and mods and everything again from scratch, or anything like that (already been through that nightmare once before when something major stuffed up :wallbash: ) as it has taken me a month just to get the game where I want it again.

Sorry this was so long, I appreciate your patience. Thank you kindly all and have a lovely day. :yes:

 

[dubiousintent]

That "rendor" error is indicating a problem with your DirectX (D3D9.dll) driver version. Please see the 'Issue - Vanilla game Hangs on startup' entry under the 'Solutions to Starting the game problems' section of the wiki "Fallout NV Mod Conflict Troubleshooting" article.

 

As for your "heap" issue, please see the 'Issue - CTD after 10-20 minutes of play post-Win10 2017 FCU' and 'Issue: CTD without warning, "Out of Memory error", or stops responding after the Main Menu' entries under the 'Solutions to "Crash To Desktop" (CTD) problems' section of the same article.

 

-Dubious-

[jeminfinity]

Hi again!

 

I apologise for not responding to this sooner, but I only just fixed my issue (finally!) recently and this is the first chance I've to had to sit down and write a proper response. I just want to say thank you kindly dubiousintent for taking the time to respond to my request to help me out. Unfortunately I never did hear back from the mod author after requesting help, so I really appreciate it :smile:

 

Like many computer issues, it seems this error can be caused by various different things, so figuring out the exact cause and fix was maddening! Unfortunately nothing I tried worked in the end, so I ended up just having to wait for my hubby to return home to help me solve the issue. At least now there is one more thing I now know how to do and have learned something new, so not a total waste I guess :wink:

 

I figured as you were kind enough (like many great people on this forum) to respond and assist me, I should pay it forward and share what fixed this issue for me. Just in case any other "non expert" like moi ever has this kind of issue, maybe this will help somebody at least and save them some great frustration.

 

So it seems that this mod, NVHR (New Vegas Heap Replacer), somehow de-registered the graphics driver from my game :sad: . We initially tried reinstalling the Nvidia drivers, which did nothing. In the end this is what worked :

 

We saved a back up of the entire game and save files (to be safe) and renamed the game directory folder "Fallout New Vegas _Original". Next, we reinstalled a completely fresh game into a separate directory folder which we named "Fallout New Vegas_Copy install". We also renamed the new save folder (under Documents- my games) of the new install "FalloutNV_fresh install". Once we did this, it made my original game recognise the drivers again and it now works perfectly once more :woot:

 

So, if anybody ever has this issue caused by these same reasons and you stumble across this, I hope it helps :wink:

 

Thanks again for your response dubiousintent and have a lovely day.

Cheers from Australia :D

Edited May 2, 2019 by jeminfinity

[dubiousintent]

Thanks for reporting back with your solution.

 

You were apparently one of the few early adopters of NVHR, which was set hidden by the author as being "broken" shortly after release. While jazzinsparis is a very reliable, prolific, and responsible author, anyone can encounter an unexpected bug when a mod get released "into the wild". There are just too many variations among the mix of hardware and software combinations possible to test them all. Which is a reason to be cautious about being an "early adopter" of new mods even from well known authors, realizing there is always a risk.

 

Whether NVHR had anything to do with your problem is much less important than that you managed to resolve the problem. Very happy to learn you worked it out.

 

-Dubious-