[Request] Unlocked Clevo V360SNRQ InsydeH2O BIOS

Hello,

I am looking for help identifying the BD PROCHOT offset in the CpuSetup EFI variable on my laptop, with the goal of disabling it from Linux by writing directly to the EFI variable.


SYSTEM

• Laptop: Multicom V3xxSNR (Norwegian reseller)
• Chassis string (from BIOS): V35_36x_37xSNR_SNRQ
• DMI manufacturer/product: “Notebook” / “V3xxSNR”
• CPU: Intel Core i9-14900HX
• RAM: 96 GB DDR5 @ 5200 MHz
• BIOS: Insyde H2O, version 1.07.05TNR (07/28/2025)
• KBC/EC Firmware: 1.09.04
• OS: Ubuntu Linux, kernel 6.17


PROBLEM

BD PROCHOT is enabled and being enforced at the EC level. MSR 0x1FC cannot be written — every write attempt is instantly reverted, even with Secure Boot disabled and kernel lockdown set to none. This caps the CPU at ~5.1 GHz under acpi-cpufreq, and at 2.2 GHz under intel_pstate in any mode.

The BIOS Advanced tab is inaccessible (locked by OEM). Multicom refused to assist.


WHAT I HAVE TRIED

• Disabling Secure Boot — kernel lockdown now shows [none] but EC still reverts MSR writes instantly
• intel_pstate active and passive modes — both cap at 2.2 GHz due to firmware policy
• RAPL sysfs power limits — these stick (currently 80W PL1 / 150W PL2) but are overridden by BD PROCHOT
• Smokeless_UMAF — no effect on this Intel platform
• fwupd — no updates available


APPROACH

Since MSR writes are blocked at EC level, I am trying to disable BD PROCHOT by modifying the CpuSetup EFI variable directly from Linux. I have successfully read the variable:

• Variable: CpuSetup-b08f97ff-e6e8-4193-a997-5e9e9b0adb32
• Full hex dump attached (cpusetup_dump.txt)

I have also dumped the following related variables if useful:
• SaSetup-72c5e28c-7783-43a1-8767-fad73fccafa4
• SetupCpuFeatures-ec87d643-eba4-4bb5-a1e5-3f3e36b20da9
• PchSetup-4570b7f1-ade8-4943-8dc3-406472842384
• OemNvPcfDcPwrLimitSetup-f3c83344-34e3-47f8-bd71-4c99ad16e55f


QUESTIONS

  1. Can anyone identify the ODM for this chassis? (Clevo? Tongfang? Other?)
  2. Is there a known offset for BD PROCHOT in the CpuSetup variable for this or a similar Insyde H2O / Intel platform?
  3. Can the IFR be extracted from the EFI variables alone (without a full BIOS flash dump), to map all offsets?
  4. Are there any other offsets worth modifying to restore full intel_pstate functionality — specifically the 2.2 GHz firmware ceiling?

I am comfortable with EFI variable writes from Linux, UEFI shell, and direct firmware modification. Happy to provide any additional dumps or diagnostic output.

Thank you.

cpusetup_dump.txt:

00000000: 0700 0000 0018 1800 0101 ff00 0001 0101 …
00000010: 0100 0101 0100 0001 0101 0000 0000 0000 …
00000020: 0000 0000 0000 0148 dc03 0004 4300 01d8 …H…C…
00000030: 4703 0000 0001 20bf 0200 0101 a8d2 0200 G… …
00000040: 0101 0101 0101 0101 0000 0000 0000 01ff …
00000050: 0202 0202 0200 0000 0000 0000 0000 0000 …
00000060: 0000 0000 0000 0000 0000 0000 0000 0000 …
00000070: 0000 0000 0000 0000 0000 0000 0000 0101 …
00000080: 0001 0100 0000 0000 0000 0000 0000 0000 …
00000090: 0000 0000 0000 0000 0000 0000 0000 0000 …
000000a0: 0000 0000 0000 0000 0000 0000 0000 0000 …
000000b0: 0000 0000 0000 0000 0000 0000 0001 0101 …
000000c0: 0100 0001 0100 0000 0000 0000 0101 0001 …
000000d0: 0118 3a3a 3434 3434 3434 3a3a 3434 3434 ..::444444::4444
000000e0: 3434 0102 0304 0506 0708 0102 0304 0506 44…
000000f0: 0708 2900 0000 0000 0000 2900 0000 0000 ..)…)…
00000100: 0000 1000 0000 0000 0000 1000 0000 0000 …
00000110: 0000 0100 0100 0101 0100 0000 0000 0000 …
00000120: 0000 0000 0200 ff00 0000 0300 0000 00e8 …
00000130: 0701 0101 0000 aa00 9001 c800 0000 0000 …
00000140: aa00 9001 c800 0000 0000 5000 5000 5000 …P.P.P.
00000150: 0000 0000 1400 1400 1400 0000 0000 0400 …
00000160: 0400 0400 0000 0000 0101 0100 0001 0101 …
00000170: 0000 0000 0000 0000 0000 0000 0000 0000 …
00000180: 0000 0000 0000 0000 0000 005c 0378 0084 ….x..
00000190: 0000 0000 0000 00b0 0000 0000 0000 0001 …
000001a0: 0101 0000 e803 0000 e803 0000 0100 0000 …
000001b0: 0000 0000 0000 0000 0000 0000 0000 0000 …
000001c0: 0000 0000 0000 0000 0000 0000 0000 0000 …
000001d0: 0000 0000 0000 0000 0001 0000 0000 0000 …
000001e0: 0000 0000 0000 0000 0000 0000 0100 0000 …
000001f0: 0000 0000 0001 0000 0000 0000 0000 0008 …
00000200: 0101 0000 0000 0202 0000 0000 0000 0000 …
00000210: 0101 0000 0000 0000 0000 0000 0000 0000 …
00000220: 0000 0000 0000 0000 0064 0001 0100 0001 …d…
00000230: 0101 00ff 0000 0000 0000 0000 0000 0000 …
00000240: 0000 0000 0000 0000 0000 0000 0000 0000 …
00000250: 0000 0000 0000 0000 0000 0000 0000 0000 …
00000260: 0000 0000 0000 0000 0000 0000 0000 0000 …
00000270: 0000 0000 0000 0000 0000 0000 0000 0000 …
00000280: 0000 0000 0000 0000 0000 0000 0000 0000 …
00000290: 0000 0000 0000 0000 0000 0000 0000 0000 …
000002a0: 0000 0000 0000 0000 0000 0000 0000 0010 …
000002b0: 0800 0000 0000 0000 0000 0000 0000 0000 …
000002c0: 0000 0000 0000 0000 0000 0000 0000 0000 …
000002d0: 0000 0000 0000 0000 0000 0000 0000 0000 …
000002e0: 0000 0000 0000 0001 0100 0000 0000 6400 …d.
000002f0: 0000 0000 0000 0100 0d02 0100 0000 0000 …
00000300: 0000 0000 0000 0000 0000 0000 0000 0000 …
00000310: 0000 0000 0000 0000 0000 0000 0000 0000 …
00000320: 0000 0000 0000 0807 001a 0400 4c04 ec02 …L…
00000330: 0000 0000 0000 0000 0101 0008 0700 0000 …
00000340: 00b0 04b0 0400 0000 0000 0000 0000 0000 …
00000350: 0000 0146 6402 0000 0000 00ff 0000 0000 …Fd…
00000360: 0000 0000 0000 0000 0000 0000 0000 0000 …
00000370: 0000 0000 0000 0000 0000 0000 0100 0000 …
00000380: 0000 0000 0000 0100 00c0 5d00 0070 1700 …]..p..
00000390: 0040 0d03 00d0 fb01 0000 0101 0000 0000 .@…
000003a0: 0000 0000 0000 0000 0000 0000 0000 0000 …
000003b0: 0000 0000 0000 0000 0000 0000 0000 0000 …
000003c0: 0000 0000 0000 0000 0000 0000 0000 0000 …
000003d0: 0000 0000 0000 0000 0000 0000 0000 0000 …
000003e0: 0000 00 …


Edit by Fernando: Thread moved into the “BIOS Modding Requests” Category and title shortened/customized

Upon posting this request, I was contacted privately by a forum user who sent me an executable bundle that he/she asked me to run with admin rights.

Is this a legitimate way to operate in this forum? I find it a bit suspicious.

@Oddan
Welcome to the Win-Raid Forum!

The Forum Administration has no knowledge about the content of private messages.
It is up to the PM recipient to evaluate, whether the sender or the tip/link is trustworthy or not.

Good luck with your specific request, which is very challenging even for BIOS modding experts!

Additional info (screenshots)

For what it’s worth, I’ve now confirmed from the Norwegian reseller that the exact model name is: Clevo V360SNRQ

UPDATE:

I have made significant progress in diagnosing this issue and can now provide much more precise information.


CONFIRMED MODEL

The exact chassis is Clevo V360SNRQ (confirmed by Multicom). The BIOS image (V3xxSNR(32M).05, version 1.07.05TNR, 32MB) has been obtained from https://repo.palkeo.com/clevo-mirror/V3xxSNRQ/ and is available to share.


IFR EXTRACTION RESULTS

I successfully extracted the IFR from the SetupUtility PE32 module using IFRExtractor-RS. The relevant offsets in the CpuSetup variable (GUID: B08F97FF-E6E8-4193-A997-5E9E9B0ADB32, VarStoreId: 0x3) are:

  • Bi-directional PROCHOT#: offset 0x7A (current value: 0x01 = enabled)
  • PROCHOT Lock: offset 0x7D (current value: 0x01 = enabled)

Offsets verified by cross-checking known settings:

  • Hyper-Threading (0x05): 0x01
  • SpeedStep (0x09): 0x01
  • BD PROCHOT (0x7A): 0x01
  • PROCHOT Lock (0x7D): 0x01

CORE PROBLEM

CpuSetup is write-protected at the firmware level. Confirmed via:

  • MSR 0x1FC writes instantly reverted by EC even with Secure Boot disabled and kernel lockdown set to none
  • efivarfs writes blocked despite remounting rw and chattr -i
  • setup_var.efi (datasone) from UEFI shell returns: “Error while setting content of variable CpuSetup: WRITE_PROTECTED”

The write protection is enforced at the firmware level, not the OS level.


WHAT I NEED

A modified BIOS image with the CpuSetup write protection removed, so that BD PROCHOT and PROCHOT Lock can be configured from the OS or UEFI shell.

I have the original 32MB BIOS image available and am happy to share it by email or upload it. I am comfortable flashing a modified BIOS via the EFI shell using the Fpt.efi and FlashMe.nsh tools included in the Clevo firmware package.

Please let me know if you can help or need any additional information.

just wanted to let you know most of the clevo intel 12th/13th/14th devices have committed FPF intel boot guard.

I see. That’s not good news.
Apart from modifying the BIOS image itself, are there other way to change the hidden/locked settings in a way that would not trigger FPF?