1. #11
    If it's still under warranty maybe you can get new sticks from AW and test. It may be an OS error that will not be fixed via hardware changes. Sometimes a corrupt file is the cause. It's best to rule out HW first though.

    Have you tried changing memory timings or PCI latancy in bios?

    <BLOCKQUOTE class="ip-ubbcode-quote"><font size="-1">quote:</font><HR>Originally posted by Buster_Dee:
    The fault says:

    The instruction at "xxxx" referenced memory at "xxxx." The memory could not be read.

    I gave examples of the instruction/memory locations in my first post. As to testing the RAM, I did that when I first got the machine and found a bad stick. Alienware provided a new stick (I have 2 sticks of DDR 400). I used a DOS program recommended by Microsoft to test it, and I let it run all day when the after I installed the new stick. I did that again about a month ago when I got tired of seeing the error (and it seemed to be happening more often). The sticks passed with the highest test settings.<HR></BLOCKQUOTE>

    ==============================
    Mudmovers
    ATI Catalyst Beta Tester
    Catalyst Feedback
    Catalyst Driver Download
    ==============================
    Share this post

  2. #12
    Hunter, I have not played with RAM settings in BIOS. It's an area I'm not familiar with. I've just tried to stay with the settings I received from AW. It doesn't look like they used aggressive settings anywgere, so I've played it "safe" from the start. Can you suggest where I can learn more about RAM? I'll give it a shot if I can up my knowledge. It's good to know it may be the OS. I also suspect itel is due for BIOS updates. I haven't reformatted in about 3 months, because getting the RAID 0 recognized was a bear. It's probably due.
    Share this post

  3. #13
    I have seen this same message Buster. In my case it usually pops up while my system is running more than one program. I run a newsreader called Grabit in the background while I play online and if both programs are trying to store and read the memory at the same time I get that error.

    Are you running any other programs? Firewall, Virus, or anything? It might be that the memory is locked by another program, not bad.
    Share this post

  4. #14
    Biker,

    It wouldn't suprise me if something was running in the background, as I sometimes forget to turn off my Norton 2004. I've only had that a couple of weeks though, and I think the problem has been going on since the machine was new. It only happens in IL2FB. I don't believe that's the cause, but it is odd. I will try to be more aware of whether it happens when background stuff is off. Thanks for the tip, and it's good to know someone else has seen this error before.
    Share this post