How to Fix Troubleshooting Sudden "Mega Crash" and Fixes for macOS Performance Issues on MacBook Pro 11.1 (Late 2013) on macOS

By Ufuk Durgun
Apps Boot Graphics guide MacBookPro macOSBigSur macOSMonterey macOSSequoia macOSSonoma macOSVentura OpenCore OpenCoreLegacyPatcher Performance USB WiFi
--

How to Fix Troubleshooting Sudden "Mega Crash" and Fixes for macOS Performance Issues on MacBook Pro 11.1 (Late 2013) on macOS

Wi-Fi, Bluetooth, AWDL, Continuity and Location Services problems usually come from chipset support, kext pairing, privacy settings or network-location corruption.

1. Prerequisites

  • Identify the exact machine: Do not continue until the exact Mac identifier or motherboard/laptop model is known.
  • List the hardware: CPU, GPU, Wi-Fi/Bluetooth chipset, Ethernet controller, storage type and current macOS build must be written down.
  • Collect the tools: Keep OpenCore, OCLP, ProperTree, MountEFI, a USB installer and a backup disk ready.
  • Use verification tools: Confirm hardware with AIDA64, HWiNFO, Linux lspci, Windows Device Manager, macOS System Information or Hackintool.
  • Keep downloads local: Save required kexts before disconnecting from the network or editing EFI.
  • Do not rush: Verify hardware compatibility before changing BIOS settings, root patches or config.plist.

2. Compatibility Snapshot

  • Target type: Treat this as a OpenCore Hackintosh or OCLP case until the exact model proves otherwise.
  • CPU support: Intel Haswell, Skylake, Kaby Lake, Coffee Lake, Ice Lake and Tiger Lake are common OpenCore targets. AMD can work, but kernel patches and app compatibility must be considered.
  • GPU support: AMD GPUs are usually the safest dGPU route; NVIDIA support is limited after Kepler; Intel iGPU success depends on generation, DVMT and framebuffer configuration.
  • Motherboard and chipset: Prefer proper UEFI firmware on Intel Z/H/B series boards. Laptop firmware is stricter and should never be treated like a desktop guide.
  • RAM, storage, network and audio: Start without XMP when debugging, prefer compatible NVMe/SATA SSDs, identify the exact Wi-Fi/Bluetooth card and note the HDA audio codec.
  • Known risk areas: Graphics acceleration, USB mapping, Wi-Fi/Bluetooth, sleep/wake, Apple services and macOS updates are the first things to test.
  • Unsupported paths: Be cautious with NVIDIA Maxwell/Pascal/Turing/Ampere, Intel Iris Xe, experimental macOS Tahoe installs and unknown laptop Wi-Fi cards.
  • OpenCore vs Clover: Use OpenCore as the modern default. Mention Clover only for legacy context or migration.

3. Installation Preparation

  1. Back up first: Keep a Time Machine backup and a zipped copy of the current EFI folder on another disk.
  2. Identify hardware before starting: Use AIDA64, HWiNFO, Windows Device Manager, Linux lspci, macOS System Information or Hackintool before editing EFI.
  3. Prepare firmware: Disable Secure Boot, Fast Boot, CSM/Legacy and CFG Lock where possible. Disable VT-d unless DisableIoMapper is correctly configured.
  4. Enable required settings: Use UEFI mode, Above 4G Decoding where appropriate, Hyper-Threading, EHCI/XHCI Hand-off, OS Type > Other OS and SATA Mode > AHCI.
  5. Prepare graphics firmware: For iGPU systems, enable iGPU Multi-Monitor when required and set DVMT pre-allocated memory to at least 64 MB if the BIOS exposes it.
  6. Create the installer: Use a 16 GB or larger USB drive, GUID/GPT partitioning and a clean installer from App Store, OCLP, ANYmacOS or gibMacOS.
  7. Format correctly: Use APFS for Catalina and newer. Use HFS+ only for older releases where that is expected.
  8. Build or refresh EFI: Update OpenCore, Lilu, VirtualSMC and required kexts as a matched set, not as random individual files.
  9. Understand the installer phases: macOS usually reboots into an installer stage and then into the target disk continuation. Pick the correct entry in the OpenCore picker each time.
  10. For OCLP Macs: Build and install OpenCore with OpenCore Legacy Patcher, then apply post-install root patches after the first successful boot.

