If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
memory issue
Fan problems aside (see below), I also have memory problem.
I came in a few days ago to find my win98 machine had crashed. I rebooted and the diagnostic lights came on (MSI KT3 Ultra motherboard, VIA KT333 chipset), indicating a memory error. The two modules each 256Mb PC2700 non-ECC, I will call A and B. A works fine in slots 1 (nearest CPU) and 3. If I put in in slot 2 the alarm sounds and nothing happens. B will not work in any slot. If I put in A and B together, B is not recognised at the BIOS startup or anywhere else. I have run memtest86. Three passes of default tests on A reveals no problem. If I put in B by itself of course the machine doesn't boot and it never gets to memtest. If I put in A and B together, memtest as far as I can see only tests A - memory is listed as 256Mb, and tests are clear. I am prepared to replaced module B, since this never works. Why does A only work in two of the three slots? (The CL is marked 2.5, and I have set it as 2... it's been like this for six months, this isn't the problem is it?) -- Susan |
#2
|
|||
|
|||
"S.Boardman" wrote in message
... Fan problems aside (see below), I also have memory problem. I came in a few days ago to find my win98 machine had crashed. I rebooted and the diagnostic lights came on (MSI KT3 Ultra motherboard, VIA KT333 chipset), indicating a memory error. The two modules each 256Mb PC2700 non-ECC, I will call A and B. A works fine in slots 1 (nearest CPU) and 3. If I put in in slot 2 the alarm sounds and nothing happens. B will not work in any slot. If I put in A and B together, B is not recognised at the BIOS startup or anywhere else. I have run memtest86. Three passes of default tests on A reveals no problem. If I put in B by itself of course the machine doesn't boot and it never gets to memtest. If I put in A and B together, memtest as far as I can see only tests A - memory is listed as 256Mb, and tests are clear. I am prepared to replaced module B, since this never works. Why does A only work in two of the three slots? (The CL is marked 2.5, and I have set it as 2... it's been like this for six months, this isn't the problem is it?) Bad slot. It happens. I've had the same thing happen. The middle slot on my 694T Pro mainboard doesn't work, but apart from that, my computer is solid as a rock. -- Bob Day http://www.bob.day.name |
#3
|
|||
|
|||
On Sat, 11 Oct 2003 22:42:24 +0100, "S.Boardman"
wrote: Fan problems aside (see below), I also have memory problem. I came in a few days ago to find my win98 machine had crashed. I rebooted and the diagnostic lights came on (MSI KT3 Ultra motherboard, VIA KT333 chipset), indicating a memory error. The two modules each 256Mb PC2700 non-ECC, I will call A and B. A works fine in slots 1 (nearest CPU) and 3. If I put in in slot 2 the alarm sounds and nothing happens. B will not work in any slot. If I put in A and B together, B is not recognised at the BIOS startup or anywhere else. I have run memtest86. Three passes of default tests on A reveals no problem. If I put in B by itself of course the machine doesn't boot and it never gets to memtest. If I put in A and B together, memtest as far as I can see only tests A - memory is listed as 256Mb, and tests are clear. I am prepared to replaced module B, since this never works. Why does A only work in two of the three slots? (The CL is marked 2.5, and I have set it as 2... it's been like this for six months, this isn't the problem is it?) Yes, it can definitely be a problem to try running CL2.5 memory at CL2... CL 2 is a higher-performance, more agressive timing. Are you running the board at DDR266 FSB and DDR333 memory speed? If so, reduce the memory speed to DDR266 to run synchronous to the FSB... in some cases it can even improve performance. In general the middle memory slot is often the least stable, so if only running two modules you may as well just leave that slot empty. The best attempt at setting memory timings might first be trying the "Auto" or "SPD" BIOS setting. If that proves instable, manually set the individual timings to the slower (higher number) settings. Dave |
#4
|
|||
|
|||
"kony" wrote in message ... On Sat, 11 Oct 2003 22:42:24 +0100, "S.Boardman" wrote: snip description... I am prepared to replaced module B, since this never works. Why does A only work in two of the three slots? (The CL is marked 2.5, and I have set it as 2... it's been like this for six months, this isn't the problem is it?) Yes, it can definitely be a problem to try running CL2.5 memory at CL2... CL 2 is a higher-performance, more agressive timing. I thought it was OK to do this as long as the memory is decent spec/quality? Are you running the board at DDR266 FSB and DDR333 memory speed? Haven't a clue! If so, reduce the memory speed to DDR266 to run synchronous to the FSB... in some cases it can even improve performance. In general the middle memory slot is often the least stable, so if only running two modules you may as well just leave that slot empty. The best attempt at setting memory timings might first be trying the "Auto" or "SPD" BIOS setting. If that proves instable, manually set the individual timings to the slower (higher number) settings. I'll have a look in the BIOS. I've shuffled them around again and the modules seem to work in slots one and three. Memtest86 records 512 Mb and even the extended tests come back fine... Why module B fails on its own, I do not know! -- Susan |
#5
|
|||
|
|||
On Sun, 12 Oct 2003 19:31:59 +0100, "S.Boardman"
wrote: Yes, it can definitely be a problem to try running CL2.5 memory at CL2... CL 2 is a higher-performance, more agressive timing. I thought it was OK to do this as long as the memory is decent spec/quality? CL2.5 isn't "decent" spec.. lower CAS # memory is the better memory. CL2.5 memory should work fine, but you're essentially overclocking it. Some people can get away with manually setting timings exceeding the manufacturer's spec, but whenever a problem arises relating to memory, it needs be returned to specified values. Are you running the board at DDR266 FSB and DDR333 memory speed? Haven't a clue! The BIOS setup should show this, either as the number (266 or 133) or as "+33". Often KT333 boards do default to running at +33, otherwise known as an asynchronous mode, since it doesn't match the FSB speed. I'd run both at DDR266, which again the bios may call 133 (MHz). I'll have a look in the BIOS. I've shuffled them around again and the modules seem to work in slots one and three. Memtest86 records 512 Mb and even the extended tests come back fine... Why module B fails on its own, I do not know! That is unusual. Perhaps being a less capable module, when it's the only module in use, the motherboard increases (lowers) the memory timings, but with both modules in, the timings are relaxed again. Dave |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
HELP: Hardware Resources - How resolve memory conflict? | FN | General | 8 | August 27th 03 11:24 PM |
memory | kony | General | 4 | August 21st 03 12:12 AM |
question about virtual memory | takashi | General | 2 | August 18th 03 12:37 PM |
Chaintech 7NIF2 motherboard - memory problems | Wuahn | General | 1 | July 26th 03 01:29 PM |
will this memory fit into a KT400 mobo? | fred.do | General | 3 | June 24th 03 02:44 PM |