• Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

Xeon in Asus X99 Sabertooth

Associate
Joined
17 Mar 2009
Posts
2,475
Location
Scotland
Hi guys I'm having to strip my dual socket build due to boot fail on my Z10PE-D8-WS.

It has the following chips Xeon HASWELL V3 2.20GHz Processor QEY6 14-CORE LGA 2011-3 which worked fine until one day no boot no usb power or display. There are engineering samples which ran for a year with no issues.
I had been trying to update the BIOS and install WIN10 when everything just went pear shaped. Have atttempted usb flash of BIOS but no change.

Anyway I'm wondering can I test these cpu's in my X99 Sabertooth board?

Asus support states that board will support Intel Xeon E5-2697-v3 (2.6G,145W,L3:35M,14C,HT) which is a higher clocked 14 core mine are 2.2Ghz.
 
Hey Colin, Ouch.

what error code is the motherboard giving ?
Imo it is more likely that if the issue occured when updating the bios the cpus are likely to be fine still.

Maybe it was a failed flash (It takes ages to flash with no visual feedback, so are you sure you let it run it's course. Last time I did it I went and had a coffee).
Or the new bios doesn't support the ES Chips you have. - meaning you'd likely need to borrow a retail chip to flash back to a older bios.

Surely it will be easier - just to try 1 cpu in the current motherboard. just as you would check ram.

You 'should' be fine to test the chips on the sabertooth too.
 
Ah man I just flashed to and even newer BIOS and when I powered up the board it went pop and smoke started pouring out of it, quickly pulled the plug but I think its well and truly dead now.
I'll have to pray the cpus are ok. I'm gutted :(

It was hanging on QCode 69, I left it for very long time just in case but nothing happened no display no usb power to mouse or keyboard either. I guess it all irrelevant now :(

Got made redundant to so can't just go buy another :(
 
For sure - after an event like that, do not plug it in again.

A bios update should not cause smoke.
Either watercooling leak, psu failure/arcing due to loose connection, or just a failed component. - It's worth contacting asus, you should be able to RMA.
 
Edit: hmm in daylight the crack isn't actually on the pipe but on the collar and only on the surface I don't think it was a leak after all.
 
Last edited:
Awwe that sucks. One of the reasons I did not sex my system up. Once it was running fast and stable I was too much of a wimp to make it snazzy. Your systems always look fantastic !

Maybe still worth contacting Asus - they maybe able to repair it at a cost, I'm not knowledgeable in such matters.

Or even possibly household insurance for accidental damage. - However you always pay for claims in the long run. Trying convince them that such a system was for home use will be interesting.
 
Yeah I'm gonna have to take it on the chin thanks for the advice though mate. I'll try the cpus tomorrow, haven't got the heart to do it tonight I've found the experience rather upsetting. I'll certainly think long and hard about WC in future.
 
It might be ok once its dried off? I spilt a cup of water on my pc once, It cut out. I tried the pc every day for a week, it kept cutting out, then, once it was dry, It turned on and continued to work for a year until I realised that pentium D's suck and so bought a C2D setup.
 
It might be ok once its dried off? I spilt a cup of water on my pc once, It cut out. I tried the pc every day for a week, it kept cutting out, then, once it was dry, It turned on and continued to work for a year until I realised that pentium D's suck and so bought a C2D setup.

I don't think so mate, the smoke coming from the capacitors was enough to tell me its not gonna survive being powered up again, if it does have any life left.
 
Ah, I missed that bit. Yeah, probably not worth further risking your other components by testing in that board then :(

That sucks man. You have my condolences, and I hope your CPUs make it through.
 
Back
Top Bottom