700 cB0 won't POST at 1050, what could it be?

[Strafe]

I have a 700 cB0 FC-PGA on an Asus CUV4X (Via 133A) with 256MB PC133 RAM (mosel chips from memory man, should do 150 at cas2), a Golden Orb and a CLA2. Running at 933 no problems although pushing it to 1.70v did solve some stability issues.

It seems to me that all components should have no problems at 150 but once I turn the PC on, The fans come one but the video never kicks in and I get no POST. I dont think heat is a problem since 933 at idle is around 70F. Is the chip just maxed or am I missing something in the BIOS?

 

[rickn]

you imply that 1050 is suppose to be some guarantee? Well it aint. You are overclocking. It is luck. If it dont make the cut, it dont make the cut. Live with it

Try cooling the clock generator chip. Set your memory timings by SPD. Get the system stable even if that means using the slowest memory timings, AGP2x etc etc. After you get stability, then start to tweak one setting at a time. You will most likely find out what is the culprit

 

[Plester]

i wouldn't hold my breath.

 

[FullRoast]

I can give you a deal on a cB0 700 that won't post beyond 882MHz, and that is with the voltage tweaked to +10%. Some cB0 700's just don't overclock well. (I just wish I wasn't the owner of one of them!)

 

[Strafe]

No I didn't expect a 1050 guarantee, I just consider myself a better overclocker than most Anyway my question was what component do you suspect is the limiting factor. I'm happy at 933 but it was so easy ...

I'll try changing the memory to CAS3 but my view is, if you have to disable some features (like AGP speed, CAS, etc...) it's not worth it.

 

[rickn]

I have a 650e @ 962mhz(148mhz FSB, memory 3-2-2-5, 4 way interleave, 1.75v) on a P3V4X, which is the earlier brother to the Cuv4X. I run Geforce DDR at 150/351(AGP4x, Sideband, Fastwrites all enabled)

I had some issues at first, and it boiled down to core voltage. Upping it to 1.75v corrected it. Play with it, find out what exactly is your "sweet spot"

 

[chottoed]

cB0 700 s-spec sl3xx
994@1.8v <-that's w/ over 140hrs of burn-in
85% stable at 1001....
don't hold your breath on that ghz...
maybe if you get a peltier or something

 

[Jhhnn]

rickn is giving you the right stuff in his 10:38 post, agp4x is pretty much a marketing blurb at this time, like an amr slot with nothing to fit into it.

 

[DaddyG]

I'd say kick up the core voltage and back off the memory timing to the slowest. This board supports asynchronous memory timing, FSB-PCI clock. That will get the memory to about 115. Try this as a test and tweak as required.

 

[Unexpected]

I run a 650E at 975 MHz / 1.7v rockstable. I also run a Geforce DDR at 150/350. The motherboard is a Abit SE6 ... The cpu runs at 995MHz in windows but prime crashes after test 10 of 29 and Unreal Tournament won't load I am using a golden orb as cooler ...

 

[rpr]

Rickn:

How have you enabled 4 way interleave on the P3V4X? I have the same board but don't see that option in the BIOS (I'm still using 1003).

 

[pvanosta]

Strafe: a lot ov VIA 133A MoBo's become unstable above 147 fsb. My MSI 6309 pretty much hits a brick wall at the same point.
I'm sure my chip can do the 150, as can all my peripherals, but the MoBo just won't do it.

 

[dakost]

Why the jump from 133 to 150 ? I thought that the CUV4X does support 140 fsb ie 980 MHZ. Did you try 140 fsb ?
You Set the memory timings at host clock - 33 and check if the cpu can do 150 fsb. If it can then the CUV4X it doesn't like the memory at 150 fsb and 1:1 timing, in which case you can increase the vio from 3.4 to 3.6V ( I think bot the P3V4X and the CUV4X as well as the cusl2 have the default vio set at 3.4V and not at 3.3 ) and try again. If it can't then this particular cpu can't do 150fsb.
To test the rest of your pci peripherals at 37.5 pci ( 150 / 4) you can also try to set the fsb to 112 - 124, then the divider is 1/3 and you'll get 37.5 - 41.3 pci. The cpu will be running at 784 - 868 MHz and the memory should be no problem. So if you have problems at 112 fsb, then it has to do with one of your peripherals.