F5F Stay Refreshed Power Users Overclocking Adjusting the CPU speed beyond its maximum supported limit while using 1333fsb on a compatible board

Adjusting the CPU speed beyond its maximum supported limit while using 1333fsb on a compatible board

Adjusting the CPU speed beyond its maximum supported limit while using 1333fsb on a compatible board

Pages (3): Previous 1 2 3 Next
T
Tuetme
Senior Member
418
02-08-2016, 05:47 PM
#11
First install CPU-Z and launch it, then inform me about the details under Clocks Core EX. The core speed is 4.3, multiplier x16, bus speed 270 Mhz, rated FSB 1080 Mhz. It's possible to adjust DRAM speed to 667 by setting rated timings for all RAM sticks in CPU-Z. I have done this before and it worked well. In CPU-Z's SPD section you can view which timing corresponds to each frequency, allowing you to determine compatible timings for all RAM models.
T
Tuetme
02-08-2016, 05:47 PM #11

First install CPU-Z and launch it, then inform me about the details under Clocks Core EX. The core speed is 4.3, multiplier x16, bus speed 270 Mhz, rated FSB 1080 Mhz. It's possible to adjust DRAM speed to 667 by setting rated timings for all RAM sticks in CPU-Z. I have done this before and it worked well. In CPU-Z's SPD section you can view which timing corresponds to each frequency, allowing you to determine compatible timings for all RAM models.

B
Bioshine
Member
62
02-09-2016, 07:15 AM
#12
If I have to replace the 2x1gb 566mhz ram, but still wonder about the CPU performance, especially with the low-end MBFS. Is it feasible to increase the FSB speed to 1333 from 1066? Thanks for the question—I'm not very experienced with overclocking.
B
Bioshine
02-09-2016, 07:15 AM #12

If I have to replace the 2x1gb 566mhz ram, but still wonder about the CPU performance, especially with the low-end MBFS. Is it feasible to increase the FSB speed to 1333 from 1066? Thanks for the question—I'm not very experienced with overclocking.

M
Maxdog_10
Junior Member
14
02-09-2016, 03:57 PM
#13
Why not? Just let me know what you've written there.
M
Maxdog_10
02-09-2016, 03:57 PM #13

Why not? Just let me know what you've written there.

D
DapperMD
Member
153
02-10-2016, 01:44 PM
#14
First download CPU-Z and run it to check what appears under Clocks Core EX. Core speed 4.3, Multiplier x16, Bus speed 270 Mhz, Rated FSB 1080 Mhz. He mentioned he could improve performance by adjusting DRAM speed to 667 by setting the rated timings for all RAM sticks in CPU-Z. He has already done this and it worked well. In CPU-Z's SPD tab, he can see which timing corresponds to each frequency, helping him determine compatible timings for all RAM models. Sorry for being slow... I now have another issue. I upgraded the microcodes for the Xeon but sometimes access Windows is possible, other times not. He posted a new thread about this problem but hasn't received any updates yet.
D
DapperMD
02-10-2016, 01:44 PM #14

First download CPU-Z and run it to check what appears under Clocks Core EX. Core speed 4.3, Multiplier x16, Bus speed 270 Mhz, Rated FSB 1080 Mhz. He mentioned he could improve performance by adjusting DRAM speed to 667 by setting the rated timings for all RAM sticks in CPU-Z. He has already done this and it worked well. In CPU-Z's SPD tab, he can see which timing corresponds to each frequency, helping him determine compatible timings for all RAM models. Sorry for being slow... I now have another issue. I upgraded the microcodes for the Xeon but sometimes access Windows is possible, other times not. He posted a new thread about this problem but hasn't received any updates yet.

C
Cokkie77
Senior Member
556
02-21-2016, 11:28 AM
#15
Are you adjusting the BIOS code without knowing what you're doing? Have you cleared the BIOS/MCOS after updating the microcode?
C
Cokkie77
02-21-2016, 11:28 AM #15

Are you adjusting the BIOS code without knowing what you're doing? Have you cleared the BIOS/MCOS after updating the microcode?

H
hdoor20
Senior Member
477
02-21-2016, 12:56 PM
#16
Satan-IR:
If you're unsure about what you're doing, altering the BIOS code isn't a wise move. Have you reset the BIOS or cleared the CMOS after updating the microcode? I understand, but I've gone through a detailed tutorial and still faced issues. Before updating the microcode, I kept seeing a message saying a new CPU was installed, which prevented me from configuring the BIOS properly. Yes, I did that twice.
H
hdoor20
02-21-2016, 12:56 PM #16

Satan-IR:
If you're unsure about what you're doing, altering the BIOS code isn't a wise move. Have you reset the BIOS or cleared the CMOS after updating the microcode? I understand, but I've gone through a detailed tutorial and still faced issues. Before updating the microcode, I kept seeing a message saying a new CPU was installed, which prevented me from configuring the BIOS properly. Yes, I did that twice.

B
Brudora
Senior Member
726
02-21-2016, 01:23 PM
#17
LeGeNdSChaO:
Satan-IR :
Altering BIOS code without knowing what you're doing isn't a wise move. Have you reset the BIOS or cleared the CMOS after updating the microcode? I understand, but I've gone through a detailed tutorial. Before updating the microcode, I kept receiving a message saying a new CPU was installed and it prevented me from configuring the BIOS. Yes, I did that twice. Have you tried removing the CMOS battery as well? If not, give it a try.
B
Brudora
02-21-2016, 01:23 PM #17

