In Monterey or Ventura during sleep (or at least black screen before sleep) I get this random freeze and the computer does not respond neither to the wake request, nor to the power reset button, so I have to force Power OFF button for shutdown. No errors are indicated and no panics are recorded. It does not happen in Windows so it is definitely MacOS specific.I have not had the freeze in Big Sur, though I have noticed random reboots (no apparent reason). Anyone has a hint on what to chase here? My OC settings and Bios settings are in my signature link for the x299.
x299 pro/se freeze in Monterey or Ventura
- startergo
- Erledigt
-
You are going with XCPMConfigLock via OpenCore instead of using it unlocked via BIOS? Why do you do so?
Is there no Option for that?Must be there, that might be the issue.
Quite much renames in ACPI Section, do you really need them? What’s your EFI built from? Full ACPI Patch based on the origin one?
Looked for that in your Textfile: found it and it is enabled, has to be disabled. Do so and don’t forget to disable the Quirk in OC. Should solve your issues. -
Thank you very much kaneske for the advise. I have changed the suggested settings and will monitor the performance.
Quite much renames in ACPI Section, do you really need them?
Are you talking about these?
What is wrong with them?
-
You’re welcome.
Yes those, since Renaming isn’t that usual today I ask why you’re using such. You must know why you did them. Any Reasons?
-
How do you map your usb things. Sounds like an usb issue.
-
Either this or defective RAM.
If you have working XCPM, of course.
-
How do you map your usb things. Sounds like an usb issue.
I use USBMap.kext, SSDT-X299-XHC.aml, SSDT-X299-XHCI.aml here.
Either this or defective RAM.
If you have working XCPM, of course.
How come the issue does not manifest itself in Windows if it was a defective RAM?
Interesting I have set up last night XMP profile for the RAM in BIOS and this morning the PC was not frozen.
-
nteresting I have set up last night XMP profile for the RAM in BIOS and this morning the PC was not frozen. Online
macOS is more Vulnerable in RAM issues than Windows is. XMP off may help many others with sleep.
Maybe you can set Timings manually and check if problem occurs.
-
Create a bootable usb thumbdrive with memtest on it. Boot with that drive and check your RAM completely.
i also have an x299 board, I don’t use unnecessary kexts or quirks.
i have an usb-ssdt and it works fine.
before I used a kext for that and also have problems with sleep / hibernate and some freezes.Take a look on how to create a custom usb ssdt. Trust me it is worth it.
-
Take a look on how to create a custom usb ssdt. Trust me it is worth it.
Any reference? Or can you attach yours as an example?
-
there are many sources on the web try to search for "USB-SSDT Hackintosh" also there is an how to here in the forum.
in the attachment you'll find my ssdt for reference. But you need to change the entire ports and settings to your needs.
Read everything attentive, it's hard for the first time. But I think it's the best way to map the usb ports correctly.
-
in the attachment you'll find my ssdt for reference
I don't see any currents defined there. Do they attach from somewhere else?
-
for me, in my case, this is in another SSDT, which I also use for Ethernet.
But I won't share it.for this you need add some code like this:
Alles anzeigenCode- Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method
- {
- If ((Arg0 == ToUUID ("a0b5b7c6-1318-441c-b0c9-fe695eaf949b") /* Unknown UUID */))
- {
- Local0 = Package (0x08)
- {
- "kUSBSleepPowerSupply",
- 0x13EC,
- "kUSBSleepPortCurrentLimit",
- 0x0834,
- "kUSBWakePowerSupply",
- 0x13EC,
- "kUSBWakePortCurrentLimit",
- 0x0834
- }
- DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))
- Return (Local0)
- }
-
Yes you're right.
You can also drop the original (it's the same way I suggested). or better you'll have to do it. If not all the crap things you don't need would be loaded (there are many ACPI things which aren't related (mostly) to Apple Computers.
and at the end of that file add the power delivery things. Or place this functionality on top of your ssdt. It doesn't matter.
But if you use the same original ssdt, there is too much unnecessary crap in it, this is why it would better to create a new one from what actually is in the original ssdt.
