Mountainjew

You say "restricts the engine to using only 2 cores" and the only way to force it to run in 2 cores is to set to cores from taskmanager If inumhwthreads=2 doesnt set it to 2 cores, you have to do it via taskman I dont see you actually says it runs on 2 cores after you set inumhwthreads=2 , so if you succeed , to run on 2 cores after the setting, then maybe you should check your cpu settings, it doesnt hurt too check if its not your factory settings Eh, it's quite a common fix, google it.

I meant that i added the 'inumhwthreads=2" to the ini, since it's a common fix for multi-core issues and restricts the engine to using only 2 cores. Though it doesn't help any :confused:

So, this is nothing new for me. I had the same issues with Fallout 3 where it would display a windows error message "fallout3/nv has stopped working" and always the same useless exception code in the event viewer (Exception code: 0xc0000005). The funny thing is, that when NV first came out about a year ago, i would rarely get any crashes. Since it has been updated over the year, it just crashes more and more. I'd say at the moment, my Fallout 3 install is probably more stable with tons more mods. The crashes are usually on transition, fast traveling, but not always. Sometimes during firefights. And of course, i've tried disabling auto-saves but it doesn't make a difference. So here's my load order [X] FalloutNV.esm [X] DeadMoney.esm [X] HonestHearts.esm [X] OldWorldBlues.esm [X] Project Nevada - Core.esm [X] Project Nevada - Equipment.esm [X] DarNifiedUINV.esp [X] F3NVProjectRealityMkIv3.esp [X] Project Nevada - Cyberware.esp [X] Project Nevada - Rebalance.esp [X] Project Nevada - Dead Money.esp [X] Project Nevada - Honest Hearts.esp [X] Project Nevada - Old World Blues (No Cyberware).esp [X] Purge Cell Buffers.esp [X] Disable Anti Cheat Minute.esp Also using NMC's medium texture pack (crashes without it also) Also using the 4GB launcher (also crashes without it) Not many mods as you can see. I tried the purge cell buffers mod in case that helped, but it doesn't, so i'll probably just remove it. I usually run with stutter remover, but i've found that running without it and without vsync is better, so i've ditched it for now. All my mods are up to date, as is NVSE. I'm currently running the 1.4.0.525 version as i told steam not to auto-update. I've tried the numerous fixes which i've had to use on Fallout 3, including codecs, tweaking the ini to run on only 2 cores/threaded ai etc. None of which seems to make a damn bit of difference in NV. So, onto my specs: Windows 7 x64 AMD 1055T Hexacore ATi Radeon 5850 - Catalyst 11.8 drivers Asus M4A89GTD Pro Corsair XMS CMX4GX3M2A1600C9 4GB Asus Xonar DX All background processes stopped via gamebooster before playing. I have 2 screens but always disable one before playing also. I've tried reinstalling a couple of times to no avail. I took off my cpu overclock also. So, i'm pretty fresh out of ideas, hence why i've come here :whistling:

Another one for Fallout 3. Mainly the setting and more connected with my character. NV was a bit lame when they just throw you into it with no background on your character. Any story, be it a book or a movie or a game has to have some character development. New Vegas had very little of it. I didn't care for any of the factions, and didn't want to help any. None of them were likeable. Fallout 3 was gripping from the first moments. I loved being a vault dweller and learning all about my characters past, only to be ejected into the wasteland. And the wasteland itself is a much more interesting place for me than the Mojave. Much more architecture to explore and admire. I admit, the tunnels did get tedious, but if you show all map markers you can skip most of them. The voice acting, script and story could use a lot of improvement, sure. But for me it was the atmosphere in Fallout 3 which is what made it great. It was a desolate, helpless place. Unlike the Mojave, too many people and not enough buildings to explore. The story and quests in NV were too open to the point you didn't know which faction you would piss off next or what repurcussions would happen. I understand that some people would like that, but it just pissed me off honestly. I ended up siding with Yes Man on my first playthrough and finished it at level 17, just because i had enough. The game just became too uninteresting for me. And the ending wasn't much to write home about. I'm doing my second playthrough now and i'm 30 hours into it on level 24, siding with the NCR. And honestly, i'm bored once again. I haven't touched it in days, and instead i'm playing Fallout 3. I guess the same people who enjoy Fallout 3 would enjoy the Stalker series, as they both have a very atmospheric, bleak feel.

