lcabezas

S3 is awesome to use and to have working. S3 completely turns off the computer and if you set it up to wake up from keyboard all you do is hit a key or move a mouse to wake it up. Much faster than shutting it down and saves energy.
 
Also you have a Classified like I do and S3 works for us maybe it doesn't work for him cause he has a Regular X58 board. His problems are different then what you have so you shouldn't even be complaining that he keeps posting that cause you don't even own the same motherboard. He paid a premium for EVGA's customer service just like all of us and he has a right to complain if they don't deliver to his standards.

Totally agreed, non-functional S3 would be damn near a deal-breaker for me as well, but the problem people are reporting is a bit of a grey area, as S3 works for even the Rev 1.0 758 boards but only up to a certain Bclk.  So the people who are complaining about broken S3 are technically complaining even though they're running the board out-of-spec.  The problem is the competition's boards handle S3 fine at 200+ Bclk, as does the Classified 760.  I've been running S3 stably at 200 Bclk since day 1 and its a feature that's very important to me.  Not only does it save power and cut down on heat/noise when not in use, but it also cuts down on dust build-up inside your case.
 
For those who are having issues, I'd try upping voltages related to RAM or relaxing timings as S3 is literally STR or "Save To RAM", so if your RAM isn't stable then reading from RAM from a suspend state can get a little dicey.
 
 
 

Davabled

HRPuffnstuff

I noticed that using the kb to start the pc required me to use the ps2 port instead of usb.

Same behavior here, when using S3 state.

Have you guys tried changing the setting in the BIOS to enable resume from USB keyboard?  Waking from USB works flawlessly for me.
 

Just wanted to let you know that I lost 4/12GB of RAM after my overclock to 4.2.  Stock clocks works great, but anything above that and bam gone... lol

Specs:
i7 920
12GB Mushkin Enhanced Redline 1600
2 4GB 5970s and 1 9800GT
Evga Classy 762
Thermaltake toughpower 1200w
2 30GB Vertex for os
2 60GB Vertex for storage

chizow

Davabled

HRPuffnstuff

I noticed that using the kb to start the pc required me to use the ps2 port instead of usb.

Same behavior here, when using S3 state.

Have you guys tried changing the setting in the BIOS to enable resume from USB keyboard?  Waking from USB works flawlessly for me.
 

I have, and that option had zero effect, regardless of which USB port the keyboard's plugged into.  Like lam_das and others, I've already gone through every BIOS/Operating System/Driver option available to me and then some.  I'm considering giving up on using S3.  (With my 759 Classified Limited Edition motherboard)
 
If I wasn't so tired I'd take some voltage readings of the USB ports in various power states (under subjective observation it appears that the USB ports are being powered off even with the keyboard boot option enabled).

In most cases missing ram at cold boot (non S3) is due to to low of a vtt setting for memory speed setting. Depending on your motherboard in most cases overclocked memory requires a vtt of about +200-+250. Alot of ppl think they need a very low vtt because high vtt will burn the chip IMC out. In majority of cases where this happens vtt is to low and distance between vdimm and vtt exceeds .45v.

New beta bios i7-970 on E760 is fail to  run DRAM Ratio 2:10 also before version.
It's run 2:8 .... but my friend's ga ud4p is can run 2:10 

hiritsuki

New beta bios i7-970 on E760 is fail to  run DRAM Ratio 2:10 also before version.
It's run 2:8 .... but my friend's ga ud4p is can run 2:10 

again user issue.

i am getting close to 2150 C7/C8.. will stop at 2200mhz as long as my cpu pll voltages dont get more than 1.95v..

justin.kerr

Best BIOS so far!! just passed 24 hours of Prime95  RAM 2100Mhz CAS 7-7-7-21 not going to list the rest of the timings. lol but not one setting on "dummy" 2280Mhz on CAS 8, 32M pi stable, did not check for prime95 stability on the 2280Mhz, doubt it would pass.
 very good job EVGA!!
and why would anyone ever leave on single setting in the whole BIOS on auto??? just get a Dell if you don't know how to setup a BIOS

agreed on both counts
a lot of noobies impressed with classy design
but has no clue how good the bios is.

i've stop listing my 2130,2140 etc .. lol.
cause been watching ppl rip off SAE clocks without due credit

You folks with the missing ram phenomena should try the full CMOS reset, i.e. removal of battery for at least 15 minutes and reinserting, loading defaults before and after flashing previously and seeing if that resolves the issue.

ShockTheMonky

hiritsuki

New beta bios i7-970 on E760 is fail to  run DRAM Ratio 2:10 also before version.
It's run 2:8 .... but my friend's ga ud4p is can run 2:10 