4. EFI and config.plist Review

  1. EFI layout: Check BOOT, OC/ACPI, OC/Drivers, OC/Kexts and OC/Tools. Every file in the folders must be reflected correctly in config.plist.
  2. Essential kexts: Confirm Lilu, VirtualSMC, WhateverGreen, AppleALC, IntelMausi or RealtekRTL8111, USBMap/UTBMap, NVMeFix and CPUFriend only when the hardware needs them.
  3. ACPI: Confirm SSDTs match the hardware generation and remove tables copied from unrelated builds.
  4. Common SSDTs: Review SSDT-EC, SSDT-PLUG, SSDT-AWAC, SSDT-PMC and SSDT-RHUB. Prefer correctly generated SSDTs over random prebuilt files.
  5. Booter: Check quirks recommended for the CPU generation; wrong memory quirks often cause early boot failure.
  6. DeviceProperties: Verify GPU, audio and network properties only contain values required for this machine.
  7. Kernel: Make sure kext order is sane: Lilu before plugins, VirtualSMC present, and network/graphics kexts matched to macOS.
  8. Misc and NVRAM: Use verbose boot when debugging: -v keepsyms=1 debug=0x100. Remove old experimental arguments once fixed.
  9. PlatformInfo: Use a suitable SMBIOS and never reuse serials from public EFI folders.
  10. SMBIOS examples: Many Coffee Lake+ desktops use iMac20,x style SMBIOS choices; many laptops use MacBookPro-style SMBIOS choices. Generate unique Serial, UUID and MLB with GenSMBIOS.
  11. UEFI: Confirm drivers such as OpenRuntime are current and that obsolete drivers are removed.
  12. Validation: Run ProperTree clean snapshot or ocvalidate after every meaningful edit.

5. Post-Installation

  1. First boot: Reset NVRAM, boot once with verbose mode, then remove temporary debug arguments after the system is stable.
  2. Move EFI internally: Mount the EFI partition on the USB and the target disk with MountEFI, copy the working EFI folder, then confirm the machine boots without the USB.
  3. Root patches: On unsupported Macs, run OCLP Post-Install Root Patch and reboot before judging graphics, Wi-Fi or audio.
  4. Core tests: Confirm Metal acceleration, audio, Ethernet/Wi-Fi, Bluetooth, sleep/wake, USB ports and shutdown.
  5. USB mapping: Map USB ports with USBToolBox/UTBMap.kext or USBMap.kext before relying on sleep, Bluetooth, internal cameras or installer input. Respect the macOS 15-port limit.
  6. Audio: Identify the HDA codec and test AppleALC layout IDs with alcid= or DeviceProperties injection.
  7. Wi-Fi and Bluetooth: Broadcom often uses AirportBrcmFixup paths; Intel usually uses itlwm/HeliPort or AirportItlwm. Bluetooth support varies by macOS release.
  8. iServices: Confirm unique ROM, MLB, serial and working NVRAM before troubleshooting iMessage, FaceTime, iCloud or the App Store.
  9. Power and sleep: Review SSDT-PLUG, CPU frequency scaling, USB mapping, hibernation and relevant pmset settings.
  10. DRM: Test protected video only after graphics acceleration is confirmed. WhateverGreen and shikigva settings are hardware-specific.
  11. Updates: Update OpenCore/OCLP and kexts before installing a macOS point update, not after a failed boot.

6. Troubleshooting

Likely Cause

On Hackintosh systems, Location Services and Continuity depend on working Wi-Fi, Bluetooth, AWDL and correct AirportItlwm or itlwm/HeliPort behaviour.