I understand that some people who can play it 'just fine' might think people who are getting crashes must be computer noobs or something. But not in my case anyway. It's just a badly coded game, and i think i've officially given up on trying to get it to play nice. If Bethesda can't spare the man hours to fix one of the most popular pc games, then i'm not prepared to waste much of my free time trying to diagnose their mistakes. Enough hours have been spent researching, testing etc on my part. It's so nice to play other games now and not have to worry about when it's gonna crash. And other games which run well and don't make my new build feel like it's 5 years old. I've had a couple of crashes in NV, but that's like 2 crashes in 60 hours. That is acceptable imo. Then there was the save corruption inside the Gammorrah, which was also acceptable and the crappy performance, which was also acceptable. But a game crashing every 5 mins - 2 hours is just so unpredictable and unacceptable for a game of this calibre. I still prefer Fallout 3 to new vegas (the architecture i think). I'm just praying that since the Gamebryo engine is being sold off, that it'll not be used in anymore of Bethesda's games and they make a decent engine. Or get the ID Tech 5 to work with Fallout 4. Or at least get ID to develop it. I can dream... :whistling: Edit: I'm actually tempted to run it in WINE on my linux drive to see if i can get a proper bug report. Dunno if anybody has tried this yet though...

Well, the PCB mod didn't seem to help much. My performance was already fine, and i kept getting transition crashes, when walking through doors. So for now i'm just using CASM to autosave every 5 minutes. Seems to take some of the annoyance away :teehee:

@ williamjames - Thanks for the suggestion, though i always keep my drives defragged, so it shouldn't be a problem :thumbsup: @ rgx02 - Cool, i haven't seen that before, i assume that clears up wasted ram or something? Almost forgot, that i've checked my ram use periodically and it's always between 900MB and 1.1GB. I'll give this a shot though, can't hurt (i hope) :woot:

I guess everybody else is as stumped as i am :whistling: Oh well, i'll wait for Fallout 3 to be ported over to NV :biggrin:

Ever since i started playing Fallout 3, i've been getting the same error "Fallout 3 has stopped working". I think i must have researched this for over 20 hours and still got nowhere. So when i first played, it was a few months ago on a completely different pc than the one i'm using now. I recently built a new system, and hoped the crashes would stop. Nope. With or without mods, i get the same error report: Faulting application name: Fallout3.exe, version: 1.7.0.3, time stamp: 0x4a40f18b Faulting module name: Fallout3.exe, version: 1.7.0.3, time stamp: 0x4a40f18b Exception code: 0xc0000005 Fault offset: 0x001878f8 Faulting process id: 0x3b4 Faulting application start time: 0x01cb8053a7ebea65 Faulting application path: F:\Games\Bethesda Softworks\Fallout 3\Fallout3.exe Faulting module path: F:\Games\Bethesda Softworks\Fallout 3\Fallout3.exe Report Id: 498cbc61-ec4c-11df-a12b-86d5e2ae30c3 This is the same code i've always got, on both systems (0xc0000005). I've done multiple uninstalls/reinstalls. Running with mods and without mods. Sometimes i can play for 2 - 3 hours without problems, but most times only 1 hour. It's very random too. Doesn't matter if i'm in a firefight, walking through a door or just exploring. Now, i do find it a bit odd that i got the exact same error on a completely different system. So here are my current specs: AMD 1050T x6 Phenom II Asus M4AGTD Pro Corsair XMS3 4GB 12800 ATI Radeon 5850 *All stock speeds And my previous specs: AMD 5600+ Asus M3A78 Pro 2GB Corsair XMS 8500 Nvidia 8800GTS OC Audigy 2 ZS *All stock speeds Both systems running windows 7 x64. I'm currently running onboard sound, as i got the crashes with and without my old Audigy 2. Here are the remedies i've tried so far: - Disabled GFWL via GFWL Disabler - Enabled 4GB allocation - Disabled DEP for F3 - Running as admin - Running without compositing or visual themes - Setting key mapping to default - Installed K-Lite and excluded F3 - Set WMP to open .ogg - Updated every driver possible - Multi-Core fix - Installed outside of \Program Files - Disabled Autosaves - Master update with FO3Edit - Disabled Anti-Ailasing - Set water multisampling to low - Forced vsync on and off And here is my load order for my current mods: [X] Fallout3.esm [X] Anchorage.esm [X] ThePitt.esm [X] BrokenSteel.esm [X] PointLookout.esm [X] Zeta.esm [X] CRAFT.esm [X] CALIBR.esm [X] EVE.esm [X] StreetLights.esm [X] Enhanced Weather - Rain and Snow.esm [X] FO3 Wanderers Edition - Main File.esm [X] Mart's Mutant Mod.esm [X] DarNifiedUIF3.esp [X] FO3 Wanderers Edition - Main File.esp [X] FO3 Wanderers Edition - DLC Anchorage.esp [X] FO3 Wanderers Edition - DLC The Pitt.esp [X] FO3 Wanderers Edition - DLC Broken Steel.esp [X] FO3 Wanderers Edition - DLC Point Lookout.esp [X] FO3 Wanderers Edition - DLC Mothership Zeta.esp [X] FO3 Wanderers Edition - Followers Enhanced (BrokenSteel).esp [X] FO3 Wanderers Edition - Optional Restore Tracers.esp [X] FO3 Wanderers Edition - Optional Restore Tracers (automatics only).esp [X] WeaponModKits.esp [X] WeaponModKits - FWE Master Release.esp [X] WeaponModKits - OperationAnchorage.esp [X] WeaponModKits - ThePitt.esp [X] WeaponModKits - BrokenSteel.esp [X] WeaponModKits - PointLookout.esp [X] WeaponModKits - Zeta.esp [X] EVE.esp [X] EVE Operation Anchorage.esp [X] EVE - FWE Master Release.esp [X] EVE - FWE Master Release (Follower Enhanced).esp [X] EVE Anchorage - FWE DLC Anchorage.esp [X] EVE - FWE with WeaponModKits.esp [X] Mart's Mutant Mod.esp [X] Mart's Mutant Mod - DLC Anchorage.esp [X] Mart's Mutant Mod - DLC The Pitt.esp [X] Mart's Mutant Mod - DLC Broken Steel.esp [X] Mart's Mutant Mod - DLC Point Lookout.esp [X] Mart's Mutant Mod - DLC Zeta.esp [X] Mart's Mutant Mod - FWE Master Release.esp [X] Mart's Mutant Mod - FWE Master Release + DLCs.esp [X] Mart's Mutant Mod - Master Menu Module.esp [X] BlackWolf Backpack.esp [X] BlackWolf Backpack - Vendor Script Replenish.esp [X] Fellout-Anchorage.esp [X] Fellout-BrokenSteel.esp [X] Fellout-pipboylight.esp [X] Fellout-PointLookout.esp [X] Fellout-Zeta.esp [X] Fellout-Full.esp [X] Enhanced Weather - Rain and Snow in Fallout.esp [X] Enhanced Weather - Radioactive Rain and Snow Plugin.esp [X] Enhanced Weather - Sneak Bonus during Storms.esp [X] Enhanced Weather - Weather Sounds in Interiors.esp [X] Enhanced Weather - REBOOT.esp [X] RCMarket-BarrelBeGone.esp [X] megalight.esp [X] richvendors.esp [X] RivenRadioMP3only.esp [X] UndergroundHideout.esp [X] GalaxyNewsRadio100[M].esp [X] Merged.esp Probably irrelevant since i get the same crashes with or without mods. So, yeah i think that pretty much covers it. I have no such problems in New Vegas, but i prefer a modded Fallout 3, thanks to the awesome mods of the people here. It's just a shame i have to quicksave every 5 mins, due to paranoia of never knowing when the next crash will come. And i just reinstalled windows a few days ago, and before installing anything, i setup Fallout and had the same issues. So i know it's nothing i've installed on my system which is causing the issue. Hope somebody can help, before i tear out my hair :unsure: