Need advice on memory issue.

Im fairly sure this is a memory problem, i cant seem to get over 220fsb at all. in fact in aggresive/turbo i cant get above 218fsb. even if i jump the vdd to 2.0v it only see's 221fsb but not in aggresive/turbo, then my bench scores drop off. i have a 2100+ hsf w/as3 on the northbridge. (waterblock on the way). im not sure if it's the Geil pc3500dc holding me back or the fact that the vdim volts only go to 2.9v. i know it's not the board i see other's going higher. when i try to go higher even just 222fsb i get a black screen & a code that's it. what do you think? :brick:

Try better cooling on the NB?

To check if it's the memory try it with 1 stick in single channel mode. Do this with both sticks, you may find that one is worse than the other.

I thought of that. i have a Dtek wb on the way. i pulled 1 stick to check them 1 @ a time but only did 1 before leaving for work, will check the other later. thanks.

I forgot, another thing to test if you have the time is the different dimm slots (with 1 stick). Sometimes it's one of the memory controllers which is worse than the other.

I tryed 1 in 1 dc slot & 1 in the regular slot, but the proformance dropped off so bad that i didnt check the other, ill have to go back & check the other slot just to eliminate that as a problem. thank's.

how did it go ?

dont know yet. my water block came in & i ripped my rig apart. will be up & running soon.

