Refrence Memory Bug

1

1magus

First time out of the vault
Everytime I leave the first town you are in to go anywhere it tries to load an encounter and freezes for me :( and I have tried reinstalling soooo what to do what to do? :P
RUNNING:
AMD Dual Core 64x 4400+
XP Home 32 Bit SP3
GeForce 8800 GTS 320MB
2GB of DDRII 4200 RAM
PLEASE HELP! I really wanna play this, I just beat the first one :(
 
Panic!

How about telling us what game we're talking about (Fallout 1 or 2) and which mods are installed :-) That might speed up finding a solution for your problem.
 
I'd assumre you knew it was Fallout 2 and the Restoration MOD. lol I mean are you having the same problem with Fallout 1?
The instruction at 004550d7 referenced memory at 00000064 The Memory could not be read from
 
If you have the problem with the restoration mod, you should have posted it in the restoration mod thread :-) Unfortunately my glass ball broke recently and my new one didn't arrive yet.
 
1magus said:
I'd assumre you knew it was Fallout 2 and the Restoration MOD. lol I mean are you having the same problem with Fallout 1?
The instruction at 004550d7 referenced memory at 00000064 The Memory could not be read from
Click to expand...

Well, yes. It could be possible that there are such problems with Fallout 1 and XP SP3. Or with vanilla Fallout 2 and XP SP3. Or with Fallout 1 or 2 and some random mod.
 
I have the exact same crash, right when leaving the first village.. I hear that's where the first Kaga battle is...

I also have XP SP3 (pro) and just plaied through Fallout 1 completely without issue and with using the new resmod. I have Fallout 2 setup and am going through different mod tests to see if I can get it to go further.

EDIT: I did another manual update to 1.2 again with a fresh download and I now got my 1.1 save past that point and into the Outcast Villager conversation. So perhaps my first 1.2 download was 'funky...' I also did a manual download this time, not the installer...
 
I have another one now also... Going into trapper town.. I did the 1.02.25 update as well as the 1.2 and this error still persists... I'm out of possible changes to try...
 
You must log in or register to reply here.
Back
Top