• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

critical exception - memory could not be written...

jwill

2[H]4U
Joined
Jun 4, 2003
Messages
2,102
this window comes up occasionally when farcry crashes "memory could not be written." ive also seen it crash with the message "memory could not be read" aswell. any ideas? system memory or video memory related, something else maybe? im guessing the system memory.

memory_issue.jpg
 
You could try downloading Memtest to test your memory. Do any other applications crash on your machine?
 
an application can't write to memory address 2, that's kernel space and is quite well protected from ordinary applications.

run through the basics, update video drivers, motherboard drivers, sound card drivers.
update to DX9.0C if you haven't already.
back off any overclocking
 
Same thing happens to me... Is the voltage on your RAM turned up any? I had my voltages set higher than stock, and when I lowered them again it stopped.
 
According to the FarCry official site , the 1.2 patch is borked. If you installed the 1.2 patch, it seems like you may need to revert to 1.1?:

Friday 23.07.2004 Far Cry 1.2 patch withdrawn
Ubisoft has taken the decision to withdraw this patch due to issues experienced by a number of users. An official statement follows:

"Far Cry patch 1.2 has shown unexpected behaviour on specific hardware configurations. These matters are mainly due to incompatibilities with several optimisations brought lately to the code, with the intent to please a large number of users.

We're currently asking CRYTEK to work on delivering a new patch as soon as possible. Until then we have decided to remove the patch 1.2 from the official UbiSoft websites."

A couple other places have players saying that they were getting the same error in 1.2 but not 1.1.

Note: I don't own FarCry but I'm bored tonight so I thought I would do some searching. My reply may be totally wrong, but worth checking out anyway
 
thanks for the replies guys.

shadow74205: thats a good idea with memtest since im running 250 fsb. ill do that tonight. and see what it says in the morning. i havent had any other programs crash on me except prime95. ive since back it down since then but im still finding the sweet spot with this system.

FreiDOg: another good idea. i think ill just reinstall xp pro again and start over. i do that several times a year anyways. ive tried backing off the overclock some but it may still be too high. ill play the game with a much lower overclock say 200x11 or so and see if the game crashes at all at that speed.

d34dly: you could say that, 3.3v pretty high but id expect the memory to take it. that could be issue though. i so much wanted to run with 250 fsb like i am now, since i bought these bh-5 chipped dimms.

Bitchnmoan: i bought the game after the update 1.2 was recalled so ive been with the version 1.1 since.

thanks again for your help guys. its appreciated. :)
 
well memtest ran for 10 hours at 250 fsb (1:1) at 3.3v. so i guess the ram overclock isnt the issue. so im happy about that.

im reinstalling windows today, so we'll see if it comes up again after that. hopefully not.
 
jwill said:
well memtest ran for 10 hours at 250 fsb (1:1) at 3.3v. so i guess the ram overclock isnt the issue. so im happy about that.

im reinstalling windows today, so we'll see if it comes up again after that. hopefully not.

Yes but just because MemTest works, doesn't mean that FarCry doesn't act funny when the voltage is up.
 
Back
Top