"wake from sleep" causes "Restart" - need help

[marcandre]

Following the Opencore guide, I built two hackintoshes, one on my HP ProBook 450 G6 laptop and the other on my desktop with an Asus TUF Gaming Z690. Everything is working.

Now I'm building another hackintosh with my old and good HP DV7 laptop. It's unbelievable that this laptop can run Monterey and Ventura so well. I want to keep it just for entertainment and light tasks. Almost everything is working.

The only problem I haven't been able to solve is "Wake from Sleep." Sleep is working, but when I try to wake from sleep, the laptop restarts (cold boot). I've tried for several days applying solutions but can't solve the problem. I'd appreciate any members who can help me solve the problem. Perhaps older members can help me because I was only able to install macOS using a DSDT with some patches applied. The attached .zip has the ioreg, terminal commands and EFI folder files.

Thanks to everyone.

HP DV7 2.zip

[marcandre]

Thanks for help verdazil, but didn't solved the restart from wake problem. Any other suggestions?

[Slice]

Look your DSDT for the method _WAK, it is responsible for a such behaviour.

[deeveedee]

@marcandre Do you see this behavior with High Sierra?  When I was getting my old laptop to run Big Sur through Sequoia with OCLP Post Install patches, I found it best to first make sure that High Sierra was working perfectly with my Open Core EFI, since High Sierra natively supports NVidia without OCLP.

 

I've seen this on my older hacks when switching from Clover to Open Core.  Try this:

• ACPI > Quirks > FadtEnableReset = True

 

I see that you have Broadcom Bluetooth kexts and Intel AirportItlwm.kext enabled - is this intentional?  Also, your config.plist seems to be a collection of attributes from multiple hacks - are you certain that all of your kexts and boot-args are relevant to this hack?

 

You might want to look at my EFI here for some ideas, since I am also using Open Core Legacy Patcher for my old NVidia graphics.

 

EDIT: If you test macOS High Sierra, do not install it on the same disk as Big Sur or later macOS.

Edited October 2, 2025 by deeveedee

[marcandre]

Slice, deeveedee. It's an honor to to talk to two longtime forum members.

 

20 hours ago, Slice said:

Look your DSDT for the method _WAK, it is responsible for a such behaviour.

Yes, it could be, and maybe the _PWR methods too. I've already looked at the DSDT in detail several times to identify any errors or if I forgot to include anything. I tried to do the best I could with my knowledge, but I'm not a DSDT expert. Perhaps you can help identify the problem and how to fix it. Thank you very much.

 

 

13 hours ago, deeveedee said:

@marcandre Do you see this behavior with High Sierra?  When I was getting my old laptop to run Big Sur through Sequoia with OCLP Post Install patches, I found it best to first make sure that High Sierra was working perfectly with my Open Core EFI, since High Sierra natively supports NVidia without OCLP.

 

I've seen this on my older hacks when switching from Clover to Open Core.  Try this:

• ACPI > Quirks > FadtEnableReset = True

 

I see that you have Broadcom Bluetooth kexts and Intel AirportItlwm.kext enabled - is this intentional?  Also, your config.plist seems to be a collection of attributes from multiple hacks - are you certain that all of your kexts and boot-args are relevant to this hack?

 

You might want to look at my EFI here for some ideas, since I am also using Open Core Legacy Patcher for my old NVidia graphics.

 

EDIT: If you test macOS High Sierra, do not install it on the same disk as Big Sur or later macOS.

I've never tried High Sierra; in fact, I only did my first two Hackintoshes, from Monterey to Ventura, on my other laptop and desktop.

With or without FadtEnableReset enabled, there's no difference. FadtEnableReset can help with restarting, but I don't have that problem.

Yes, this DV7 has a separate Broadcom Bluetooth and Intel WiFi.

The config.plist was created from scratch, and I used the settings I considered necessary for the laptop, running some configuration tests of course.

Because of the hardware (CPU, GPU, and Bluetooth), I need the kexts and boot-args to avoid a kernel panic or Bluetooth not working. Nothing unnecessary.