Reported Issue Fix
  1. Create a rollback point: Make a Time Machine backup and keep a copy of your last working EFI folder before editing OpenCore, kexts or root patches.
  2. Confirm the exact chipset: Identify the Wi-Fi, Bluetooth and Ethernet controller from System Information, Hackintool or Linux/Windows device manager.
  3. Use the correct network stack: Match AirportItlwm, itlwm, HeliPort, IntelBluetoothFirmware and BlueToolFixup to the exact macOS version.
  4. Reset macOS network state: Remove the current Wi-Fi service, reboot, add it again, then reconnect to a simple WPA2 network before testing advanced features.
  5. Check privacy permissions: Open System Settings > Privacy & Security > Location Services and confirm Location Services, Maps, Weather and system services are enabled.
  6. Test Apple features separately: Verify normal internet first, then Bluetooth, then AirDrop/Continuity. Do not debug all three at the same time.
Common Hackintosh/OCLP Checks
  • Kernel panics: Read the last verbose line and check /Library/Logs/DiagnosticReports after boot. Note whether the failure is EarlyBoot or UserSpace.
  • Stuck at Apple logo or progress bar: Boot with -v keepsyms=1 debug=0x100, photograph the last line and check Booter, Kernel and storage quirks.
  • LOG:EXITBS:START: Review firmware settings, CFG Lock, Booter quirks, OpenRuntime and outdated OpenCore files.
  • DSMOS has arrived or graphics hand-off stall: Check GPU support, WhateverGreen/NootedRed/NootRX choices, SMBIOS and display connector patches. Try -wegnoegpu or agdpmod=pikera only when the hardware calls for it.
  • USB keyboard, mouse or ports not working: Try a USB 2.0 hub, check XHCI settings, rebuild USB mapping and avoid exceeding the macOS port limit.
  • No graphics acceleration: Confirm Metal support in System Information, review framebuffer/AAPL ig-platform-id values and remove unsupported NVIDIA or Iris Xe assumptions.
  • Wi-Fi, Bluetooth, AWDL, Continuity or Location Services not working: Match AirportItlwm/itlwm, BlueToolFixup and Bluetooth firmware to the macOS version.
  • Ethernet not working: Confirm the PCI ID and switch between IntelMausi, RealtekRTL8111 or another hardware-specific kext as appropriate.
  • Audio missing or partial: Change the AppleALC layout ID, verify the HDA codec and remove conflicting audio injections.
  • Sleep, wake, battery drain or shutdown problems: Check USB mapping, power management, Bluetooth wake sources, hibernation and stale NVRAM.
  • Installer cannot see the disk or APFS/update errors: Confirm AHCI/NVMe support, APFS formatting, date/time, installer integrity and storage kexts. Recovery/prohibited errors can be caused by wrong system date.
  • iServices not working: Clear NVRAM, verify unique ROM/MLB/serial values and confirm the Apple ID is not blocked from activation.
  • App crashes, CEF/Chromium blank screens, Safari/App Store/iCloud issues: Verify graphics acceleration, network identity, SMBIOS services and hardware acceleration settings.
  • macOS update broke boot: Boot from the USB EFI, restore the previous EFI, use an APFS snapshot or restore from Time Machine before attempting another update.

7. Dual Boot and Advanced Configuration

  • Dual boot: Prefer separate physical disks for macOS and Windows/Linux where possible. A shared EFI can work, but it is easier to damage.
  • Windows recovery: If Windows fails after OpenCore changes, repair the Windows BCD and restore the desired boot order from firmware.
  • EFI protection: Keep a backup because Windows updates can overwrite, reorder or add EFI boot entries.
  • Boot picker: Use OpenCore picker entries deliberately and reset NVRAM after major bootloader changes.
  • Custom ACPI: Use iasl and MaciASL only when needed. Decompile the original DSDT and patch device paths such as _HID and _ADR carefully.
  • CFG Lock: GRUB or UEFI shell setup_var methods are risky; use them only with a verified offset for that exact BIOS.
  • SMBIOS refinement: Change SMBIOS only when needed for hardware support or Apple services, then re-test iMessage/iCloud carefully.
  • OpenCore polish: Add OpenCanopy, Resources, HiDPI icons and picker themes only after the system is reliable.
  • Advanced security: Consider Secure Boot Model, SIP, FileVault and root patch trade-offs only after the base system is reliable.
  • Performance tuning: Add CPU power management, USB mapping and sleep fixes after boot, graphics and network are already stable.

8. Verification, Maintenance and Rollback

