Try 2.11 someone else reported an issue in the 2.12 ( http://forums.evga.com/EVGA-X79-Dark-BIOS-212-Released-m2205283.aspx ).

You can flash any BIOS revision you want.  In my experience, rev 2.10 has been solid.  No issue's.

Let us know how those BIOS rev's work out for you or if you have any other questions...

I'm not sure what to make of all those crazy readings.  Look how low your +3.3v reading dropped to as well.
 
Are you running any other monitoring software while you have the HW monitor running?  If so, shut those down to see if it makes any difference.
 
Also, do you have "Internal PLL Override" enabled in the BIOS?  If not, try enabling it.  (may not make any difference, but worth trying)
 
I use Aida64 Extreme to do all my monitoring and have never seen anything like what you're seeing.  As far as software monitoring goes, I've found it to be the most accurate.  You can get a trial version and info here >>  http://www.finalwire.com/
I've been using this (paid version) for years.  Wouldn't be without it.
 
Do you have a spare PSU to try out in case your current one could be causing power issue's?

Akriant

bdary
I'm not sure what to make of all those crazy readings.  Look how low your +3.3v reading dropped to as well.
 
Are you running any other monitoring software while you have the HW monitor running?  If so, shut those down to see if it makes any difference.
 
Also, do you have "Internal PLL Override" enabled in the BIOS?  If not, try enabling it.  (may not make any difference, but worth trying)
 
I use Aida64 Extreme to do all my monitoring and have never seen anything like what you're seeing.  As far as software monitoring goes, I've found it to be the most accurate.  You can get a trial version and info here >> 
I've been using this (paid version) for years.  Wouldn't be without it.
 
Do you have a spare PSU to try out in case your current one could be causing power issue's?

1. Nope, I've turned off all other monitoring software, and left only Prime, control panel and HW running during the blend test.
2.PLL Override is enabled.
3. I thought Aida 64 Extreme only showed real-time readings @  trial version, so I wouldn't be able to see those spikes, unless I glue myself to the monitor for 5h+ during the course of the test.
 
P.S. I'm using 2 y.o. Lepa G1600 PSU, so plenty of power there.
 
How accurate is EVGA's Eleet?
 
 

Hmm, you may be right about Aida's trial version.  Been several years since I used it before buying.
 
You could try Eleet for a comparison to what HW is showing you.  At least you'd have a comparison.
 
Yes, your Lepa is plenty of power.  I am just wondering why HW is showing such strange voltage readings?  From out of spec rail readings to the various voltage spikes you referred to??  Trying to narrow this down to hardware or software issue's.

It's possible the extension cables could cause these issue's.  Try using Eleet to see how the numbers compare to when using HW.  Hopefully it's a reporting error in HW's software.
 
I wouldn't spend any money on a PSU yet until I tried to rule out software or possibly a mobo issue.  I only asked in case you just happened to have another laying around.

Akriant

bdary
It's possible the extension cables could cause these issue's.  Try using Eleet to see how the numbers compare to when using HW.  Hopefully it's a reporting error in HW's software.
 
I wouldn't spend any money on a PSU yet until I tried to rule out software or possibly a mobo issue.  I only asked in case you just happened to have another laying around.

Well, I have OCZ 850w GOLD PSU (*shudders*), but it's only for the darkest day, or the blackest night, that thing coil whines like crazy.
Yeah, I'll do some testing with Eleet tonight.
I really Hope it's HW misread, rather than psu or mobo (especially the latter, I've just put up my loop together), but it might be PSU ----> my previous system would go unstable, if psu was turned off from the power for couple of days, and I'd have to reset, and then run prime for 2mins, then reset again, and then put in new OC settings, and then it would work. (Msi Xpower II mobo)

That's interesting.  And that was happening with your current PSU I take it?
 
Yeah, test it out with Eleet when you have time and see what you get.  You have the OCZ PSU to fall back on at least for testing purposes if need be.

Eleet shows only real time volgaes, just checked, as well as Aida 64 Extreme (on trial mode).
 
On a side note: After 5h of Prime and 2h of gameplay last night, I've got back today home, and I'm getting constant 09C BSOD ever 30 minutes or so =\, aside from Vcore, what may be causing it? VSA sagging @ Intel Spec setting in Bios? or VTT? (VSA set at 1.188-1.1196, VCCIO set at 1.155) (running 32gb ddr3 1866 Gskill Ram, tried XMP, tried manual, tried 1333 with 11-11-11-30 timings -> still getting the code. Last night was going fine, today this mess, RAM from previous build, had it memtested for 24h with 0 errors on last build, so idk).
 
Update: Error code on mobo is usually 51, 52 or 53. Even with one stick. 0_o

I will do just that, when I'm done with testing. What I am seeing is that (and right now I don't have a multimeter on my hands, so I can't confirm my suspicion) in-bios Vcore readings might be severely off. Why am I saying that? Well, when I pumped 1.37v through my 3930k back in Xpower II, I  was getting up to 70c on some of the cores @ 4.5/4.6ghz. With this board, using the same tim, same waterblock, same rads, same pumps and having roughly the same room temperature, I am barely hitting 60-62c on cores. The board claims that vcore is at 1.36v, but HW monitors implies that it might be 1.32 actually, with dips to 1.305. If that is the case then no wonder I can't get it stable. (although I did 2.5h of prime today at 4.2ghz from coold boot, and same yesterday before going to bed, at 1.28v, and that worked well it seems). I'm going to grab a multimeter to see what's really going on, in the mean time I'm increasing vcore by 0.005 increments. If the readings in bios are really wrong, then that's why I might be getting 09c as well.

AAAAAND an Update:
I've been testing it all day back on Wednesday, tinkering with Vcore. Installed OCCT to test + see the readings. Basically Vcore is 1.32 under any software aside from Bios and eleet. Still waiting on my multimeter to arrive on Monday. But back to my progress: 4h of OCCT, and then all next day stable as well @ 4.3ghz with that Vcore. I'm away from my rig for the weekend, but if things keep up the way they do right now, I'll prly be able to hit my 4.5 ghz at that rate.

bdary

Akriant
AAAAAND an Update:
I've been testing it all day back on Wednesday, tinkering with Vcore. Installed OCCT to test + see the readings. Basically Vcore is 1.32 under any software aside from Bios and eleet. Still waiting on my multimeter to arrive on Monday. But back to my progress: 4h of OCCT, and then all next day stable as well @ 4.3ghz with that Vcore. I'm away from my rig for the weekend, but if things keep up the way they do right now, I'll prly be able to hit my 4.5 ghz at that rate.

Sounds like you're getting everything dialed in...
 
I do have a question though.  1.32v vcore under any software reading??  That's pretty bad.  Aida64 reads pretty close to what is set in BIOS.  Personally, I wouldn't use any software that would give me voltages that far off.  That's (1.32v) more vcore than I use for a stable 4.5Ghz OC with Vdroop enabled.

Well, each chip is different.  I had to make a jump from 1.27 for 4.2ghz to those 1.32 for 4.3ghz. 1.32 (1.31 under load). 13.2vcore via CPU-Z, H-W monitor, AIDA 64.

bdary
I would suspect a reporting error if it was one program, possibly two, but all those reporting the same thing that far off.  I would suspect a sensor failure.  The only thing that keeps me from feeling 100% about that is, you mentioned in a previous post that Eleet reports correctly as well as in the BIOS.  This is strange.

Yeah, but I'm not worrying, temps are fine, and tomorrow I'll get the actual multimeter readings

Any feedback on this yet?