I looked at your EFI in detail. Wow, you did a good job and must have spent a lot of time getting to the final result. There are a lot of ketxts and patches. Unfortunately, I couldn't find anything in the EFI that could help solve the problem; mine and your laptop have very different hardware. But I appreciate you sharing your information.

And if you have any other tips, I'd appreciate it.

[deeveedee]

@marcandre It definitely sounds like you know what you're doing.  Have you tried asking ChatGPT (or your favorite AI chat bot)?

[marcandre]

On 10/3/2025 at 12:39 PM, deeveedee said:

@marcandre It definitely sounds like you know what you're doing.  Have you tried asking ChatGPT (or your favorite AI chat bot)?

Hey deeveedee, I saw in an old post of yours that you used ACPIDebug from Rehabman. Do you know if the kext still works with Ventura? I'm trying to use it to find the cause of the restart, but it's not working. Even though the process is simple—adding the kext, applying the patches, RMDT, and instruments from the repository, and adding the RMDT to the methods—no results appear in the logs. Any suggestions?

[deeveedee]

@marcandre I use Monterey for ACPIDebug.  Also, completely disable SIP (in Open Core: csr-active-config = <FF0F0000>).

Edited November 17, 2025 by deeveedee

[Thebes Knossos]

I had this problem on my old Acer.

Fixed with RTCMemoryFixup.kext . After you have to exclude memory region(s) 

https://dortania.github.io/OpenCore-Post-Install/misc/rtc.html#finding-our-bad-rtc-region

For my Acer this setting works:

            <key>4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102</key>  
            <dict>
                <key>rtc-blacklist</key>
                <data>sg==</data>
            </dict>

Edited November 25, 2025 by Thebes Knossos

[marcandre]

On 11/25/2025 at 10:56 AM, Thebes Knossos said:

I had this problem on my old Acer.

Fixed with RTCMemoryFixup.kext . After you have to exclude memory region(s) 

https://dortania.github.io/OpenCore-Post-Install/misc/rtc.html#finding-our-bad-rtc-region

For my Acer this setting works:

            <key>4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102</key>  
            <dict>
                <key>rtc-blacklist</key>
                <data>sg==</data>
            </dict>

Thanks for the tip Thebes Knossos, but that was one of the first things I tested. I did another test now just to be sure, and it didn't solve the problem. Apparently, this laptop doesn't have any bad regions. I also tested it now with High Sierra/Clover to see if the problem was only on the Ventura/Opencore, but the same thing happens. I've been trying to solve this for the last 30 days; it's discouraging. But thanks again.

[marcandre]

On 10/2/2025 at 3:39 AM, Slice said:

Look your DSDT for the method _WAK, it is responsible for a such behaviour.

Slice, you're the Clover expert
I'm currently using Clover with High Sierra to see if I can figure out the cause, but I haven't been able to solve it. If you can help me, I'd be grateful.

[marcandre]

Just to be clear, the system sleeps and I can "wake" the system by clicking the Power button, but instead of resuming, the system performs the BIOS Power-On Self Test and cold-boots. The logs do not show any errors which means the problem occurs before the kernel log is able to record

[Max.1974]

12 hours ago, marcandre said:

Just to be clear, the system sleeps and I can "wake" the system by clicking the Power button, but instead of resuming, the system performs the BIOS Power-On Self Test and cold-boots. The logs do not show any errors which means the problem occurs before the kernel log is able to record

Hi @marcandre 

 

I managed to get perfect sleep and wake, with Bluetooth and everything working, using these patches on my Lenovo T14, E470, and some of my desktops. Some of them are from Rehabman and others I edited myself.

 

USBWakeFixup.kext.zip

 

SSDT-GPRW.aml.zip

 

SSDT-SLEEP.aml.zip

 

SSDT-WAK.aml.zip

 

SSDT-PTWK.aml.zip

 

 

 

Opencore-patches-sleep-wake.plist.zip

 

 

[sambul65]

Hi Max.1974,

 

I can't wakeup my device with NVMe system drive from Hibernation when using Clover to boot it. No way to put it to sleep either, as it doesn't wakeup as well from it. Any help ideas? 

 

What are the advantages of using OpenCore vs Clover on an old laptop like yours? Are you booting Hakintosh or Windows, and from what drive type?

Edited December 6, 2025 by sambul65