Yes I did but I'm afraid the kext folder is a bit to heavy for the forum. Do you need the full kext folder ? Or the config.plist is enough ?
-
Become a Premium Member for $25/year with no ads to improve your community experience. Upgrade to Pro Account for faster response and no wait times!
Random freezes on Sonoma 14.5
- Thread starter JMB13
- Start date
- Joined
- Jul 22, 2018
- Messages
- 9,074
- Motherboard
- Supermicro X11SPA-T
- CPU
- Intel Xeon W-3275 28 Core
- Graphics
- 2xAMD RX 580 8GB
- OS X/macOS
- 13.x
- Bootloader
- OpenCore (UEFI)
- Mac
- Mac mini
- MacBook Pro
- Mobile Phone
- Android
- iOS
EFI is normally supposed to be under 25MB limit. A few kexts like Itlwm and AirportItlwm doubles the size. As per the feedback, users will soon able to upload upto 50MB.
Although a full EFI is required, you can omit the kexts which are of bigger size.
- Joined
- Jul 22, 2018
- Messages
- 9,074
- Motherboard
- Supermicro X11SPA-T
- CPU
- Intel Xeon W-3275 28 Core
- Graphics
- 2xAMD RX 580 8GB
- OS X/macOS
- 13.x
- Bootloader
- OpenCore (UEFI)
- Mac
- Mac mini
- MacBook Pro
- Mobile Phone
- Android
- iOS
The EFI seems as per the guide and requires a few modifications only:
- You can fine tune by adding the MCHC (if the board doesn't expose one in IOReg or is MC which you can rename to MCHC).
- Another good advice would be to disable the ResizeAppleGpuBars using -1.
- You shouldn't require AAPL,slot-name for the Audio device.
- Kexts are not in sorted order. Mandatory kexts should load first.
- You should consider enabling the TRIM by setting the ApfsTrimTimeout to the macOS defaults using -1.
- Also, set the KernelArch to Any.
- As you're not using Hibernation, disable HibernateSkipsPicker.
- If you're not using Windows or Linux and/or don't need the IGPU there, you can disable it within the BIOS.
- Set the APFS MinDate and MinVersion to Auto.
The rest looks good!
- You can fine tune by adding the MCHC (if the board doesn't expose one in IOReg or is MC which you can rename to MCHC).
- Another good advice would be to disable the ResizeAppleGpuBars using -1.
- You shouldn't require AAPL,slot-name for the Audio device.
- Kexts are not in sorted order. Mandatory kexts should load first.
- You should consider enabling the TRIM by setting the ApfsTrimTimeout to the macOS defaults using -1.
- Also, set the KernelArch to Any.
- As you're not using Hibernation, disable HibernateSkipsPicker.
- If you're not using Windows or Linux and/or don't need the IGPU there, you can disable it within the BIOS.
- Set the APFS MinDate and MinVersion to Auto.
The rest looks good!
Hi !
You seem to have found the culprit. I didn't have crashes yet. Except when I installed a Crucial P3+ in replacement for the samsung that was formatted in exFat, after formatting it in APFS, seems to work properly. Tnanks !
Ragarding that, where can I find the info to understand what it is and how to do the changes ?
- Joined
- Jul 22, 2018
- Messages
- 9,074
- Motherboard
- Supermicro X11SPA-T
- CPU
- Intel Xeon W-3275 28 Core
- Graphics
- 2xAMD RX 580 8GB
- OS X/macOS
- 13.x
- Bootloader
- OpenCore (UEFI)
- Mac
- Mac mini
- MacBook Pro
- Mobile Phone
- Android
- iOS
Glad to hear that the culprit was found!
All these changes has to be made in your EFI.
- Joined
- Jul 22, 2018
- Messages
- 9,074
- Motherboard
- Supermicro X11SPA-T
- CPU
- Intel Xeon W-3275 28 Core
- Graphics
- 2xAMD RX 580 8GB
- OS X/macOS
- 13.x
- Bootloader
- OpenCore (UEFI)
- Mac
- Mac mini
- MacBook Pro
- Mobile Phone
- Android
- iOS
This seems to be a CPU related crash. Note that we had several cases where the CPU was actually faulty and had to be replaced and no crashes since then. At first the crashing rate was slow but it increased over time and was happening on other OS as well. Use Prime 95 to check. Raptor Lake and Raptor Lake Refresh are prone to crashing.
It could be also due to your BIOS Settings or some wrong parameters in EFI. If you can attach the EFI, it would be nice.
I ran the Prime 95 test, I freezed on mac but went to the end on both Windows 11 and Linux. I installed the latest BIOS version that takes in consideration the 13xxx and 14xxx issues, but eggtectively the default values are not the same, in perticulary SVID that is set by defaut to intel safety mode instead of auto and small and long duration power to 253. After I ran a memtest86 from windows and got errors with the 128GoRAM, meaning the 4 RAM slot populated. I removed 64Go and (removed A1B1 slots and kept A2B2 polulated as indicated in the MB user manal) and ran again memtest86, no issue. I highly doubt I have a RAM stick issue, I thing the issue is more to the MB that can't deal with 128Go/4 populated slots, at least with default values.
I'm running Rember mem test, so far no issue.
But... now when I start OSX, I have a memory mismatch issue notification just after login ! How can I get rid of that ? I did 2x reset NVRAM.
What do you need from my EFI ? Because I think I can't upload it entirely.
- Joined
- Jul 22, 2018
- Messages
- 9,074
- Motherboard
- Supermicro X11SPA-T
- CPU
- Intel Xeon W-3275 28 Core
- Graphics
- 2xAMD RX 580 8GB
- OS X/macOS
- 13.x
- Bootloader
- OpenCore (UEFI)
- Mac
- Mac mini
- MacBook Pro
- Mobile Phone
- Android
- iOS
Umm, if the processor has some sort of memory channel issues or some of the memory slots has dirts and lints, memtest will throw error so double check on that.
Also, these newer generation platforms have too much problems, not just on macOS. Try to disable XMP and then check. With XMP Enabled, some boards do not work well.
Follow Step #3 in the guide referenced below:
Also, ensure the RestrictEvents is implemented correctly.
The complete EFI. Use Google Drive.
Here is the goole drive link for the EFI :Umm, if the processor has some sort of memory channel issues or some of the memory slots has dirts and lints, memtest will throw error so double check on that.
Also, these newer generation platforms have too much problems, not just on macOS. Try to disable XMP and then check. With XMP Enabled, some boards do not work well.
Follow Step #3 in the guide referenced below:
Also, ensure the RestrictEvents is implemented correctly.
The complete EFI. Use Google Drive.
EFI - Google Drive
drive.google.com
Do you have more infos about how to implement RestrictEvents ?
Also regarding XMP, the performance wirh XMP enabled and disablesd are quite not the same ! I read also that I could give a little voltage boost on the RAM, but I'm not the king of overclocking, so I don't want to do mistakes. It seems to work well with 64Go RAM, and it is eufficient for me. Also if I want to go back to 128, I'll have to unmount all the cooling system, and I do'nt have time for that right now...
Regarding the stp 3, I dont have any Sleep Wake Failure files in /Library/Logs/DiagnosticReports
Last edited:
Similar threads