Verification Checklist
  • Maps can locate you without falling back to a stale location.
  • Wi-Fi reconnects after reboot and sleep.
  • Bluetooth remains available after a cold boot.
  • Console no longer shows repeated wireless or location daemon errors.
Maintenance
  • Update OpenCore, OCLP and kexts before a macOS update, then reboot and test before installing the update itself.
  • Keep dated EFI backups, especially before changing SMBIOS, graphics patches, USB maps or root patches.
  • After every macOS update, check graphics acceleration, Wi-Fi/Bluetooth, audio, sleep/wake and Apple services again.
Rollback Plan
  • Restore the previous EFI if Wi-Fi disappears completely.
  • Switch from AirportItlwm to itlwm + HeliPort, or the reverse, if the issue is specific to one driver path.
  • Use Ethernet or USB tethering while testing so you do not lose access to downloads.

9. References and Glossary

  • Primary guide: Use the Dortania OpenCore Install Guide for architecture-specific OpenCore rules.
  • Project releases: Check Acidanthera release notes before updating OpenCore, Lilu, WhateverGreen, AppleALC or VirtualSMC.
  • Unsupported Macs: Use OpenCore Legacy Patcher model notes before installing or updating macOS on real Macs.
  • Community references: Compare symptoms with r/hackintosh, TonyMacx86 and InsanelyMac, but never copy an EFI without auditing it.
  • Glossary: EFI, ACPI, SSDT, DSDT, kexts, SMBIOS, NVMe, APFS, iGPU/dGPU, HDA, verbose, panic and picker are the key terms to understand.

Related searches: OpenCore · OCLP · EFI · macOS troubleshooting

Original Question: "Troubleshooting Sudden "Mega Crash" and Fixes for macOS Performance Issues on MacBook Pro 11.1 (Late 2013)"

Guide: Understanding and Resolving the Lag and Crashes on MacBook Pro 11.1 (Late 2013)

Experiencing a sudden crash with a half black, half white screen followed by extreme lag, graphical glitches, and desktop freezes on your MacBook Pro 11.1 (Late 2013) can be frustrating, especially when everything was working smoothly before. The crash you experienced could be caused by several factors, including GPU, CPU issues, or problems introduced during the patch process (e.g., PIpatch). Here's how to troubleshoot the situation and get your system back to working order.

Possible Causes of the "Mega Crash"

  1. Graphics Issues (GPU or iGPU):

    • The MacBook Pro 11.1 uses an Intel Iris Pro GPU, and sometimes these can have compatibility issues with patched graphics kexts. In particular, issues may arise with hardware acceleration or incorrect patches like PIpatch (which modifies the graphics settings).
    • The graphical glitches (like the rainbow wheel and the half-black screen) could point to a GPU crash, often due to an incompatible patch or missing driver (kext) for the integrated GPU.

  2. macOS Update and Patch Issues:

    • If macOS was trying to update in the background when the crash occurred, a pending update could have caused the system to behave erratically, especially when the system tries to apply updates that are incompatible with the current kexts or patches.
    • If you hadn’t disabled the automatic update feature or applied certain patches (like PIpatch), this could have triggered the system freeze or crash.

  3. Resource-Intensive Application (SketchUp):

    • SketchUp is a relatively resource-heavy application, and running it after a patch could have triggered the GPU or CPU to overheat or run into performance issues, especially if the system was patched improperly or if the GPU wasn’t fully supported in the patch.

Step-by-Step Guide to Solve the Issue

Step 1: Boot into Safe Mode

  1. Reboot your system while holding down the Shift key.
  2. This will boot macOS into Safe Mode, where only essential kexts and drivers are loaded. If the system works fine in Safe Mode, the issue is most likely related to a faulty kext or patch.
  3. If your system is stable in Safe Mode, proceed to the next steps. If the system still crashes, there may be a deeper issue with your hardware.

Step 2: Check GPU Settings and Remove Problematic Kexts

  1. Remove or Disable GPU Patches:

    • Since you mentioned using PIpatch and having issues, try disabling it or removing the associated kexts.
    • In your config.plist, disable or remove any settings related to graphics (e.g., device-id, framebuffer, etc.).

    Example of removing GPU patches:

    xml
    <key>Graphics</key>
