RD600 first look and general questions

[cadaveca]

1.42 v on NB

This way your problem. As I have stated before, it took small voltage to get 450mhz, but much more to get 400mhz 1:1. Typically, crashing beofre CMOS has been checked means chipset volts are too low(or ram). I have tested my ram on otherboard so know it's max, and never reboot a failed overclock attempt such as you did. This could have been your mistake..could have been not enough voltage, but I have done the same as you, and not had any issues. However, the one difference I see right away is that my cheapy sticks are 512mb d9's with 400/533/677 SPD(ram is stable 533 3-3-3-9 @ 1.8v), and they always seem to boot this board @ 533mhz after a CMOS clear.

BTW...best way I have found to deal with a C1 is too do a power-reset CMOS clear. If after the clear you still have a C1, then you need to swap to other ram.

where did you get this info

BTW how high do you thinkchipset temps can be 24/7..you seem to have alot of knowledge on the board limitations

I read it somewhere, cannot remember where, but the person posting the info was not someone who's posts I take lightly. Unfortunately I cannot remember the source. I do however remember that this info does conicide with what I hav found with my use of the board.


My chipset was 62-63c on load with stock heatsink. Changing to AS5 only dropped temps a couple of degrees. Currently I have an Thermalright HR-05 on the chipset, and under 1.66v in bios i get 50c max loaded. If i had stock cpu voltage, this would be far too much, as I do believe there is a "buffer" where cpu voltage and chipset voltage must be in order for proper operation. If the values are too far apart, damage will occur that will not make itself known for a while. The same can be said for all the other voltages...they all need to be within a specific ratio of one anotheras the components on the board are only capable of shaping these voltages in certain ways. Same for every board tho.

[nealh]

[QUOTE=cadaveca;2080382]This way your problem. As I have stated before, it took small voltage to get 450mhz, but much more to get 400mhz 1:1. [q]

I agree after the fact I wished I pushed this to 1.48v with 390 1:1

Typically, crashing beofre CMOS has been checked means chipset volts are too low(or ram). I have tested my ram on otherboard so know it's max, and never reboot a failed overclock attempt such as you did. This could have been your mistake..could have been not enough voltage, but I have done the same as you, and not had any issues. However, the one difference I see right away is that my cheapy sticks are 512mb d9's with 400/533/677 SPD(ram is stable 533 3-3-3-9 @ 1.8v), and they always seem to boot this board @ 533mhz after a CMOS clear.

I bought KVR 1 gb stick..1.8v DDR2...but it did not work as well...no matter ram slot

BTW...best way I have found to deal with a C1 is too do a power-reset CMOS clear. If after the clear you still have a C1, then you need to swap to other ram.

I tried this as well as everything Tony recommended at DFI forum site, battery removal....I tried for 3 days various combinations of things that should have cleared cmos for a boot...somehow the bios got pooched
I wish I had kept the mobo and tried to get a new bios chip

my new board just will not run my ram at 500mhz async like the first one..2.2v 500mhz 5-6-5-5-18-24-42-2t, auto strap
this ran memtest 86+ 1.7 test 5 for 50 passes, winmemtest for 1000%, blend prime95 for 20 hrs

I error out after 7 passes on test 5 now

I read it somewhere, cannot remember where, but the person posting the info was not someone who's posts I take lightly. Unfortunately I cannot remember the source. I do however remember that this info does conicide with what I hav found with my use of the board.
My chipset was 62-63c on load with stock heatsink. Changing to AS5 only dropped temps a couple of degrees.

My chipset sucks?? Microcool whisper xe gave idles of 59C..poor contact with shim??

I went back to same cooling on my old board ..1.42v idle was 47/48c and load was 53/54...stock HS, AS5 and 120mm fan blowing on it

Now same cooling at 1.36v..stock HS,AS5 and 120mm fan(lower ambients as well)..idle at 53/54...load was 58C(rare noted 60)

Currently I have an Thermalright HR-05 on the chipset, and under 1.66v in bios i get 50c max loaded. If i had stock cpu voltage, this would be far too much, as I do believe there is a "buffer" where cpu voltage and chipset voltage must be in order for proper operation. If the values are too far apart, damage will occur that will not make itself known for a while. The same can be said for all the other voltages...they all need to be within a specific ratio of one anotheras the components on the board are only capable of shaping these voltages in certain ways. Same for every board tho.

now this is a very important point...cant recall what other board this was an issue...if you set one voltage too low and one too high the difference was a chip and board killer

