Re: VENICE 3500+ can't be OC'd now, makes no sense.
On Tue, 08 May 2007 13:47:36 -0400, Bob Brown INC. wrote:
> Installed a new SATA II drive, from that point it wouldn't allow a
> BOOT without me taking ALL OC off. Tried just very minor OC and it
> refused to Boot.
>
> That makes no sense.
>
> Why does SATA II drives Force you to undo all OC'ed properties?
Perhaps the bus that runs the sata drives isn't locked and goes beyond
specs when you oc the system bus. Look for some sata bus settings in the
bios.
Re: VENICE 3500+ can't be OC'd now, makes no sense.
Bob Brown INC. wrote:
> Installed a new SATA II drive, from that point it wouldn't allow a
> BOOT without me taking ALL OC off. Tried just very minor OC and it
> refused to Boot.
>
> That makes no sense.
>
> Why does SATA II drives Force you to undo all OC'ed properties?
You've got plenty of adjustments in there, clock-wise. Verify that
none of the BIOS settings have reset themselves. If anything is
on "Auto", switch to a manual setting. For the PCI Express clock,
switch from [Auto] to [100MHz]. The PCI bus clock normally runs
at 33Mhz. You can try picking values for all of those, save the
BIOS settings, and try again.
The manual claims PCI Express and PCI clocks are independent of
the main CPU clock, so that should not be the problem. The purpose
of using manual settings, is in case there is a problem with
the BIOS.
When you add a new drive, that will change the boot order. A lot
of Asus BIOS have that annoying feature. It means visiting the
BIOS, every time you change the storage configuration.
Re: VENICE 3500+ can't be OC'd now, makes no sense.
On Wed, 09 May 2007 01:18:59 -0400, Paul <nospam@needed.com> Let
everyone including the NSAs Internet database storage program know as
they typed on their keyboard faster than a monkey on crack the
following:
>Bob Brown INC. wrote:
>> Installed a new SATA II drive, from that point it wouldn't allow a
>> BOOT without me taking ALL OC off. Tried just very minor OC and it
>> refused to Boot.
>>
>> That makes no sense.
>>
>> Why does SATA II drives Force you to undo all OC'ed properties?
>
>You've got plenty of adjustments in there, clock-wise. Verify that
>none of the BIOS settings have reset themselves. If anything is
>on "Auto", switch to a manual setting. For the PCI Express clock,
>switch from [Auto] to [100MHz]. The PCI bus clock normally runs
>at 33Mhz. You can try picking values for all of those, save the
>BIOS settings, and try again.
>
>The manual claims PCI Express and PCI clocks are independent of
>the main CPU clock, so that should not be the problem. The purpose
>of using manual settings, is in case there is a problem with
>the BIOS.
>
>When you add a new drive, that will change the boot order. A lot
>of Asus BIOS have that annoying feature. It means visiting the
>BIOS, every time you change the storage configuration.
>
> Paul
Re: VENICE 3500+ can't be OC'd now, makes no sense.
"Bob Brown INC." <sillyspammers@bots.dumb> wrote in message
news:iqd143hsliag13eojnicamvefr7vu9f0kd@bbb.org...
> Installed a new SATA II drive, from that point it wouldn't allow a
> BOOT without me taking ALL OC off. Tried just very minor OC and it
> refused to Boot.
>
> That makes no sense.
>
> Why does SATA II drives Force you to undo all OC'ed properties?
SATA2 shouldn't cause the problem by itsef.My WD 120GB sata 2 drive is
running fine in a slightly FSB overclocked PC . A64 4000+(2.4) runnig at
2.55ghz.