DFI RDX200-DR troubles

[mike]

UPDATE: Any NEW user of the RDX board should be leaving the CPU VID SPECIAL CONTROL option in the BIOS at default - when they first start a BRAND NEW BOARD- or serious trouble could arise !!!

ALSO THE BATTERY SHOULD NOT BE REMOVED





Either I am the unluckiest person in the world or there are some serious troubles with some batches of the DFI 200RDX-DR motherboard.

I was testing 2 different boards and have 3 dead CPUs at this point.

My first board killed a FX57 and a X2 4800+ , the second board just died along with another FX57 - funny thing while while typing a post in DFI-Forum about the first 2 deaths.

The boards were in their own indivudual set-ups - so no other commonhardware could have been the culprit - besides my bad luck which I had plenty lately.

[4rory]

Wow thats alot of money you just lost.

[jetjaguar]

id wanna kill someone if i lost 2 fx-57s and a x2 4800+

[mike]

At first I wanted to kill myself - when it happen on board #1 I tried to trouble shoot what went wrong with the first FX-57 and stuck in a 4800+ which shortly died as well. Bad luck I thought.

But when now it happend with board #2 with another FX57 on a complete different setup I decided against suicide...curious o see how DFI will react.

[Victorshen]

ggggeeeeeezzzzz

what happened?
mind give us some more details?

[bachus_anonym]

Sweet jebus! That's over $3k in CPU's. Any chance to recover anything from that? Any ideas or hints of what might have happened there? How did that happen? Any particular pattern? Are you 100% positive CPUs are dead?

[mike]

2 CPU I know 100% that are dead - the FX57 that went 20mins I am not sure yet - but from the burn marks on the socket - I have no doubt that it is a goner too. I am hoping that DFI will find a solution to make me less angry...

[mike]

Board 1 - the little balck spot is a burn mark in the socket

[mike]

Board # 2 - this bard has 2 burn marks and are in a different spot.

[zabomb4163]

no DFI 200RDX-DR for me or any of my freinds now...

[mike]

Maybe it was a bad batch of boards. The only pattern that I could see that ITE Smart guardian would sometimes show odd voltages.
Normally it would read ~1.4V and after a reboot it would read out of the blue ~1.65V. I had seen this happen with the first board but at that point I thought that there were problems with the Smart Guardian, especially with CPUZ not reading voltages etc. I had suspected that something is fishy with voltage regulation of the board, but couldn't prove it nor pinpoint it.

But when it happened earlier today with board #2 I got very suspicious and was just about to post something in DFI-Street forums about it, when all the sudden in the middle of typing my screen immediately went black. How ironic. The cpu at that point was running at 1.8GHZ ( 9X multi, 200FSB, 1.4V )

[Supertim0r]

can't you rma your cpu ? If it's the DFI fault you'll have to get a refund from DFI

[revenant]

O M G . . . that sucks. wow... sounds like a bad batch of boards... like some of the contacts under the sockets were too close together and shorted? I am no mobo mfg, lol, but that's my WAG... yeah, I am all ears as to what DFI has to say about this.. whew... crazy!

[Absolute_0]

just curious, what PSU was being used?

[Dumo]

Maybe it was a bad batch of boards

Mike, what s/n?......Mine D539005XX. I believe is the first batch for sale here...

[elected]

Hi fellas!

I have read similar things happening to the FX-57s in muropaketti (finnish). Apparently Sampsa, The Stilt and macci have all blown one FX-57 each while testing the Grouper board. Macci's FX-57 only works with 2x256mb memory so they think it might be a memory controller related issue.

Another finnish user also reported similar things with his 146 opteron while using the CF-DR (computer froze while lowering multiplier and it only works with 2x256mb memory). Luckily his opteron came back to life when he overvolted it with 1.7 vcore.

Sampsa asked ATI support about this but apparently they haven't seen anything like this in their testing. I was looking forward to buy the Grouper myself but all the delays and now this problem forced me to go with the DFI nf4 ultra.

Please remember that this is all second hand knowledge and I'm sure they will post their own findings soon...

[Psyche911]

Hi fellas!

I have read similar things happening to the FX-57s in muropaketti (finnish). Apparently Sampsa, The Stilt and macci have all blown one FX-57 each while testing the Grouper board. Macci's FX-57 only works with 2x256mb memory so they think it might be a memory controller related issue.

But the memory controller is on the CPU...

[babyelf]

i think he meant after the FX57s were blown?

[revenant]

There is some sort of memory controller on the mobo also I would think... the pathway on the mobo between the cpu socket and the memory slots has to be controlled by something.

[elected]

But the memory controller is on the CPU...

Well I'm not the expert on the subject but from what I have read they think that the mobo might break the cpu's memory controller or something.

[G H Z]

Wow, I'm glad I didn't run my board yet. I would not be happy if I lost my 0516 WPMW....

[Dynasty]

I have two RDX-200's sitting here, one is in use S/N is D54015xxx.
Second board still in box un-opened. I am running an FX 55 SD on the board with 1.5V nothing odd to report. No voltage spikes, no power surges.
All is fine for now. But, I am little concerned now reading this.
I don't want to mount on phase and lose an FX 57.
DFI really needs to look into this matter thoroughly.

[kiwi]

hmm, this is very strange. Really sad to hear that.
From the picture I can see that only 1 or 2 cpu socket pins are burnt. Are there any burn marks on the cpu itself? If you can't get cpu RMA you might wanna try replacing burned pins. Not on this board though.

[alpha0ne]

Very sad to hear of your loss mikeguava, you must feel shattered

I really hope DFI play fair with you on this, myself and thousands of other DFI users will be watching this thread very closely

[Sampsa]

Yes, I've managed to kill one FX-57 CPU with Sapphire's Grouper motherboard. Although it's based on ATI's reference design unlike DFI's mobo.

I was testing my Redline XP 4000 memory and ran CPU at default voltage and default cooling. When I succesfully ran spi8m @ 250 MHz and took a screenshot the system froze and never woke up again.

CPU is dead and the reason is unknown. All I know is that I turned the power off from PSU after system froze. No burn marks or anything in socket or CPU.