<dict>
    <key>DisableGraphics</key>
    <true/>
</dict>

  2. Reset the NVRAM/PRAM:

    • After removing the patch, reset the NVRAM to clear any residual settings that might cause graphical glitches or configuration errors:
    • Turn off the Mac, and then hold Command + Option + P + R during boot until the system restarts.
    • This will reset display settings, volume, and other parameters that might be causing graphical issues.

Step 3: Check for Pending Updates and Disable Them

  1. Disable Automatic Updates:

    • As you encountered the "update pending" issue, it’s possible that macOS tried to apply an update when it wasn’t ready. To avoid future problems, disable automatic updates.

    • You can do this by going to System Preferences > Software Update, then uncheck the box that allows macOS to automatically download and install updates.

  2. Manually Check for Updates:

    • Once the system is stable, you can manually check for updates by going to System Preferences > Software Update and installing only those that are compatible with your patched system.

Step 4: Reapply the Patch Correctly

  1. Reinstall PIpatch: After ensuring the system is stable, reinstall the PIpatch (or other GPU patches). But ensure that you are using the correct kexts for your hardware, specifically the Intel Iris Pro GPU.

  2. Use OpenCore or OC Patcher:

    • If you are using OpenCore Patcher (as a tool to patch macOS), ensure that the config.plist is properly set up for your MacBook Pro 11.1 (Late 2013). Double-check the SMBIOS, GPU-related patches, and ensure the correct kexts are present.

Step 5: Check System Logs for Clues

  1. Check the Console Logs:
    • After rebooting and before applying patches, open Console.app (Applications > Utilities > Console) and check for any kernel panics, crash reports, or other warnings that could indicate the cause of the issue.
    • Look specifically for errors related to GPU, kexts, or graphics acceleration.

Step 6: Consider Using a Different Patch or Version of macOS

  1. Test Different Patches:
    • If PIpatch continues to cause issues, consider using a different patch or method for enabling GPU acceleration. For example, WhateverGreen.kext is a popular alternative for handling Intel GPUs.
  2. Try an Older macOS Version:
    • If you're running macOS Sonoma or another newer version and experiencing issues, consider downgrading to a stable version like macOS Ventura or macOS Monterey, which might be more compatible with your hardware.

Step 7: Hardware Check (Optional)

  1. Test the Hardware:
    • If you've tried all of the above steps and the issue persists, there could be a hardware-related issue. Check the RAM, SSD, and GPU using diagnostic tools or Apple Diagnostics to rule out any faulty components.

Conclusion

The "Mega Crash" you encountered was likely a combination of GPU-related issues, pending updates, and possibly a patch conflict. By following these steps, you can remove problematic patches, ensure system stability, and prevent the issue from happening again. Start with the basics: remove any unnecessary graphics patches, reset the NVRAM, disable automatic updates, and gradually reapply patches as needed.

If the issue continues despite these steps, consider testing a different patching method or downgrading to a more stable version of macOS.

Sudden "Mega Crash"

i'm on a macbook pro 11.1 ( late'13) 2,6Gz- 8Gb - Sequoia Patched.

mac went flawlessly for 3 days after the patch ( even better than before, i guess a total erase of 10 years of shit helped too) until yesterday i opened a sketchup file ( already used after patching) and things went antartica like south. sudden half black half white screen. stuck AF . rainbow roller etc. 10 min after still like this. forced shut. after rebooting desktop image turned to black and everithing was EXTREMELY laggy. specially graphic like opening windows effect ecc. i thought it was something about the GC patch so i tried removing PIpatch to rinstall later . but i ended up with the " update pending issue" and no internet connection to do the Mr. Macintosh workaround, lol

right now i've manage to connect through a THUNDER-ETH adapt disabled the phantom update, reinstalled PIpatch and everything seems back normal.
Main question is. WTF caused all of the massive initial freeze/fuckup ? was said update all the time or was a gpu-cpu issue? how to solve this w/o all this trouble lol?
Open patcher n00b

Thanks

submitted by /u/gilletti-
[link] [comments]
[► Source]
Share:
on 7:56:00 AM

Leave a Reply

Loading comments...