We've been waiting for months... Would be nice to know ETA, at least.

Hopefully more, until s2011 is out, tbh...

I was wondering if I need to start with the 1st update for the (170-BL-E762-A1), or will the newist one have all of the old updates?
 
Also should I buy a battery back-up system for my computer? I have a lot of money into it and it has all new parts + I have a 3D screen, I would have it already if it was not $1,500.00, or is it just alright if I don't have it. My home's power is unreliable.
 
Please Note: all parts are mostly EVGA. Including the 1200w power supply. Thanks EVGA, keep up the good work.

with evga boards and their phoenix bios,is there a standard set of switches used when flashing the bios?.
i remember abit had a specific string,and in this forum i have seen a couple different examples,some without the R for restart,some not saving the old bios etc

Now are you 100% sure about this? Also will it have all the old ones in it?

dejanh

Use /Wb /cd /cc switches only when flashing.  Reboot and restore defaults, then save and reboot again, then adjust as needed.

thanks for your reply,and that link on all the switches and thier meanungs

New bios now please.
 
K Thax!

dejanh

Alucard666

New bios now please.

K Thax!

That's the spirit!

Keep hoping

 
Sometimes it's all we have left ;-)

I'm guessing double pumping when VT is on will never be fixed? :(

Alucard666

davidgomez79

I'm guessing double pumping when VT is on will never be fixed? :(

system still double pumps when bios changes are made.

This is normal though, isn't it? I know this has been the case with the past few Asus boards I've owned.
 
The VT double pumping is a bug I'm pretty sure. Hopefully they fix it soon.

lam_das

Let me throw in the shout out for S3 issue. Please fix S3 issues with Rev 1.1 (newer rev) of 758 boards in the next update.

 
Random observation re S3 problems: it may very well be a BIOS bug, but there's some OS and app interaction involved as well - at least on my 1.1 machine.
 
I had plenty of S3 problems early on: occasional hang going to sleep, more frequent hang shutting down after a successful sleep/wake.  At some point things got stable other than some ridiculous reported temps in eLeet after a few sleep/wake cycles.  I couldn't pin down what had changed, so I didn't post anything about it.
 
Recently I changed my old security setup (Avast Free and Sphinx firewall control) and installed ESET Smart Security.  My old S3 problems came back :(  I lived with it for a few days to verify that it wasn't just an unfortunate coincidence.  Uninstalled ESET, reinstalled Avast and Sphinx, and S3 has been stable since.
 
I don't mean to let my friends at EVGA off the hook on this.  It may be/should be fixable in BIOS.  Maybe this kind of interaction explains why not everyone has problems with S3.
 
[edit] To be clear, I'm not saying it isn't a BIOS problem.  This post was an attempt to add another data point - whatever that's worth.  To toss a little more *stuff* at the wall: I'm not overclocked (except running RAM @ spec) and the weird eLeet temp is a reported system temp _below_ ambient.
 
Z.

after i updated my bios to 77 there is no more option for [logo boot]:( is that suppose to happen? and also I can no longer do audio over hdmi:( is that also suppose to happen?

lam_das

Resume from S3 working and showing large temperatures happens only if I use Auto Vcore. As soon as I set a manual vcore, the third resume from S3 fails. That's not OS problem. That's BIOS issue!

 
More likely an issue with just running too high of an OC specifically your blck for stable S3 resume. Some boards are more tolerant that others. Another flag: running 12GB of memory can cause issues trying to run extreme blcks. Remember stock operation is guaranteed. Extreme over clocks... not so much.

ShibbyDPHS

New BIOS please, I want to update sometime soon.

Any specific issue?

HeavyHemi

lam_das

Resume from S3 working and showing large temperatures happens only if I use Auto Vcore. As soon as I set a manual vcore, the third resume from S3 fails. That's not OS problem. That's BIOS issue!

More likely an issue with just running too high of an OC specifically your blck for stable S3 resume. Some boards are more tolerant that others. Another flag: running 12GB of memory can cause issues trying to run extreme blcks. Remember stock operation is guaranteed. Extreme over clocks... not so much.

The issue with S3 resume has been present from a long time(I did not have 12GB RAM then). And as you can see in my sig, I can run a super-stable 4.4 clock on this machine on manual vcore. I can't do 3.6Ghz with manual setting on vcore AND resume on 3rd S3. Doesn't that tell you something? It tells me that S3 and manual vcore setting is broken after about 180 BCLK, whereas S3 and Auto vcore work upto about 196 BCLK. This is a BIOS bug because upon resume from S3, the manual vcore codepath is not restoring something, which happens automatically if we use auto vcore. If I had the code in front of me, I can probably debug it in few hours but EVGA has no motivation to do it, which is the real shame in all this.