Well i installed my NB water block after giving the NB a light sanding & now i hit 221fsb( posts 221.99) in turbo/aggresive:) . but 1 mhz higher wont go.:( . i just finished my chiller but havent insolated yet. ill know better in a few days.

I'd say you need a little more juice to the ram, Vdimm mod ?

try the l12 mod it seems to work great heres a linky http://www.xtremesystems.org/forums/...threadid=15300 good luck im gonna do it as soon as my boards back from rma:)

and that vdimm scares me i tryed it once and it looked perfict and the board was dead. still haven found a good guid for it eather.

everything ive read says the L12 mod is for getting over 200fsb. i may try it anyway, i can always wipe it if it doesnt work. i think i might do the vdimm mod because i heard others say that geil mem seems to need extra volts.

its pc3500, 220fsb @ 2.9vdimm isnt the problem, its the NB, disable everything, firewire, integrated gpu, everything not needed, sound also, and that should help you well over 220 fsb.

or do the vdd mod.

Quote:

---

Originally posted by vlad
everything ive read says the L12 mod is for getting over 200fsb. i may try it anyway, i can always wipe it if it doesnt work. i think i might do the vdimm mod because i heard others say that geil mem seems to need extra volts.

---

read the thred i gave you the link for ints not just to get over 200fsb.

:thumbsup:

If you have a barton, it's a 166MHz cpu. So you at least have to cut the brigde defaulting 133MHz. But it depends on what nb rev U 've got. C1 doesn't need the mod, A2,3 do need it. Maybe there is a way to do the pin mod under the cpu too in order to getting the mod (with warranty) done. :confused: :D

But I read somewhere (it's been a while ago) the rga has it limits around 220MHz :shrug:

Quote:

---

Originally posted by SAE
If you have a barton, it's a 166MHz cpu. So you at least have to cut the brigde defaulting 133MHz. But it depends on what nb rev U 've got. C1 doesn't need the mod, A2,3 do need it. Maybe there is a way to do the pin mod under the cpu too in order to getting the mod (with warranty) done. :confused: :D

---

There is, I just did it about 3 hours ago on a 2500+. :D

That was for my NF7-S v1.2 (A3 NB). You just need to connect pin AH30 (fsb_sense1) to AK30 (Vcc). The white line in this pic shows how to do it;

You either need more vdimm or more vdd. 2.9 isnt always enough believe it or not...not to mention maybe you need to evaluate the timings you are trying to run bud.

If I am not mistaken, on NF2 boards, the ram is getting its juice off the 3.3 rail...you need to have a look at your rails and let us know if they are terribly low or fluctuating alot under load.

thanks guys for all the help. so here it is. i built this rig for OCing/benching only so everything that isnt needed is disabled. i went with the RGA because it already has vdd adjustable in bios
& i figured 1 less thing to mod. since my last post i changed the settings from aggresive/turbo to opp/expert then from 2.3.3.8 to
2.5.3.3.8 & bumped the vvd from 1.8 to 2.0v. i still havent hooked up my chiller. i want to insulate the right way before using it, anyway i did a 1/2 ass(temp) insulating job to the WB's, chilled w/ice to 20c & now she goes 11x225fsb, i tryed to go higher w/lower multi but nogo. @2480mhz after a short burn she ran all benchs but 3DMark(need more vcore but already maxed) kicks back to desktop. runs pcMark=7702cpu/6937mem. sandy went dhry=9316 whet=3716 integer=13761 float=14681. im going to burn in a little more to see if she'll run 3D. ill still try the L12 mod once i get the chance, i'd also like to try the 8 bit mod in the link
DR.YT gave me. i started a thread on vcore mod for the RGA/RDA.
im @ 2.2v in bios but usdm shows only 2.14v. this step seams to love the volts, maybe it wont need as much once i chill to freezing.
i hope! i'd like to get 2.5ghz stable & i'd like to see 20k/2k1 before retiring my nonpro for a 98pro. thanks again, any more idea's pass'em on .:thumbsup:

Quote:

---

Originally posted by vlad
kicks back to desktop.

---

Don't think it's the cpu. If being kicked back to dt the ram should be considered the cause :stick:

I've been kicked back to desktop before and it was becasue my vcore was too low.

Quote:

---

Originally posted by iceman2g
I've been kicked back to desktop before and it was becasue my vcore was too low.

---

Oh. I did not know that :)

I always thought it could only be mem errors like I often read here in the forums :D

Quote:

---

Originally posted by vlad
& i'd like to see 20k/2k1 before retiring my nonpro for a 98pro

---

Well 100MHz cpu = ~300-400 points (if fsb and everything else is the same) so you have a bit to do to get 700. I think below-ambient cooling definitely helps a lot with these Bartons so get that chiller hooked up. :D
Good luck, and very nice clocks on that 9700np btw! :toast:

Of course tRAS-11 is faster than -4. With tRAS 4 you allow the controller to kill the transfers before they are even initiated ..

here are all gory details:


http://www.lostcircuits.com/memory/ocz3700/3.shtml

Quote:

---

Originally posted by unregistered
Of course tRAS-11 is faster than -4. With tRAS 4 you allow the controller to kill the transfers before they are even initiated ..

here are all gory details:


http://www.lostcircuits.com/memory/ocz3700/3.shtml

---

i tryed 11 from having 7.. and my windows install went to crap.. my hdds would lock, and all this crap happened..

Windows still is jacked since i did that even after setting it back to 7..

So i dunno, it may bench great, but my system didnt seem to liek it for some reason..

Well, again, setting tRAS too high will not buy you anything either. The rule of thumb is: tRAS= tRCD+CL+2 (or +3). This way you have all your parameters matched up and working with each other instead of against each other.

If you set tRAS too long, it shouldn't have too much of an effect, except for unnecessary delays of the page closing in case of a single burst transfer. I don't see how this could mess up Windows, most likely, you have some "creeping corruption" from your earlier tRAS=4 settings somewhere.

see: http://www.lostcircuits.com/advice/bios2/7.shtml

My recommendation is to reformat your drive and start clean.

Unfortunately, the kcik to desktop could be any number of things, but since ram timing changes altered 4 fsb, I would imagine it is the culprit, try tightening the setting to 2,2,5,2 and thell us what happens.

IF you get post code c1,01,02,03,c2,c3,or 2b, congradulations; it is your memory.

Would more voltage help solve the kick to desktop problem?

Quote:

---

Originally posted by iceman2g
Would more voltage help solve the kick to desktop problem?

---

i use to think it was a memory problem, but after alot of hours
trying diffrent things i found that whenever my overclock got a little shakey in 3DMark2k1 it always needed more vcore. 2k3 is even worse plus its more senstive to gpu OC's in addition. i can max the core/mem in 2k1 but not in 2k3. later.