LeGeNdSChaO:
Satan-IR :
Altering BIOS code without knowing what you're doing isn't a wise move. Have you reset the BIOS or cleared the CMOS after updating the microcode? I understand, but I've gone through a detailed tutorial. Before updating the microcode, I kept receiving a message saying a new CPU was installed and it prevented me from configuring the BIOS. Yes, I did that twice. Have you tried removing the CMOS battery as well? If not, give it a try.

J
Juky_Juk
Member
53
02-23-2016, 12:33 PM
#18
Satan-IR :
LeGeNdSChaOs :
Satan-IR :
If you're unsure about your BIOS code, altering it isn't a wise move.
Have you reset the BIOS or cleared the CMOS after updating the microcode?
I understand, but I've gone through a detailed tutorial. Before updating the microcode, I kept seeing a message saying a new CPU was installed and it blocked me from configuring the BIOS.
Yes, I did that twice.
Have you tried removing the CMOS battery? If not, give that a shot too.
In fact, I did exactly that. I didn't use the pin method.
J
Juky_Juk
02-23-2016, 12:33 PM #18

Satan-IR :
LeGeNdSChaOs :
Satan-IR :
If you're unsure about your BIOS code, altering it isn't a wise move.
Have you reset the BIOS or cleared the CMOS after updating the microcode?
I understand, but I've gone through a detailed tutorial. Before updating the microcode, I kept seeing a message saying a new CPU was installed and it blocked me from configuring the BIOS.
Yes, I did that twice.
Have you tried removing the CMOS battery? If not, give that a shot too.
In fact, I did exactly that. I didn't use the pin method.

C
Clutchman76
Junior Member
13
02-23-2016, 08:31 PM
#19
LeGeNdSChAoS :
Satan-IR :
Messing with BIOS code if you're not sure what you are doing is not a very good idea.
Have you reset BIOS or cleared CMOS after updating the microcode?
I understand, but I followed a detailed tutorial. Before updating the microcode I kept seeing a message saying a new CPU was installed and it prevented me from configuring BIOS.
Yes, I did it twice.
Have you tried removing the CMOS battery? If not, give that a go.
Actually, I did exactly that. I didn't use the pins method.
Turn off the device, unplug it from the wall outlet, hold the power button for 15-20 seconds to discharge the capacitors, then remove the battery, touch the pins briefly for 10-15 seconds, reinsert the battery, and plug it back in to power up.
C
Clutchman76
02-23-2016, 08:31 PM #19

LeGeNdSChAoS :
Satan-IR :
Messing with BIOS code if you're not sure what you are doing is not a very good idea.
Have you reset BIOS or cleared CMOS after updating the microcode?
I understand, but I followed a detailed tutorial. Before updating the microcode I kept seeing a message saying a new CPU was installed and it prevented me from configuring BIOS.
Yes, I did it twice.
Have you tried removing the CMOS battery? If not, give that a go.
Actually, I did exactly that. I didn't use the pins method.
Turn off the device, unplug it from the wall outlet, hold the power button for 15-20 seconds to discharge the capacitors, then remove the battery, touch the pins briefly for 10-15 seconds, reinsert the battery, and plug it back in to power up.

I
ImDaMan123
Member
68
02-28-2016, 06:16 AM
#20
Satan-IR :
LeGeNdSChAoS :
Satan-IR :
LeGeNdSChAoS :
Messing with BIOS code if you're not sure what you are doing is not a very good idea.
Have you reset BIOS or cleared CMOS after updating the microcode?
I understand, but I followed a detailed tutorial. Before updating the microcode I kept seeing a message saying a new CPU was installed and it prevented me from configuring bios.
Yes, I did. Even twice.
Have you tried removing the CMOS battery? If not, give that a go.
In fact, I did exactly that. I didn't use the pins method.
Turn off the device, unplug it from the wall outlet, hold the power button for 15-20 seconds to discharge the capacitors, then remove the battery, touch the pins briefly for 10-15 seconds, reinsert the battery, plug it back in and start it up.
Just tried it. Same outcome.
I
ImDaMan123
02-28-2016, 06:16 AM #20

Satan-IR :
LeGeNdSChAoS :
Satan-IR :
LeGeNdSChAoS :
Messing with BIOS code if you're not sure what you are doing is not a very good idea.
Have you reset BIOS or cleared CMOS after updating the microcode?
I understand, but I followed a detailed tutorial. Before updating the microcode I kept seeing a message saying a new CPU was installed and it prevented me from configuring bios.
Yes, I did. Even twice.
Have you tried removing the CMOS battery? If not, give that a go.
In fact, I did exactly that. I didn't use the pins method.
Turn off the device, unplug it from the wall outlet, hold the power button for 15-20 seconds to discharge the capacitors, then remove the battery, touch the pins briefly for 10-15 seconds, reinsert the battery, plug it back in and start it up.
Just tried it. Same outcome.

Pages (3): Previous 1 2 3 Next