Printable View
Interesting - your temps are a bit higher than mine were, considering that I was on air. On the other hand voltage is slightly higher and possibly other parts in your loop cause a little warm up also.Quote:
Originally Posted by OPPAINTER
Rig #1 was on BH, Rig #2 was on TCCD - and I also had much more problems with the TCCD running proper. Looks like it's in the design of the boards to favor Bh/utt
My system is completely incased with low fan RPMs for the Radiator, intake, and exhaust. The quiet solution:D This would explain my temps. I also cool the vid card with the water loop.Quote:
Originally Posted by mikeguava
OPP
http://www.xtremesystems.org/forums/...id=39592&stc=1
Not to offend the OP and the other dude with the blown FX, but there are alot more people that have no cpu issues(###) then there are with(2), so it doesn't seem to fair to put a such a label on these boards just yet. When different people start loosing cpus left and right, then i think such a label is justified. It's just my oppinion i guess :p:
I guess it looks like I'll be testing my dfi cf with a 3000, looks like the 175 will have to hold off on testing for a couple days. What bios were u guys using when your boards died Mike and Sampsa?
well, it looks like the SLI DR Expert is for me....
I can barely afford hardware as it is, without having to deal with a motherboard thats getting a reputation for destroying CPU's...
Good thing for ClawHammer's as they can with stand higher voltage
then both Toledo and San Diego cores. I just mounted my FX 55 ClawHammer
on Vapo LS to RDX-200. Going to run it atleast 14-16 hrs for next two days and see if anything goes wrong with cpu. :cool:
P.S:This could be more of an isolated situation then we think it is.
I don't think RDX-200's are plagued with this.
Lets hope not. Still it's something that needs to be looked at further for everyone's benefit. I'm sure Mike would not have posted about this if he didn't feel there was good reason.
wonder if DFI will react the same way to this as they did to the 5V jumper on the ultra that killed memory. how many people lost memory before the doubters stopped blaming the user?
mikeguava I'm so sorry for your lost .
My dream for the ultimate mobo just came to a crashing halt.:(
Time to look at the nf4 expert I guess
Remember guys, EXPERT have the same 4-phase that CF-DR have..
I hope the fault is'nt in 4-phase :(
I would..Quote:
Originally Posted by jetjaguar
I'm sorry to hear about your losses. It's really extremeley annoying to lose 3 top caliber cpu's on one board. And I appreciate that you still act very calm about this matter.
I'd like to say that I've also been using A RDX-200 mb with FX57 for the last two weeks. At first I have the high htt problems like everyone else has here. But with the latest bios from DFI this problem is history now. I think that your board could be faulty or there's a power issue in your rig.
PS: About the 1.48 cpu vcore, I gave it manually from the bios in order to overclock the cpu a bit. It's not a mb issue ;)
http://www.geocities.com/baseskiozan/280mhz1m.JPG
dfi boards killing ram..now cpus???
i also read in a review about the sappire ati board that also killed a cpu during testing..
I agree with you, it's too eaarly to be to pessimistic about the boards. I do not want to discredt DFI nor ATI - I think both companies makes some of the best product out there on the market.Quote:
Originally Posted by Diverge
To give a bit of background and my reason for this posting here a bit more detail about my experience with the RDX.
I have been building high end computer-based FX and videoediting system professionally for more than eight years and am currently also involved in a PC related endevour.
In my past I have never ever had any hardware failure like this happen to me before.
On the intial runs with the new board, I only focused on getting crossfire to work properly, which created many headaches for me.
I had previously managed to get the board very stable with plenty of overclock headroom if it was to be needed ...
But at the time when all my troubles started I was running bone stock - to ensure that I can properly troubleshoot Dual GPU Crossfire related issues I was having.
Again during my CF testing the sytem was bone stock, ram VERY loose . CPU often times running with a 12X multi.
Cpu and memory monitoring were only given secondary attention, but I had noticed several times that voltages didn't make fully sense to me - some voltage jump after reboots etc.
I noted this in the back of my mind to be something to look at, at a later time and made an half-hearted attempt to find the voltage measuring points for a multimeter to monitor the VDD and VCORE. I posted something in that respect in dfi-street, but at that point never looked into it. Dual GPU was my priority at that point.
I was during at 3DMark05 run that my first FX57 suddenly died. I tried to reboot the system and it would immediately shut down again.
I thought somehow the bios got corrupted etc, and was slowly but surely eliminating any component step by step to find the source of why the system wouldn't start anymore.
I finally put in the X2 4800+ and the system - and it did boot again. My first reaction was ":banana::banana::banana::banana: - I can't believe my own personal golden FX57 died - man that's weird. "
When just a couple of minutes later the X2 went, I started to think that the board did this. But I then I reasoned that the FX57 might have damaged the board - and now the board killed the CPU in return.
These were my first reactions - but the more I thought about in retrospect - the more I felt that the board had caused this, remembering the voltages jumpos etc.
I shared this sentiment with various friends PRIVATELY, told them how and why I felt the board had caused this but took things with stride, because I couldn't be sure on what the reason really was.
When yesterday I started testing board # 2 with a virtually brand new FX57, I made sure to pay very close attention on how the board behaved and kept a very close eye on Smart Guardian to dectect any unusual voltages changes.
After a reboot all the sudden I had seen ITE SMart Guardian read 1.64V or 1.68V ( don't rememeber for sure - I immediately shut the PC down). As soon as I saw this voltage increase, I felt much more certain about what the culprit for my previous terminal hardware failure was.
The next boot voltages seemed fine again and I rushed off to the support forums at dfi-street.com to make a posting about my suspicions and troubles.
In the middle of typing my story, the system all the sudden went dead - and my worst fear came true.
At this point I can only assume that the culprit of my troubles were the boards - each board was in its own setup every single component was different for each board - PSU, RAM, GPU, HDD were all different. The ONLY common part they shared was a 2000W UPS system to supply clean power. I am willing to bet all that I have that the UPS was not the cause. One board was shipped by UPS, the other by Fedex -well the only other common denominator is me and Miami...
I want to stress again, that it might have been just a bad batch of motherboards that I received, maybe it was the worst luck ever. I do not want to make any assumption whether it was the power regulation, ATI chipset etc. - just something went very very wrong - and two seperate DFI 200RDX-DR apear to be in the middle of everything.
Do you rember where the review was?Quote:
Originally Posted by calcal
xbitlabs.com
Been a lurker for a long time, but wanted to post a thought here.
Is it possible it isn't a board issue at all, but a BIOS issue again? BIOS 704 for perfectly fine nF4's had an issue with certain cpu voltage combinations that did result in dead CPU's if I recall correctly. It would seem possible that those with dead CPUs used those combinations and others did not? Maybe avoid the +1xx% settings for a while and just use the regular VCORE setting...
Just a thought..
good pointQuote:
Originally Posted by wjkandl
I don't think bios is too blame when burn mark appear in cpu socket.Quote:
Originally Posted by wjkandl
This pic was from Mike's board:
http://img360.imageshack.us/img360/4...20817ab.th.jpg
*** Read Below ***
I believe we shouldn't jump to conclusions here. Sampsa lost a CPU on a different board from Sapphire, not the DFI one, and other members have also provided proof that their boards are working fine, with minor memory related issues.
While I do believe MikeGuava is being sincere with respect to the problem, this may very well be an isolated incident FOR THIS BOARD. In no way are there CPUs dying everywhere on this board. I imagine DFI goes through extensive testing on many different CPUs before they release it to the public.
It is always up to members to purchase a motherboards they like and many factors go into getting the one they want including compatiblity and such, so it's fine if you would like to see this issue addressed before making a similar investment, but please keep in mind that there is no concrete and consistent evidence that the extent of MikeGuava's problems, which we all sympathize with, represent the majority of motherboards in question here.
Thank You.
Perkam
wow mike, sorry to hear :(
thx for sharing this with everybody so people can watch out if their boards act weird too.
was the vcore jump really fast? from 1.4 to 1.65v suddenly?
how long did it stay that high? just for a second?
what bios were you running?
what psu?
any mods on the board or psu?
what vdimm?
what vtt?
any unusual settings you tried?
I think you also have a point here. With my second RDX board it was the combination of 1.425V + 102.5% that caused the jump to 1.6xV. I can't fully remember the combination of the settings when I was running my first board.Quote:
Originally Posted by wjkandl
Really sorry to hear this, Mike :( Let's hope that this will be concluded soon so we don't have to quess anymore reasons for this.
How ever, this doesn't change my mind. I was, and I'm going to get this board as soon as they got some x1800 xt's in stock to Europe.
The RDX200 is using the same Vcore regulator as the NF4's. The only difference is the fact that the 4th phase has been put into use on the RDX. If there is an issue with the board killing CPU's, I would say that its probably BIOS related, and nothing to do with the regulators implementation on the board.
I've been running a 3700 in my board since Thursday, and I've not had any problems with Vcore spikes or dead CPU's etc. I've had a DMM connected to the Vcore supply and I've seen no noticable spikes either.
Quote:
Originally Posted by saaya
Actually I wasn't clear about the voltage jump - it is not that within Windows the voltage changes - it is that with a reboot the voltage is suddenly higher. This is what makes me believe that it could potentially lie within the bios.
I had the Vcore set to 1.425V +102% - when I saw the jump to 1.6?V
The first CPU went with the stock shipping bios, the second with a beta, the third with the latest released bios by DFI.
The hardware for board #1 were:
FX57 / X2 4800
Geil ONE BH ( 3.4V)
X850XT CF / X850XT
T7K250 HDD
OCZ PS 600W PSU
Specs for board #2:
FX57
G.Skill 4800LE ( 2.7V)
X850XT
Seagate 7200.9 HDD
Aspire AS680W 680W PSU
I didn't try any unusal settings at all, had all non essential mobo components turned off ( 1394, SIL, Audio IRDA etc. ) LDT 3X, HTT HP enable, 200FSB, 166 mem divider,very loose mem timings.
PSU and Mobo were all stock - PSU voltages set spec with DMM - clean power supplied by a UPS