Quote:
|
Originally Posted by treeninja i tried:
Stock BIOS: 201*11, Vcore:1,6V, Vdimm:2,76V, 2-2-2-11 blue screen
Stock BIOS: 202*11, Vcore:1,6V, Vdimm:2,76V, 2-2-2-11 blue screen
then tried:
Stock BIOS: 200*11, Vcore:1,6V, Vdimm:2,76V, 2-3-3-11 it was OK
Stock BIOS: 201*11, Vcore:1,6V, Vdimm:2,76V, 2-3-3-11 blue screen
Blue screen appeard at varius timings, even if i have 2,5-3-3-11. What is wrong? |
Hiya,
There shouldn't be so sudden change in stability while raising the FSB - I mean from "Ok" to "blue screen" 1MHz higher. As you may have noticed, timings don't seem to have any influence here - your memory should be capable of doing 2-2-2-11 up to FSB 210-220, especially with just one stick 256MB (the less memory the better FSB overclock).
I know two possible reasons for such a situation :
1) Your
PSU is giving it's last breath -
OC just a little more and it will die in flames (I'm more serious than kidding).
2) The Lack of L12 mod - some timings for nForce2 chipset are set to FSB133, even when you raise your FSB in bios - just because FSB133 is the default one for your CPU. FSB200 is like a threshold - one step further and you get instability.
A friend of mine has had similar problem with Athlon XP T-bred 1700+ and an Epox 8RDA3+ rev.2.1. At FSB200 everything was fine, at FSB201 his PC was unstable, no matter what he did to change that situation. With L12 mod and just one stick of RAM (256MB) he achieved then FSB240 with ease (stably!).
Quote:
|
Originally Posted by treeninja what is changed in modded bios? can somenone explain me in few words? |
L12 mod bulit in (soft L12) => more on it you can find here :
http://www.geocities.com/trats102002/nf7sFsbsense.html
Changed FSB 133&166&200 ROMSIP tables (some chipset timings and more - don't ask me for details!
)
Different alpha memory timings - sort of hidden memory timings (some of them can be set in bios on DFI motherboards).
If I recall something more, I'll make an update.
cheers and good luck!