[Request] AMITSE/AMI Patch for Clevo P750ZM-G BIOS

Hi everyone,

I’ve been working on unlocking the Chipset menu on my Clevo P750ZM-G BIOS for the past 3 weeks.
Here’s a complete summary of what I’ve achieved and where I’m stuck.
I also performed a hardware upgrade GTX970M to GTX1070 (not the mobile version)I’ve flash the vBIOS to unlock all my 2 Display Port and 1 HDMI, g-sync not in the flash.

Hardware:
Clevo P750ZM-G (Z97 chipset, i7-4790K delidded + liquid metal)
BIOS: AMI Aptio IV
Flash chip: GigaDevice GD25Q64B (8 Mo, SOIC-8, dumped via CH341A)
4 x 8GB Kingston HyperX 1600Mhz CL9 1.35v

Objectives Achieved:
Removable EEPROM
U11 flash chip (GigaDevice GD25Q64B) is soldered but on removable socket
Direct access via CH341A SPI programmer (3.3V modified)
Easy dump/flash workflow without desoldering

Wake-on-LAN (WOL) - FULLY FUNCTIONAL
Force enabled via AMIBCP in BIOS (no Linux kernel driver needed)
Validated with magic packet from Home Assistant
System wakes reliably from sleep/hibernation
Persists across reboots

CPU Undervolt - VALIDATED & STABLE

Undervolt: -115mV CPU / -108mV Ring voltage
Stock temps: 96°C under load
After undervolt: 74°C stabilized (22°C gain!)
CPU Voltage Mode: Adaptive
Validated with 30+ min stress test

Temperature Improvements:

Before: 96°C peak under stress
After: 74°C Package stable (without even repasting)

Fans still not at 100% at 74°C
Estimated 70-75°C after fresh thermal paste application

BIOS Modifications Tested:

  1. AMIBCP Option Visibility:

Set all options to USER level visibility
Result: Unlocked most Overclocking/Advanced options
Enabled Wake-on-LAN was forced enable via AMIBCP (it’s a visible option in Chipset/PCH IO submenu)

CPU/Ring voltage offsets now accessible
BUT: Chipset menu tab still completely hidden

  1. IFR Patching (SuppressIf True → False):
    Extracted somes modules
    Patched somes occurrences
    Flashed and tested

Result: No change to Chipset menu visibility

What’s Still Locked:

Chipset menu tab (completely hidden)
Memory voltage control (1.5V → 1.35V) - nested under Chipset submenu2.

AMIPSE Reverse Engineering (3-Day Investigation):
I guess Chipset menu is protected by 3 filtering layers:

Layer 1 - IFR Level (Identified):
Suppress If { QuestionId 0x25B equals 0x1 }
Variable 0x25B (TPD4) at NVRAM offset 0x28C
VarStore: EC87D643-EBA4-4BB5-A1E5-3F3E36B20DA9
When TPD4=0x1, Chipset menu hidden

Layer 2 - AMITSE ClassGUID Whitelist (Patched, No Effect):
Located whitelist at PE32 offset 0x180046580
Only 2 GUIDs in original table
Patched: Added Chipset GUID ADFE34C8-9AE1-4F8F-BE13-CF96A2CB2C5B
Modified loop counter: CMP BX, 0x2 → CMP BX, 0x3 at 0x48FA
Result: Both patches confirmed in flashed BIOS but NO effect

Conclusion: Not the primary blocking mechanism

Layer 3 - Runtime AMITSE Evaluation (Still Investigating):

AMITSE likely has runtime function evaluating IFR conditions
Reads Setup NVRAM TPD4 flag at offset 0x28C
Executes: “if TPD4==0x1 then suppress Chipset FormSet”
This appears to be the actual blocking point
Exact patch location still being identified

Tools & Methods Used:

flashrom - Direct SPI flash dump/write via CH341A (3.3V modified)

UEFITool 0.28 - Module extraction and replacement
ifdtool - Intel Flash Descriptor manipulation
Ghidra - Reverse engineering AMITSE PE32
Python - Binary patching & hex analysis
AMIBCP 4.55 - BIOS setup option visibility control

Current Status:

WOL fully functional
CPU undervolt stable (-115mV/-108mV, 74°C)
Memory timings accessible (but voltage still locked behind Chipset menu)

Chipset menu still hidden despite Layer 1 & 2 patches⏳ Layer 3 runtime evaluation - seeking expertise

Files:
Stock BIOS backup: bios_backup_stock-P750ZM.bin

Partial unlocked BIOS: WOL-CPU-MEMORY-OC-BIOS-v1.bin

Next Steps:

Identify exact AMITSE runtime function that evaluates TPD4 condition

Patch the suppression logic or modify TPD4 default value
Consider upgrading flash chip to GigaDevice GD25Q128 (16 Mo) for future microcodes
Consider upgrading BIOS to allow nvme boot.

Looking For:
AMITSE/AMI internals expertise to identify where the runtime condition evaluation happens and how to effectively patch it.

This is my first time 100% digging into a BIOS modding :slight_smile:


Edit by Fernando: Thread title customized