my cpu vcore is at 1.52 and NB volt. at 1.36...I think this ok...not sure what difference is too great

[cadaveca]

I realyl want to blame your ram for most of your issues. This may not seem to make such sense, but seeing so many issue with Micron IC's(D9's), it's hard to not place blame there. Some of my Crucial kits won't boot any more @ default(400mhz 5-5-5-15 1.8v)...actually only one does. The others cause C1 issues. C1 i beleive is memory initialization, so either memcontroller or mem is at fault under these circumstances. However, you should be able to get a non-stable boot long before C1 occurs...so you adjusted too many options at once, IMHO, to get a C1.

I set my ram not based on speeds, but based on what timings give me a certain amt of bandwidth. This is key...as 3400mb/sec @ CAS4 or 3400mb/sec @ CAS5 are virtually the same thing to the memory IC...but at the same time, different for the memory controller. With this in mind, I have very tangible goals when tweaking, as well as limits.


In regards to your chipset, i cannot say it sucks without playing with it myself. Sometimes hotter chips scale farther, sometimes not. depends on whether the heat is leakage related, or current related. Leakage on hot chip generally means cooling will bring it in line, but if the current is making chip hot, then not much can help it. this is the same for pretty much all silicon...chips with high leakage can handle higher current. current is not Volts, BTW, but amperage. Pretty much like "b" conroe's...pretty sure the only difference is the IC's on bottom of chip pcb, that allow more current to the chip...easily explains why "b" chips tend to go farther...they have more current available. Also explains the heat of those chips too.

[nealh]

I realyl want to blame your ram for most of your issues. This may not seem to make such sense, but seeing so many issue with Micron IC's(D9's), it's hard to not place blame there. Some of my Crucial kits won't boot any more @ default(400mhz 5-5-5-15 1.8v)...actually only one does. The others cause C1 issues. C1 i beleive is memory initialization, so either memcontroller or mem is at fault under these circumstances. However, you should be able to get a non-stable boot long before C1 occurs...so you adjusted too many options at once, IMHO, to get a C1.

ok but why did the cheapo ram not allow a boot....Again when I made my changes that killed the board...async to sync, lower fsb to 380, and lowered ram speed and used known good timings with no change in vdimm

BTW..this same crucial booted right up on the new board at default bios settings(1.8v 667 5-3-3-3)

I set my ram not based on speeds, but based on what timings give me a certain amt of bandwidth. This is key...as 3400mb/sec @ CAS4 or 3400mb/sec @ CAS5 are virtually the same thing to the memory IC...but at the same time, different for the memory controller. With this in mind, I have very tangible goals when tweaking, as well as limits.

what gets you 3400mb/sec at cas4? my cas4-4-4-4-18-24-42@400 settings per memtest 86+ 1.7gives a bandwidth of like 2700mb/sec
cas5-6-5-5-18-24-42 at 500 gives me about 3110 mb/sec

In regards to your chipset, i cannot say it sucks without playing with it myself. Sometimes hotter chips scale farther, sometimes not. depends on whether the heat is leakage related, or current related. Leakage on hot chip generally means cooling will bring it in line, but if the current is making chip hot, then not much can help it. this is the same for pretty much all silicon...chips with high leakage can handle higher current. current is not Volts, BTW, but amperage. Pretty much like "b" conroe's...pretty sure the only difference is the IC's on bottom of chip pcb, that allow more current to the chip...easily explains why "b" chips tend to go farther...they have more current available. Also explains the heat of those chips too.

interesting info..

[nealh]

Blah..room temp is 76F/24.5C..my idle temps on my chipset now with 1.36v ...54/55C

[cadaveca]

i run 4-4-3-4-12-16-28-3-4-3-3-2-2-5, 401mhz, sync, for 3356mb via memtest.

Don't get me wrong, not blaming the issue on you, but like you say, it doesn't sound right. Could be the board...very possible...however if something corrupted BIOS as to make it not bootable, and it was before, only user error is the cause. I'm not saying you were stupid in your settings or anything, but that it was your actions that killed the board. All settings you may have changed may have been valid...but your fingers still pushed the buttons that made it die. Had everything stayed at stock ,I bet the board would still be alive.

And yes, i know this board is meant to be overclocked. But it's the overclocking that killed it. Bad chipset, bad B.O.M., bad luck, doesn't matter.

