Official ASUS P67/H67 BIOS Updates

[djshortsleeve]

Yes, AI Suite II is software that you use from within Windows. It has overclocking options, DIGI+ options (for P8P67 series and Maximus IV Extreme), monitoring options, etc.

For some reason, this will not install. I have a perfect running version of 7 x64 and when I try with the CD or even downloaded files from ASUS, nothing happens.

 

[bankster55]

Thanks for the reply.
Any thoughts on the BIOS screen issue?

previous bios screens are MSDOS text with basic VGA 640 X 480 res
this bios is C++ GUI with fancy GRAPHICS
your "TV" HDMI has dif aspect ratio than PC
you are going to have to go DVI DVI or change aspect ratio or p size in monitor controls

 

[Haunty]

For some reason, this will not install. I have a perfect running version of 7 x64 and when I try with the CD or even downloaded files from ASUS, nothing happens.

Try turning off UAC and running setup as administrator, or boot into safe mode and run it. I had problems getting it to install too.

 

[bankster55]

well, I guess I know now why the newer bios dont recognise SDD on Intel SATA 6GBs
and how to fix
now I can load 1253 fearlessly
heh heh

 

[PioneerPro]

previous bios screens are MSDOS text with basic VGA 640 X 480 res
this bios is C++ GUI with fancy GRAPHICS
your "TV" HDMI has dif aspect ratio than PC
you are going to have to go DVI DVI or change aspect ratio or p size in monitor controls

That makes sense, its a different format.
What is the format the new bios screen is outputting, 1280x1024 60Hz?

Played around in the monitor menus but nothing seems to help,
its probably not a supported resolution over the HDMI inputs.

All I have is HDMI inputs.

Seen on other forums others are having this issue as well,
might be a suggestion to offer a 720p or 1080p output option in the bios.

 

[mv2devnull]

well, I guess I know now why the newer bios dont recognise SDD on Intel SATA 6GBs
and how to fix
now I can load 1253 fearlessly

Would you tell us too?


I do have some other issue. Not sure, if it is even related to the P8P67 Pro that I have.

First, I did enable that (APM PCIe). Haven't noticed "double-boots".
JMicron, Marvel, Azalia, Firewire - all disabled. Intel in RAID-mode.
Intel 80GB G2 into port1 (6GBps), DVD to port6.
diskpart GPT with 128MB ESP, 32MB MSR, 56GB data.
(Note: new Linux distros do come with 'gdisk', an 'fdisk' for GPT.)
EFI install of Windows 7.

Nvidia GTX460 card and Auzentech Forte 7.1.
Two Corsair CMV4GX3M1A1333C9 (i.e. 2x4GB 1333MHz), slots A2 and B2.

Everything seemed to succeed, and drivers from Asus CD got installed too. (Not the Suite)
Added two RAID1 arrays: 2x Samsung F3 1TB, ports 2&3 and 2x Seagate 500GB, ports 4&5.

However, after a while of use Windows started to freeze. Mouse was still able to move, sporadically, but eventually the only option was a hard power-off.

There are some errors in the event log, but not systematically for all freezes. There might be some 30s timeouts. It is not clearly connected to network, disk, or other load.

Windows does have a memory tester, which gleefully does two passes without errors. I don't have a functional memtest86+ v2.40 on a stick yet and older versions fail to load.

I did flash BIOS to 1253, but situation remains the same.
Updated Intel Gigabit driver, Intel chipset driver, Intel RST, but still get freezes.
Last action was removal of Auzen Forte, but haven't used the system long enough yet to say whether that makes a difference.


Summary: Intel SSD is visible to boot. Windows acts up, but cannot blame anyone in particular.

 

[corpfan1]

I am running 1053 and getting the 1600MHz RAM issues.

Basically I have Gskill Ripjaws X 1600 CL8...and it is AUTO set to 1333 CL9 by the BIOS.

If I change it to 1600MHz manually OR via XMP profile, I get BSOD when I boot right before Windows.

System is 100% stable at 1333...but can't get anything to work at 1600MHz.

Trying to figure out what to do...a bit shy to go to 1253 until people have better luck with it, or until there is another release that is a bit more stable.

