Thread: Overclock E8500 voltages etc

I test a little of my intel E8500 oc. I use SetFSB. Beyond about 370mhz for the FSB (which puts Proco @ 3515mhz), I am entitled to an error message and the pc freezes. I just watched my tensions and the CPU is powered 1.136v on average, according to cpu-z. It is a normal value? To about 3.8GHz (my goal level for starters), I must increase this value. It must be performed by the bios or there is dedicated software? Finally, what value I put about to reach 3.8GHz without heating up the cpu? Incidentally, I have a pretty tower type cooler.

Well then, in my opinion this is not a voltage problem, but rather a memory problem, then I'm just guessing, because I know the rest of your config, but that seems the most coherent. Could you give us the rest of your config (especially: Motherboard and ram)?

After Me, I can only discourage you to use SetFSB if you access the BIOS and you have access to editable and values needed for overclocking.

So actually it should not be the ram, windows which are just boring.

Okay so I advise you to go into your BIOS, you put the FSB to 370 (as you say you blocked at this frequency), normally you should have nothing else to touch.
Check that your ram is 1:1.

With that, it should start, launching a small gender 10min OCCT to see if there are no worries, and monitor your temperature, do not (well should be avoided) it exceeds 80 ° C.

With a fsb of 400, some CM did not even need to increase the voltage of the chipset (the P45 was not even scared).

Well after like the others sync to 1:1 and increase the vcore with fsb termination voltage ...
The CPU PLL did you even really need to touch it!

I advise you to OC from the BIOS, it will avoid you some inconvenience. To achieve the desired voltage you will need to test your chipset, 4Gh = 450 (approximately) FSB, your RAM out of sync at the bottom and do the same for your coef rises and your FSB until unstable, then increases its voltage and so on until you find the maximum frequency that you could afford.Then test your RAM in the same way, and then passes Proco. This way of OC can identify more quickly or is the problem of instability.

There may be something possible with sort () php actually. In place of having an ORDER BY in my SQL query, I FETCH it into another sort () and then I post with ECHO!

There is a similar example on the PHP website (the link you gave me). The example explains how to sort alphabetically by names of people with 3 fields (first name, middle name and last name) where the second name does not exist.

If you want to correctly sort your IP do not store in the form of strings? Either you go to the barbarian with a field type INT unsigned ip containing 4 bytes. The advantage is that you can sort with a whole procedure is precisely because of numbers.

Either you go to the barbarian bis 4 fields with TINYINT (1 byte = 255 max values) containing 4 numbers associated with your IP. Your sort is by simply doing ORDER BY Ip1, ..., IP4.