Memtest wrong?

[genjaguar]

Well I can run my computer perfectly(Prime stable) at 240HTTx10 at 1.5vcore with ram at 1:1 at 2.6vdimm(could probably do lower) with timings of 2.5-4-3-7. I ran memtest for over 17 1/2 hours at 2.5-3-3-7 with a vdimm of 2.5 and vcore of 1.45 and everything else the same and it didn't have a single error.
When I try to run 3dmark05 it froze or gives me errors and is unstable in games. What would this mean?

[Major]

It means your memory is probably not the cause of 3d crashing. I'd look at lowering the LDT multi . Also you should up the agp voltage .1v (1.6) to see if that helps.

Also it could simply be a bad install of either the video drivers, directx, NForce, or 3dmark05. Are you overclocking your video card ? If so that might also be something that you should try setting to default clocks.

Are you sure the AGP is locked ?? you can check it with clockgen.

[genjaguar]

Well my LDT multi is at 4x. I can run 3dmark05 fine with my video card overclocked with the memory at 2.5-4-3-7. It's at 561/1120 which isn't that high. AGP lock is at 66mhz in bios(66.67 in clockgen).

[blackjok3r]

tyr lowering the graphics card to stock and testing the psu with SnM psu test. Just run that and see voltage fluctuations. If they vary a lot from idle to load then its the psu.

[mad mikee]

Stepping info can't hurt.

1) run memtest # 8 for 10 loops to make sure all is really well (maybe). memtest stable != windows stable, can you pass 4m spi and OCCT basic test?

Usually those tight dreamy alpha timings fall apart in windows and have to be scaled back:bsod:
Give the mem a kick upwards to 2.7 just for grins, that small an amount shouldn't hurt anything. You can experiment w/ what to scale back after you get somewhere :D

Will check up here in the morning

[genjaguar]

Well my cpu is CBBID 0451. Ill run memtest #8 and get back to you.

[genjaguar]

I looped test #8 and while I was gone it did 68 passes at 2.6vdimm without a single error.

[STEvil]

You might need to set AGP to 67mhz for the lock to actually work.

[genjaguar]

Clockgen reads it at 66.67 so I think 66 locks it as well.