Jump to content

11dayz

Members
  • Content Count

    13
  • Joined

  • Last visited

About 11dayz

  • Rank
    New Member
  1. There is a sticky on the subject for crying out loud! http://www.dfi-street.com/forum/showthread.php?t=40178
  2. Some of the settings have an affect on the stability of the CPU/RAM interface, that is on-die memory controller, so you aren't just playing with the RAM when you tweak that stuff. I was at a wall at 275 fsb on my board for a while and asked this community why this was so, since it should go to at least 350. I hadn't reached the max CPU o/c. I made sure I never went over my max memory O/C and had no errors in memtest, yet the answer was still in the DRAM settings. I didn't think that would be it, but sure enough it was there. I had set everything to auto or left it at default thinking it should be stable. It wasn't. The solution was to manually set everything to suit my hardware using the two guides I posted for reference. Now the board is stable up to those extremely high FSB clocks that are advertised. Sure it may not be the problem you are having, but since it solved my problem, I suggest to anyone o/c'ing to not leave the settings at auto and to not use a standard "optimized" or "safe" set, as these may not be the most stable settings for your hardware. It would be best to figure out the best settings for you
  3. I would suspect the optimized defaults are not suitable for you. Given the instabilities, did you try the safe settings? I would go into the DRAM settings and set the parameters such that it is tailored to your set up and not some generic "optimized" setup. From what I hear, setting the following will gives the best stability: Max Async Latency - 8.0 Nano Seconds Read Preamble Time - 5.5 Nano Seconds For the rest, look here: DFI NF4 BIOS Memory Guide and here Optimized A64 Memory Timings Guide Just my thoughts. Good luck.
  4. Unless you keep it 30 C in your house, I think your idle temperature is high, even for the stock HSF. If your extra fan doesn't help, I would reseat the HSF. If you didn't do it already, scrape off the thermal crud that was on the stock heat sink and use some Artic Silver or a similar quality paste. The overclocking guide explains the vid special control. You really should read it closely to get the most out of the board and CPU. I have been tweaking this system for about 3 weeks and I'm sure there are still things I can tweak. You have the same memory (I found max at advertised timings to be 210 MHz) and CPU stepping (which is apparently a bad one) as I do so below are the settings that got me the most from the CPU as of yet, maybe it will save you some time. Your mileage may vary, of course. Genie BIOS Settings: FSB Bus Frequency - 280 LDT/FSB Frequency Ratio - 3 CPU/FSB Frequency Ratio - 9 PCI eXpress Frequency - 102Mhz CPU VID StartUp Value - 1.5v CPU VID Control - 1.5v CPU VID Special Control - Auto LDT Voltage Control - 1.40v Chip Set Voltage Control - 1.70v DRAM Voltage Control - 2.70v DRAM Configuration Settings: DRAM Frequency Set - 140=RAM/FSB:07/10 Command Per Clock (CPC) - Enable CAS Latency Control (Tcl) - 2.5 RAS# to CAS# delay (Trcd) - 03 Bus Clocks Min RAS# active time (Tras) - 06 Bus Clocks Row precharge time (Trp) - 03 Bus Clocks Row Cycle time (Trc) - 09 Bus Clocks Row refresh cyc time (Trfc) - 13 Bus Clocks Row to Row delay (Trrd) - 02 Bus Clocks Write recovery time (Twr) - 03 Bus Clocks Write to Read delay (Twtr) - 02 Bus Clocks Read to Write delay (Trwt) - 02 Bus Clocks Refresh Period (Tref) - 2048 Cycles Write CAS Latency (Twcl) - Auto DRAM Bank Interleave - Enabled DQS Skew Control - Auto DQS Skew Value - 0 DRAM Drive Strength - Normal 2 DRAM Data Drive Strength - Level 2 Max Async Latency - 8.0 Nano Seconds DRAM Response Time - Normal Read Preamble Time - 5.5 Nano Seconds IdleCycle Limit - 64 Cycles Dynamic Counter - Enable R/W Queue Bypass - 16 x Bypass Max - 07 x 32 Byte Granularity - Disable(4 Bursts) Good luck
  5. Sorry to hear that, but it mirrors my experience so I guess this stepping blows. I lost p95 stability on core 0 at about 2450. Even though it is not according to Hoyle "stable" I run it at 2520 because it is 3dmark loop stable and I really only stress the computer while gaming. I guess I'll just overvolt it and burn it out so I have an excuse to get a new CPU
  6. I'll be interested to hear the results. Good luck 25 Idle, 40 Load typically. It varies by a couple degrees as I micromanage my A/C to offset electric bill rate hikes :mad: Load temps got up to 44 when I tried 1.65v just to see if I could get higher. At that voltage I could get into windows at 2.6 but superPi would error out.
  7. I haven't heard of any problems with CPU-Z like this. It is consistent with a 9/10 divider like Timmay said. Just check the frequency using a different program (Everest or Sandra or whatever) and you can eliminate CPU-Z being the problem. Get A64 Tweaker and you can confirm what your divider is once you are in Windows.
  8. 2520 (280x9 @ 1.5v) Stepping CCBWE 0607UPGW I'm pretty dissappointed with mine. Haven't seen many people with the same stepping either, so I can't compare. Genie BIOS Settings: FSB Bus Frequency - 280 LDT/FSB Frequency Ratio - 3 CPU/FSB Frequency Ratio - 9 PCI eXpress Frequency - 102Mhz CPU VID StartUp Value - 1.5v CPU VID Control - 1.5v CPU VID Special Control - Auto LDT Voltage Control - 1.40v Chip Set Voltage Control - 1.70v DRAM Voltage Control - 2.70v DRAM Configuration Settings: DRAM Frequency Set - 140=RAM/FSB:07/10 Command Per Clock (CPC) - Enable CAS Latency Control (Tcl) - 2.5 RAS# to CAS# delay (Trcd) - 03 Bus Clocks Min RAS# active time (Tras) - 06 Bus Clocks Row precharge time (Trp) - 03 Bus Clocks Row Cycle time (Trc) - 09 Bus Clocks Row refresh cyc time (Trfc) - 13 Bus Clocks Row to Row delay (Trrd) - 02 Bus Clocks Write recovery time (Twr) - 03 Bus Clocks Write to Read delay (Twtr) - 02 Bus Clocks Read to Write delay (Trwt) - 02 Bus Clocks Refresh Period (Tref) - 2048 Cycles Write CAS Latency (Twcl) - Auto DRAM Bank Interleave - Enabled DQS Skew Control - Auto DQS Skew Value - 0 DRAM Drive Strength - Normal 1 DRAM Data Drive Strength - Level 1 Max Async Latency - 8.0 Nano Seconds DRAM Response Time - Normal Read Preamble Time - 5.5 Nano Seconds IdleCycle Limit - 64 Cycles Dynamic Counter - Enable R/W Queue Bypass - 16 x Bypass Max - 07 x 32 Byte Granularity - Disable(4 Bursts)
  9. I use the 140 and it doesn't show up for me either.
  10. Thanks a bunch! I went in and set the timings and I am now up to 290 on the fsb and still climbing. Damn you Auto setting! I appreciate the inputs
  11. Excellent. I have something to go on. I didn't think the memory settings would be a factor if I left them at default when I knew my max Mem O/C at default. I'll try tweaking them and manually setting them. I do notice that you (Monty312) have a similar setup as I do, and your overclock is lower than I would expect. Why are you at 2403 MHz? Don't want to go over stock voltage? *edit* I only ask because I would like to know if there was a similar circumstance holding you back as when I was oc'ing. I had to bump up the Vcore at about 2.2Ghz
  12. I was hoping to avoid having to get into those parameters, but I will certainly read up on them and start messing with them. I appreciate the advice. I was hoping I was doing something obviously stupid, so if anyone else has any ideas, please let me know
  13. I am trying to provide as much info as I can so don't get scared by the long post I have been tweaking this system for about a week and feel I have hit a wall. I found my max RAM O/C to be 209 at default settings, so I always use the divider to keep the RAM frequency below this value. To find the CPU max, I kept the CPU multi at default (9x) and, using the dividers, kept the RAM below spec (200 MHz) as I raised the FSB. I got to 277, giving me 2492 MHz, and things were not stable enough to continue. So I thought I was one of the unlucky ones that got a poor overclocking Opty 165. I then decided to see how far the board would go and dropped the multi down to 8. Again, keeping the RAM below spec, I went to keep raising the FSB to see what the board is capable of. To my suprise, I could not go any higher on the FSB. So even at 278x8=2224 MHz, I could not get stability once windows loaded. It appears to me that I may have not hit the limit of the CPU, but rather the limit of the board. I find this hard to believe since these boards typically get into the 350's at least, which is why I bought it. So I am here to seek any thoughts as to what I may be doing wrong. Here are my settings: HTT Ratio = Auto Cool & Quiet = Disabled CPU VID Startup = 1.5 CPU VID Control = 1.5 CPU VID Special = Auto LDT Volt = 1.4 Chipset Volt = 1.8 DRAM Volt = 2.6 DRAM .03v = Disable Again RAM Timings and settings are kept at Auto/Default, with the only thing I change being the divider. Temps @ load CPU=39, PWMIC=54, Chipset=46 Things I have tried with no success -Raising/Lowering CPU VID -Raising/Lowering LDT Volt -Raising/Lowering chipset Volt -Raising/Lowering RAM volt -Manually setting HTT Multi to 3 -Manually setting RAM Command Rate to 2T (RAM default 1T) -Manually setting RAM CAS to 3 -BIOS N4d623-2
×
×
  • Create New...