Basic overclocking guide

Bm4n

This post is being processed/translated. The original version will be shown:

Bueno esto ya prácticamente está, se admiten sugerencias. Si queréis fijarlo, quizás se pueden quitar otras cosas antiguas como lo de los A64 o hacer una base de datos global de OC para no tenerlo separado en varias ramas.

Nemo

This post is being processed/translated. The original version will be shown:

Buen trabajo, mucho mejor con fotitos donde va a parar…

krampak

This post is being processed/translated. The original version will be shown:

La mayoría de los conceptos están en mi guia que desfijé cuando jordiqui colgó su guia sobre OC en i7 (al contener conceptos similares pero más modernos). No se que tal lo ves, alguna sugerencia de cómo unificar el tema ?

Bm4n

This post is being processed/translated. The original version will be shown:

Yo más que nada la he hecho para que sea algo neutro, que no hable de como hacer OC a un CPU especifico que para eso ya están las que hay por ejemplo la del i7. Pero cuando uno no tienen ni idea no necesita que le digan valores específicos porque sino no aprendes nada, necesitas conocer la base, y luego ya ponerte a exprimir al máximo el CPU mirando los valores que les van bien a otros.

Yo dejaría fijadas las ramas de OC a CPUs actuales como el i7 y quitaría temas que hablen de procesadores antiguos, y las bases de datos las metería todas en una, una lista con CPUs y valores que cada forero pueda poner sus datos y añadir a la lista.

Por ejemplo, algo sencillo:
http://foro.hardlimit.com/overclock/t-base-de-datos-global-de-overclock-en-hl-60577.html

Incluso se puede dar permiso a todos los veteranos para que podamos trabajar en una misma lista, si quieres creo el post

etgasu

post from 2003, well thanks bm4n, I'm a newbie if knowledge but it helped me a lot this post thanks:)

defaultuser

@Bm4n:

I've made it mostly neutral, so it doesn't talk about how to OC a specific CPU, because for that there are already guides, like the one for the i7. But when you have no idea, you don't need specific values because otherwise you don't learn anything, you need to know the basics, and then you can start squeezing the most out of the CPU by looking at the values that work well for others.

I would leave the OC branches set for current CPUs like the i7 and remove topics about old processors, and put all the databases into one, a list with CPUs and values that each forum member can add their data to and add to the list.

For example, something simple:
Global overclock database in HL - HardLimit

You can even give permission to all the veterans so we can work on the same list, if you want I'll create the post

Just kidding :risitas:
The best way to help someone is to teach them to help themselves

The forum really needed a neutral guide, explaining the basics, and as brief as possible.
Then it would be interesting if in each section of the guide there was a link to deeper and more specific guides, but this guide would remain brief, concise, and focused on the basics (frequency ratios, buses, etc.)

The reason for this guide is self-explanatory; the impatient ones, the ones who think they should be explained everything, the ones who want it all chewed up but still listen to you and want some notions of what they're really doing.
Basically, literally everyone who comes in to ask about OC, because the others have already documented themselves first and come in to ask for details.
There will even be those who get confused in more technical and extensive guides and in this more summarized one will clear up their doubts.

I agree with what Bm4n says, let's link to OC database(s) (and by the way to the other guides).
And if you do any unification, in my opinion a guide with the profile I described would be pending.

Now I'll give you a pin Bm4n

Salu2.

PD:
Oops, it looks like I put the last pin on you and it won't let you repeat it... I'll have to look for another candidate more

Bm4n

Thank you very much, I'm glad it's helpful although I think it's time for a new, more advanced version. When I have some time, I'll get to it

etgasu

:sisi::sisi:

cxvdssdhj