Memory, or MOBO problem?

[frost75]

I have bought a brand new set of Team group Chronos DDR500 2x1GB Micron series memory. Something is seriously wrong with the DDR settings for both of my motherboards.

 

For my LP SLI-DR Expert, In the orange slots, running the memory at its rated speed through bios config, of 250mhz(ddr500) memtest shows it at 130mhz, so does CPU-Z in windows. Memtest also comes with screens coliding together when i try to switch options, sometimes locking up in those places.

 

I tried the yellow slots, I cannot even post if i set bios to 250mhz. No matter 2T or 1T, nothing. I tried my old pny optima ddr400 2x512 at 250mhz but those wont boot no matter what at 250.

 

As for my older board, ultra-d, there is not even a setting showing for 250mhz in bios. Only 230mhz. Alright, well I tried that, memtest shows it at 200mhz.

 

On both boards, they both have the newest BIOS 04/06/06, these tests were also without any overclocking settings what-so-ever.

 

Why would ultra-d not even show more then 230mhz in bios settings? It shows the same limitation with my old memory. As far as this memory, it is tested to run with DFI boards(specificly listing the SLI-DR Expert). What could be the problem here? Perhaps a specific memory or other board setting I need to try? Perhaps something else?

[Sharp]

Hello,

 

On the ultra-D what CPU are you using?

 

Running the memory higher than the FSB is pointless.

[frost75]

I used my older A64 3000+ Venice.

 

It may be pointless, but If the memory wont even run on stock, theres something wrong. I am not going to try and overclock my CPU etc again with this new memory, until I know the memory is working correctly.

[Sharp]

With that CPU thew 250Mhz DRAM:FSB ratio should be there.

 

Have you ever clear the CMOS on the board?

- Place the jumper in the clear position for 10mins.

- Then move it back and see what happens.

[tasr]

Put only one memory module in the orange slot closest to the edge (both motherboards). The clear the CMOS as Sharp said.

 

Then memtest test #5 and #8 for 15-20 passes. Then repeat with other module.

 

Give that a try and post your results.

[frost75]

Both modules, no errors, on 200 & 250mhz BIOS setting.. Both modules, 130mhz @ 250mhz BIOS setting. Both modules, 200mhz @ 200mhz BIOS setting. I got a email today from team tech, all he told me was to check my PSU. Not only did I try upping the rails which did nothing. BUT, I tried running the PSU with ONLY the motherboard plugged in. NO power to the Video card(only had 1 inserted), no HDD connected period. Same results, as I told him in reply. That was not of to much help to me. I doubt I need more than 520W SLI + adjustable rails until I add even more to the pile.

[Sharp]

Memtest also does not always detect the frequency when you use dividers.

 

"when i try to switch options,"

Are you saying you used the menus in memtest to change the timings?

This is something that does not work well.

 

I would say stop using the higher dividers (230/250), they offer no improvement.

 

Stay with 1:1 or lower to help you overclock.

[frost75]

no I switch the settings in BIOS, not in memtest. Also it is not just memtest showing low frequency, even CPU-Z shows it, and I can tell by how slow the pc runs. Im going to try OC'ing with 200, hopefuly it will not do the same thing when it hits 250+ on the memory.

[frost75]

Alright, I have managed to get the memory mhz up, however something confuses me. The BIOS loading screen, does not show the DDR with the FSB addition, it only shows the multiplier. As in, its set to 200 1/1, so loading screen shows DDR400. However, the FSB is set to 280, which is DDR560. Memtest shows it at DDR560, so does CPU-z. Why does the BIOS loading screen only show the multiplier speed? Does it not count the FSB, only the main memory settings? Or is this still a sign something is wrong.

 

As for the DDR560, memtest is showing it stable with stock 3-3-3-8 1T timings, at 2.87v. Running this current setting in windows, with CPU @ 10x multi, 1.45v. So OC seems to be going good thus far, but I'm curious about this whole memory thing.