Now WTF still CTD

[hangman_86]

Ok here it is..running with no mods straight game..dealt with CTDs since I bought this game waited for this new patch and was finally having some success with no crashing.. well that is no longer the case.. running an intel7 with 8gbs ram n a raedon 5750 win 7 x64.. seems to be mission based for the crashing.. initial crash was on the gi blues mission when walking towards the guard.. newest one is the mission to kill the brotherhood.. any ideas on what is causing these CTDs? Have standard codecs that came with system and this is the only game installed so far.. all drivers are current for vid n audio..

[AcesTranquility]

Ok here it is..running with no mods straight game..dealt with CTDs since I bought this game waited for this new patch and was finally having some success with no crashing.. well that is no longer the case.. running an intel7 with 8gbs ram n a raedon 5750 win 7 x64.. seems to be mission based for the crashing.. initial crash was on the gi blues mission when walking towards the guard.. newest one is the mission to kill the brotherhood.. any ideas on what is causing these CTDs? Have standard codecs that came with system and this is the only game installed so far.. all drivers are current for vid n audio..

 

Do the crashes appear at certain locations or points of the game, or are they totally random?

 

A solution for allot of CTD is to disable steam on-line mode and play the game off-line. If this dosent work try the following...

 

If you are using steam then try and run the game directly from steam and not via a short cut and see if this helps.

 

Secondly, If this does not work try running the game in windowed mode and see if you have any improvement if you do use this to make working in windowed mode better

http://newvegasnexus.com/downloads/file.php?id=35882

 

If none of the above work, reinstall Catalyst control centre. Try rolling back the driver to a earlier patch.

 

Get back to me if the above work or dont :)

Edited December 17, 2010 by AcesTranquility

[hangman_86]

Well none of the solutions are working, in fact the crashes are increasing in frequency.. The 2 quest based crashes that are very consistant are The House Always Wins, V. Which occurs when approaching Hidden Valley area, no matter the direction of approach or distance thereof, generally within the cursor sized distance to way point.... Second is G.I. Blues.. It occurs when near Northgate Entrance whether or not I hire the bodyguard mid way to the bus entrance to freeside

 

Faulting application name: FalloutNV.exe, version: 1.2.0.314, time stamp: 0x4cfdf842

Faulting module name: FalloutNV.exe, version: 1.2.0.314, time stamp: 0x4cfdf842

Exception code: 0xc0000005

Edited December 17, 2010 by hangman_86

[secksegai]

Have you done any ini editing to enable multi-core threading?

 

Do you have FFDSHOW installed?

[GreatestDay]

Have you done any ini editing to enable multi-core threading?

 

Do you have FFDSHOW installed?

 

I don't like it when people just spit out alleged fixes that they themselves haven't tested. Thanks for trying and everything but don't post like 10 different random "fixes" if you don't know whether they do anything. Honestly this is the most ridiculous game I've ever played. 30 minutes of gameplay and 3 random crashes, it's so frustrating. If Bethesda can't fix it, what makes you think those other alleged fixes will?

 

It's not people's settings or rigs that cause the problem, it's the game files themselves because stupida$$ Bethesda won't bother testing their product before releasing it. It's absolutely SHOCKING that they would deem this kind of state as "release-ready".

 

Personally I have disabled FFDShow for FNV, everything up to date, windowed mode and turning down game settings, list goes on and on, nothing works. The only thing that HAS worked is the mouse acceleration off-trick, I'm very glad for that.

Edited December 21, 2010 by GreatestDay

[secksegai]

Have you done any ini editing to enable multi-core threading?

 

Do you have FFDSHOW installed?

 

I don't like it when people just spit out alleged fixes that they themselves haven't tested. Thanks for trying and everything but don't post like 10 different random "fixes" if you don't know whether they do anything. Honestly this is the most ridiculous game I've ever played. 30 minutes of gameplay and 3 random crashes, it's so frustrating. If Bethesda can't fix it, what makes you think those other alleged fixes will?

 

It's not people's settings or rigs that cause the problem, it's the game files themselves because stupida$ Bethesda won't bother testing their product before releasing it. It's absolutely SHOCKING that they would deem this kind of state as "release-ready".

 

Personally I have disabled FFDShow for FNV, everything up to date, windowed mode and turning down game settings, list goes on and on, nothing works. The only thing that HAS worked is the mouse acceleration off-trick, I'm very glad for that.

 

You obviously don't realize how much time I spend offering help in this forum. I run the game with a less than adequate setup and get more stable performance on an aging (ancient in computer terms) machine compared to some of these folks with nice rigs. I don't waste my time offering advice on something I haven't tested myself - unless I'm just speculating and then I mention that it just be a guess.

 

FFDshow will cause instability, something I know firsthand after experiencing it firsthand - in the least it will bog you down probably wasting cycles. You also assume too much in general - just because the Official Company can't get something working properly, doesn't mean the fan base won't as some of said fans have extensive technical knowledge. Replacing the d3d9.dll isn't new, as I've had to do it before for certain games when they had issues with the latest drivers - but usually its a matter of new drivers no longer compatible with an older game, as opposed to a brand new game not running optimal code for the operating system as I believe has been the issue for FONV. I'm not all that familiar with dynamic link libraries or programming, but it doesn't mean I can't utilize someone's fix, especially when the description of said problem and fix provided makes sense to me.

 

I've crashed far more than 3 times in half an hour, though usually that's because something crashed my original game and I'm trying to recreate the situation so I know what variable is causing it (so I can avoid it or fix it in the Geck).

 

If 3 crashes in half an hour has you up in arms, what are you doing playing a Bethesda game? Stick to Blizzard =P

[AcesTranquility]

Have you done any ini editing to enable multi-core threading?

 

Do you have FFDSHOW installed?

 

I don't like it when people just spit out alleged fixes that they themselves haven't tested. Thanks for trying and everything but don't post like 10 different random "fixes" if you don't know whether they do anything. Honestly this is the most ridiculous game I've ever played. 30 minutes of gameplay and 3 random crashes, it's so frustrating. If Bethesda can't fix it, what makes you think those other alleged fixes will?

 

It's not people's settings or rigs that cause the problem, it's the game files themselves because stupida$$ Bethesda won't bother testing their product before releasing it. It's absolutely SHOCKING that they would deem this kind of state as "release-ready".

 

Personally I have disabled FFDShow for FNV, everything up to date, windowed mode and turning down game settings, list goes on and on, nothing works. The only thing that HAS worked is the mouse acceleration off-trick, I'm very glad for that.

 

The solutions I gave above have had success in the past with other's experiencing frequent CTD's. While you have said this "mouse acceleration fix" worked for you it could do jack s*** for other people. Every solution I posted I believe could have helped solving this problem. It is always a good Idea to try the most common fixes for CTD's first. And these common solutions are ones that I have used for fallout 3 and what are known by others in many forums to solve the crash problems.

[HeavyHandz]

 

I don't like it when people just spit out alleged fixes that they themselves haven't tested. Thanks for trying and everything but don't post like 10 different random "fixes" if you don't know whether they do anything. Honestly this is the most ridiculous game I've ever played. 30 minutes of gameplay and 3 random crashes, it's so frustrating. If Bethesda can't fix it, what makes you think those other alleged fixes will?

 

 

Do your other games work fine? Maybe your video card is fried, maybe your RAM chips are dying? Troubleshooting a non-linear game developed on an aging engine by a company that is known for making crash happy games that is integrated into Steam is to be expected. Crashing is to be expected. Why are you complaining when people are trying to help you? Obsidian is probably even less capable of fixing these problems than Bethesda was so we can't count on them to fix the CTDs and everything else we've grown to live with. You gotta try out the known workarounds. If all other options fail, make a restore point. Run system restore. Or, backup your save, uninstall the game and delete the entire folder. Hey at least you won't be losing 300 mods in the process. If that doesn't work make sure your computer isn't the issue. My buddy was having the same problems you describe with WoW and FO3 and he found out his video card was cooked. He got a new one and he's back to being a pasty hermit.

[Snowy77]

The crashes to desktop have become utterly intolerable with this game. It is becoming more frequent. The game is fundamentally unplayable. I will be going back to FO3 which has no problems in this regard. Its not the video cards its the game/Steam interface. I believe there was a minor update recently, since then I've had problems. Especially with the AI of Powdergangers. Can't go anywhere near them without the game crashing. This has happened since the last patch. The game was mostly stable before that patch and I was running a large number of mods with no problems. I've cut than number to a quarter with no luck at all. I've run it with almost no mods and it still crashes every 10 minutes. Pathetic programming and using Steam as a client is a very bad idea. Its crap. This game is a total waste of time and money.

[Snowy77]

Why is running a game through Steam a problem???

 

One can't collect a patch library, reload the game at a working patch of their choice. Where are the patch downloads? What good are they anyway if Steam handles the rebuild of the game from disc? Bad idea, bad system.