no issues so far...

Most notably, the new BIOS builds include a High Precision Event Timer (HPET), a hardware timer used to supplement and replace the periodic interrupt function of the aging Real-Time Clock (RTC). In comparison to the RTC and Programmable Interval Timer (PIT), the High Precision Event Timer can produce periodic interrupts to the CPU at much higher resolutions than the RTC is capable of. Unfortunately, the feature is only compatible with newer operating systems including Windows Vista, Windows 7 and the x86 versions of Mac OS X.

In addition, the BIOS engineering team has added a “Reserve RC for Bridge” feature that enables resources for five VGA’s and has also implemented a way to disable a PS/2 keyboard in Device Manager if no PS/2 keyboard is present.

EVGA releases plethora of X58 SLI BIOS updates

Was wondering what the *NEW* HPET Mode was used for..Googled this..:)
Common Options : 64-Bit Mode, 32-Bit Mode
Quick Review
This BIOS option is linked to the HPET Support BIOS option. HPET Support must be enabled for this BIOS option to be active.
The HPET, short for High Precision Event Timer, is a new system timer developed by Intel and Microsoft to replace the four system timers currently in use. Some HPETs have 64-bits wide registers which can also run in the 32-bit mode. This is where the HPET Mode BIOS option comes in.

Setting it to the 64-Bit Mode allows the 64-bit operating systems and applications to make full use of the HPET's 64-bit registers.
Setting it to the 32-Bit Mode forces the HPET's 64-bit registers to run in the 32-bit mode. This allows proper operation when used with a 32-bit operating system.

If you are using a 64-bit operating system, you should select the 64-Bit Mode so that the operating system and 64-bit applications can make full use of the HPET's 64-bit registers. There is no harm in selecting the 32-Bit Mode although it will mean a potential reduction in counter resolution and/or functionality.
If you are using a 32-bit operating system, you should select the 32-Bit Mode.
If you are dual-booting between a 64-bit operating system and a 32-bit operating system and both support the HPET, select the 32-Bit Mode. If the 64-bit operating system supports HPET while the 32-bit operating system does not (e.g. Windows XP), then you can select the 64-Bit Mode.

before i update, is anyone still getting the double pump on boot up?

lawtq

OH MY GOD!!!

S3 Sleep works flawlessly with this bios, rev 1.1 board, it has never ever worked before, finally, a 2 second bootup!!

And this is with a 4.4ghz OC!

You are not kidding us, right? some sort of April (its not april, I know) fool joke...or something...

I am going to be flashing this one soon!

what a classic waste of time!

Still no S3 resume for me. (rev 1.0).

System hangs on resume so I must power off. Then the BIOS reports the system processor has changed. I must reload my BIOS settings to get back where I was before the S3 sleep.

8800gts320

Was wondering what the *NEW* HPET Mode was used for..Googled this..:)
Common Options : 64-Bit Mode, 32-Bit Mode
Quick Review
This BIOS option is linked to the HPET Support BIOS option. HPET Support must be enabled for this BIOS option to be active.
The HPET, short for High Precision Event Timer, is a new system timer developed by Intel and Microsoft to replace the four system timers currently in use. Some HPETs have 64-bits wide registers which can also run in the 32-bit mode. This is where the HPET Mode BIOS option comes in.

Setting it to the 64-Bit Mode allows the 64-bit operating systems and applications to make full use of the HPET's 64-bit registers.
Setting it to the 32-Bit Mode forces the HPET's 64-bit registers to run in the 32-bit mode. This allows proper operation when used with a 32-bit operating system.

If you are using a 64-bit operating system, you should select the 64-Bit Mode so that the operating system and 64-bit applications can make full use of the HPET's 64-bit registers. There is no harm in selecting the 32-Bit Mode although it will mean a potential reduction in counter resolution and/or functionality.
If you are using a 32-bit operating system, you should select the 32-Bit Mode.
If you are dual-booting between a 64-bit operating system and a 32-bit operating system and both support the HPET, select the 32-Bit Mode. If the 64-bit operating system supports HPET while the 32-bit operating system does not (e.g. Windows XP), then you can select the 64-Bit Mode.

this will hopefully be the fix to the BSODing of loading profiles in games
 
IRQL and System_Service_Exception

Anyone else tried this bios???

the.illegalnaut

before i update, is anyone still getting the double pump on boot up?

I would be curious as well...
 
Bob

KFIELDS

Still no S3 resume for me. (rev 1.0).

System hangs on resume so I must power off. Then the BIOS reports the system processor has changed. I must reload my BIOS settings to get back where I was before the S3 sleep.

 
I get the exact same issue on my 1.0 board.
 
S3 is still bugged. My system wont resume properly. Requires a hard boot to get it working after a failed resume.
 
 
For those that think the double boot is a problem... It was introduced a few revisions ago and thats when they made the statement that it was normal. They made the bios do it on purpose.
 
Whats its been? like 9 bios revisions now and still no fix.. We with the rev 1.0 boards sure got screwed out of our $300+ investment.
 

I remember seeing where it was normal, but can anyone explain why. And is this every time you turn you rig on, or only in certain situations?

My configuration

Intel Core i7-975 extreme
Plate Mother Evga classified x58 SLI 141-Bl-E760-A1
Memory kit Corsair 12 GB P Triple / I7 hx3x12g1600c9
 Evga GTX 285
HD SSD 160 GB Intel 34Nm p / SO
HD Seag. 1,5 TB p / TB data
Source Corsair TX 750W.
Bluray LG BH08LS20
Cabinet HAF 932
Windows 7 Ultimate Portuguese 64 bits.

I need virtualizar of mine PC, But I need move in BIOS, how to hit a BIOS assuredly?


South America, I am in Brazil.

If I have a raid set up will updating the bios result in me having to rebuild my raid? (raid 0)