UHD630 temperature jumps up to 80°C!

[Asural]

22 hours ago, deeveedee said:

@Asural I will inspect your extracted ACPI and let you know if I have suggestions.  Test without ACPI > Add > DMAR.  You probably don't need it.  The increase in CPU temp without framebuffer-stolenmem doesn't make sense to me.  If your hack does not crash when booting without framebuffer-stolemem and you don't see any functional issues while using your hack without framebuffer-stolenmem, then you don't need it.

 

EDIT: @Asural You won't notice any difference when you disable your "ACPI > Add > DMAR" patch because you implemented it incorrectly (and because you probably don't need it).  In order to add you own DMAR table, you must drop the original System DMAR with "ACPI > Delete".  See here.  Again, I doubt you need to patch DMAR.  Test without it to confirm.

 

22 hours ago, deeveedee said:

@Asural I inspected your DSDT and confirmed that my SSDT-AWAC-HPET-RTC.aml is correct for your HP 400:

• SSDT-AWAC-HPET-RTC.aml sets HPTE = 0.  This disables Device HPET (HPET._STA = 0). This means that you don't need any of the other HPET patches as I mentioned earlier.
    Reveal hidden contents

           Device (HPET)
              {
                  Name (_HID, EisaId ("PNP0103") /* HPET System Timer */)  // _HID: Hardware ID
                  Name (_UID, Zero)  // _UID: Unique ID
                  Name (BUF0, ResourceTemplate ()
                  {
                      Memory32Fixed (ReadWrite,
                          0xFED00000,         // Address Base
                          0x00000400,         // Address Length
                          _Y17)
                  })
                  Method (_STA, 0, NotSerialized)  // _STA: Status
                  {
                      If (HPTE)
                      {
                          Return (0x0F)
                      }
  
                      Return (Zero)
                  }

• SSDT-AWAC-HPET-RTC.aml sets STAS = 2.  This means that your original System RTC device is disabled (RTC._STA = 0):

    Reveal hidden contents

              Device (RTC)
              {
                  Name (_HID, EisaId ("PNP0B00") /* AT Real-Time Clock */)  // _HID: Hardware ID
                  Name (_CRS, ResourceTemplate ()  // _CRS: Current Resource Settings
                  {
                      IO (Decode16,
                          0x0070,             // Range Minimum
                          0x0070,             // Range Maximum
                          0x01,               // Alignment
                          0x08,               // Length
                          )
                      IRQNoFlags ()
                          {8}
                  })
                  Method (_STA, 0, NotSerialized)  // _STA: Status
                  {
                      If ((STAS == One))
                      {
                          Return (0x0F)
                      }
                      Else
                      {
                          Return (Zero)
                      }
                  }
              }

 

•  It also means that your original System AWAC is disabled (AWAC._STA= 0):

    Reveal hidden contents

          Device (AWAC)
          {
              Name (_HID, "ACPI000E" /* Time and Alarm Device */)  // _HID: Hardware ID
              Name (WAST, Zero)
              Name (WTTR, Zero)
              Method (_PRW, 0, NotSerialized)  // _PRW: Power Resources for Wake
              {
                  Return (GPRW (0x72, 0x04))
              }
  
              Method (_STA, 0, NotSerialized)  // _STA: Status
              {
                  If ((STAS == Zero))
                  {
                      Return (0x0F)
                  }
                  Else
                  {
                      Return (Zero)
                  }
              }

   

Conclusion: SSDT-AWAC-HPET-RTC.aml that you copied from my HP 800 is correct for your HP 400.

 

 

EDIT:

 

The ACPI guide that said patching DMAR was necessary for BigSur is wrong unless it was patching DMAR for a specific case.  As Verdazil said, there are specific cases (e.g., certain Ethernet cards) that may require a patched DMAR or disabled VT-d.  My HP 800 doesn't need patched DMAR, so I doubt your HP 400 needs patched DMAR.

 

I'm currently testing the ACPI configuration you recommended.

I'm confused because the behavior changes depending on the AAPL and ig-platform-id selection, but I've currently selected <00009B3E>.

 

By the way, are there any specifications for graphic-options = <0C000000>?
 

1 hour ago, Max.1974 said:

 

@AsuralClover works like a charm for me. It’s easier to use and provides more kexts from the Clover GitHub for system monitoring. 

 

Try my compiler app by RehabMan. It’s only for system monitoring. 

 

https://github.com/maxpicelli/HWSensors-RehabMan-HWSensors-Modify/releases/tag/FakeSMC 

 

 

 

 

 

Download HWMonitor DMG

 

HWMonitor.dmg 2.09 MB · 0 downloads

 

1 hour ago, Max.1974 said:

@Asural This EFI has been well structured for your model.

You can try adapting the SSDTs or extracting its ACPI tables using Hackintool. 

 

EFI-Hackintosh-HP400-G5-main.zip 5.65 MB · 0 downloads

 

 

 

Thanks, I was just giving up on @deeveedee's CLover sample.

I'll give it a try tomorrow, I'm too tired to open my PC today.

 

Append:

There's no FakeSMC...
I started installing Sequoia, but this EFI is just OpenCore, right?
 

Edited January 20 by Asural

[deeveedee]

@Max.1974 That looks familiar.  Where did you find that EFI?

 

@Asural I stopped maintaining my CLOVER example.  If you read my instructions, you'll see that my CLOVER example was last updated for macOS Catalina.  DeviceProperties "graphic-options" is from a real MacMini8,1 DeviceProperties.  It is cosmetic.  I leave it in the DeviceProperties for my own personal reasons, but not needed for our hackintoshes.

 

I don't remember recommending any changes to your chosen value for AAPL,ig-platform-id, but why are you confused by the fact that your hack's behavior changes when you change AAPL,ig-platform-id?  That is exactly what you should expect.  it's important to experiment with various values for AAPL,ig-platform-id to find the one that works best for your hack.  You should recognize the EFI that Max.1974 provided since it is my MacMini8,1 EFI with a few modifications.  You may need to make the following changes to the EFI that he provided:

• PciRoot(0x0)/Pci(0x1F,0x3): DeviceProperty No-hda-gfx disables audio over DP/HDMI.  You will need to remove this DeviceProperty if you are not using graphics adapters and you want audio through your displays 
• PciRoot(0x0)/Pci(0x2,0x0): these device properties are specific to my hack's DP->DVI-D adapters.  They may or may not work for your hack.
• USBPorts-16.kext and USBPorts-noHS14.kext are specific USB port maps for my HP EliteDesk 800 G4/G4 mini.  I don't know if these USB port maps are suitable for your HP 400.  You can safely delete these kexts from your OC/Kexts folder

 

EDIT: Note that the USBPorts.kext in the EFI provided by Max.1974 is specifically for SMBIOS MacMini8,1 (the SMBIOS that I chose for my hack). You would need to change this if you are using a different SMBIOS.

Edited January 20 by deeveedee

[Max.1974]

Hi @deeveedee I found it on git hub

 

https://github.com/AiltonOcchi/EFI-Hackintosh-HP400-G5

 

@Asural just for test SSDTs you can choose your configuration that already works 🤩

 

 

[Max.1974]

14 hours ago, Asural said:

 

 

I'm currently testing the ACPI configuration you recommended.

I'm confused because the behavior changes depending on the AAPL and ig-platform-id selection, but I've currently selected <00009B3E>.

 

By the way, are there any specifications for graphic-options = <0C000000>?
 

 

 

Thanks, I was just giving up on @deeveedee's CLover sample.

I'll give it a try tomorrow, I'm too tired to open my PC today.

 

Append:

There's no FakeSMC...
I started installing Sequoia, but this EFI is just OpenCore, right?
 

 

Need looking for Clover EFI basic on Olarila.com  No suffering no stress !! After that you can do fine tune 

 

@Asural I would like you to do a test to see if the temperature goes down. Use only non-dynamic wallpapers, nothing like those that come with the system, please use only simple wallpapers. And please post the result. 

 

My Lenovo intel Comet Lake /  intel UHD 630 after change Wallpaper and no more lags 

 

 

 

Spoiler

 

 

 

 

 

 

 

 

 

 

 

Edited January 21 by Max.1974

[Asural]

15 hours ago, Max.1974 said:

Hi @deeveedee I found it on git hub

 

https://github.com/AiltonOcchi/EFI-Hackintosh-HP400-G5

 

@Asural just for test SSDTs you can choose your configuration that already works 🤩

 

 

 

The content is a copy of @deeveedee's, and it's for an old version of MacOS, so it doesn't work.
 

 

9 hours ago, Max.1974 said:

 

Need looking for Clover EFI basic on Olarila.com  No suffering no stress !! After that you can do fine tune 

 

@Asural I would like you to do a test to see if the temperature goes down. Use only non-dynamic wallpapers, nothing like those that come with the system, please use only simple wallpapers. And please post the result. 

 

My Lenovo intel Comet Lake /  intel UHD 630 after change Wallpaper and no more lags 

 

 

 

  Reveal hidden contents

 

 

 

 

 

 

 

 

 

 

 

 

I looked at Olarila.com, but it's difficult to find what I'm looking for among the ads.
I tried changing the wallpaper to a solid color, but there was no change in the temperature.
 

21 hours ago, deeveedee said:

@Max.1974 That looks familiar.  Where did you find that EFI?

 

@Asural I stopped maintaining my CLOVER example.  If you read my instructions, you'll see that my CLOVER example was last updated for macOS Catalina.  DeviceProperties "graphic-options" is from a real MacMini8,1 DeviceProperties.  It is cosmetic.  I leave it in the DeviceProperties for my own personal reasons, but not needed for our hackintoshes.

 

I don't remember recommending any changes to your chosen value for AAPL,ig-platform-id, but why are you confused by the fact that your hack's behavior changes when you change AAPL,ig-platform-id?  That is exactly what you should expect.  it's important to experiment with various values for AAPL,ig-platform-id to find the one that works best for your hack.  You should recognize the EFI that Max.1974 provided since it is my MacMini8,1 EFI with a few modifications.  You may need to make the following changes to the EFI that he provided:

• PciRoot(0x0)/Pci(0x1F,0x3): DeviceProperty No-hda-gfx disables audio over DP/HDMI.  You will need to remove this DeviceProperty if you are not using graphics adapters and you want audio through your displays 
• PciRoot(0x0)/Pci(0x2,0x0): these device properties are specific to my hack's DP->DVI-D adapters.  They may or may not work for your hack.
• USBPorts-16.kext and USBPorts-noHS14.kext are specific USB port maps for my HP EliteDesk 800 G4/G4 mini.  I don't know if these USB port maps are suitable for your HP 400.  You can safely delete these kexts from your OC/Kexts folder

 

EDIT: Note that the USBPorts.kext in the EFI provided by Max.1974 is specifically for SMBIOS MacMini8,1 (the SMBIOS that I chose for my hack). You would need to change this if you are using a different SMBIOS.

 

I'm currently investigating the system log, but since the content recorded varies slightly depending on the OS version, I'm currently testing it on a Tahoe.
When testing on a Sonoma, specifying AAPL,ig-platform-id = <06009B3E> in VGA.plist disables acceleration, but it displays normally on a Tahoe.

 

When the room temperature is 10°C, I don't notice much of a temperature rise, so I suspect it might be a bug in the Intel Power Gadget.

 

ADD：

I didn't state it clearly, but index1 = DPtoHDMI, index2 = built-in VGA, index3 = add-on VGA.

 

I hadn't created SSDT-XOSI.aml, so I added it.

There is no function to create SSDT-XSPI.aml, so what does SSDT do?
Nothing was working in the system log.
 

Dual.plist HDMI.plist VGA.plist

Edited January 21 by Asural

[Max.1974]

4 hours ago, Asural said:

 

The content is a copy of @deeveedee's, and it's for an old version of MacOS, so it doesn't work.
 

 

 

I looked at Olarila.com, but it's difficult to find what I'm looking for among the ads.
I tried changing the wallpaper to a solid color, but there was no change in the temperature.
 

 

I'm currently investigating the system log, but since the content recorded varies slightly depending on the OS version, I'm currently testing it on a Tahoe.
When testing on a Sonoma, specifying AAPL,ig-platform-id = <06009B3E> in VGA.plist disables acceleration, but it displays normally on a Tahoe.

 

When the room temperature is 10°C, I don't notice much of a temperature rise, so I suspect it might be a bug in the Intel Power Gadget.

 

ADD：

I didn't state it clearly, but index1 = DPtoHDMI, index2 = built-in VGA, index3 = add-on VGA.

 

I hadn't created SSDT-XOSI.aml, so I added it.

There is no function to create SSDT-XSPI.aml, so what does SSDT do?
Nothing was working in the system log.
 

Dual.plist 28.83 kB · 1 download HDMI.plist 28.29 kB · 0 downloads VGA.plist 28.29 kB · 0 downloads

 

@Asural  The EFI I posted is not outdated; I updated it to OpenCore 1.0.7, but okay. I hope you can manage to sort it out. This week I’m going on vacation and will be traveling.  

[Asural]

I investigated the system log to see what changes were made by changing the UHD630 framebuffer.
I concluded that only the Hackintool display changed, but the ioreg contents remained unchanged.
(I haven't verified the changes caused by the SMBIOS, so I'll post details later.)

 

Currently, the system log indicates that the temperature rise is related to communication...
1. Changed Kernel/Block/item0/com.apple.iokit.IOSkywalkFamily = YES to NO
2. Disabled MVMe settings in the BIOS and disabled Kernel/Add/item3/NVMeFix.kext
3. Set the HDMI framebuffer to LSPCON

 

The frequency of temperature rises has decreased.

I looked at the system log to find the time when the temperature rise occurred...
1. Bluetooth tries to connect even though it's not running.
2. com.apple.xnu:skywalk tries to connect even though it doesn't exist.

 

You can tell if Bluetooth is connected by monitoring ioreg because the color of the connector information changes.

Skywalk is not supposed to exist, but it's being started somewhere.

 

I read this thread and tried itlwm.kext, but it didn't work.

Do you know anything about the current communication settings for the Tahoe? Please let me know.
 

When I tested it with the RX570, I got a lot of similar system logs about Bluetooth and Skywalk, but no temperature rise.
 

ADD:

RealtekRTL8111.kext v3.0.4 is working fine on HP400G5SFF, thanks @Mieze,
It was working with v3.0.4 until yesterday, but today it only works with v2.4.2... This is a common problem, but the cause is unknown.

 

 

Base07.plist.zip

Edited January 26 by Asural

[Asural]

On 1/21/2026 at 5:30 AM, Max.1974 said:

Hi @deeveedee I found it on git hub

 

https://github.com/AiltonOcchi/EFI-Hackintosh-HP400-G5

 

 

@Asural just for test SSDTs you can choose your configuration that already works 🤩

 

 

Since FakeSMC is still running, I measured it using ACPIMonitor and IntelCPUMonitor as well.
Intel Power Gadget seems to have detected a temperature rise, but HWMonitor seems to have detected it as a voltage rise.
We won't know until after June whether the heat being emitted by the PC will be noticeable when the temperature rises.

 

With LCPCON installed, only the HDMI would not return on Sleep/WakeUP, so I removed LCPCON.
I think I'll leave the current settings as they are.
 

Base09.plist.zip

[Max.1974]

@Asural are you using Clover 🍀? Are you fix the processors temperature ? Congrats 🫡

[Asural]

16 minutes ago, Max.1974 said:

@Asural are you using Clover 🍀? Are you fix the processors temperature ? Congrats 🫡

Thank you!
However, I only used FakeSMC.kext and the contents are OpenCore.
I would like to start it with Clover, but I can't find any samples.

 

As for temperature rise, it will be difficult to observe unless the indoor temperature exceeds 20 degrees.