I mean, if i take your approach, then it MUST be YOUR fault, as my board works fine. Without both boards in my hands, there's really no comparison to be made. Now, if i got 4 brand new boards(not boards given as RMA, they are never new, merely returns, 99% of the time), and all of them died, 3 of them died, heck even if one of them died, I'd be a bit upset, but that's not the case here. We've got one guy returned his board and got back two duff boards. To me, this is no surprise. They didn't pull new boards off of the shelf...DFI doesn't even do that. I sent in RMA board direct to DFI, marked with invisible ink, got the same back. Didn't overclock worth a damn for me when i got it back, but whatever. Couldn't get 300FSB out of it(NF4). Dude who bought the board got 300mhz easy as pie. My fault? Did he know some trick i didn't? Nope. Just used different parts.

So, we got different parts, my board works, your doesn't. I say it's your other parts. Based on the C1 error on diagnostic LED, I'd blame your ram. Do i know this is the cause 100% for sure? Nope. 10%? Nope. But it was something that made it die...

[nealh]

i run 4-4-3-4-12-16-28-3-4-3-3-2-2-5, 401mhz, sync, for 3356mb via memtest.

nice..401 sync...I wonder if the 401 value is what helps the sync..I have seen alot of talk regarding how some fsb just dont work and others do

I tinkered a tiny bit last night...all async-2t with NB at 1.36v
tried 451 mhz on my Crucial 10th anniv..@2.1v 4-4-4-4-18-24-42-3-6-3-3-2-2-5 with cpu at 390 fsb(3500) I get 2974 mb/sec
changed cpu to 3465(lowered speed to see effect)...bandwith was essentially the same 2924 mb/sec
then lowered cpu to 3455...ram at 451 as above
bandwidth was 2999 mb/sec...passed 27 passes of test 5 on memtest 86+ 1.7

Don't get me wrong, not blaming the issue on you, but like you say, it doesn't sound right. Could be the board...very possible...however if something corrupted BIOS as to make it not bootable, and it was before, only user error is the cause. I'm not saying you were stupid in your settings or anything, but that it was your actions that killed the board. All settings you may have changed may have been valid...but your fingers still pushed the buttons that made it die. Had everything stayed at stock ,I bet the board would still be alive.

And yes, i know this board is meant to be overclocked. But it's the overclocking that killed it. Bad chipset, bad B.O.M., bad luck, doesn't matter.

I cant disagree with this...I did make the changes and hit the buttons..so I agree user error in the end is the issue
But they sell the board knowing it will be overclocked and I payed a premium(my fault), I expected a bit more tolerance, esp since it did not seem as comapred to others experiences I was pushing too hard

I mean, if i take your approach, then it MUST be YOUR fault, as my board works fine. Without both boards in my hands, there's really no comparison to be made. Now, if i got 4 brand new boards(not boards given as RMA, they are never new, merely returns, 99% of the time), and all of them died, 3 of them died, heck even if one of them died, I'd be a bit upset, but that's not the case here. We've got one guy returned his board and got back two duff boards. To me, this is no surprise. They didn't pull new boards off of the shelf...DFI doesn't even do that. I sent in RMA board direct to DFI, marked with invisible ink, got the same back. Didn't overclock worth a damn for me when i got it back, but whatever. Couldn't get 300FSB out of it(NF4). Dude who bought the board got 300mhz easy as pie. My fault? Did he know some trick i didn't? Nope. Just used different parts.

Again based on your comments, I have to agree with you...it was my fault but I still expect if the product is advertised to techies like us for overclocking...I hope it will have better tolerances

My analogy is a car...if you buy Honda your expectations will be different than if you buy a Corvette..you will pay differently as well

I am pretty sure from the process the RMA board was a new one....I got Newegg to cross-ship it....the packaging on the mobo anti-static bag...was untouched...The rep claimed they were shipping a new board

HS still had gumball thermal paste(some users would never remove it and reapply but many buying this board will)
can I be 100% sure it is a new board no, of course but based on box appearence and contents, antistatic bag...pretty sure it is brand new

So, we got different parts, my board works, your doesn't. I say it's your other parts. Based on the C1 error on diagnostic LED, I'd blame your ram. Do i know this is the cause 100% for sure? Nope. 10%? Nope. But it was something that made it die...

I agree again...even with the same exact parts....we will have a different although close experience and your skills probably are better than mine
I always get a little less performance/overclock vs others...which is ok

[cadaveca]

