PDA

View Full Version : Issues with memory insanity after 1.03 - about to throw my pc out the window..

thedooch
10-21-2005, 03:48 PM
Dear Community,

I am hoping very much someone can help me. Ive been playing bf2 for some time without any problems.

After installing the 1.03 patch i came across the memory insanity error when loading any map, single or multiplayer.

My pc is a beast so there really shouldnt be any problems with it being too lame for the job

These are the following things ive tried..

Uninstall / reinstall LOADS of times.
Uninstall XPpro / Reformat / Reinstall
Download patch again.. and again..
Install on different h/drive
Test memory for errors
Update BIOS

Now im still having this damn issue and im hoping someone can help me before i go mad. :cry: :(

Many Thanks

TheDooch
ptegan
10-21-2005, 03:52 PM
EA UK Forums (http://forum.eagames.co.uk/viewtopic.php?t=3409)


The "Memory Sanity" error seems to be being caused by Serial-ATA drives not having the correct motherboard drivers installed. Please check your drivers if you are having this problem. If you are getting the Memory Sanity error pop up and do not have SATA please let us know.
thedooch
10-21-2005, 03:54 PM
Thanks for the quick reply,

Ive done that... Also strange that it worked up until 1.03

Any other ideas?

TheDooch
ptegan
10-21-2005, 04:08 PM
Not what you need to hear but this guy :

http://forum.eagames.co.uk/viewtopic.php?t=7577

had to reinstall XP once he got the memory errors after installing the 1.03 patch.

Others have found that while the SATA drivers were ok, they needed to update their RAID drivers which was an option on their mobo though not actually in use (i.e. they didn't have a RAID set up).
thedooch
10-21-2005, 04:13 PM
Thanks ptegan

I appreciate your time, its been a while now without BF2 and im getting fed up!

I'm updating everything i can think of at the moment.

If i find a fix ill post it here so that others may learn from this mare!

TheDooch
thedooch
10-22-2005, 11:09 PM
ok, i think ive solved this issue, i hope if anyone else gets this problem this may help.

It was a netdisk h/drive on a lan which was conflicting somehow. One of these...


http://www.ximeta.com/


later