• Welcome to Overclockers Forums! Join us to reply in threads, receive reduced ads, and to customize your site experience!

Need help overclocking please

Overclockers is supported by our readers. When you click a link to make a purchase, we may earn a commission. Learn More.
As i raise cpu frequency to 210 my memory clock changes to 420/840 560/1120 700/1400 840/1680
Should i choose 560/1120?
 
Leave the memory clock alone for now. It's just reflecting that the memory frequency rises with the CPU frequency increase and the various "dividers" as we call them will all change. The CPU Frequency is the master system bus and the other bus frequencies are tuned to it. I think I explained that in an earlier post and now you see it working out in real life. Eventually, I hope to get the CPU Frequency bus high enough that the memory speed is back up to around it's full 1333 MHz rated speed.
 
Keep going. Add 10 MHz increments until you can't pass the stress test and then backup 5 MHz and retest. Post back with pics of HWMonitor that reflect max temps for the last successfully run stress test.

I also need you to (along with HWMonitor) post pics of CPU-z tabs: CPU, Memory and SPD. I cannot tell where your frequencies are if you don't.

Temps look real good so far.
 
2nd test:
 

Attachments

  • Untitled-2.jpg
    Untitled-2.jpg
    231.1 KB · Views: 80
  • Untitled-1.jpg
    Untitled-1.jpg
    141.1 KB · Views: 94
3rd test :
 

Attachments

  • Screenshot_1.png
    Screenshot_1.png
    19.6 KB · Views: 88
  • Screenshot_2.png
    Screenshot_2.png
    47.6 KB · Views: 55
  • Screenshot_3.png
    Screenshot_3.png
    16.9 KB · Views: 69
  • Screenshot_5.png
    Screenshot_5.png
    71.7 KB · Views: 91
  • Screenshot_4.png
    Screenshot_4.png
    17.1 KB · Views: 59
Keep going. No need to post after every increase increment. Just when you fail the stress test so we can look at the frequencies and voltages to figure out what adjustments might help.
 
what do you think should i go further?
 

Attachments

  • Screenshot_1.png
    Screenshot_1.png
    21.5 KB · Views: 69
  • Screenshot_2.png
    Screenshot_2.png
    15.1 KB · Views: 69
  • Screenshot_3.png
    Screenshot_3.png
    21 KB · Views: 56
  • Screenshot_4.png
    Screenshot_4.png
    19.5 KB · Views: 51
  • Screenshot_6.png
    Screenshot_6.png
    67.7 KB · Views: 105
Go as far as you can go until you fail the stress test. Cut back to 5 MHz increase increments now. Soon, we will need to give attention to your memory timings as they are looking too tight for the frequency. I've got to be somewhere. I'll check this later tonight.
 
at this point i've got a bluescreen (as soon as i started prime to test - bump bluescreen).
 

Attachments

  • Screenshot_3.png
    Screenshot_3.png
    17.5 KB · Views: 53
  • Screenshot_2.png
    Screenshot_2.png
    16.5 KB · Views: 55
  • Screenshot_1.png
    Screenshot_1.png
    19.4 KB · Views: 58
  • Screenshot_4.png
    Screenshot_4.png
    17.2 KB · Views: 58
  • Screenshot_6.png
    Screenshot_6.png
    29.9 KB · Views: 79
Not real surprised that you have a quick BSOD.
1. Your DDR3-1333 ram is running at DDR3-1441

2. Your ram timings at DDR3-1333 are supposed to be 9, 9, 9, 24, 33
but you have them at the faster overclocked speed set to 8, 8, 8, 20, 27 and 1T where 2T
is often easeir with AMD setups. My mobo actually shows faster at 2T in MaxMem.

3. So you need to at least loosen the timings to the recommended settings and REtest.
The ram may not lke the DDR3-1441 speed, but it might do it with the more correct timings.

4. I also notice the HT Link speed is up to 2161.47Mhz and that might be too high for that Deneb processor.
Some don't like to be overclocked much over their 2,000Mhz default speed.

5. And if you are going to run 2431.7Mhz for the CPU_NB speed, you may need to raise the
CPU_NB voltage into the 1.25V range or sometimes even a little more.
RGone...
 