Yeah nealh, your new board is working. It might need some spanking to get in line, but then it really sounds as if your ram is starting to die. I'm sure you've seen the other threads here on those sticks...your probably came form teh same batch...ordered when the "huzzah" was going around. I did too...those sticks are toast.


And yes, this board is a bit disappointing. But it's an old chipset hanging with the top guns, and not doing all that shabby, so i don't mind much. But 975x is much faster, in everything, it seems.

There are large holes is performance...if you check back to some of Tony's posts from when this board first came out, as well as eva2000's, you'll find that there are 3-4mhz holes where performance falls behind, due to the offset of the cpu bus and memory bus on the chipset. you must pick numbers that divide evenly, or performance suffers.

[marauder16]

hmm, I have a problem. I'm currently at 426*9 1.61V on idle in windows. Now when my CPU gets on 100% load by running orthos, after some time CPU-Z reports multi-drop to 6 so the CPU runs @ 2556MHz, everest reports it too, but orthos and coretemp don't. It didn't show before, @ 3.7Ghz it is always at set speed, no drop. the C1E function is disabled in BIOS, is there anything else that could be causing this? thnx

[nealh]

Yeah nealh, your new board is working. It might need some spanking to get in line, but then it really sounds as if your ram is starting to die. I'm sure you've seen the other threads here on those sticks...your probably came form teh same batch...ordered when the "huzzah" was going around. I did too...those sticks are toast.

UGH....are you saying this becasue it will not run at 500mhz anymore..or did you note something else in my posts

I was impressed last night when I was able to do 451 4-4-4-4-18 at 2.1v, when I was only on my old board to 500 with 2.2v 5-6-5-5-18
I should note if I give the ram 2.23v=bios 2.25v reading(vs 2.2v bios setting on old=2.22v) ..I was able to run a few passes at 500 5-6-5-5-18 with 3115mb/sec with cpu at 3500...but I really want to keep the ram from max voltage as I saw so many sets die

my biggest concern is going to be chipset temps....Ambient temps are going up...my room last night 76F/24c...idle chipset temps are now 54/55..by summer in florida I will have 25/26C ambients

I am serious looking at WCing block but I really hate the idea of rd600 specific block and while I like a MCW30..I am not sure the clip menchanism will keep a good tight fit with my tube routing

I could not get my Microcool Whisper XE to fit correctly with shim in place and was concerned I would damge the core without it

Considering a Swiftech MCX 159CU..now

And yes, this board is a bit disappointing. But it's an old chipset hanging with the top guns, and not doing all that shabby, so i don't mind much. But 975x is much faster, in everything, it seems.

I realize the chipset is older technology..though realy did not understand this until after buying...only 975x board I like was the Badaxe2....but reports did not seem to show consistent 400+ fsb(though for me in the end it does not matter as I cant run 3600) and the lack of lower multiplier

There are large holes is performance...if you check back to some of Tony's posts from when this board first came out, as well as eva2000's, you'll find that there are 3-4mhz holes where performance falls behind, due to the offset of the cpu bus and memory bus on the chipset.

this seems to be a bug a boo for all intel boards....

you must pick numbers that divide evenly, or performance suffers.

are you referring I assume to fsb and ram speed? do they need to divide evenly as a given number ie cpu speed 384 vs 385..or cpu vs memory speeds ..384 vs 451(cant do 450 in bios)

[cadaveca]

what i mean is that the fsb and ram speed should , hopefully, follow the default ram multi's, 2:3, 1:1, 4:5, it does not have to be exact...but i find that say 432 for ram, is divisible by 4. So to me, fsb should be divisible by 3, giving 3:4 split, almost. If it's not you get a slight latency hit because the ratio is whacked, and this drops bandwidth.


BadAxe 2 is ok, but it's slot arrangement doesn't suit my needs. I have one tho...and have no issues getting over 400FSB. Mind you I have no issues doing such on P5W(68MOAG, 450FSB no problem) or XBX1 too(over 50% using windows, 417FSB, rebootable. more is only prevented due to clockgen), and lots of others DO have issues reaching such speeds.

It's really weird, because I have bought many parts...spent about 15k already this year on Core2Duo cpu's, boards, and DDR2. Very few of the issues I see related on forums are ones that I have had. All my e6600's(23 now) reach 3.6ghz. all of my E4300's(15) cannot do 400FSB, but 333FSB for 3ghz, @ stock volts and cooler each can do without problems. So either I got EXTREMELY lucky on all the parts I have(which i HIGHLY doubt), or something else is amiss here. I got a couple of quads when they first came out...ran into same FSB issues most had...but when it comes to Core2Duo clocking, I've yet to get a really bad chip. Mind you I don't mind pumping 1.6v for 3.6ghz, if needed.

