stupid question?
- Thread starter nicnac1
- Start date
Good stuff there! 
Get into BIOS and Load Optimised Defaults then save & exit, back into BIOS and disable the advanced CPU options like we did before, save & exit.
Get your memory running at DDR2-1066 again and make sure thats all fine, if so push back to 333MHz-FSB/1066MHz System Bus and see if any new memory dividers are possible?
At 9x333/3.0GHz peek at the vCore and see of it still reads the same as before also check load temps.
If you can't get the memory running at DDR2-1066 in conjunction with a 1333MHz System Bus then select one of the other memory multis. You went for DDR2-1000 before which is fine but you could also try the DDR2-1100 option!
Have a snoop through the BIOS and let me know if there is anything changed, new options, layout etc . . . .
Get into BIOS and Load Optimised Defaults then save & exit, back into BIOS and disable the advanced CPU options like we did before, save & exit.
Get your memory running at DDR2-1066 again and make sure thats all fine, if so push back to 333MHz-FSB/1066MHz System Bus and see if any new memory dividers are possible?
At 9x333/3.0GHz peek at the vCore and see of it still reads the same as before also check load temps.
If you can't get the memory running at DDR2-1066 in conjunction with a 1333MHz System Bus then select one of the other memory multis. You went for DDR2-1000 before which is fine but you could also try the DDR2-1100 option!
Have a snoop through the BIOS and let me know if there is anything changed, new options, layout etc . . . .
evening
Right, had a flick through the new bios and i can honestly say that i can see no difference except it is displaying version 17! lol
1066 still isn't available so i tried running prime95 with the memory at DDR2-1100 and it crashed so i'm guessing it's not up for that at the moment!
got the memory back to 1004MHz and ran prime95/couple of games at the settings above and got the following results
vcore idle - 1.300
vcore load - 1.270
temp idle - 42C
temp load - 60C (tuniq tower fan at 50%)
memory - 1004MHz
so far so good
Right, had a flick through the new bios and i can honestly say that i can see no difference except it is displaying version 17! lol
1066 still isn't available so i tried running prime95 with the memory at DDR2-1100 and it crashed so i'm guessing it's not up for that at the moment!
got the memory back to 1004MHz and ran prime95/couple of games at the settings above and got the following results
vcore idle - 1.300
vcore load - 1.270
temp idle - 42C
temp load - 60C (tuniq tower fan at 50%)
memory - 1004MHz
so far so good
Evening nicnac1,
when you run your memory at DDR2-1100 did you leave the vDimm on [Auto]? The Kingston HyperX I have here runs 550MHz (DDR2-1100) with the vDimm set manually to [1.82v]. If you left the Ram voltage on [Auto] and prime crashed there is a slight chance the sticks are maybe over-volting and running to warm? (are they warm?) anyways thats something you can come back too, just wanted to let you know to get some ram voltage testing in when you can as we may need some memory that can run 550MHz
Anyways we got work to do, no particular order so the first thing to try is restart computer, into BIOS and change the FSB from 333MHz to 355MHz leaving everything else as it is, save & exit.
That should get you roughly 3.2GHz on the CPU and get your Memory running at full 533Mhz speed (DDR2-1066).
Very simple start, can you confirm it works!
when you run your memory at DDR2-1100 did you leave the vDimm on [Auto]? The Kingston HyperX I have here runs 550MHz (DDR2-1100) with the vDimm set manually to [1.82v]. If you left the Ram voltage on [Auto] and prime crashed there is a slight chance the sticks are maybe over-volting and running to warm? (are they warm?) anyways thats something you can come back too, just wanted to let you know to get some ram voltage testing in when you can as we may need some memory that can run 550MHz
Anyways we got work to do, no particular order so the first thing to try is restart computer, into BIOS and change the FSB from 333MHz to 355MHz leaving everything else as it is, save & exit.
That should get you roughly 3.2GHz on the CPU and get your Memory running at full 533Mhz speed (DDR2-1066).
Very simple start, can you confirm it works!
Good good!
You may wanna have a little time 30-60mins to confirm thats all good, make sure you reboot the PC a few times to see that it POSTs fine and also switch the PC off fully and unplug it from the mains, wait a few seconds and power up, this is because the POST can sometimes go fubar and the reboots and full power off help to confirm everything is good so far . . .as well as a bit of Prime in Windows and a few games apps etc, your just getting a feel for things, the PC should be bitchin fast where you are now (3.2GHz CPU/1420MHz System-Bus/DDR2-1066 Memory) but theres more!
You may wanna have a little time 30-60mins to confirm thats all good, make sure you reboot the PC a few times to see that it POSTs fine and also switch the PC off fully and unplug it from the mains, wait a few seconds and power up, this is because the POST can sometimes go fubar and the reboots and full power off help to confirm everything is good so far . . .as well as a bit of Prime in Windows and a few games apps etc, your just getting a feel for things, the PC should be bitchin fast where you are now (3.2GHz CPU/1420MHz System-Bus/DDR2-1066 Memory) but theres more!
Last edited:
Ok just to clarify, the cold-boot test isn't meant to be done after a blue screen, its a test by itself when you think everything is hunky dory.
If you back in windows now at 3.0GHz (9x333) with Memory at 500MHz (DDR2-1000) then thats good, if you got a PC that won't load windows thats bad!
I'd also like to mention there is an outside chance that during these overclocking tests we may balls up Windows so it wont load. Most peeps who like an easy life have a full current backup of their O/S drive so if it gets borked then can do a Restore in like 10mins.
You don't risk damaging the drive itself but the data could go gaga!
If you are using just a single hard disk with your O/S and data all crammed in then we may need to tread carefully. Whats the deal? do you have all your data (My Documents etc) living on a second drive? Have you got any backup software that loads up from a CD-ROM/Optical?
If you back in windows now at 3.0GHz (9x333) with Memory at 500MHz (DDR2-1000) then thats good, if you got a PC that won't load windows thats bad!
I'd also like to mention there is an outside chance that during these overclocking tests we may balls up Windows so it wont load. Most peeps who like an easy life have a full current backup of their O/S drive so if it gets borked then can do a Restore in like 10mins.
You don't risk damaging the drive itself but the data could go gaga!
If you are using just a single hard disk with your O/S and data all crammed in then we may need to tread carefully. Whats the deal? do you have all your data (My Documents etc) living on a second drive? Have you got any backup software that loads up from a CD-ROM/Optical?
While you working away I'll let you know whats next!
first go into BIOS and change the memory divider so its running 1:1 sync (i.e the same speed as the FSB so if 333MHz-FSB then select DDR2-666) then save & exit then back into BIOS and select the same 355MHz-FSB as you did before and let me know if the PC blue screens again. The difference this time around is we are reducing the strain on the Northbridge by slowing the memory down [1:1/710MHz] instead of [3:2/1066MHz]
On the outside chance that works fine (3.2GHz CPU/1420MHz System Bus/DDR2 710) then reboot back into BIOS and drop the Multiplier down from [x9] to [x6] save & exit and cross your fingers as you will now be running your NBCC at 533MHz. good luck!
first go into BIOS and change the memory divider so its running 1:1 sync (i.e the same speed as the FSB so if 333MHz-FSB then select DDR2-666) then save & exit then back into BIOS and select the same 355MHz-FSB as you did before and let me know if the PC blue screens again. The difference this time around is we are reducing the strain on the Northbridge by slowing the memory down [1:1/710MHz] instead of [3:2/1066MHz]
On the outside chance that works fine (3.2GHz CPU/1420MHz System Bus/DDR2 710) then reboot back into BIOS and drop the Multiplier down from [x9] to [x6] save & exit and cross your fingers as you will now be running your NBCC at 533MHz. good luck!
Last edited:
/While we’re having a short interlude...
This is fast becoming a definitive guide.
Nicnac1, you struck overclocking gold – regardless of the outcome...
Big.Wayne, once this thread has completed its course you should compile your entries and edit them, accordingly, into the above format as you will have, essentially, written the very ‘comprehensive guide’ that you feel is lacking from these boards.
You will have done all the grunt work by the time the thread has run its course and it will only need minor amendments/appendages for other setups.
I’ve never read a more comprehensive walk through. Your articulate attention to detail is a real asset in this kind of instruction/guide and, as such, should be compiled and edited for a sticky. (Obviously, reposted as a dedicated thread of its own.)
You may disagree, but before you do, i would re-read what you have written to date and what you anticipate writing in your next few replies. Even you, modesty permitting, will realise that this would be a missed opportunity if this thread’s contents were to disappear?!
It would still require quite a bit of work to get it flowing into one continuous guide but it’s worth it – what do you reckon?
Here endeth the sermon...
This is fast becoming a definitive guide.
Nicnac1, you struck overclocking gold – regardless of the outcome...
I feel bad that after three years people on OcUK forums still have to ask these starter questions . . .there should be a complete walk-thru posted up in stage by stage moves that takes a keen nOOby right through the various steps, I supect this doesn't exist because its a lot of work and perhaps no one understands all the stages!
Big.Wayne, once this thread has completed its course you should compile your entries and edit them, accordingly, into the above format as you will have, essentially, written the very ‘comprehensive guide’ that you feel is lacking from these boards.
You will have done all the grunt work by the time the thread has run its course and it will only need minor amendments/appendages for other setups.
I’ve never read a more comprehensive walk through. Your articulate attention to detail is a real asset in this kind of instruction/guide and, as such, should be compiled and edited for a sticky. (Obviously, reposted as a dedicated thread of its own.)
You may disagree, but before you do, i would re-read what you have written to date and what you anticipate writing in your next few replies. Even you, modesty permitting, will realise that this would be a missed opportunity if this thread’s contents were to disappear?!
It would still require quite a bit of work to get it flowing into one continuous guide but it’s worth it – what do you reckon?
Here endeth the sermon...
/While we’re having a short interlude...
This is fast becoming a definitive guide.
Nicnac1, you struck overclocking gold – regardless of the outcome...
Big.Wayne, once this thread has completed its course you should compile your entries and edit them, accordingly, into the above format as you will have, essentially, written the very ‘comprehensive guide’ that you feel is lacking from these boards.
You will have done all the grunt work by the time the thread has run its course and it will only need minor amendments/appendages for other setups.
I’ve never read a more comprehensive walk through. Your articulate attention to detail is a real asset in this kind of instruction/guide and, as such, should be compiled and edited for a sticky. (Obviously, reposted as a dedicated thread of its own.)
You may disagree, but before you do, i would re-read what you have written to date and what you anticipate writing in your next few replies. Even you, modesty permitting, will realise that this would be a missed opportunity if this thread’s contents were to disappear?!
It would still require quite a bit of work to get it flowing into one continuous guide but it’s worth it – what do you reckon?
Here endeth the sermon...
+1
If i had found anything even nearly this good when i started out, then my life would have been a lot easier!
While you working away I'll let you know whats next!
first go into BIOS and change the memory divider so its running 1:1 sync (i.e the same speed as the FSB so if 333MHz-FSB then select DDR2-666) then save & exit then back into BIOS and select the same 355MHz-FSB as you did before and let me know if the PC blue screens again. The difference this time around is we are reducing the strain on the Northbridge by slowing the memory down [1:1/710MHz] instead of [3:2/1066MHz]
On the outside chance that works fine (3.2GHz CPU/1420MHz System Bus/DDR2 710) then reboot back into BIOS and drop the Multiplier down from [x9] to [x6] save & exit and cross your fingers as you will now be running your NBCC at 533MHz. good luck!
Sadly didn't boot at 355MHz @ 1:1
got to the windows logo and blue screened
got all my files backed up on an external HD and still got the vista installation disc... i'd be able to rebuild on that wouldn't i?
the voltages are still on auto, is that ok?
Interesting, although a fail it does help build up a picture of how the kit acts!
It's strange that it won't boot at 355MHz-FSB with the memory running [1:1] sync when you tried an hour ago using the faster [3:2] memory divider with the same FSB it booted fine . . . .although eventually it blue screened in Windows!
Go back to 333MHz and try again with the memory [1:1] sync (DDR2-666).
I'm just looking at the manual for your board and it seems to have a very healthy selection of voltage controls so we may need to be switching to manual over-ride quite soon!
Confirm the 333MHz-FSB with 1:1 sync while I ponder the next best step!
I also just saw what great voltage monitoring you have with that board courtesy of ABIT uGuru!
I'm interested in:
CPU Core Voltage
DDR2 Voltage
CPU VTT 1.2v Voltage
MCH 1.25v Voltage
ATX +12v (24-Pin Connector)
ATX +12v (8-Pin Connector)
I'm interested in:
CPU Core Voltage
DDR2 Voltage
CPU VTT 1.2v Voltage
MCH 1.25v Voltage
ATX +12v (24-Pin Connector)
ATX +12v (8-Pin Connector)
Ok that's as expected, so to recap
3.0GHz CPU, 333MHz-FSB (1333MHz System Bus) and 500MHz/DDR2-1000 is good
3.0GHz CPU, 333MHz-FSB (1333MHz System Bus) and 333MHz/DDR2-666 is good
3.2GHz CPU, 355MHz-FSB (1420MHz System Bus) and 533MHz/DDR1066 boots sometimes and eventually Blue screens in Windows, also sometimes doesn't go past POST
3.2GHz CPU, 355MHz-FSB (1420MHz System Bus) and 333MHz/DDR2-666 just doesn't POST?
Is that correct so far?
Ok so rebooting into BIOS can you tell me what voltage the Northbridge (MCH) is getting at the moment and tell me what the voltage options are on it from minimum to maximum? Obviously you will need to take it off [Auto] and have a read . . . .
3.0GHz CPU, 333MHz-FSB (1333MHz System Bus) and 500MHz/DDR2-1000 is good
3.0GHz CPU, 333MHz-FSB (1333MHz System Bus) and 333MHz/DDR2-666 is good
3.2GHz CPU, 355MHz-FSB (1420MHz System Bus) and 533MHz/DDR1066 boots sometimes and eventually Blue screens in Windows, also sometimes doesn't go past POST
3.2GHz CPU, 355MHz-FSB (1420MHz System Bus) and 333MHz/DDR2-666 just doesn't POST?
Is that correct so far?
Ok so rebooting into BIOS can you tell me what voltage the Northbridge (MCH) is getting at the moment and tell me what the voltage options are on it from minimum to maximum? Obviously you will need to take it off [Auto] and have a read . . . .
Yup, absolutely right... will check the MCH now