Mine worked fine, and i think angry_games used one as well in the OC database at dfi-street.Quote:
Originally Posted by Hybrid
Printable View
Mine worked fine, and i think angry_games used one as well in the OC database at dfi-street.Quote:
Originally Posted by Hybrid
Thanks! :toast:
ever heard of SNDS? intel processors are still a little bit more fragile than amd processorsQuote:
Originally Posted by calcal
Jort I can't believe this - there are things popping left and right now! I am sorry to hear you also took a beating. Glad you'll be able to RMA - 2 of my CPUs aren't RMA'able FX57 has IHS off - X2 4800+ had been dropped before and has marks...Quote:
Originally Posted by Jort
I was just thinking of doing another run with a third board and an Opteron - I think I am going to pass.
DFI told me that the new FX57 was suposedly still working along with one of the boards - kinda doubt it - but I shall see.
I have also killed one FX-57 with Grouper board. I was doing some memory testing at that moment. The system froze when I was changing the multiplier (from 12x 200MHz to 13x 200MHz). After this the cpu was completely dead.
This happened few months ago.
macci has also killed two FX-57 cpu´s with the same board.
The first one died under cascade cooling, and the second one has a partially broken memorycontroller. The cpu works and overclocks like it did before, but only 2x 256MB sticks can be used. If he tries to use 2x 512MB, either the system won´t boot, or it crashes all the time (if it even can reach to windows).
Same board and memory works fine with another cpu.
mikeguava and Jort [H]ard]OCP posted an article on thier problems with the
DFI crossfire, here is a quoteCould this be the problem facing dead Cpu's?Quote:
Originally Posted by HardOCP
The whole article
Quote:
Originally Posted by The Stilt
Sorry Stilt - sounds like an epidemic right now with any new board out there!
Read this - makes sense for Macci's porblem with the second CPU.
http://www.xtremesystems.org/forums/...t=79509&page=1
1st FX57 and X2 died running Geil One BH @ ~ 3.4V or more...
Quote:
Originally Posted by Jort
Can you give us some more details on what memory etc. you were running? Did you contact DFI about this?
http://www.dfi-street.com/forum/showthread.php?t=27644
its all here.
before i am going to boot the mobo i'll contact dfi :)
All of you guys are killing CPUs with high VDIMM on the Grouper/Halibuts right? I know Macci was using BH5 or VX. I know Sampsa was using Mushkin Redline at 250 MHz, so it must have been at high VDIMM. I also know Sampsa was at default (low) Vcore. How many of you have been running with elevated Vcore when VDIMM is high? Also, isn't it strange that all the 90nm CPUs seem to be getting damaged?
Maybe you guys are taking high VDIMM for granted since it was somewhat fine with Rev CG. But remember rev CGs came with higher default core voltage AND more importantly was on a different process node.
Before everyone starts blaming the motherboards, realize what you are doing. If a CPU dies at default voltage (ALL of them, not just Vcore) then there is definitely a problem. If you are killing CPUs at elevated VDIMM, especially over 3V then it's a completely different story.
We have gotten failure analysis results of some of the CPUs that have died on us under the cascade (running high VDIMM and high Vcore) and they all had dead memory controllers. What does this tell me? If you under the cascade and/or run with high VDIMM (even with elevated Vcore) you might be asking for trouble. We have had CPUs run for many weeks under cascade cooling and high VDIMM and Vcore, others didn't last more than a day or two.
Quote:
Originally Posted by The Stilt
Grayskull- please don't make it sound that this is a known fact - now that Tony gave the info about what migh be going on. All of us have been using these kinds of voltage differentials on NF4 boards for quiet some time - and in my case on several test rigs in 24/7 setups.
You are right it seems to be targeting the 90s - something that should have been addressed in Beta testing - no?
If it was known to the board manufacturers that the voltage differntial is a known killer - why was there not a warning etc. out there?
What Tony has stated shouldn't come as a surprise (it doesn't surprise me at all :) ). It is a known fact (or should be) that whenever you overvoltage above the stated specifications, there are no guarantees. How can you expect motherboard vendors to warn you if there is no quantifiable amount of differential that is known to cause damage? As far as AMD is concerned, overvoltaging and overclocking is illegal and not recommended. Unless a specification is posted from AMD, anyone trying to guess at a number is doing just that, guessing. The real value depends upon internal ASIC design and can vary with process. ;) So we've gone from 130 nm processors, to 90 nm and soon they'll probably be going to a finer technology and things might change again.
Also, don't think that any vendors are extensively qualifying their boards across multiple processors at anything other than specified voltages. It's not happening as far as I know.
Last, just because a certain lot of processors might be fine, doesn't mean others will. Process variation as well as the undoubted process tweaks that are constantly happening to boost speed and yield could also affect things.
Bottom line, overvoltaging is risky and YMMV.
Quote:
Originally Posted by mikeguava
Here's some stock settings trouble with my board, if I change any setting at all in the bios it wont boot, also, if I try to run 2 dimms it won't boot using slots 2/4 and using ballistix. This is all at stock. My board is going back I guess I will try the Grouper board now. Kinda silly that I can't even turn off the intro x200 screen and have the bios work This is using the new bios. I'm gonna try a diff ati board now. Tired of Nvidia so I won't be getting one of those.
grayskull, you KNOW it's related to the boards. How many people lost chips like this on the ultra-D boards? Not many if any I can think of... I and MANY others ran high voltages (I personally have run 3.8vdimm and stock vcore and 3.8vdimm with 2vcore through 3 different 90nm CPUs on my ultra-D with no issues even with watercooling and with dry ice) without the things dying. CPUs are dropping like flys now.
If this was an issue with the chips and voltage settings we all should have lost hundreds of chips since the 90nm chips were released by AMD. Unless you get some engineers on here who know everything and anything about these boards and chips you're going to have a hell of a time trying to convince us overclockers who have done the exact same things with the same chips in older boards with no problems that this is a voltage issue. This is worst occurance of deaths I've seen since the A64s first came out and modded shuttle boards were consuming clawhammers.
Someone arrest Fugger, Shamino, Macci OPP, OPB & CO immediately!!!!Quote:
Originally Posted by Grayskull
All kidding aside - I can totally understand form where you are coming from.
But what if the user is setting all the recommended voltages for his combination of hardware - it quickly becomes a grey area.
In my case I combine a DFI RDX board, a AMD FX57 CPU and Geil One BH memory and set within all recommended operating voltages. well with the Geil Mem it is between 3.4V to 3.7V ( and fully covered under warranty). AMD says 1.4-1.45.
Now who is at fault ? The Memory's ? - The CPU? The User? or the board manufacturer who has to combine everthing in one pot?
Another good example - same thing for me in the beginning - I get a brand spanking new RDX board - I throw in my Geil One -the board will not post - nothing...I throw in TCCD - now I can post - wellonly after raising the votlage significantly I can post with my BH memory - and I heard that the board was optimized for UTT/BH - hmm.Quote:
Originally Posted by fareastgq
One more thing - I think we can be pretty sure at least from this wave of potentially completely unrelated (or realted ) occurances of 90mns deaths, it doesn't appear to have anything to do with the ATI chipset ( nor NF4 chipset) in itself.
I have had nothing but trouble with this board from the moment I got it :mad:
I am experiencing the exact same problems as this.
http://www.hardocp.com/article.html?art=ODg4
Quote:
Running Into Trouble
I took delivery of our DFI CrossFire motherboard and prepped it for testing. We almost immediately ran into problems. The first thing I noticed was that I could not save my BIOS settings, exit the BIOS, and then reboot. After attempting to save and leave the BIOS, the motherboard would freeze at a blank screen. Resetting the board would allow a reboot, but that did not always work; sometimes a hard power down was needed. The reboot issues did not stop there. Even once we got an OS installed, the motherboard still exhibited reboot issues where it would hang on POST. Sometimes it would hang at IDE detection, sometimes at Silicon Image RAID controller detection, and sometimes it would hang after setting the interrupt channels. Then again, sometimes it would reboot just fine, but most times it would not. Checking the DFI support forums, I found that I was not alone in experiencing these issues.
Sheik,
Yes, this appears to be a wide spread problem. My finger is exhausted from pushing the reset-switch all the time. WE NEED A NEW BIOS.
-k0nsl
Quote:
Originally Posted by Grayskull
my cpu died WITHOUT oc'ing, i coudn't even welcome the POST screen.
maybe its related to there "super" 4 phase power design.
anyone taken the time to look at the burned pins and compare them to the AMD processor sheets to see which pins exactly seem to be getting too much current?
If we can find that out we can tell which part of the board may be operating incorrectly (over/undervolting and/or pulling high/low for increased/decreased amperage).
I've just checked the pins against the s939 pinout. 2 of the pins appear to be Vss (ground), and one of the pins is Vddio (the DDR SDRAM I/O ring power supply, according to the datasheet :confused: )Quote:
Originally Posted by STEvil
oooo does sound like memory controllers.
Board # 3 running perfectly fine for 8 hours now.
I really hope, u won't burn any more CPU's with the new board mike.
I'm kind of excited what's gonna hapen with my board. Just waiting for X1800 XT to get all together.
isnt that somthing you should have mentioned BEFORE the boards hit retail? "oh by the way this board will somtimes kill your processor 1 in 4 times if you use more than 3vdimm"Quote:
Originally Posted by Grayskull
you knowly marketed a product to us that you knew to be faulty. does anyone else see a problem with this?
personally i think its sickining to see what effectively is people being "beta" testers in retail products.( in more areas than just these,, games also )
killing cpus that cost 3-4 times the board doesnt make sense, when the technology is there to in house test most any situation, especially if the board is considered an enthusiast board.
certainly the builders and in house testing recreated what other boards that were predescsors(sp lol ) and problems /situations have experianced to eliminate that from any new technology.
i simply dont understand the mentality of developers and companies that release a product with out ever finding out the many variables that it will encounter.
now i understand that they feel the need to get it out to the public for review and hitting the shelves asap, but then again, it is well known that the DFI boards are very finicky in comparison the other manufactures.
i have long held out hope for the new board, and have my x1800xl and 2x512 4200EL TCCD's and 4000+ just sitting here in boxes waiting for something to run them on.... but im becoming discouraged more and more everyday.
i can only hope that ALL the manufacturers of the ATI chipset will get it together soon......
Flash
It's not ATI's chipset, it's the power layout on these new boards. The eXpert is killing CPUs as well and it runs on the tried and tested NF4 chipset we've all been using. The power layout has to be faulty.Quote:
Originally Posted by flashnc
Yes...on the board where the two pins were burned it was a VDIMM and nearby GND pin that burned. On the single burned pin board is was a GND pin in the memory section.
Quote:
Originally Posted by STEvil
Huh? When will you guys get it? Running a CPU at close to 2V Vcore and 3.5+V VDIMM at -100C is asking for trouble. That is the only condition that I have lost a couple of CPUs. If you think that the board is faulty if the CPU dies under these conditions, then you aren't seeing the obvious.
I have tried around 100 Grouper boards all with high end CPUs over the last year (FX53,FX55,FX57, all the X2s) and never lost one that wasn't under the cascade and/or at super high voltage.
Quote:
Originally Posted by zabomb4163
look around these forums.....seems like 1/2 of the boards have killed processors. Why are we not seeing this with any other boards?
Sorry if this had already been posted. Thought it was relevant.
HardOCPQuote:
Now knowing that this certification program is in place, and ATI is launching their CrossFire motherboard press campaign with DFI motherboards, one would think that DFI would damn sure be on the certification list. WRONG. Actually, not only is the DFI CrossFire motherboard not listed, but they are also not listed as a partner in the program at all. Call me crazy, but it seems to me that if you are going to put all your eggs in one basket, it would certainly be a “certified” basket if I was running ATI.
Form my problems I don't know - I really can't see right now how it has anything to do with the ATI chipset.
I have built two systems on this board with no issues. One is a FX55, TCCD 1GB dual channel, X850XT PE and X850 CF. <---this system is running stock clocks and has had no issues. The other is a 4000+ @2.75GHz 1.5V, TCCD 1GB ram @ DDR500 2.7Volt, FSB 500, and a X1800 XL. (My big issue is the 2nd system is running RAID 5 and the softraid 5 is giving me trouble. I corrupted the RAID set when I did not have enough Volts to the CPU.)
I know many here run high volt on ram but I also remember many A64 chips losing mem controllers a couple years ago when people were volt modding their boards. (Turn the VR and POW! cpu was dead.) Also many SLI-DR boards had long term issues with the 5V jumper enabled. I personally like using ram that stays below 3V for anything but a single bench run.
The RDX200 does need some more bios work and I am concerned over running high RAM voltage but the issues are not ATI related.
My Halibut board runs flawless....same chipset.
IMO it should read DFI :DQuote:
Originally Posted by mikeguava
I haven't read the previous answers.....but i will tell my problems....!:)
First aff all i have tested on this board one FX57 2x3000 venice and one 3800 venice too!
1.Sometimes if you change some settings on the bios and then restart the machine(as always) it stucks on the second led and i have to power it off and then power it on again!Then it's ok!
2.I think that if you have small VID control ( >1.500) , when you start the machine , when it goes to the last led of the 4 it makes a restart automaticcaly and then boots normally!
3.When you have Vdimm more than 3.89 it doesn'e get to windows.....memtest is ok!!!
4.I think it is showing less 8-9C at the cpu!
All these with the new bios......!!!!¨)
grayskull your saying about 2V and -100Quote:
Originally Posted by Grayskull
but me was 1.4V and roomtemp.
so thats out of the question :)
but thats old news, the new news is that i'll get a new board tomorrow.
now i need to wait for my cpu rma .... :mad:
i stand corrected... :slap:
i guess i should have said "all those working with the ATI chipset"...i do realise it wasnt the chipset and something to do with the board voltages.
ok let me ask anyone this......i simply want to buy a board to run this X1800XL and 2x512 OCZ4200EL TCCD's on, that is crossfire ready ( even though i may not use crossfire till all the bugs are worked out and the x1800xt master obviously becomes widely avalible )
i have run asus for my last 3 builds and have always considered buying a DFI , though ive always gone asus for their reputation for stablility ( in my case they always have been ) and decent basic overclocking. :toast:
i oc with using basic mem and voltage tweaks, but i dont think i will try to delve into extreme oc'ing, though i do push things to the limit with my little bit of knowledge gleaned from places such as this. :stick:
i have preordered a A8N32 d sli ( i know, i know, why a sli board a crossfire card?? ) manly because it has some new technology, and wanting the best out there, that board in single pcie would be great i would think.....but then im stuck with buying a new board if i ever go crossfire which i will at some point.
so....do i get the DFI RDX200..run it with basic overclocking, and wait for the problems to be corrected???? or go with a single slot mindeset for now....?..
i dont see myself pushing high voltages..one of the reasons i went with the TCCD's.... i will run my cpu @ as high as 1.60 and...on water when testing oc, and probably limit my mem voltage to 2.9maybe just a little more.
sell me this board..... :stick: thanx
Flash
Also take into account that the boards Grayskull was killing the CPU's were most likely majority of the Sapphire mobo's, The DFI is based off a non-refrence design that is supposed to be more effiencient than the refrence ATi crossfire, as I've been reading, I dont think I've seen one single person state that the Sapphire boards are diffrent than the RDX.
Sampsa lost a 57 to the sapphire... At UNDER stock clocks.
Well here is another board;
http://www.xtremesystems.org/forums/...2&page=2&pp=25
ASUS A8N32 NForce4. Totally different implementation...same problem. it wasn't out more than a few days and already one death. Now check out the voltages 3.2V VDIMM. Coincidence :nono:
Quote:
Originally Posted by zabomb4163
What's your explination for that one Mr. Grayskull? And why have no ultra-D boards killed CPUs? Does this Asus use a new power regulation setup as well? I believe it does since its 8 phase or some crap.Quote:
i think my a8n32 is now defective. it's now taken a second processor..at completely stock.
And high VDIMM
Quote:
Originally Posted by afireinside
Because with NF4 ultra-D and DR-SLI we have to up vcore (auto/default wont work) to run >3.2V Vdimm...remember :)Quote:
Originally Posted by afireinside
With RDX and Expert theres no jumper and I can run 3.5V mem. with default vcore and kill my FX57.
Quote:
Originally Posted by mikeguava
Rectifying some assumptions...Quote:
Originally Posted by mikeguava
As per these photos of burnt CPU socket, the 3 pins are assigned for 2 of ground (VSS) and one for DDR SDRAM I/O ring power supply (VDDIO). These pins assignment were not affected by VCORE, FYR.
Note: Captured pages can be found within AMD 939 CPU datasheet from website.
My 3200+ is still alive and the board is performing good. Will have a Opteron 144 here in four days to test with aswell, since my 3200+ (Venice DH-E3) will only do 2.95Ghz
I have NO issues with this board other than the boot-problems [startup, detection & before the loading screen of Windows].
Another sad thing is the lack of SATAII, oh well. I'm still quite happy.
-k0nsl
Quote:
Originally Posted by Supreme_Evil
Hiya, welcome to the forums and thanks for your input!
On DFI Street forums Oskar Wu is asking to the ones with boot problems to download a small file to save current BIOS settings into a txt file.
Hopefully he can reproduce alot of errors and this will make it, hopefully, easier for him to see what is going on.
http://www.dfi-street.com/forum/showthread.php?t=29755
Hi guys,
I want to know if someone has noticed that with this MainBoard an huge Vcore Voltage is needed for reach a CPU stability in overclock :(
My CPU is stable only with 1,7V at 2520 MHz, like shown in signature :(
it's normal? :confused:
Bye
I am not finding that. CPU voltage to reach OC has been normal for me. I have a 4000+ at 2.75GHz on that board. Vcore is 1.5VQuote:
Originally Posted by ::Tiger::
ouch!! :eek:Quote:
Originally Posted by AACDIRECT
ok, so I suppose it's caused probably by the CPU :(
:owned:
DFI would supposed to be prior technical partner of ATi CrossFire motherboards (Click on this), regarding ATi certified motherboard program is certification of former non-CrossFire ATi based motherboards. Regarding the symptom you have (if you have) might caused by isolated incident since more users were purchased LANPARTY RDX200 CF-DR and system works properly. And the primary components were seems to be selected from high-end requirement; they should not affect CrossFire capability.Quote:
Originally Posted by Sheik
Above is for your reference.
got a new board today, i tried it with my superflower psu and it gives 4 leds.
wich is normal because i don't have a cpu atm... how does that come ...:p
tomorrow a friend will maybe pass with his venice and w'll test it together with 7800GTX:)
http://www.belgium-coolingsolutions....Postscreen.JPG
finaly got it up and running^^
Anyone know where I can check the CPU voltage with a multimeter?
Thanks
http://xtremesystems.org/forums/show...32#post1126032 ;)Quote:
Originally Posted by G-Man
Jort:
What kind of a grahpic card are you using? I wish my RDX200 screen would look that way ;)
-k0nsl
S3 Virge powah ^^
@Jort...Finally :toast:
Got to see some 3dmark05 scores. :explode:Quote:
Originally Posted by Jort
EDIT:
Had a awful day and posted something that was kinda emotional. For the beginning on I had attempted to be as objective as possible and want to remain so. So I removed what I worte earlier.
DFI thinks that part of my porblems were not related to to the board - rather to my CPU abuse and contamination. See below post by DFI.
I personally have an other opinion. But we'll leave it at that. X2 was running golden as well as my first FX57 that went ( not pictured - this one has IHS removed...lol). I really feel VERY strongly about another culprit involved but that remains to be seen
uh oh i hope they are not losing their edge in customer service, thats the one of the few reasons why most people give their unreliable boards the time of day, aside from high overclocks.
Hi, guys:Quote:
Originally Posted by mikeguava
Here is the content of report from DFI you have all been waiting for!
....................
Received two M/Bs and two CPUs from one of our U.S. customers, the condition of two CPUs listed below:
M/B 1: LP UT RDX200 CF-DR R.A02 S/N: D53900494 : During initial test, M/B booted up and loaded into Windows XP, and motherboard also functioned normal after an overnight burn in test.
M/B 2: LP UT RDX200 CF-DR R.A02 S/N: D54016042 : the analysis shows this M/B is damaged after used. The analysis report is listed below:
CPU: AMD Athlon 64 FX 57 : During initial test, it was able to load into Windows XP, however the metal pins of CPU have the sign of electric short caused by Heat Sink Compound stuck on surface of CPU metal pins (illustrated on photo 1~3), system will occasionally down by the changes of humidity and temperature in surrounding area.
CPU: AMD Athlon 64 X2 4800+ Dual core: the analysis verified CPU is damaged. The analysis report is listed below:
http://dfics.dfi.com.tw/dfi_cs//RDX2...ue/Photo_1.jpg
Photo 1
http://dfics.dfi.com.tw/dfi_cs//RDX2...ue/Photo_2.jpg
Photo 2
http://dfics.dfi.com.tw/dfi_cs//RDX2...ue/Photo_3.jpg
Photo 3
1. The damaged component is High site MOSFET Q6 on M/B PWM circuit. The damage was caused by U13(MOSFET controller) and surrounding area having contact with unknown liquid and consequently created a short phenomenon between 12V Vin and GND.(illustrated photo4 and 5) This electric short phenomenon contributed to the M/B sudden malfunction and permanent damage (burnthrough) in High Site MOSFET.
http://dfics.dfi.com.tw/dfi_cs//RDX2...ue/Photo_4.jpg
Photo 4
http://dfics.dfi.com.tw/dfi_cs//RDX2...ue/Photo_5.jpg
Photo 5
The damage analysis report of AMD Athlon 64 X2 4800+ Dual core CPU:
CPU appeared to have physical damages from its appearance. Those damages extended into CPU inner layer circuit board. The photos from photo 6 to 12 illustrated two corners of this CPU were damaged by severe external impacts.
http://dfics.dfi.com.tw/dfi_cs//RDX2...ue/Photo_6.jpg
Photo 6
CPU’s appearance has physical damages.↑
http://dfics.dfi.com.tw/dfi_cs//RDX2...ue/Photo_7.jpgPhoto 7
Enlarge 100X of CPU damages(left hand corner)↑
http://dfics.dfi.com.tw/dfi_cs//RDX2...ue/Photo_8.jpg
Photo 8
http://dfics.dfi.com.tw/dfi_cs//RDX2...ue/Photo_9.jpg
Photo 9
http://dfics.dfi.com.tw/dfi_cs//RDX2...e/Photo_10.jpgPhoto 10
Enlarge 100X of CPU damages(right hand corner)↓
http://dfics.dfi.com.tw/dfi_cs//RDX2...e/Photo_11.jpg
Photo 11
http://dfics.dfi.com.tw/dfi_cs//RDX2...e/Photo_12.jpg
Photo 12
How could this CPU function normal after this type of severe damages? And further more, a reasonable speculation of concerning the CPU might be the primary suspect damaged itself in the first place and in result of started to have effects and caused further damages on M/B.
Summary:
This unusual M/B component burnthrough phenomenon is a Single accident caused by inappropriate usage(unknown liquid penetrated into M/B electric circuit), and CPU was having damages by unknown external impact.
Both of this two root causes belong to inappropriate usage by customer.
Hiya Supreme Evil,
As you could have seen in my conversation with John Hillig ( ViperJohn) it was mentioned way early in our conversation about the condition of the X2 - I had written about this in my emails to support as well. It appears to me that the focus of your investigation was based on looking on the cpus rather what else could have caused this.
As far as the liquid goes - I had also said about the condition the CPUs were in when you received them were not in the condition when they were used.
Good job!
I hope you made sure that these residue of unknown liquid were in the appropriate loactions - or were they in a unrelated location?
WHat is the recommended Memory and at what voltages for the board?
Thats it..no more overcloking :)
Overlooked photo #5 - ouch! I wonder what that was. That certainly does look like liquid! Prooly was dried condensation from an earlier dry ice run. Does it conduct? Hehehe
I am moving on, gots other things to worry about.
Quote:
Originally Posted by Dumo
Doubt you gonna let your yellow box sit idle too long!
Quote[http://img105.imageshack.us/img105/1...shot0340gz.jpg]
@Mike..So, your 0516 is ok?
B/way yellow box will be mod for SLI and new and improved black box is coming ;)
I'd imagine so - like I said early in the thread I never tested it again and only assumed it was dead after having seen the burn marks on the socket. The board also still supposedly runs. Don't make fully sense to me, but I'll see soon myself.
In responding to Mike’s opinion, let’s look at Photo 4.Quote:
Originally Posted by mikeguava
On Photo 4, the area around Q6 and U13 is PWM area, primarily convert 12V power source to become Vcore for CPU power consumption.
Here we have an enlarge view of U13 on Photo 5; obviously you can see the stains on the U13’s pins.
U13 is a MOSFET driver, any damage on U13 will cause MOSFET sudden shut down, and MOSFET sudden shut down will lead to CPU power failure. This type of situation is highly possible to cause CPU damages.
However, from the evident received so far, it is still hard to reach any certain conclusion of saying which possible root cause happened first and triggered up the chain reactions to this set of M/B and CPU.
Also, this CPU issue is the only one case reported to us for over one month after the release of LP RDX-200 CF-DR. Therefore we would like to say that we still consider this case as a single accident, and of course, we will continue to observe users’ feedback on LP RDX-200 CF-DR and provide adequate customer service to you.
Here is some information you might find them useful.Quote:
Originally Posted by mikeguava
1.A list of momory sticks we have tested with LP UT RDX-200 CF-DR.
2.Voltages setting for LP UT RDX-200 CF-DR
In theory dried condensation could be conductive. Also when you were running maybe there was a little bit of liquid still not dry.Quote:
Originally Posted by mikeguava
I had a thought on the thermal paste on the pins. As you said AS Ceramique is non conductive.....so then it is an insulator. Right? IF some were on the pins could it not prevent a good contact. As the board tried to feed power to the cpu the poor contact would make for a higher load and also generate tons of heat. That would explain the burn mark too. Just a thought and my :2cents:
Sucks that you had the problem. Don't take this wrong but I really hope that the issue was related to user error. It would really suck if the board was a CPU killer. Install mistakes are easier to fix and we all make mistakes. (My last mistake was me wiring a SATA power wrong and blowing up a new HD....DUMB on my part. :am: )
how did you get AS Ceramique on the pins in the first place?
HOLY $HIT. Those have got to be a few of the coolest pictures I've ever seen of a cpu (sorry Mike). As per our PM's, I was trying to hint @ something to prepare you for what I had already knew ;) At least this whole ordeal hasn't resulted in a total loss for you. Hopefully, you'll be able to get the hw back up and running (although I'd personally be somewhat scared to try that mobo again :p: )........
Actually no - even if you throw in a ton of dielectric grease the pins will still make perfect contact.Quote:
Originally Posted by AACDIRECT
Quote:
Originally Posted by situman
that was after the cpu was taken out - I am pretty sure that it wasn't even Ceramique, but rather liquid from dissambling the waterloop after crash#3 .The CPU was laying by the side when things got messy. I have same looking white liquid on my mouse remote and keyboard - so I am 99% sure that's that it. The CPU had been discarded in a high traffic are of my workplace and was eventualy thrown on a couch where it even picked up some more dirt, before I shipped it out to DFI.
The CPU was basically new when I took it in the board and 100% not contaminated.
Wonder why there were burn marks below the sockets are a lot more appearant if something above the socket caused the shorts.
Quote:
Originally Posted by s7e9h3n
Yes kinda figured that.
You know also what I said about how well this particluar X2 did prior to this incidient. So that the CPU in itself wasn't bad at all - even with those corners - BOY they look awesome in extreme magnification! It ran like a charm, better than the 4600+ from you.
I know dielectric grease works that way. More specifically I was talking about AS Ceramique. I have never put any into a MB socket to test. (I have done some sub-ambient cooling so I know dielectric grease is good stuff.) I have heard of people using thermal paste as a substitute for dielectric grease. It was more of a specific thought to Ceramique used that way. (Obviously AS5 would not be so good used that way. ;) )Quote:
Originally Posted by mikeguava
EDIT: I have not personally ever used Ceramique or any other thermal paste other than how it was intended so this is more of a question..... could it be possible?
Sucks you have had this trouble.....nothing worst than having hardware die.
As was said before.....pretty cool pics.
Yup, I know you really liked that 4800+ of yours :( I'm telling you though, that 4600+ I got you isn't exactly what I'd consider an "average" oc'r ;) As the younger brother of OPB's god-like 4600+ (R.I.P.) your 4600+ ran a good 3-4C cooler than his @ the same Vcore. Although the memory controller wasn't quite as strong, it still is one of the better ones I've ever seen on ANY x2. A little OT, but did you notice a cold-bug with that cpu + ln2? Also, are you still planning to send it off to OPB for a few runs @ PCMark? I'm glad to hear the cpu is still up and running. OPB tortured his 4600+ and it handled everything like a champ - until meeting one very screwed up socket :p:Quote:
Originally Posted by mikeguava
hey mikeguava and dumo,
here it is.
http://www.belgium-coolingsolutions....800GTX/20K.JPG
http://www.belgium-coolingsolutions....um_cooling.JPG
http://www.belgium-coolingsolutions....ig_running.JPG
with 3dmark05 we got 97** max atm.
tomorrow benching 780 with ln² with teammembers:D
Dude!! You showed the Q-TIPS!! That is the biggest overclockers secret....now everyone will know how to get awsome scores. :rofl:Quote:
Originally Posted by Jort
try to mount an SP90 on a 7800GTX takes skillz, no everyone can do that.
We play open cards;)
Quote:
Originally Posted by AACDIRECT
hint: di-electric grease in place of thermal paste ;)
Thats the bug in the 704 bios for the NF4 series. However, my brother just noticed something on his DFI CF-DR. at auto, his volts were spot on for his x2. MANUALLY set to 1.3V no multi thing, just trying to get it a little cooler, smart guardian read 1.55V - the whole time.Quote:
Originally Posted by persivore
Personally, i think its a bios issue again with regards to Vcore and newer CPU types (fx57 and X2's seem the bad cores)
My brother was on the stock (shipping) bios: any bad luck with the new official beta?
The offical beta has been tons better than the shipping bios for me.Quote:
Originally Posted by Mussels
Ummm...mike's not exactly a noob - I think he would know if he installed a cpu and bent some pins in the process.....Quote:
Originally Posted by 3800venicecore
it could have got bent in the shipping, on the way to the RMA people. and i cant quite remember if this was the thread or not, if it was, he said earlier that after it died he just tossed it around a lot, even left it on the couch: damage ahoy.
New beta bios at last :) http://www.dfi.com.tw/Support/Downlo...FLAG=B&SITE=US
Cool...lets see how this one goes :)
I got finally my X1800XT and put all togother... and I have serious troubles with this mobo. It wont be stable if oc even little bit (FSB 210). Kind of common warning message is: "MS Windows has detected and recovered from device failure. Save your works..." And resolution before this message is dropped to 640x480. I think it's some how related to GPU card.
Edit: forgot to mention that this error-message come i.e. in 3Dmark when testing CPU.
this reviewer at vr-zone says the pci bus is not locked on the RDX200 http://www.vr-zone.com/index.php?i=2893&s=14
I think this is true as my pci adsl modem can't connect when i overclock to much :/
got to try this latest bios i reckon
Here is one thing that needs to be know? Is the Vdimm feeding both ram and memory controler? If yes then when upping the Vdimm you are upping the voltage beeing feed to the memory controler.
Is there a way to read the voltage to the memory controler to see if this is the case?
It's not the case.Quote:
Originally Posted by SnipingWaste
And if it is/isnt?Quote:
Originally Posted by SnipingWaste
Are you going to tell DFI/ATi how to design a m/b?
New beta bios has a bug and it doesn't show up the Sil3114 raid bios ... :confused:Quote:
Originally Posted by cyclepath
But ... the fixed the problem with the 4 leds when you enable usb keyb/mouse support .
say, with the eating cpu problem, is it just a select few motherboards, or 1/4 or 1/2 of the mobo's, and is there any way of finding out weather you have a hungry motherboard or not? i was hoping to get this motherboard, but i only work during christmas and spend all my monies on a pc...
and ited be kinda crap to keep on RMA'ing cpu's every 10 - 20 min that i get it...
Not every RDX200-CF DR is causing this.
I have been running with voltage avg. of 1.66-1.772 on
an fx 55 CH and the cpu its still very much alive.
Don't be scared, if you plan on going CrossFire or want ati chipset board
the RDX200 is best choice for what is currently available for CF boards. :cool:
I got the 2nd CPU back from DFI along with 2 new boards. The CPU still works like a charm!
Board #1 burn out could certainly have been caused by an earlier dry ice run - if the board got messed up without having an intitial damage, which then slowly but surely went further and then eventually killed the cpus. I have run NF4 lanparty boards full of condensation for 24hours for an extreme abuse test and didn't get any problems - this could have just been the one time it did have an impact.
The thing what made me doubt things is that all those deaths were caused during air runs.
Board #2 still is a real mystery to me - especially with the voltage rise that I had seen. I know for SURE that the cpu was clean - but that's all yesterdays news...
I do not know why the second board had the burn marks on the pin socket - I had actually taken both sockets apart and the "burn" were MORE appearent form below the socket. I suspect something wasn't perfect with that board - but didn't cause any damage to any hardware - and if only to itself :-)
DFI had sent me 2 new boards ( I told them to just send me the broken ones - since I had killed 'em...) and eventually I will fire them up again. But no gems will go in for now...but the both should be working great as they had been tested for a while by DFI
THIS IS EXCATELY WHAT I WAS REFERRING TO! BEING A POTENTIAL X2 KILLERQuote:
Originally Posted by Mussels
This is what happend to me with board #1 as well as with board #2
I hadn't followed this thread and just saw this. Now I am getting more suspicious again. I still have a brand new untouched RDX board from my first batch and will look for that again when I find the time.
One thing is sure - once all the bios bugs are sorted out - this will be a GREAT board!
Just came to my mind, that maybe my power is too insufficient for this set up? So what kind of powers you guys have? I mean u who have this mobo working fine.
i have a rdx with a 500W psu and its working fine now:)
UPDATE: I finally started up one of the new boards. Within 30mins I managed to get TWICE the same problem - where I get a huge boost in voltage.
There is no doubt in my mind that my X2 went due to the voltage jump that the boards can induce.
Things are becoming much clearer now. I had the voltage set to 1.4V and 104.8% and got 1.6V out (- ouch) and once 1.4V and 102.X% resulted in 1.56V.
The way this happens I am pretty sure is when you switch CPUs - the bios gets stuck in the start-up value ( 1.55V) and adds whatever % you have added. X2 4800 RIP! I will have to confirm that later - to find a sure way to reproduce this problem.
the board this happend was one from DFI directly and on bios 10/11. The boaord is REV3 and has none of the biosreboot problem ( which is nice!)