new BIOS for DFI infinity 975X

Quote:

---

Originally Posted by Dax5

mine wont post even after powering off for just a few min.

---

I guess its good I never turn off my system then :) Although I understand the occasional need certainly.

I'm going to give Raja's (raju's?) oc method a try and see if I can't crack 360.

@Raja: btw, did you mean to say set all to manual or auto?

UPDATE: Re-flashed to 0830, set ram divider to 533, all other settings to auto in ram except increased all drive strengths to 3x. After a few tries, it booted at 360! That's a first for my board and I'll keep at it to see where I end up. cpu-z reports ram @ 361, 1:1, 5-5-5-15-20

try turning off your pc for 5min then power back on. see if it cold boots

My cold boot problems on 0731 are getting ridiculous, and I only have the system clocked to 320FSB still. I am also getting random blue screens like once every couple of days, though I am not sure why. I think a couple of them were due to the onboard sound, so I updated the realtek driver (no I am not going to buy a pci sound card) but I got one today even with the updated driver, but I was in the middle of something and lost about 10 minutes of my work since my last save so I was too pissed to bother looking at what the blue screen said.

I am getting a little miffed at DFI's lack of support for this board. If they hadn't put out beta BIOS it would be one thing but they did several weeks ago and they should have ironed out all the bugs by now >:(

Well, anything at or over 365 still won't post, so I managed to squeeze out another 5mhz fsb with 0830 thus far... not really what I was hoping for. I haven't run Orthos, but I have 2 clients running F@H and its just fine @ 51/52C @ 100% CPUsage

Try This.. i got better results from adjusting it.

SLP_S4# Assert Bandwidth - 1 to 2

Alright, I'll give that a shot. I'm having stability problems even at 360 though. Orthos Gromacs runs fine @ 59/58c per core temp. Super_pi_mod works @ 1m but breaks on 4m and 8m ("not exact in round"). Running 5-5-5-15 @ 451mhz (4:5) and 3248ghz (360fsb in bios/361 per smartguardian). 1.42v to cpu, 2.14v to mem, 1.74 to nb. 46c idle.

I'm also having problems booting up although it seems like 'restarts' from windows work mostly okay once things are going.

crank up your NB volts to 1.75, either bump up your memory volts or use a lower divider and then try again.

im also running the 4:5 divider.

i dont have problems rebooting too.. it's when you cut off the power that things start to go wrong haha

I feel kinda noobish for asking this, but can someone please clarify on the voltages for me?

I know the mv increment thing is the increase to CPU voltage from stock.

I know what CPU voltage is :rolleyes:

CPU VTT Voltage - This is the CPU Voltage Termination correct? What the heck does that mean? :confused:

NB Voltage - Is this simply the voltage for adjusting the voltage supplied to the processing part of the NB or does it also adjust the MCH voltage? Are they one and the same? And if not does that mean you cannot manually adjust the MCH through bios on this board?

Right Guys, i think i've sorted my cold boots, but its 2 early 2 say for sure. No cold boot prob for 2 days (5-6 starts).
Here are my settings:

Quote:

---

Genie BIOS

Over Clock Mode Select.............. - Manual
PPM Function........................ - Disabled

CPU Clock Setting................... - 360Mhz
O.C. Failed. Control................ - 1Mhz
PCIE Clock Sync. With............... - O.C. Mode
PCI Clock Setting................... - 102MHz
SATA Clock Sync. With............... - Fix 100Mhz
CPU and PCIE Clock Turbo............ - H/W Turbo
CPU Turbo Add-On Speed.............. - Disabled
PCIE Turbo Add-On Speed............. - Disabled

CPU VID Offset Setting.............. - + 175.0mV
Default CPU Voltage................. - 1.32500v
CPU VTT Voltage Setting............. - 1.25v
DRAM Voltage Setting................ - 2.15v
NB Chip Voltage Setting............. - 1.65v


DRAM Timing and Config

DRAM Timing Selectable.............. - Manual
CAS Latency Time.................... - 5
DRAM RAS# to CAS# Delay............. - 5
DRAM RAS# Precharge................. - 5
Precharge Delay (tRAS).............. - 15
System Memory Frequency............. - 667Mhz
Refresh Mode Select................. - Auto

---

The changes i made are added .5v to vtt voltage & SLP_S4# Assert Bandwidth - 1 to 2 (not a clue what it does or even if it made a difference). All other settings are the same as before. I'm not able to push any further till i invest in some w/cing as my temps are hittin 68' with orthos & my week 24 conroe needs a lot of voltage.

thats good to hear! =) unfortunately im fed up with this board! im getting a new one tomorrow. still decidin between gigabyte and asus =)

It pisses me off to say this but i am going to hold onto to this board until i see what the RD600 from DFI is like. I hate them for the lack of support for this board but I'm not going to not buy the RD600 if its as good as people claim it is.

One thing for sure though if they cant deliver with this RD600 board my view of DFI will be forever tarnished.

Why dont they just release a new bios for this thing. It is turning so many people off buying their products they must see that.

Quote:

---

Originally Posted by Btrice

My cold boot problems on 0731 are getting ridiculous, and I only have the system clocked to 320FSB still. I am also getting random blue screens like once every couple of days, though I am not sure why. I think a couple of them were due to the onboard sound, so I updated the realtek driver (no I am not going to buy a pci sound card) but I got one today even with the updated driver, but I was in the middle of something and lost about 10 minutes of my work since my last save so I was too pissed to bother looking at what the blue screen said.