Need to figure this out so I can move on with things.

 

[Dufus]

Gary, it seems that the hardware version has been incremented in BIOS 1253 for the P8P67 models Evo, Pro, Standard and Saber which means the BIOS cannot be easily downgraded to an earlier version, or is there an undocumented procedure? What is the reason for this and is it likely to be a continuing trait with future BIOS releases?

 

[bigi]

Running 1053 still.
Intel 80 GB SSD not visible in boot devices (Same as PioneerPro's issue)

When I proceed with Win7x64 install, it starts fine. SSD shows up, but then setup says something like "cannot install on this drive, cannot see partition", etc.

I've tried both types of Intel SATA in AHCI. Formatted SSD with diskpart, Win7, gpart. Still no go.

Is this a driver issue???

I took the SSD to other box and Win7 installs right away.

 

[Majic 7]

Running 1053 still.
Intel 80 GB SSD not visible in boot devices (Same as PioneerPro's issue)

When I proceed with Win7x64 install, it starts fine. SSD shows up, but then setup says something like "cannot install on this drive, cannot see partition", etc.

I've tried both types of Intel SATA in AHCI. Formatted SSD with diskpart, Win7, gpart. Still no go.

Is this a driver issue???

I took the SSD to other box and Win7 installs right away.

I just finished putting my system together. Asus PRO, 8Gbs Corsair Vengeance 1600, 2600k. Updated to 1053 before installing OS. Win7-64. Installed OS on my Intel 160 SSD with no problems. Installed most of the stuff on the Asus DVD with no problems. So far so good. Asus probe reads 34 for temp, bios reads 42 after updating to 1053. 160 is plugged into the #2 6GB SATA port.

 

[bigi]

I just finished putting my system together. Asus PRO, 8Gbs Corsair Vengeance 1600, 2600k. Updated to 1053 before installing OS. Win7-64. Installed OS on my Intel 160 SSD with no problems. Installed most of the stuff on the Asus DVD with no problems. So far so good. Asus probe reads 34 for temp, bios reads 42 after updating to 1053. 160 is plugged into the #2 6GB SATA port.

Which build of Win7x64 do you have? Integrated SP1?

 

[Majic 7]

Which build of Win7x64 do you have? Integrated SP1?

No, just w7-64HP retail I bought at Office Depot yesterday. No SP1.

 

[bankster55]

yeah youre at 1053, not 1253?
i really need to see a diskmanager screenshot (with the Win 7 sniptool) to see if Win 7 made your install GPT

 

[ahurtt]

I am running 1053 and getting the 1600MHz RAM issues.

Basically I have Gskill Ripjaws X 1600 CL8...and it is AUTO set to 1333 CL9 by the BIOS.

If I change it to 1600MHz manually OR via XMP profile, I get BSOD when I boot right before Windows.

System is 100% stable at 1333...but can't get anything to work at 1600MHz.

Trying to figure out what to do...a bit shy to go to 1253 until people have better luck with it, or until there is another release that is a bit more stable.

Need to figure this out so I can move on with things.

My RAM did the same thing in terms of being clocked to 1333 by the Auto setting even though it is 1600 RAM. I fixed it by setting the speed to manual and setting the 1600 option. I did not get any blue screens like you're describing but it was being clocked down when left on Auto. I am using BIOS v.1253 and things are OK for me. You might try booting up in 1333, use CPU-Z to get the SPD settings table for the RAM for 1600 and note the SPD table settings down on paper and try to set the timings manually as well and see how that does for you.

 

[Majic 7]

Sorry don't know how to insert image here and it's not worth it to me to set up an account somewhere. It partitioned the drive just like a new install with the 100 MB boot section and the C partition.

 

[bankster55]

O.K. no prob m8te

 

[corpfan1]

CPUZ just shows the settings that are current (1333 ones and their accompanied timings).

Not really sure what to try..debating on 1253.

My RAM did the same thing in terms of being clocked to 1333 by the Auto setting even though it is 1600 RAM. I fixed it by setting the speed to manual and setting the 1600 option. I did not get any blue screens like you're describing but it was being clocked down when left on Auto. I am using BIOS v.1253 and things are OK for me. You might try booting up in 1333, use CPU-Z to get the SPD settings table for the RAM for 1600 and note the SPD table settings down on paper and try to set the timings manually as well and see how that does for you.

 

[corpfan1]

Oops...figured it out...here is a screenshot. These are the settings I tried manually too with no dice (the XMP settings).

My RAM did the same thing in terms of being clocked to 1333 by the Auto setting even though it is 1600 RAM. I fixed it by setting the speed to manual and setting the 1600 option. I did not get any blue screens like you're describing but it was being clocked down when left on Auto. I am using BIOS v.1253 and things are OK for me. You might try booting up in 1333, use CPU-Z to get the SPD settings table for the RAM for 1600 and note the SPD table settings down on paper and try to set the timings manually as well and see how that does for you.

 

[Masonw@ASUS]

That makes sense, its a different format.
What is the format the new bios screen is outputting, 1280x1024 60Hz?

Played around in the monitor menus but nothing seems to help,
its probably not a supported resolution over the HDMI inputs.

All I have is HDMI inputs.

Seen on other forums others are having this issue as well,
might be a suggestion to offer a 720p or 1080p output option in the bios.

The only thing I can think of is seeing if your TV has overscan/underscan options and try adjusting those. Unfortunately we can't change the output that UEFI uses.

 

[eddietandy]

I was able to get this suite to install after running the patcher twice, but decided to uninstall because of the DPC latency spikes. The uninstall process did not remove the Digi+ VRM package, and left behind 3 Windows services, but the software and its uninstaller are now gone. Also have remnants left in the registry and some binaries still in Program Files.

So I guess it's safe to manually remove these three leftover services, or are these part of SmartDoctor?

ASUS Com Service
ASUS HM Com Service
ASUS System Control Service

I guess I should also try reinstalling then uninstalling again. I'm not too fond of software that doesn't clean up after itself properly.

 

[Gary Key]

1. If any of the following devices are not detected or not usable:
- Devices installed on PCIEx1_1 slot
- Devices installed on PCIEx1_2 slot
- The additional SATA6G port from Marvell 9128
- eSATA controller
- Devices installed on PCI_1 slot
- Devices installed on PCI_2 slot
- Onboard 1394 controller
- Second LAN
Please check the device manager under 'Storage controllers' , look for a device with the name 'ACS-6xxxx'. The manufacturer is 'Accusys Inc.' and will have an exclamation mark next to it.
This driver may be installed automatically when users run Windows Update, which causes a malfunction of these devices. Please uninstall the driver,reboot, and then those devices/slots will be available. We have asked MS to pull this driver from the auto update procedure.
2. If you are receiving random BSOD (Blue Screen of Death) under Windows 7 OS without any warning at stock or what appears to be stable OC settings, please download the following patch from Microsoft to have the problem fixed (98% fix rate): This hotfix will be in SP1.
http://support.microsoft.com/kb/979444
3. If you are experiencing long boot up times (greater than 30 seconds) or slow performance of SATA HDD or SSDs, please remove Intel RST 10.1.1008 if you have it installed and use the Intel boxed AHCI driver in Windows 7 or Windows VISTA. For XP users please try IDE mode until Intel releases a new update. The new update will also include full support for bootable RAID arrays over 2TB in size along with other bug fixes/performance enhancements specific to P67 (new firmware will be released to the board manufacturers also).
4. If you are still unable to install AiSuiteII after using the Patcher file, you might be using a COA hack for Windows 7. Please reinstall OS without the hack and it will work. If you are sure the OS install is hack free, then please PM me.
5. If you are unable to enable SLI support with various versions of Nvidia drivers (especially 266 and up), please reinstall the OS with the latest BIOS installed. I know this is drastic, but the SLI key format has changed and the OS might not recognize the new key in the updated BIOS (especially if non released NV drivers were previously installed, drivercleaner will not clear this setting during an uninstall). This should not occur in future BIOS releases.
6. If you are unable to display BCLK properly, not able to overclock under the OS (including Auto Tuning)…etc, please ensure the Intel MEI driver from the support CD or latest version from Intel has been installed. All controls related to the CPU are controled by the MEI under the OS and several even in UEFI mode. I think this is a must install under the Sandybridge platform even if you manually overclock.
7. If the power saving features not working after updating to BIOS 1253, please verify the power profile has been set to balanced mode instead of Performance Mode. As long as EIST is not disabled or CPU Voltage is to manual mode (use offset), the power saving modes will continue to operate normally. In addition, if you have enabled Internal PLL Voltage, then resume/hibernate will not work correctly until Intel has an update (or this might end up being standard operating mode).
8. The differences between the EPU switch, UEFI EPU option, and EPU under AiSuite II is as follows:
- EPU Switch: Once enabled, it will enable EPU option in BIOS and default to auto mode.
- EPU option in UEFI: Various options are available to select the level of power saving (lowering Vcore voltage when the system load decreases). Both the BIOS option and EPU switch will not effect performance, however stability at high overclocks will depend on the quality of the CPU and DRAM used.
- EPU under AiSuite II: Same as previous generations, 3 modes to choose from, AUTO (dynamic change multiplier and Vcore based on CPU load), High Performance (EPU OFF), and Max power saving (Drop CPU multiplier to lowest multiplier with relative VID decreases).

We will have a new BIOS set in about a week or so that will address additional bug fixes and improve performance/overclocking.

 

[Anomaly1964]

So at this point how do I get both my SSD and HDD to be recognized...?

Asus Sabertooth P67...
OCZ 120GB SSD...
Samsung F3 Hdd...
Bios 1253...

 

[Masonw@ASUS]

I was able to get this suite to install after running the patcher twice, but decided to uninstall because of the DPC latency spikes. The uninstall process did not remove the Digi+ VRM package, and left behind 3 Windows services, but the software and its uninstaller are now gone. Also have remnants left in the registry and some binaries still in Program Files.

So I guess it's safe to manually remove these three leftover services, or are these part of SmartDoctor?

ASUS Com Service
ASUS HM Com Service
ASUS System Control Service

I guess I should also try reinstalling then uninstalling again. I'm not too fond of software that doesn't clean up after itself properly.

Hi eddie,

I'm not sure if those are part of SmartDoctor or AI Suite II, but since some remnants were left behind after your uninstall I would suggest to remove them and if you need you can reinstall SmartDoctor.

 

[mv2devnull]

I don't know that I would have installed any "SmartDoctor", but I did install and uninstall Probe and monitor of AI Suite II and those same three services were left over.

 

[bankster55]

Questions for Gary Key

#1
What is the "boxed Intel AHCI driver"?
The one on the support CD?
Needing to remove the 10.1 Intel driver is very sad, since it is the only driver that allows proper SSD TRIM action, and makes an astonishing difference.
#2
If you have Win 7 with SP1 slipstreamed, or the integrated ISO floating around, and since SP1 has all updates, I guess that means the accusys driver is on the iso and will be instaled during the O/S install - no way around it. Right? (I know the SP1 is not official for 2 months, but most here already have it)
#3
Can you explain this behavior;
A certain few knowledgable users like kittysox here cannot install Win 7 to their SSD on Intel SATA6 ports with a spindle HDD on SATA3, but Win 7 installs perfectly fine when the SSD is moved to Intel SATA3. Then after moving drive back to SATA6 it disappears.
Is it certain SSD firmware cant be detected on the SATA6?
Whats puzzling is on the P67 schematic the SATA3 and SATA6 are on the same SB bus
#4
I had read a bunch of reviews on the net about the various ASUS P67 mobo before i bought mine, and not a single one ever mentioned word one about any install or run prob of any kind during install or benchmarking. How is this possible? Doesnt the fact that theres a mad rush going on with bios updates drivers updates and MS interactions, doesnt this mean the P67 chipset was not really ready for release at this point in time?
#5
The EFI bios has three segments
The graphical shell coded in C++
The MBR segment in MSDOS
The third segment is the EFI GPT coding
Can you tell me if this is also coded in MSDOS?
I am guessing it would have to be