Charloz24 Member Joined Jul 14, 2003 Location Canada Apr 19, 2004 #1 This message appear sometime when folding (tinkers, not gromacs) or in the windows explorer: The instruction at "0xf7c4c3c5" referenced memory at "0xf7c4c3c5". The memory coould not be "read". Is it memory corruption? Or windows xp problem?
This message appear sometime when folding (tinkers, not gromacs) or in the windows explorer: The instruction at "0xf7c4c3c5" referenced memory at "0xf7c4c3c5". The memory coould not be "read". Is it memory corruption? Or windows xp problem?
glock19owner Member Joined Nov 6, 2002 Apr 20, 2004 #3 Charloz24 said: This message appear sometime when folding (tinkers, not gromacs) or in the windows explorer: The instruction at "0xf7c4c3c5" referenced memory at "0xf7c4c3c5". The memory coould not be "read". Is it memory corruption? Or windows xp problem? Click to expand... Usally a windoze XP problem is a memory issue...especially on a NF2 MB... What memory and timings and FSB are you running at?
Charloz24 said: This message appear sometime when folding (tinkers, not gromacs) or in the windows explorer: The instruction at "0xf7c4c3c5" referenced memory at "0xf7c4c3c5". The memory coould not be "read". Is it memory corruption? Or windows xp problem? Click to expand... Usally a windoze XP problem is a memory issue...especially on a NF2 MB... What memory and timings and FSB are you running at?
OP Charloz24 Member Joined Jul 14, 2003 Location Canada Apr 20, 2004 Thread Starter #4 I don't know why, because I used to do 217 fsb on this memory (for month and month of folding) And I was running it now only at 200 fsb....
I don't know why, because I used to do 217 fsb on this memory (for month and month of folding) And I was running it now only at 200 fsb....
Digital_Cowboy Member Joined Feb 17, 2004 Location 192.168.1.1 Apr 20, 2004 #5 run memtest. Tha'll tell you if your ram is bad for sure.