I am getting a little miffed at DFI's lack of support for this board. If they hadn't put out beta BIOS it would be one thing but they did several weeks ago and they should have ironed out all the bugs by now >:(

---

Well the blue screen happened again, this time I made sure I saw where the problem was and it said serial.sys. Now I had both my unused serial ports disabled in BIOS, wonder if that is what caused it. Not sure why it would though, if its disabled in BIOS windows shouldn't see it. Never had a problem disabling them in the past with other systems.

there's no sense holding on to this crap. i thought i had a winner before. now im pretty sure that the infinity line sucks

DFI vs. MSI – Conroe 975X Motherboards Tested - http://www.tweaktown.com/articles/953/

looks like a clear win for DFI from that review. However 378FSB isnt anything mindblowing...

Stil gettin cold boots, also got a fcuked up issue: pc posts ok showing 360fsb, but in windows when i check with cpu-z i'm at 266fsb. It takes a cmos clear & reset oc to sort it out. Any1 any ideas?
Hows that new bios? I'm afraid to try :mad:

well i can't say if this new 9/13 is better or worse to overclock but with me it really help to use lower volts with cpu. 8/30 i had to use 1.43v with 350x10 but now 1.39v is no problem :)

Quote:

---

Originally Posted by Keiki

well i can't say if this new 9/13 is better or worse to overclock but with me it really help to use lower volts with cpu. 8/30 i had to use 1.43v with 350x10 but now 1.39v is no problem :)

---

Nice to know. I'm pumpin 1.47V @ 360fsb. Is yours a week 24 by any chance?
Any1 else using this bios?

colfin22: nope it's week 29.

after 3.5ghz@1.39 success i decided to go even higher but it seems to be no go
quick orthos with 3.6ghz and 1.43v seemed to be stable so i went to 3.75ghz@1.47v and lowered the ram ratio from 4:5 to 1:1, it booted fine to windows but orthos ran only for 2mins then tried to restart but it crashed and wouldn't boot at all before i cleared cmos from mobo >_< and one strange thing is that the power led in my case wont shut down anymore at all until i unplug cord from psu and now when i boot from total shut down it blinks for about 10seconds O_O

Tried the 0913 bios for the last while & had no luck with it. Couldn't get 360fsb to pass orthos, it kept crashing & i had the same issue as you: that it wouldn't post after crashing. Took cmos clear to sort it out. Tried everything.......running ram at 1:1 with loose timings, upping voltage etc. IMO this new beta is the worst oc'er i've come across. Its very buggy. I'm back on 0731 now.

BTW, Dfi have confirmed to me that there are parts of 0830 that overwrite 0731, that don't rewrite when you flash back to 0731, which might cause the issues i've been having. This is their email:

Quote:

---

I have done a bit of checking and have determined that when updating to the 0830 version certain areas of the DMI are overwritten, when flashing back to the 0731 they are not. Try reflashing the BIOS in DOS mode (not thru windows or a windows DOS session) with the 0731 version. This time however type in the following at the A: "awdflash 97TID731.bin /f/cc/nbl/qi" (Without quotation marks of course). The extra switches will then "format" the chip and allow the DMI to be rewritten in accordance with the 0731 BIOS. Of course I have not had any problems with "cold boot" either way so I can't say if this will help for sure, but it should get rid of any residual traces of 0830 and is worth a try. Let me know if it helps.

---

Havn't tried this yet, gonna connect my floppy later & try.

Quote:

---

Originally Posted by colfin22

Tried the 0913 bios for the last while & had no luck with it. Couldn't get 360fsb to pass orthos, it kept crashing & i had the same issue as you: that it wouldn't post after crashing. Took cmos clear to sort it out. Tried everything.......running ram at 1:1 with loose timings, upping voltage etc. IMO this new beta is the worst oc'er i've come across. Its very buggy. I'm back on 0731 now.

BTW, Dfi have confirmed to me that there are parts of 0830 that overwrite 0731, that don't rewrite when you flash back to 0731, which might cause the issues i've been having. This is their email:



Havn't tried this yet, gonna connect my floppy later & try.

---

Great work man ill give this a try along with 913

BTW.......sounds noobish.........can some1 explain how i get in2 dos and get the "A:" command prompt, i've only ever pressed alt & f2 to enter the awdflash utility & this autoloads from the floppy, but it doesn't format the chip 1st and appears not to overwrite the last segment. Do i make a dos boot disk?
Some1 pls explain


Edit: ok i figured it out. i'll report back later whether i'm still gettin cold boots or not.

Quote:

---

Originally Posted by colfin22

Stil gettin cold boots, also got a fcuked up issue: pc posts ok showing 360fsb, but in windows when i check with cpu-z i'm at 266fsb. It takes a cmos clear & reset oc to sort it out. Any1 any ideas?
Hows that new bios? I'm afraid to try

---

I was getting that same issue, the failed overclock would kick in after it wouldn't post on the first boot, knocking me down by 5Mhz in post but then in windows CPU-Z showed no overclock at all. A simple reset of the system and going into BIOS and upping it back to 320 fixed that.

At this point I really could care less if I can overclock beyond 320FSB, I just want it completely stable at that speed and no cold boot issue. But based on these alpha bioses doesn't look like that is going to happen.

Very stable now on 0731 @ 360fsb after doing the "format before flash" Dfi advised me on (posted above). Give it a try. It seems to work. No cold boots or failed oc's so far, its like it was on 0731 before i tried the beta's. I'm happy with this, but its too early to say cold boots are gone for sure. I'll keep ye posted. :banana: :banana: :banana: :banana: :banana: :banana:


Might try 0913 later, had issues with it earlier today, but now that i know how to format before flashing its prob worth tryin again.