[Brian y.]

Can anybody get past 530FSB w/ this board?? I have been stuck there w/ my E6600. Another question, can anybody tell the difference between the 300 & 333
bootstrap? I did not see any differences when running Super Pi or PC Mark05....

[marauder16]

ok, can anyone tell me how to disable EIST in this board's BIOS? I can't find a setting that would look like it does that, I ran through the whole BIOS a couple of times.

[nealh]

what i mean is that the fsb and ram speed should , hopefully, follow the default ram multi's, 2:3, 1:1, 4:5, it does not have to be exact...but i find that say 432 for ram, is divisible by 4. So to me, fsb should be divisible by 3, giving 3:4 split, almost. If it's not you get a slight latency hit because the ratio is whacked, and this drops bandwidth.


BadAxe 2 is ok, but it's slot arrangement doesn't suit my needs. I have one tho...and have no issues getting over 400FSB. Mind you I have no issues doing such on P5W(68MOAG, 450FSB no problem) or XBX1 too(over 50% using windows, 417FSB, rebootable. more is only prevented due to clockgen), and lots of others DO have issues reaching such speeds.

It's really weird, because I have bought many parts...spent about 15k already this year on Core2Duo cpu's, boards, and DDR2. Very few of the issues I see related on forums are ones that I have had. All my e6600's(23 now) reach 3.6ghz. all of my E4300's(15) cannot do 400FSB, but 333FSB for 3ghz, @ stock volts and cooler each can do without problems. So either I got EXTREMELY lucky on all the parts I have(which i HIGHLY doubt), or something else is amiss here. I got a couple of quads when they first came out...ran into same FSB issues most had...but when it comes to Core2Duo clocking, I've yet to get a really bad chip. Mind you I don't mind pumping 1.6v for 3.6ghz, if needed.

Thanks...nice info

Have you had any e6600 die from 1.6v...there seem to be sporadic reports of slow death/degradation...I not really happy using 1.52v on my e6600(temps are fine)

BTW, why do you think the ram is dying..not sure I understand why?

I will definitely watch this and send in for RMA if need be....problem is I returned my cheapo ram(it wasnot so cheap $85 for soemthing I would not use)

15k on parts...what do you do with all the stuff....

[nealh]

ok, can anyone tell me how to disable EIST in this board's BIOS? I can't find a setting that would look like it does that, I ran through the whole BIOS a couple of times.

