- Joined
- Sep 8, 2001
- Location
- In the Dark!!
Memory problems!!
Am i right in thinking my memory has errors or is suffering from some fault? I have 1 stick of 256mb Samsung pc2700 and when i try and run an fsb above 138 i get lockups and non posts in windows xp(even with cpu voltage increase to 1.8v). I did manage to run it @ cas 2.0 for a few months, but scince flashing my A7v333r with the latast bios 1014, when I run the memory test at boot up it constantly cycles through the count and then restarts until i press the esc button. Sometimes it doesn't even get that far and im just left with the processor indentity and no memory count at all.
If i put it into cas 2.0, it now reads the memory value as being 33768mb when in actual fact its just a 256mb stick. I;ve just bought a XP2200+ and am longing to clock a high fsb.
It seems to run fine at 133 with 4/5 divider, but no chance of getting it anywhere near 166. Please advise.
I have flashed back to previous bios's but i get the same problem with all, It started happening when i had my 1.4 T-bird installed, so i dont think its the chip, could it be the motherboard?
MDA.
Am i right in thinking my memory has errors or is suffering from some fault? I have 1 stick of 256mb Samsung pc2700 and when i try and run an fsb above 138 i get lockups and non posts in windows xp(even with cpu voltage increase to 1.8v). I did manage to run it @ cas 2.0 for a few months, but scince flashing my A7v333r with the latast bios 1014, when I run the memory test at boot up it constantly cycles through the count and then restarts until i press the esc button. Sometimes it doesn't even get that far and im just left with the processor indentity and no memory count at all.
If i put it into cas 2.0, it now reads the memory value as being 33768mb when in actual fact its just a 256mb stick. I;ve just bought a XP2200+ and am longing to clock a high fsb.
It seems to run fine at 133 with 4/5 divider, but no chance of getting it anywhere near 166. Please advise.
I have flashed back to previous bios's but i get the same problem with all, It started happening when i had my 1.4 T-bird installed, so i dont think its the chip, could it be the motherboard?
MDA.
Last edited: