PDA

View Full Version : Problem with E6600 Or Dfi Infinity Mobo on O/C


dpoverlord
05-15-2007, 09:16 PM
Greetings,
I am really sure that my CPU E6600 Can O/C more than I have gotten it (3431.0mhz) I got it to 12 hrs Dual Orthos and 1 prime stable. The problem occurs when I raise my FSB passed 380 to 390 and higher. When I raise the FSB 390 the screen goes black with my HD's running and LED lights on. Occasionally I can reboot from this into the bios but mainly I have to CMOS Clear. I doubt the CPU is causing this so what can I do to fix the Mobo? I am using the 12/16 bios. Any help is appreciated.

Also is there a way I can test this theory by lowering the Multiplier? I still have not found a setting in the 12/06 bios that allows me to change the multi from 9 to 8 or 7. Thank you.

Also would the 2/27/07 bios or 97TID227 BIOS make a difference? I just want to really test this CPU since I have awesome cooling and it seems the board is holding me back

dpoverlord
05-16-2007, 06:14 AM
I will try that when I get home. I left the machine @ 380FSB 1.31V and the settings were:
Genie BIOS

PPM Function........................ - Enabled

CPU Clock Setting................... - 380Mhz
PCIE Clock Setting.................. - 110MHz
SATA Clock Sync. With............... - Fix 100Mhz

CPU VID Offset Setting.............. - + 100.0mV
Default CPU Voltage................. - 1.3250v
CPU VTT Voltage Setting............. - 1.20v
DRAM Voltage Setting................ - 2.10v
NB Chip Voltage Setting............. - 1.65v


DRAM Timing and Config

DRAM Timing Selectable.............. - Manual
CAS Latency Time.................... - 4
DRAM RAS# to CAS# Delay............. - 4
DRAM RAS# Precharge................. - 4
Precharge Delay (tRAS).............. - 15
System Memory Frequency............. - 533Mhz
Refresh Mode Select................. - 15.6
Write to Precharge Delay............ - Auto
Write to Read Delay (Same).......... -Auto
Write to Read Delay (Diff).......... - Auto
Read to Write Delay................. - Auto
Write Recovery...................... - Auto
Read Recovery....................... - Auto
Read Delay.......................... - Auto
Data A Drive Strength............... - 1.75
Data B Drive Strength............... - 1.75
x8 Control Drive Strength........... - 2
x16 Control Drive Strength.......... - 2
x8 Clock Drive Strength............. - 2
x16 Clock Drive Strength............ - 2
Command A Drive Strength............ - 2
Command B Drive Strength............ - 2

This is running stable so far at 8 hours when I get home it will be running round 20 hours. The computer is running 1 Orthos Stress test, 1 prime 95 and it already ran an OCCT Torture test at the same time.
The temps via Core temp are reading around 50-55C on Core 1 and Core 2 ( Smart guardian reads 65C for some reason). I also reapplied the AS5 as was suggested before via the thin line method. The only issue I may have had is that the Thermalright Ultra 120 Extreme is massive(especially with a 120mm 72cfm SIlenX fan) and while I was mounting, the heatsink still moved left and right a little as I was trying to screw it to the motherboard via the mounting plate.

I am not really sure what I could be doing wrong. I will try setting the mem to SPD? Instead of manual? Or just set everything to Auto. Maybe I should clear the CMos again and possibly flash to a bios that lets me set the Multi? What do you think?

http://img524.imageshack.us/img524/6593/20hour3431mhzll7.jpg

dpoverlord
05-16-2007, 06:26 PM
I did what was suggested and went into my bios and raised the Voltages to see if it would help in getting the mobo passed 380FSB. This is what I did:

A. CPU VID Offset Setting.............. - + 200.0mV
CPU VTT Voltage Setting............. - 1.30v
DRAM Voltage Setting................ - 2.10v
NB Chip Voltage Setting............. - 1.65v
The system hung as was seen before just a black screen when I turn on with the bios not even loading.

B. CPU VID Offset Setting.............. - + 200.0mV
CPU VTT Voltage Setting............. - 1.35v
DRAM Voltage Setting................ - 2.10v
NB Chip Voltage Setting............. - 1.7v

Same issue nothing

C.CPU VID Offset Setting.............. - + 225.0mV
CPU VTT Voltage Setting............. - 1.35v
DRAM Voltage Setting................ - 2.10v
NB Chip Voltage Setting............. - 1.75v

Most disturbing to me these are very high values for Voltages. And I am still getting no response. I am going to try loading the 2/27 bios and see if this helps I am very befuddled as to what is going on.
I even made sure I turned off all CPu enhancements PPM, then in memory everything was on auto except I set it to 400mhz and 533mhz. Any ideas?


I also changed and this reflects the same values on 12/05 and 2/27/07 bios on the DFI INfinity 975/G/X I am not sure as to what I am doing wrong is there maybe a Windows O/C method I can try. Has anyone had these issues since it does not make sense that I am hitting a wall of not being able to go over. I would at least like a shot at getting over 3.43GHZ

andyOCZ
05-17-2007, 11:20 AM
Hi, these settings are with an older BIOS, but should get you close:

http://www.ocztechnologyforum.com/forum/showpost.php?p=208107&postcount=3

Let us know if it helps.

dpoverlord
05-17-2007, 05:02 PM
I tried 4-4-4-15 and I still got a black screen what settings are you reco'ing?

andyOCZ
05-17-2007, 08:37 PM
I tried 4-4-4-15 and I still got a black screen what settings are you reco'ing?

Sorry, I'm not sure what you are asking.

Try testing each stick alone and let me know your results.

dpoverlord
05-18-2007, 06:41 AM
I tried changing the CAS timings on the ram and nothing works. I fail to understand what could be going on with this setup that it won’t even post at 381 or 382. But at 380 it does it with no problems whats so ever even when I am using a strap of 667mhz. I tried doing 1 dimm at a time as well and this made no difference. What is going on that NOTHING happens after 380. I get it to post with no issues at 380... Also, is there a way someone at ocz can tell me what settings on this ram would work the best in making the ram loose enough to accept a higher fsb?

andyOCZ
05-18-2007, 10:17 AM
I did some research and found that the older BIOS before the 12/01/06 version had sever FSB limitations. You don't list what BIOS you are running. The BIOS issue has nothing to do with memory, timings or settings.

Here is a link to DFI's BIOS page for your board: http://us.dfi.com.tw/Support/Download/bios_download_us.jsp?PRODUCT_ID=4696&CATEGORY_TYPE=LP&STATUS_FLAG=A&SITE=US

It takes a while to load, so be patient.

Let me know how it goes.

dpoverlord
05-18-2007, 12:08 PM
I did some research and found that the older BIOS before the 12/01/06 version had sever FSB limitations. You don't list what BIOS you are running. The BIOS issue has nothing to do with memory, timings or settings.

Here is a link to DFI's BIOS page for your board: http://us.dfi.com.tw/Support/Download/bios_download_us.jsp?PRODUCT_ID=4696&CATEGORY_TYPE=LP&STATUS_FLAG=A&SITE=US

It takes a while to load, so be patient.

Let me know how it goes.

I dont understand what your referring to.
My bios is listed in my signature. It reads 12/06, currently though I am using the 2/27/07 bios since I felt it may help me get it passed 380FSB. What are you reco'ing me doing?

Praz
05-18-2007, 12:45 PM
Try a different processor and see if the issue remains. The memory is not the problem.

andyOCZ
05-18-2007, 01:40 PM
I didn't read all the way to the bottom to see your BIOS rev.

I would love to help you, but many factors will stop your overclocking. It could be your CPU as it must be able to hit the FSB. You should be able to run the memory at rated speed and keep you FSB low with proper settings.

You should head over to the DFI forums and see if you can get help. The only info I have is what I linked you to above. Sorry!

dpoverlord
05-21-2007, 07:02 AM
Why would it be the CPU though? If it hits 380 with no issues wouldnt it at least post @ 385 to 390 and just give me a BSOD?

andyOCZ
05-21-2007, 03:47 PM
Why would it be the CPU though? If it hits 380 with no issues wouldnt it at least post @ 385 to 390 and just give me a BSOD?

Your CPU can give a BSOD just like memory can. Your chipset might even be the problem and cause a BSOD.

If you use a lower memory divider, your memory is running at a lower "FSB" than your CPU. If you have the memory set lower and you get a BSOD, it's not your memory causing it.

Since I don't have you and your system here in front of me, it's difficult to teach you how to find your CPU maximum. you chipset maximum and memory maximum overclocks. There are many very good overclocking guides that you can find with a google search. You should read up and experiment until this starts to make more sense.

dpoverlord
05-31-2007, 05:57 PM
Problem Solved Thanks!
http://csd.dficlub.org/forum/showthread.php?p=21663#post21663