Found a fix for constant crashes

[trebonus]

Thought I'd pass this along:

 

I was having constant crashes- game was unplayable- and I tried all different kinds of mod combinations, the multicore fix, stutter fixes, clean installs, etc... all to no avail- was crashing every 5 minutes- if I even made it that far. It was brutally depressing.

 

Then I remembered how I played a heavily modded f3 game without incident before upgrading my mobo/processor to a quad core and to windows 7 x64. I thought it might be the multicore issue with the gamebryo engine and that the f3 .ini fix that's posted all over just wasn't doing enough...

 

So I went into msconfig through windows and disabled three of the cores on my processor and rebooted. Detailed instructions are below.

 

After making the change, I've had it running for over 45 min and I've been running all over the place shooting things on god mode with a heavily modded fook2/mmm/wmk/etc build. Amazingly, no crashes yet. It's kind of surreal after all the crashes I had been enduring. I hadn't seen this fix posted anywhere else, so I thought I'd pass it along. Long live f3!

 

Instructions Disabling Cores in Windows XP, Vista, and 7

• 1

  Click "Start." Click "Run" if running Windows XP.

• 2

  Type "msconfig" in dialog box. Click "OK" or press "Enter."

• 3

  Click the "Boot" tab. Click "Advanced Options."

• 4

  Click the arrow under the Number of Processors. Choose "1" to indicate that you only want 1 core enabled. Click "OK." (I'm currently using just 1- the game is stuttering, but not crashing... will try 2 next).

• 5

  Restart the computer.

 

[M48A5]

You have gone overboard with your change. Now you cannot use the full potential of your CPU with any other program. And it would appear you did not look very hard. The change to limit the computer cores is posted all over this and other sites. Go back and restore your computer and follow these instructions: http://forums.bethsoft.com/topic/1465357-installing-fallout-3-with-windows-78-and-xp/

[trebonus]

1- im fully aware of the consequences of only using one core... I have to go through the incredible inconvenience of undoing the change and rebooting when I want to use all 4 cores... one Im willing to live with to play f3.

 

2- you didn't seem to read my post too clearly- I suggest you re-read it. I already tried the multicore fix in the f3 ini file thats posted all over the internet to limit the number of cores the game uses... and it didn't have any effect. This change did. And if you went and read forums where that change is posted, you'd see that it works for some multicore systems and not others for some reason. Me included. So I've shared a slightly more extreme and possibly game-saving fix.

[PQRavik]

This trick worked for me as well. Like trebonus, I tried the multicore fix too, and it didn't help. Actually reducing the number of cores, using msconfig did work. I hope someone can use this as a clue to create a better fix for fallout 3. BTW, I've got a Gigabyte motherboard with Intel Q6600 Processor and 4 gig of ram memory.

[trebonus]

Yeah- I don't know the first thing about how to create a fix or why the multicore wouldn't work for some pcs- this was all I could think of doing before resorting to trying an install on my old 32bit xp... I've got an msi mobo w/ an intel i7 quad core for what its worth to more able minds.

 

And now I've got 5+ hrs of playing the game w/ the msconfig fix, and no freezes... it's amazing how small-time mod-created crashes feel after the 5min freezeups of the quad core problem...

 

EDIT: I've started getting some of the crashes again after going to two cores... removed the multicore fix and it's generally stable and will play for extended periods on one core, but sometimes for no more than a couple min...

Edited July 12, 2014 by trebonus