DFI RDX200-DR troubles

[::Tiger::]

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.5V

ouch!!
ok, so I suppose it's caused probably by the CPU

[Supreme_Evil]

I have had nothing but trouble with this board from the moment I got it

I am experiencing the exact same problems as this.

http://www.hardocp.com/article.html?art=ODg4

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.
Above is for your reference.

[Jort]

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

[Jort]

finaly got it up and running^^

[G-Man]

Anyone know where I can check the CPU voltage with a multimeter?

Thanks

[persivore]

Anyone know where I can check the CPU voltage with a multimeter?

Thanks

http://xtremesystems.org/forums/show...32#post1126032

[k0nsl]

Jort:

What kind of a grahpic card are you using? I wish my RDX200 screen would look that way

-k0nsl

[Jort]

S3 Virge powah ^^

[Dumo]

@Jort...Finally

[AACDIRECT]

S3 Virge powah ^^

Got to see some 3dmark05 scores.

[mike]

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

[situman]

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.

[Supreme_Evil]

Looks like DFI is sticking me the middle finger - Dielectric grease was the cause of all my troubles according to DFI, as well as some AS ceramique on the bottom of my CPU - LOL. Dielectric grease and AS ceramique are not conductive.
X2 haveing been dropped previosuly and having bad marks on the corners was obivously the cause for that one to go ... Well the chip really looks like hell - but it was benching at 3.4GHZ overl:banana::banana::banana::banana:ed even with it that superficial damage. It was running 24/7 on a DFI nF4 board until I ripped it out to check out RDX board. BS

Having a FX 57 without IHS obviously is the cause of dying...I am not going to argue with them.

DFI rules!

Hi, guys:
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:


Photo 1


Photo 2


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.


Photo 4


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.



Photo 6
CPU’s appearance has physical damages.↑

Photo 7
Enlarge 100X of CPU damages(left hand corner)↑


Photo 8


Photo 9

Photo 10
Enlarge 100X of CPU damages(right hand corner)↓

Photo 11


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.

[mike]

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?

[Dumo]

Thats it..no more overcloking

[mike]

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.

Thats it..no more overcloking

Doubt you gonna let your yellow box sit idle too long!

[Dumo]

Quote[]

@Mike..So, your 0516 is ok?

B/way yellow box will be mod for SLI and new and improved black box is coming

[mike]

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.

[Supreme_Evil]

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?

In responding to Mike’s opinion, let’s look at Photo 4.
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.

[Supreme_Evil]

WHat is the recommended Memory and at what voltages for the board?

Here is some information you might find them useful.
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

[AACDIRECT]

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?

In theory dried condensation could be conductive. Also when you were running maybe there was a little bit of liquid still not dry.

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

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. )

[situman]

how did you get AS Ceramique on the pins in the first place?

[s7e9h3n]

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 )........

[mike]

In theory dried condensation could be conductive. Also when you were running maybe there was a little bit of liquid still not dry.

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

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. )

Actually no - even if you throw in a ton of dielectric grease the pins will still make perfect contact.

how did you get AS Ceramique on the pins in the first place?

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.

[mike]

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 )........

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.