- May 15, 2006
- 708
- 1
- 81
Originally posted by: fritzfield1234
How about the e6600?
E6600 already runs a 1066Bus speed so the BSEL mod is of no value for this CPU.
Originally posted by: fritzfield1234
How about the e6600?
Originally posted by: Mr Vain
You will probably need to do mods to go higher from here on.
Originally posted by: enDings
Originally posted by: Mr Vain
You will probably need to do mods to go higher from here on.
- Hello Mr Vain, thaks for ur answer ^^!!!! I don't understand what means "do mods" u can explain it? Some tutorials or something?
- Thanks again
Originally posted by: Mr Vain
Read thru this tread as it is very good for modding this motherboard.
http://forums.vr-zone.com/show...3127&highlight=Mr+Vain
:thumbsup:
Originally posted by: enDings
Originally posted by: Mr Vain
Read thru this tread as it is very good for modding this motherboard.
http://forums.vr-zone.com/show...3127&highlight=Mr+Vain
:thumbsup:
- Only i can mod with touching de Micro? not bios? If i ut Vram on high? T_T
I dont wanna touch the micro T_T cry
Originally posted by: Mr Vain
Wow Dude get's 359FSB with Clock Generator and pencil mods.
http://www13.plala.or.jp/setfsb/
Quote post 322
http://www.xtremesystems.org/f...7017&page=13&highlight
Originally posted by: Silakka80
To Norest:
I`m running with e6750 and it works underclocked.
now fsb is 305 X 8 = 2440 mhz
so if you buy that cpu i recommed that you buy better mobo also.
this mobo is full of SHIT!!! don`t buy it !!
i`m runned now with assrock 1 mont and will buy new
inno3d , evga , xfx 680i
or some asus p5k3 deluxe
help me to deside witch is better??
Originally posted by: Lozzo
Originally posted by: Silakka80
To Norest:
I`m running with e6750 and it works underclocked.
now fsb is 305 X 8 = 2440 mhz
so if you buy that cpu i recommed that you buy better mobo also.
this mobo is full of SHIT!!! don`t buy it !!
i`m runned now with assrock 1 mont and will buy new
inno3d , evga , xfx 680i
or some asus p5k3 deluxe
help me to deside witch is better??
The E6750 is a 1333Mhz FSB CPU, and this board is only certified for 1066FSB, so obviously it will not run a 1333Mhz CPU at its rated speed anyway.
Regarding the setFSB utility. There is a thread on this board somewhere relating to this util and the Asrock boards elsewhere. Anyway, upon my ASrock 4CoreDual-VSTA, SetFSB only reads my board frequencies properly if I set the clockgen to the RTM866-485 as opposed to the RTM866-890 as suggested.
For example, at the moment it reads my current FSB/DDR/PCI-E/PCI as 290/580/118.8/33.3 Mhz respectively.
As an aside, as you can tell from above, setFSB *does* show the PCI/PCI-E clock as being locable/adjustable independently of the FSB as any changes I've made in the BIOS to see if it does reflect BIOS settings (trying an odd PCI freq, or an odd PCI-E freq) have been shown by setFSB.
Anyway, using SetFSB I've had my E2160 up at a FSB of 320 stable so far, and this without any volt/pencil mods, standard cooling and DDR2/667 RAM set as 533Mhz with 5-5-5-15 timings. However, things looked like they were getting a bit toasty on my standard cooling, so I backed down to my usual BIOS settings of 290Mhz. I've yet to have the time to try tweaking further up, the 320 was just a shot in the dark, rather than raising in steady increments. I did try a quick shot at 333 but it just froze up on me.
Originally posted by: brokencase
I also get the erroneous pll id error when I run the
updated setfsb utility on my Asrock 4CoreDual-SATA2.
I've tried some of the other PLL's and they did not work either.
I'm guessing that the later boards like the SATA have different PLL's
Update, I have been able to overclock the Q6600 on the SATA through the bios.
I am running BIOS rev 1.50. I am up to 275 right now. I need to setup a torture test before I attempt to go further. Like a couple of instances of SuperPi or Prime95 running for a few hours.
Originally posted by: Lozzo
Bables : Sounds like your BIOS/CMOS settings are a bit screwy.
Reset the CMOS by the jumpers on board, keep everything standard, flash BIOS to latest version (maybe best to do it the good old fashioned DOS way, rather than the windows BIOS update, considering the random flakiness you're having.) ,reset CMOS again and try again. At least you'll be back to a known setting/config then.