look at this screen in Genie Bios..scroll down to bold
CPU Vid Control: 1.4625v
CPU VID Special ADD: Auto
DDR2 Ram 1.8 Voltage: 2.20v
CPU VTT 1.2V Voltage: 1.23v
NB Core 1.2V Voltage: 1.42v
NB PLL 1.8V Voltage: 1.93v
NB PLL 1.2V Voltage: 1.21v
NB PCI-E 1.2V Voltage: 1.22v
NB Core 1.2V convert from: 1.97v
SB Core 1.2V Voltage: 1.23v
Clockgen Voltage: 2.92v
GTL REF Voltage control: Enabled
CPU Core 1/2 GTL REF Volt: 48
CPU Core 3/4 GTL REF Volt: 48[
North Bridge GTL REF Volt: 128
CPU PLL Setting Overide: Enabled
PLL Override loop count: AUTO
Conroe P-State Multiplier: x9
C1E Function: Disabled

[Brian y.]

Have you tried to disable the C1E function?

[marauder16]

it is disabled, but the EIST isn't, that guy from CPU-Z told be that after looking at the registry dump of mine.
don't know where else to look..

EDIT: for some reason, that line in the bios is set to disable and can't be changed, anyone know why is that?

[cadaveca]

Thanks...nice info

Have you had any e6600 die from 1.6v...there seem to be sporadic reports of slow death/degradation...I not really happy using 1.52v on my e6600(temps are fine)

BTW, why do you think the ram is dying..not sure I understand why?

I will definitely watch this and send in for RMA if need be....problem is I returned my cheapo ram(it wasnot so cheap $85 for soemthing I would not use)

15k on parts...what do you do with all the stuff....

LoL high-end rigs topping 4k is not uncommon...15k is not much in the scheme of things. Filling an office with new machines took care of most of the hardware. Friends that are gamers but not into overclocking or anything like that took care of the rest. I have 3 Conroe rigs of my own...and about to sell them off to buy new ones.

in Regard to 1.6v killing a cpu, no, not happened yet, but I HAVE seen cpu's loose thier legs and not go further than 3.6ghz after attemping for more @ 1.6v. Each of these needed 1.5v for 3.6v, and would do 3750 @ 1.6v, but after extended burn-in(aircooling, 70c plus temps) they no longer could do 3700, even.


I think ram is dying because BOM of these sticks has changed over time, and you have issues that seem mostly ram-related. You only revise hardware if there is an issue. I have had many sets of this IC and pcb combo die, although i really think it's a small SMD on the pcb, and not the pcb itself that is the problematic part.

It's hard to say yes, it's dying, or no, it's not, without having them in the same board that they first started in. Very easy to see if they are still capable this way, and this is why I have many rigs. One to test ram, one to test cpu, one to use. Friends will come over to game, so it's all worthwhile for me.

LoL. best part is that you are under water, and concerned about 1.5v...when I'm talking air! Anyway, it's hard to find conclusive evidence of problems, or lack thereof, without proper testing. It's impossible with just one set of hardware, and the more you add to the mix, the easier it is to fnd correlations between everything. this is why i have very many issues with many of the comments in this thread, as they do not look at the whole picture, and merely focus on a small part, which, while useful, is not accurate.

[nealh]

LoL high-end rigs topping 4k is not uncommon...15k is not much in the scheme of things. Filling an office with new machines took care of most of the hardware. Friends that are gamers but not into overclocking or anything like that took care of the rest. I have 3 Conroe rigs of my own...and about to sell them off to buy new ones.

in Regard to 1.6v killing a cpu, no, not happened yet, but I HAVE seen cpu's loose thier legs and not go further than 3.6ghz after attemping for more @ 1.6v. Each of these needed 1.5v for 3.6v, and would do 3750 @ 1.6v, but after extended burn-in(aircooling, 70c plus temps) they no longer could do 3700, even.


I think ram is dying because BOM of these sticks has changed over time, and you have issues that seem mostly ram-related. You only revise hardware if there is an issue. I have had many sets of this IC and pcb combo die, although i really think it's a small SMD on the pcb, and not the pcb itself that is the problematic part.

It's hard to say yes, it's dying, or no, it's not, without having them in the same board that they first started in. Very easy to see if they are still capable this way, and this is why I have many rigs. One to test ram, one to test cpu, one to use. Friends will come over to game, so it's all worthwhile for me.

LoL. best part is that you are under water, and concerned about 1.5v...when I'm talking air! Anyway, it's hard to find conclusive evidence of problems, or lack thereof, without proper testing. It's impossible with just one set of hardware, and the more you add to the mix, the easier it is to fnd correlations between everything. this is why i have very many issues with many of the comments in this thread, as they do not look at the whole picture, and merely focus on a small part, which, while useful, is not accurate.

I agree today it is not hard to hit thousands for a high end rig....

I agree with your comments and wish I could afford the time and wife factor to have several test rigs..but this would never be justifiable expense to her...

Thanks for the interesting insights and observations...

BTW, excuse my ignorance what is BOM

[cadaveca]

BOM is bill of materials....the parts that go into making a card, whether mobo, cpu, mem, vga...the list of SMD's and such that make up the component. Usually in revisions of a product, this changes. If it's a pcb change, then typically you get a whole new product name. This is why ASUS, gigabyte, etc have many boards that are the same, but different name, slightly different functionality. What differs between the products is the BOM(like Striker and P5N32-E, but not). this means not the main parts(at least to me), but hte supporting parts. Not memory IC's, nor gpu, but all the other parts, capacitors and such.

[nealh]

FYI:
new bios
http://www.dfi.com.tw/Support/Downlo...FLAG=A&SITE=US

[erwinz]

at long last.. a bios..

will try this later..

[Pete@X]

FYI:
new bios
http://www.dfi.com.tw/Support/Downlo...FLAG=A&SITE=US

Small hint: Do a byte to byte compare ...

[AbelJemka]

I think the same but readme not the same. I've not taste the beta bios so i can't say if he rise vddr to 1.95V so maybe based on beta bios but with little (or big) changes.

[nealh]

Small hint: Do a byte to byte compare ...

are you suggesting they posted an official bios that does not do what they list in the readme...

the support on this board has been blah so far...so no surprise to me if this is the case