• Fixed issue where the system would blue screen (with error code
0x0A) on the resume from S3.
• Updated E820 table to claim the area.
• Fixed possible issue with Windows* installation.
• Fixed issue in E820 table where the BIOS would list overlapping
regions if they had the same start address.
• Added supervisor password check for chassis intrusion event.
• Updated SMBIOS Processor Family.
• Fixed invalid event "Memory Size Decrease" and "Intel ME Interface
Initialization failed" logged after BIOS update with Express BIOS
Update, iFlash reboot method and BIOS recovery method.
• Fixed issue with overlapped memory ranges.
• Fixed issue where password becomes invalid when loading defaults
with "F9" and then reboot.
• Fixed issue where Memory Type Range Registers (MTRR) are not in
sync after S3 resume.
• Implemented Fault Tolerant Firmware ID solution.
• Implemented new SMRR feature according to the new BWG.
• Fixed issue where SMBIOS Type 10 (On Board Devices Information)
structure for On-board LAN "Description" field is incorrect when
On-board LAN is disabled.
• Fixed SMBIOS issues seen with the WLK 1.3 SMBIOS HCT test.
• Updated iAMT Intel(R) ME Firmware to 22.214.171.1247.
• Update iQST ME FW to 126.96.36.1997.
• Added security for SMM.
• VTD requirement Zero memory used for IGD GTT.
• Fixed issue of slow boot time for memory of more than 4GB.
• Updated support for high power PCIe adapters.
• Added updates to improve security.
• Added function to prompt for Supervisor/User password if set in
BIOS setup before allowing BIOS update.
• AddED the Downgrade password security check.
• Added the Firmware ID check to find the BIOS ID.
• Changed display string for Intel 64 Architecture support.
• Added handler for AP exception.
It is highly recommended to always use the most recent driver version available.
Do not forget to check with our site as often as possible in order to stay updated on the latest drivers, software and games.
Try to set a system restore point before installing a device driver. This will help if you installed a wrong driver. Problems can arise when your hardware device is too old or not supported any longer.