i7 970? Possible microcode not added yet.

So .. please add new microcode about i7 970 

mmuthiah

I have updated this BIOS.  I'm still having  "3.99g usable out of 6G" memory issue.   So its not useful for me at least.  I hope they will release a fix for this issue.

did you try DRAM for MCH option?

Guys with missing ram should also try cleaning the contacts on their sticks with a soft cloth and alcohol and blow out the slots with compressed air just to make sure that good contact is being made.

mmuthiah

I have updated this BIOS.  I'm still having  "3.99g usable out of 6G" memory issue.   So its not useful for me at least.  I hope they will release a fix for this issue.

Does it do this when the memory is clocked around say DDR3 1066 or DDR3 1333?

usually the fix for this is to increase CPU VTT slightly, if that doesnt work increase vDIMM (or both).

Also removing the memory and putting them in 1 module at a time can help and also giving them a littlw "wiggle" once they are in the slot can help.

I had this issue when i installed my Classified replacement, only 3.99GB was showing up, i removed 1 stick at a time and when i was down to 1 stick in the red slot cloest to the CPU socket the board would not POST.  I removed that module and replaced it giving it a little wiggle, the system was able to POST. I then put in the second memory module, POSTed, 4GB showed up, i then put in the last module after a shutdown and when i restarted all 6GB showed up.

Another thing that can cause memory to drop out is a weak module, try loosening timings or underclocking it to see if that brings back the 2GB misisng.

Also make sure that all your Memory modules work separately to make sure you dont have a faulty module.

Also as a last resort reseating the CPU can help.  When you remove the CPU make sure there are no bent pins in the socket or any damaged pads/contacts on the underside of the CPU.

Is this still BETA? Bc the 64 BIOS has been unstickied. If that's the case, shouldn't the thread title be updated?

lam_das

@molten: this is a BIOS issue and nothing to do with seating of RAM or dust or timings or even voltages. My 12GB RAM gets detected and works stably at 21x196 (2:8 puts it just under the rated 1600Mhz) with SZ50 BIOS. But with this BIOS, I can't see my RAM beyond 149BCLK. I go back SZ50 and everything is detected again and stable.

Some people have reported success by locking MCH to DRAM RATIO instead of Auto. I learned that after I had moved back to SZ50. So, may be more people with dropping RAM should give that a try and report. I think this BIOS did something to lock MCH in some fashion, because there were couple of changes for memory compatibility in the Changelog.

Its not guaranteed to be a BIOS issue as this doesnt happen to everyone using this BIOS.

Also memory dropping out on these platform has been a well documented phenomenon, it started way before this BIOS was released, basically when this platform was released this issue was a problem.

It may be in this case that it is to do with the BIOS but thats not guaranteed so its best to give people all the info instead of just saying "its a BIOS issue".

Also it seems you failed to notice he said "i am still having "3.99GB usable out of 6 G" memory issue" which indicates this is a long running issue for this particular person that started before the update to this BIOS.  He also does not mention its related to BClock like your is, so again you cant just assume hes having the same issue as you and put it down to a BIOS issue.

At the end of the day you may be right and the fix you gave will work but its best to give all the information and all the possible solutions. Since i dont have the particular issue you have, so have no experience with fixing it and the fact you had already mentioned it i gave other alternatives without repeating any advise already given (that i noticed).

Just because someone gives alternative solutions does not mean they are saying that your suggestion(s) were wrong.

Shifter

I was also missing 2 gigs of memory. Tried reseating memory, did not work.  Resetting CMOS, didn't work.
 
Finally, I took off the waterblock cooler, took out CPU, looked for bent pins - none were bent.  I used compressed air to clean out the socket.
 
Put CPU back on and whatnot, booted up my 2 gigs of RAM, then i put in my OCed settings, worked fine ever since.
 
Hopefully it continues to work.

sometimes reseating the CPU in itself will work and also uneven pressure of the heatsink/waterblock can cause the CPU not to sit 100% correctly in the socket which can also make memory drop out.

Glad you got your sorted.

lam_das

@molten: I didn't mean that your suggestions were not valid. They are good suggestions and people should do those things if they always have or had issues with memory disappearing. But this BIOS upgrade behaves that way because of memory related changes that have gone in and documented in the Changelog. Why it doesn't affect all installs, I don't know. May be its a 758 only thing. May be it affects older CPU models only.

cool

Its best to give all the angles, even if they dont need that information now it may help them later.  In future posts referring to this issue i will mention your reason/fix also if you have not done it already along with the other lists of possible solutions for this issue.