SATA "bottleneck"
Tags:
Last response: in CPUs
Switched from Parallel ATA to SATA and performance is sensibly increased. However, over FSB 225 the disk is not detected. Anybody knows how to get around this ???
More about : sata bottleneck
The bus on which the integrated SATA ports are is'nt frequency locked for the A8V-MX, only the SATA ports connected to the Promise controller found on the Deluxe version have that feature, or so I've read on This Thread
Related ressources
- Insane Amount of Problems with OS Install x79 Intel SATA /RAID Drivers - Forum
- Does a presario v6000 have a sata connection for a ssd hard drive - Forum
- SATA 2 vs. SATA 3 cable - Forum
- WD 80gb sata hard disk failure - Forum
- Opinions and price of this PSU........... - Forum
Quote:
The bus on which the integrated SATA ports are is'nt frequency locked for the A8V-MX, only the SATA ports connected to the Promise controller found on the Deluxe version have that feature, or so I've read on This Threadthis is the problem for you.....
dont feel bad...i have NO LOCKS(PCI/AGP/SATA/NOTHING) at all and 4 sata drives....if i try 225 i will kill all my drives(corupt all data on them)....
however i do not think that board has a promise controller onboard(said above too)....is that the MATX board right? with all 4 sata ports on the VIA SATA/Raid controller...
the only thing i could see working is a PCI sata controller(as long as your pci bus is locked).....but IMO its not worth it in your case.....why not just stick at 220? its still a useful OC
I hope this helps
Quote:
Is't it possible that the disk itself does not respond? It's not totally locked if I can set my FSB at 225!The problem is that the SATA bus clock is not locked at all, so moving your system clock (whatever its called on that mobo - system clock, HTT, FSB, whatever) also overclocks the SATA bus. In your case, your HDD and/or SATA controller has an oc limit of 25mhz (I only got about 10mhz). If you're lucky, moving it back down below 225 will let you boot up again. In my case (not an Asus, a Soyo) it wouldn't boot and I had to reformat & reinstall.
Mike.
That is what we are trying to say "You SHOULD lock the SATA ports". Most will stop/have issues at ? frequency while overclocking. The reason for the ? is that is an unknown per controller/MB.
Alot of people while attempting an overclock will lock those to a certain freq so as to not have issues.
Sid beleives that your MB does not have the capability to LOCK the SATA. If so you are limited in your capabilites to OC.
Alot of people while attempting an overclock will lock those to a certain freq so as to not have issues.
Sid beleives that your MB does not have the capability to LOCK the SATA. If so you are limited in your capabilites to OC.
It's a feature (or lack of thereoff) of your motherboard chipset that is causing the problems you are experiencing. That's the good old PCI lock bug.
At stock settings, everything is fine since all the frequencies are within specs, as you increase the bus (be it the HT or FSB) all the other bus that are using it as a reference point see an increase in their operating frequencies as well.
In your case, a 225MHz HT clock is ~12% over specs, that's still within the tolerance margin of the PCI bus (36~37MHz or so), as you increase it over 38MHz, either the devices or the controller itself start failing, that's the wall you're hitting right now.
Due to that design flaw, the best you can hope for is a 12% OC unless you get a motherboard that was designed with overclocking in mind.
What we refer to as a PCI (or AGP) lock is a workaround that keep the bus frequencies separated from one an other by using dividers, this is something manufacturers integrate into their motherboards during conception so there is no way to force it on.
You can always try to swap your SATA HDD for IDE and hope that the PCI lock is working for that particular controller.
At stock settings, everything is fine since all the frequencies are within specs, as you increase the bus (be it the HT or FSB) all the other bus that are using it as a reference point see an increase in their operating frequencies as well.
In your case, a 225MHz HT clock is ~12% over specs, that's still within the tolerance margin of the PCI bus (36~37MHz or so), as you increase it over 38MHz, either the devices or the controller itself start failing, that's the wall you're hitting right now.
Due to that design flaw, the best you can hope for is a 12% OC unless you get a motherboard that was designed with overclocking in mind.
What we refer to as a PCI (or AGP) lock is a workaround that keep the bus frequencies separated from one an other by using dividers, this is something manufacturers integrate into their motherboards during conception so there is no way to force it on.
You can always try to swap your SATA HDD for IDE and hope that the PCI lock is working for that particular controller.
Quote:
It's a feature (or lack of thereoff) of your motherboard chipset that is causing the problems you are experiencing. That's the good old PCI lock bug.At stock settings, everything is fine since all the frequencies are within specs, as you increase the bus (be it the HT or FSB) all the other bus that are using it as a reference point see an increase in their operating frequencies as well.
In your case, a 225MHz HT clock is ~12% over specs, that's still within the tolerance margin of the PCI bus (36~37MHz or so), as you increase it over 38MHz, either the devices or the controller itself start failing, that's the wall you're hitting right now.
Due to that design flaw, the best you can hope for is a 12% OC unless you get a motherboard that was designed with overclocking in mind.
What we refer to as a PCI (or AGP) lock is a workaround that keep the bus frequencies separated from one an other by using dividers, this is something manufacturers integrate into their motherboards during conception so there is no way to force it on.
You can always try to swap your SATA HDD for IDE and hope that the PCI lock is working for that particular controller.
Looks like I have to hold my FSB 225 tight!
Multipliers on A64 CPUs are locked upward so yeah, no other options than either be happy with his current OC, using IDE HDDs instead of SATA (they're supposed to be good up to 270MHz) or getting an OC friendly mobo.
My mobo have similar limitations, SATA ports 1 & 2 crap out even on a mild OC, fortunately, SATA 3 & 4 are fine. The Deluxe version of the A8V behave the same as my K8N Neo2, the two "extra" SATA ports it have over the MX version will work just fine.
My mobo have similar limitations, SATA ports 1 & 2 crap out even on a mild OC, fortunately, SATA 3 & 4 are fine. The Deluxe version of the A8V behave the same as my K8N Neo2, the two "extra" SATA ports it have over the MX version will work just fine.
I have a new build coming up so I will get to play again! I actually may go with the "BadAxe" Intel board used for the Conroe testing/OCing. 1mhz increments for nearly everything gives a whole lot of leeway for a good solid OC.
I might even be putting together a merom HTPC for a client (side business). That should be fun. Have a limited form factor and limited heat disipation so need to stay cool!
I might even be putting together a merom HTPC for a client (side business). That should be fun. Have a limited form factor and limited heat disipation so need to stay cool!
Quote:
Multipliers on A64 CPUs are locked upward so yeah, no other options than either be happy with his current OC, using IDE HDDs instead of SATA (they're supposed to be good up to 270MHz) or getting an OC friendly mobo.My mobo have similar limitations, SATA ports 1 & 2 crap out even on a mild OC, fortunately, SATA 3 & 4 are fine. The Deluxe version of the A8V behave the same as my K8N Neo2, the two "extra" SATA ports it have over the MX version will work just fine.
The MX has 4 SATA ports too! Tou are saying that just bt changing the connector position can improve overclocking?
Quote:
It's a feature (or lack of thereoff) of your motherboard chipset that is causing the problems you are experiencing. That's the good old PCI lock bug.At stock settings, everything is fine since all the frequencies are within specs, as you increase the bus (be it the HT or FSB) all the other bus that are using it as a reference point see an increase in their operating frequencies as well.
In your case, a 225MHz HT clock is ~12% over specs, that's still within the tolerance margin of the PCI bus (36~37MHz or so), as you increase it over 38MHz, either the devices or the controller itself start failing, that's the wall you're hitting right now.
Due to that design flaw, the best you can hope for is a 12% OC unless you get a motherboard that was designed with overclocking in mind.
What we refer to as a PCI (or AGP) lock is a workaround that keep the bus frequencies separated from one an other by using dividers, this is something manufacturers integrate into their motherboards during conception so there is no way to force it on.
You can always try to swap your SATA HDD for IDE and hope that the PCI lock is working for that particular controller.
I just locked the AGP/PCI to 66.6/33.3 and it just didn't boot at all, black screen and monitor off so I had to reset the defaults with the jumpers.
My board CAN lock PCI but I don't know why it doesn't work.
Will a PCI controller solve my problem or what else?
Related ressources:
- Forum"AMD To Ditch Initial AM2 2x1MB On Desktop CPUs"
- Forum"Mobo Makers Provide Info On AMD Pricing Strategy"
- Forum"Dell To Sell More AMD Machines"
- Forum"Core 2 Duo May Not Launch Until September"
- Forum"All About Socket F"
- Forum"AMD Waits For 65nm To Crank Up The Megahertz"
- Forum"Socket AM2 ATHLON 64 3000+ Hits 2.735GHz"
- Forum"Real" Conroe Benches
- ForumSandisk crusier mini "crashed"
- More resources
!