RGone, I think he already increased the NB voltage to 1.25 according to my earlier instruction. But you and I are thinking along the same lines about the memory and the timings as you can see from post #29.

So, gorgeto, cut the FSB back from 270 to 260 and retest not for 20 minutes but for two hours. Report back with results. If you can pass that long Prime95 stress test then we can consider you stable. If not but it runs for 20 minutes or so then you are almost stable and just need some minor tweaking.
 
RGone, I think he already increased the NB voltage to 1.25 according to my earlier instruction. But you and I are thinking along the same lines about the memory and the timings as you can see from post #29.

Yes, and why I double stamped it. He did not change it when you mentioned it but went ahead and upped the FSB and thus the speed. Seeing such is why I mentioned the CPU_NB, since I have no actual idea he upped it per previous.

Oh well. Such is life at times.

Have a good Sunday "trents".
RGone...
 
After running prime for 1h and 10min i got a bluescreen at 260 fsb - testing now at 250 fsb for 2h.
 
Hold on there! If you could run Prime95 for over an hour it may not be necessary to reduce the fsb at all. Both RGone and I think you need to address your memory timings.

Please put the fsb back to 260 and then post pics of CUP-z tabs: CPU, Memory and SPD and tell us what were the temps under load for the core and CPUTIN at 260 MHz fsb. Don't assume the problem is that the fsb is too high for the CPU. It could be the memory timings or it could be temps are the real problem.
 
Last edited:
this is at 260fsb and i think the cputin Value was around 52 i don't remember the min and the max value.
 

Attachments

  • Screenshot_1.png
    Screenshot_1.png
    18.9 KB · Views: 52
  • Screenshot_2.png
    Screenshot_2.png
    15.6 KB · Views: 39
  • Screenshot_3.png
    Screenshot_3.png
    19 KB · Views: 36
  • Screenshot_4.png
    Screenshot_4.png
    18.6 KB · Views: 36
Go into Memory Timing in bios and change these values to what you see in the column labeled JEDEC #4 with the addition of making the Command Rate (CR) 2T instead of 1T. You will see many more timings listed in bios than what you see in CPU-z but only concern yourself with the ones listed in CPU-z. Leave the others on Auto. If the terminology differs between your bios and CPU-z keep in mind that most of these values you need to change occur near the top of the list in bios with the exception of CR which is down toward the bottom. If you are not sure that you have made changes to the correct items then make the change and boot back into Windows where you can see the CPU-z memory tab and look at the values there to see if what you wanted to change actually got changed. Then retest at fsb of 260 mhz. Oh, also lower the HT Link from 8x to 7x. Note: The Memory tab of CPU-z shows what your frequency and timing values are currently set to in bios. The SPD tab shows what the memory manufacturer recommends.
 

Attachments

  • Memory.PNG
    Memory.PNG
    29.2 KB · Views: 53
this is what i did as you said but after 20 min of prime test i got BSOD
any suggestions?
 

Attachments

  • Screenshot_1.png
    Screenshot_1.png
    16.9 KB · Views: 40
  • Screenshot_2.png
    Screenshot_2.png
    21.9 KB · Views: 26
  • Screenshot_3.png
    Screenshot_3.png
    18.9 KB · Views: 27
  • Screenshot_5.png
    Screenshot_5.png
    20.2 KB · Views: 24
What does HWMonitor show as the max vcore you are seeing under load? My advice at this point would be to add a small amount of vcore but I don't want you to exceed 1.5v under load. Your motherboard seems to be adding a hefty amount of offset to whatever you declare the CPU vcore to be in bios.

The other thing I would suggest is that you reduce FSB to 255 MHz and retest if vcore is already too high to allow adding more.

I also noticed that you are running 12gb of ram. What programs are you running that make that much ram an asset? Photoshop? CAD? Audio/Video editing/rendering? That much ram is going to be putting extra strain on the IMC of the CPU (IMC=Integrated Memory Controller).
 
Yes i have installed Kingston 4 GB DDR3 PC3-10700(667mhz) (2x) - of them
Apacer 2 GB DDR3 PC3-10700H(667mhz) (2x) - of them - i'm running programs for music production that why i need that much ram memory :)
 
Back