nosisab Posted August 21, 2009 Share Posted August 21, 2009 *CUT FOR PROSPERITY* BUT BY ALL MEANS make sure to delete the fallout3.ini, since it may have harmful video configurations. Well, I got rid of every trace I could find of FO3 when I uninstalled it at the advise if another person... But I can tell you, the heat was fine, actually it was below normal for most game play sitting at around 45 degrees Cel (113 Deg Far) seeing as the game would crash and BS within minutes of starting play... No overclocking... yet... I wanna but that's another story... >.< But it mostly happens while leaving the Vault for the first time... after the recheck of what stats you want and your name and all that crap... But it is random, sometimes I can get into the wastes and run around for a few minutes, sometime, like before I dumped all those mods in just before, I ran around for a good 20 to 30 minutes with no crash... The thing that gets me is that it all started happening when I started to introduce mods back after installing Fook2 Beta... cos I played just FOOK2 for a while, I got up to the Citadel... But I did get a couple when I upped my AA and AF... but I got that back into working order... after a little work... 2x and 15x I can handle (Respectively, if anyone has an EN9800GT and are wondering) but yeah... it's now back at default so I don't think it's that... (from a default Fallout3.ini) I thought it maybe overheating but my computer is basically new... it is only a month old... and all other games work, like TD:U, CS:S, UT3, The Sims 3, X3:TC and C&C3 (Yeah... I think I like the number 3 too much as well... >.<) and all of these games have max settings basically... well from memory... and are all running at 1920x1080... just like Fallout3... hell I run SC:FA with both monitors... Which brings me to the reason I am here at the Nexus... I personally think it's Fallout 3... it's the only game that does it... I hope this is enough info to get a general picture of what I am doing... And what I can do...Yes, I too don't think the troubles being the settings, since you covered the main procedures and it's a localized issue (just one game) you are already in the correct path. It seems to be a mod issue or mod conflicting. To this point on I can't be more helpful, sorry. Better letting the people actually (I mean ATM") playing the game and experienced with the mods have the words. Link to comment Share on other sites More sharing options...
nfckitten Posted August 21, 2009 Author Share Posted August 21, 2009 *CUT FOR PROSPERITY* conflicting. To this point on I can't be more helpful, sorry. Better letting the people actually (I mean ATM") playing the game and experienced with the mods have the words. Yeah, thanks anyway for the effort mate, much appreciated... Oh... 1 thing for anyone else... It does it mods or not... Link to comment Share on other sites More sharing options...
nfckitten Posted August 22, 2009 Author Share Posted August 22, 2009 Ok, I think I fixed it... fingers crossed and knock on wood... and anything else you would do... It seems that a driver roll back was all that was needed... was easy to do too... So if you have the 190.38 nVidia XP 32 bit drivers and your fallout keeps Blue Screening with some crap about NV4_disp.dll (read the full BSOD error code in a previous post...) then roll back to drivers that you know work... so unless the ones that came with your card are really old or bugged to the crap... use that... well that's what I did and it seems to be working now... Enjoy people! Link to comment Share on other sites More sharing options...
n0t0ryczny Posted September 10, 2009 Share Posted September 10, 2009 Hey, I know what it is. Seriously. Luckily my Fo3 developed tendency to CTD instead BSOD lately:DIf you noticed something like stuttering just before CTD... It's memory. Video or RAM, it actually does not matter. Happens a lot more often if you tampered with Fallout3.ini and Falloutprefs, especially when increasing celll/texture memory allowance (originally Fo3 uses just about 50 megs of RAM for some content, it's optimised to rum on 1GB of memory). So, increasing that allowance (up to 256 megs of 3 gigs of RAM in my case) noticeably reduces stuttering when passing from one exterior cell to another, when game has to display new LOD and objects. Especially when your game is full to the brim with replacement textures and new content. Lots of battling creatures may also cause stuttering, as lots of small objects pushed/forced to fly by explosion. When something like that happens, Bethesda's wonderkid devours another portion of system memory. Due to way the system is built (I'm talking about 32-bit) Windows will not give the game more than half of the physical memory... And here the problem arises. Fallout closely fits all allowed space, thus pushing nv4_disp.dll out of memory. Windows tries to compensate this by using the virtual memory (swap file) and fails miserably. Display driver is woefully late, and the PC gets clogged with unprocessed data. BSOD. Hope my fairytale clears the sky a little... So, try not to use the plugins you don't really need, keep to smaller texture packs... Or upgrade your PC. Link to comment Share on other sites More sharing options...
Recommended Posts