ohhhhhhhhhhhhhhhhhh, I did solve the exactly way, tried even Supermicro that made me buy v2 CPU, hence, v2/v3/v4 cpus... all fail... we did swap the motherboard and it work. One of hte things I did request for the DC guys was to check for grounding points that will explain this result very well...hey @tconrado did you manage to get this fixed?
I just did some critical server maintenance yesterday and when i put it all back together again, I got DC detect failure for the first time ever. It turns out that you get that problem if the memboard isn't inserted all the way into the mobo. It also turns out that some memboard connectors are thicker than others!!!! One of my memboards can literally only fit into one slot and none of the others (it won't even go in when I sit on it, yes - I did that - don't try that at home.)
So when I returned that memboard to the slot where it "belonged", everything worked fine after that. Maybe it was a similar case for you? If it were up to me, I would check all the pins in the mobo connector. Memboard issues are almost always an issue of geometry.
Also, after taking the motherboard out I noticed that there were more standoffs installed on the backboard than necessary. Now I bought this system entirely prebuilt. These metal standoffs were TOUCHING THE METAL TRACES ON THE BOTTOM. I was absolutely furious. Whoever built my system deserves a slap in the face. But anyways after taking the unnecessary ones out, all my system's issues spontaneously resolved. This could also be the case for you!! Maybe the metal standoffs have been shorting something important!!
To anyone else reading this, if you get a persistent VBAT lower non recoverable (nr) error even after swapping for a new CMOS battery, updated IPMI firmware and BIOS (which is the first thing that Supermicro would tell you to do), in the absence of visible damage of the motherboard, check the standoffs under the motherboard.
so the best part: did u notice any difference between the rev of the boards? I think Supermicro changed the boards and did properly mention it!