Jump to content

3,259 posts in this topic

Recommended Posts

49 minutes ago, Andrey1970 said:

Delete it:

372314449_2020-01-2410_33_39.png.c80160d10a16dbd69fb6287b5410ee4d.png

 

And add HfsPlus.efi

HfsPlus.efi.zip

thanks Andrey1970 worked Recovery partition with HfsPlus.efi

I have second issue that when I play 60fps video 1080p with QuickTime player then little screen flickering black 

nothing issue with 30fps only issue is 60fps

I think this is Shiki related bug 

how can I solve this? any idea

Share this post


Link to post
Share on other sites
Advertisement

When you update OpenCore please make sure turnon KeySupport =Yes

 

 

1057976923_ScreenShot2020-01-24at7_03_41AM.png.64efff399c43316d303eb8d62144b62b.png

 

1516546508_ScreenShot2020-01-24at7_11_17AM.thumb.png.932083f1adf6978c673ac2cc50195ca4.png

 

 

PMCR update for X299 WU8

SSDT-PMC1.aml

 

1219603178_ScreenShot2020-01-24at8_16_31AM.png.a8d1ac84d9dc6da427d1fa519942dfca.png

 

Edited by nmano

Share this post


Link to post
Share on other sites
3 hours ago, nmano said:

When you update OpenCore please make sure turnon KeySupport =Yes

 

 

1057976923_ScreenShot2020-01-24at7_03_41AM.png.64efff399c43316d303eb8d62144b62b.png

 

1516546508_ScreenShot2020-01-24at7_11_17AM.thumb.png.932083f1adf6978c673ac2cc50195ca4.png

 

 

PMCR update for X299 WU8

SSDT-PMC1.aml

 

1219603178_ScreenShot2020-01-24at8_16_31AM.png.a8d1ac84d9dc6da427d1fa519942dfca.png

 

 

Method STA & Name CRS must be outside Method DSM

 

Screen Shot 2020-01-24 at 17.43.20.png

Share this post


Link to post
Share on other sites

Hey,

 

How to rename ECDV to EC using Opencore? I tried this, but no luck:

 

 

Screen Shot 2020-01-24 at 6.02.10 PM.png

Share this post


Link to post
Share on other sites
12 minutes ago, Andrey1970 said:

R: 45435F5F 

Looks like it isn't working. After boot:

 

 

Screen Shot 2020-01-24 at 6.28.18 PM.png

Share this post


Link to post
Share on other sites

Hi

I have a problem I have tried this in Mojave and Catalina but both macOS the result is same. the issue is when I use Bootcamp to install Windows 10 it starts and complete the installation in macOS. but when it restarts some how BOOT folder DELETES itself from EFI folder which render non bootable and system goes into BIOS setup screen. OC folder remains intact.

Any help appreciated,

Thank you,

Share this post


Link to post
Share on other sites

@Andrey1970 do you have any idea why BOOT folder in EFI folder deletes itself when using BootCamp? tried several times but result is same.

 

Thank you,

Share this post


Link to post
Share on other sites
35 minutes ago, mathew2019 said:

@Andrey1970 do you have any idea why BOOT folder in EFI folder deletes itself when using BootCamp? tried several times but result is same.

 

Thank you,

Because Winblows installs it own EFI, which will delete any existing EFI currently on the ESP. It’s best to completely disconnect the drive that you have your opencore EFI on when installing Winblows.

Share this post


Link to post
Share on other sites

Hi Pavo

 

Thank you for the reply but it wont delete the entire EFI folder. The OC folder in EFI folder / partition is still there..only BOOT folder which contains BOOTX64.efi deletes. so is it a bug or some settings need to be added in Config.plist? Please see the screen shot of EFI folder attached here with.

 

 

OC-EFI-FOlder.png

Edited by mathew2019

Share this post


Link to post
Share on other sites

The BootX64.efi is basically a re-directing module. That is what UEFI looks for in drives in order to add it to the boot menu entry for your mobo. If you are installing Windows it "could" potentially replace that file for its own which will make the BootX64.efi file direct it to the Winblows boot.efi (windows bootloader) location. Again I suggest you disconnect the drive completely that has OpenCore EFI on it and install Windows on its own.

 

Share this post


Link to post
Share on other sites

Pavo

 

But then how do you dual boot with Windows on single drive? because I am partitioning it and there is no other drive..

Share this post


Link to post
Share on other sites
4 minutes ago, mathew2019 said:

Pavo

 

But then how do you dual boot with Windows on single drive? because I am partitioning it and there is no other drive..

You install Winblows first and then install macOS second and add your OpenCore EFI after.

Share this post


Link to post
Share on other sites
1 hour ago, mathew2019 said:

Pavo

 

But then how do you dual boot with Windows on single drive? because I am partitioning it and there is no other drive..

 

You have to deploy Windows manually using DISM tool. Here is manual. It's in russian. Use Google translate. 

https://applelife.ru/threads/manual-ustanovka-macos-i-windows-na-odin-xard-poshagovo.38295/page-30#post-548639

 

Share this post


Link to post
Share on other sites
4 hours ago, Pavo said:

Because Winblows installs it own EFI, which will delete any existing EFI currently on the ESP. It’s best to completely disconnect the drive that you have your opencore EFI on when installing Winblows.

umm no it doesnt. it removes BOOTX64.efi and the /EFI/BOOT folder as part of the boot camp installation, when OS X and Windows are shared on the same disk.

 

so much misinformation in this thread these days, reminds me more of a clover thread.

 

 

Just install OS X first as then use the boot camp assistant to install Windows.

 

note more recent versions of boot camp assistant may create the modified windows installer on a ExFat usb drive instead of Fat32.

 

either copy the files onto a Fat32 or add a ExFat uefi driver to OpenCore.

Edited by UefiBooter
spelling

Share this post


Link to post
Share on other sites
19 hours ago, HmO said:

 

Method STA & Name CRS must be outside Method DSM

 

Screen Shot 2020-01-24 at 17.43.20.png

If you remove DSM you can't get this detail.

1691207619_ScreenShot2020-01-25at5_46_48AM.thumb.png.cb7f8aa9717fc852a20f720d56bb4126.png

Share this post


Link to post
Share on other sites
13 hours ago, UefiBooter said:

umm no it doesnt. it removes BOOTX64.efi and the /EFI/BOOT folder as part of the boot camp installation, when OS X and Windows are shared on the same disk.

 

so much misinformation in this thread these days, reminds me more of a clover thread.

 

 

Just install OS X first as then use the boot camp assistant to install Windows.

 

note more recent versions of boot camp assistant may create the modified windows installer on a ExFat usb drive instead of Fat32.

 

either copy the files onto a Fat32 or add a ExFat uefi driver to OpenCore.

Exactly this is what I was also initially doubt on, because in clover if you install dual boot with Windows the Windows wont delete the EFI folder nor boot folder. so if this happens only on Opencore then it should be something to do with the boot loader. I wasn't using USB installer as in Catalina if you use bootcamp then it will ask for Windows installer iso and it create some background installer process then systems restarts. this time the system boots into BIOS instead of starting install procedure. 

 

If you add BOOT folder manually to the EFI partition/folder then you can complete the Windows installation without any issues. you do not need any USB installer to compete Windows installation. If you choose manual option then on boot picker windows installer option still remains and every time system will boot into the Windows setup. 

 

I will try your suggestion and also look into vandroiy2012 instruction to see if this resolves the issues, I will post it back the results,

 

Thank you,

Edited by mathew2019

Share this post


Link to post
Share on other sites
1 hour ago, nmano said:

If you remove DSM you can't get this detail.

1691207619_ScreenShot2020-01-25at5_46_48AM.thumb.png.cb7f8aa9717fc852a20f720d56bb4126.png

How about you stick to original SSDT-PMC.aml like @HmO suggests, and additionally try to add "this detail" via config.plist>DeviceProperties?

Share this post


Link to post
Share on other sites
1 hour ago, mathew2019 said:

Exactly this is what I was also initially doubt on, because in clover if you install dual boot with Windows the Windows wont delete the EFI folder nor boot folder. so if this happens only on Opencore then it should be something to do with the boot loader. I wasn't using USB installer as in Catalina if you use bootcamp then it will ask for Windows installer iso and it create some background installer process then systems restarts. this time the system boots into BIOS instead of starting install procedure. 

 

If you add BOOT folder manually to the EFI partition/folder then you can complete the Windows installation without any issues. you do not need any USB installer to compete Windows installation. If you choose manual option then on boot picker windows installer option still remains and every time system will boot into the Windows setup. 

 

I will try your suggestion and also look into vandroiy2012 instruction to see if this resolves the issues, I will post it back the results,

 

Thank you,

 

I forgot to mention, i put the OpenCore BOOTX64.efi inside /EFI/OC and add it manually using bcfg boot add 0 BOOTX64.EFI "BootStrap"

 

Share this post


Link to post
Share on other sites

After 2 days struggling finally, I can make a boot :hyper: But I have a problem; every restart I am getting AMI post screen go to BIOS with F1 and choosing "Discard Changes & Exit" then boot. Why I am getting this on every restart or boot?

 

IMG_0104.thumb.JPG.363e9dbb3c676459386f6b2dd0cf85e4.JPG

Edited by telepati

Share this post


Link to post
Share on other sites
10 minutes ago, telepati said:

After 2 days struggling finally, I can make a boot :hyper: But I have a problem; every restart I am getting AMI post screen go to BIOS with F1 and choosing "Discard Changes & Exit" then boot. Why I am getting this on every restart or boot?

 

IMG_0104.thumb.JPG.363e9dbb3c676459386f6b2dd0cf85e4.JPG

go in to your bios an you can hide the F1 post

Share this post


Link to post
Share on other sites
14 minutes ago, telepati said:

After 2 days struggling finally, I can make a boot :hyper: But I have a problem; every restart I am getting AMI post screen go to BIOS with F1 and choosing "Discard Changes & Exit" then boot. Why I am getting this on every restart or boot?

 

Just enable this patch. It's an RTC problem. Or you can use RTCMemoryFixup.kext https://github.com/acidanthera/RTCMemoryFixup

 

924336774_2020-01-2519_06_24.png.6212afbafe7e1436404eac062bfe85f1.png

Edited by vandroiy2012

Share this post


Link to post
Share on other sites

Does  OpenCore support Sandy Bridge cpu?

Does  VirtualSMC.kext support Sandy Bridge cpu?

Share this post


Link to post
Share on other sites
4 minutes ago, anmool said:

Does  OpenCore support Sandy Bridge cpu?

Does  VirtualSMC.kext support Sandy Bridge cpu?

Yes. Yes. But these questions don't belong to the bootloader.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Similar Content

    • By DanZiRuleZ
      Dear All, 
       
      trying to install Catalina on my ASUS Z87 Plus, I followed the Haswell guide to the letter, all set up now, USB stick boots ok, Catalina installs on SSD, but then when trying to boot it I am receiving Kernel Panic and no idea how to move forward. 
       
      Have the debug options, but opencore will only dump boot messages where I don't see much sticking out.
       
      My last resort would be just installing clover on the already installed SSD's EFI partition, it at all possible. High Sierra is working fine and I did get Clover with Mojave once but stuck with High Sierra with my GTX960 video card...
       
      Attached is the kernel panic and my EFI setup if anyone can help me troubleshoot.
      Many thanks
      D.
       

      EFI.zip
    • By n.d.k
      After several weeks of testing OC bootloader,  disecting its source code and also Clover's source code as well, I finally switch from Clover to OC as my main bootloader. Wait! don't get the wrong idea that OpenCore is better than Clover. They both work equally well, producing a bootable macOS as an end result with simliar boot time. OC design direction is different with Clover, I believe it's not intended as a Clover replacement, but more narrowing down to macOS specifically. However, macOS is not the only OS that i am using, so, i decided to add some minimal necessary source code modification to the OC to get some of the features I need. I like to share my customized OC forked https://github.com/n-d-k/OpenCorePkg , you have to compile it yourself if you want, i will not provide pre build binary.    
       
      Additional features/changes:
      ============
       
      [ Multi-Boot ]
        - ACPI patches are optional for non macOS with setting ACPI->Quirks->EnableForAll to yes (default is no).
        - Booter Quirtks, SMBIOS and Device Properties patches will only applied to macOS.
          
      [ Hotkeys ]
        - Full functional Hotkeys [1-9] corresponding to Boot Entry's Index number and dedicated W (Windows) / X (macOS) keys can be used without seeing Boot Picker.
        - While in boot picker, F10 can use to take a snapshot of the screen.
                
      [ Ui Boot Picker ]
        - Bios Date/time, auto boot to the same OS or manual set to always boot one OS mode, and OC version are displayed in boot picker.
        - Auto boot to previous booted OS (if Misc->Security->AllowSetDefault is NO/false).
        - macOS Recovery/Tools Entries are hidden by default, use Spacebar in Boot Menu as a toggle on/off to show/hide hidden entries.
                
      [ Custom Entries ]
         - Custom entries are now listed first in picker menu and by the orders they are appeared in Misc->Boot->Entries, before all other entries.
         - Ability to change entry name found by auto scanner by adding custom entry with the exact same device path,
           this will give users the option to complete change how all boot entries listed in Boot Picker.
          
      [ Others ]
         - No verbose apfs.efi driver loading (if using apfs.efi instead of ApfsDriverLoader.efi).
          - ndk-macbuild.tool script are set to compile with latest edk2 (One can easily set to stable edk2 if prefer).
          - NvmExpressDxe driver build script are also available for system without native nvme support. (Compatible with OC and Clover).
       
      Usage:
       - To build OpenCore, run "./ndk-macbuild.tool" at Terminal (require Xcode and Xcode Command Line Tool installed, and open xcode to accept license agreement before compiling).
       - To build NvmExpressDxe driver, run "./buildnvme.sh".
       
      4k screen resolutions

       
       

       
      Customized by @btwise

       
       
       
    • By SniperBuddy
      Hello guys,
      I'm relatively new to the world of hackintosh.
      I'm trying to install the latest Mac OS - Catalina with the help of Opencore, however, this is the error that's displayed while booting from the USB:
       
      https://drive.google.com/open?id=1Xd4V2wZ2fEsgRyfVcXlJHXMPGa85g2s3
       
      You can take a look at my config.plist file from here - https://drive.google.com/file/d/17FZpTcVp4RFSaxdm6yW4uELkt7MaLdmt/view?usp=sharing
       
      I'm using the Acer E575 G laptop with Kabylake (i5 7200u)
       
      Any help would be gladly appreciated!
       
       
       
       
    • By Krani93
      Hi guys,
       
      I'm trying to install Catalina on a Lenovo m720q (i5-8600T with B360).
      After some other issues I'm know stuck at attached screen.
      Im using latest opencore version and have my EFI folder attached.
       
      Can someone help me I've got no clue what to try next :/ 
       
       
      Cheers!

      EFI.7z
    • By BlitzPanzer
      Catalina 10.15.3, OC 0.5.5

      Follow the OpenCore AMD Vanilla Guide, everything works fine iMessage, Siri, FaceTime, Continuity, Airdrop, Audio, WiFi
      But here is the problem
      Once I restart or shutdown and reboot, I will have kernel panic, so i have to reboot once again, then no more kernel panic, straight back to the system.
      Down below are the 3 kernel panic reports I got after I am back to the system, also provided specs, kexts, drivers and config.plist I used.
      Please someone help me with the problem
      Thanks in advanced   

      System Specs
      CPU: Ryzen R5 3600
      MOBO: MSI B450 Mortar Max
      RAM: Kingston HyperX Fury 16GB*2 3200MHz DDR4
      SSD: Kingston A2000 500GB NVMe PCIe
      GPU: Gigabyte RX 570 Gaming 4G v2.0
      PCIe: BCM943602CS Kexts:
      AppleALC
      AppleMCEReporterDisabler
      BrcmBluetoothInjector
      BrcmPatchRAM3
      HDMIAudio
      Lilu
      MacProMemoryNotificationDisabler
      NightShiftUnlocker
      NVMeFix
      RealtekRTL8111
      VirtualSMC
      WhateverGreen Drivers:
      ApfsDriverLoader
      AppleUsbKbDxe
      FwRuntimeServices
      VBoxHfs config.plist:
      https://drive.google.com/file/d/1M22Tvn7W-Zf_b_-J52oLcfjECj5qAcp6/view

      Kernel Panic Report 1
      panic(cpu 0 caller 0xffffff801b8652fa): Kernel trap at 0xffffff7f9f212fe3, type 14=page fault, registers: CR0: 0x000000008001003b, CR2: 0xffffffa3ce87c000, CR3: 0x00000000263ba000, CR4: 0x00000000003406e0 RAX: 0xffffffa3ce87c000, RBX: 0x0000000000005434, RCX: 0x0000000002000000, RDX: 0x0000000003000000 RSP: 0xffffffa3ce75bb60, RBP: 0xffffffa3ce75bb80, RSI: 0xffffff806d3141c0, RDI: 0x0000000000000000 R8: 0x0000000000000001, R9: 0x0000000000000026, R10: 0x00000000f8000000, R11: 0x0000000000000070 R12: 0xffffff805cc7c900, R13: 0xffffff835806f000, R14: 0x0000000000000000, R15: 0xffffff8068d2da50 RFL: 0x0000000000010246, RIP: 0xffffff7f9f212fe3, CS: 0x0000000000000008, SS: 0x0000000000000010 Fault CR2: 0xffffffa3ce87c000, Error code: 0x0000000000000002, Fault CPU: 0x0, PL: 0, VF: 1 Backtrace (CPU 0), Frame : Return Address 0xffffffa3ce75b5c0 : 0xffffff801b73bb2b mach_kernel : _handle_debugger_trap + 0x47b 0xffffffa3ce75b610 : 0xffffff801b8734d5 mach_kernel : _kdp_i386_trap + 0x155 0xffffffa3ce75b650 : 0xffffff801b864f4e mach_kernel : _kernel_trap + 0x4ee 0xffffffa3ce75b6a0 : 0xffffff801b6e2a40 mach_kernel : _return_from_trap + 0xe0 0xffffffa3ce75b6c0 : 0xffffff801b73b217 mach_kernel : _DebuggerTrapWithState + 0x17 0xffffffa3ce75b7c0 : 0xffffff801b73b5fb mach_kernel : _panic_trap_to_debugger + 0x21b 0xffffffa3ce75b810 : 0xffffff801bed2aa9 mach_kernel : _panic + 0x61 0xffffffa3ce75b880 : 0xffffff801b8652fa mach_kernel : _sync_iss_to_iks + 0x2aa 0xffffffa3ce75ba00 : 0xffffff801b864ff8 mach_kernel : _kernel_trap + 0x598 0xffffffa3ce75ba50 : 0xffffff801b6e2a40 mach_kernel : _return_from_trap + 0xe0 0xffffffa3ce75ba70 : 0xffffff7f9f212fe3 com.apple.kext.AMDRadeonX4000 : __ZN29AMDRadeonX4000_AMDHWRegisters4readEj + 0x53 0xffffffa3ce75bb80 : 0xffffff7f9f24a795 com.apple.kext.AMDRadeonX4000 : __ZN28AMDRadeonX4000_AMDVIHardware19getRegisterAperSizeEv + 0x23 0xffffffa3ce75bba0 : 0xffffff7f9f212ef0 com.apple.kext.AMDRadeonX4000 : __ZN29AMDRadeonX4000_AMDHWRegisters4initEP11IOPCIDeviceP30AMDRadeonX4000_IAMDHWInterface + 0xfa 0xffffffa3ce75bbe0 : 0xffffff7f9f2325c1 com.apple.kext.AMDRadeonX4000 : __ZN26AMDRadeonX4000_AMDHardware4initEP11IOPCIDeviceP28AMDRadeonX4000_IAMDHWHandlerRjP16_GART_PARAMETERSP14_FB_PARAMETERS + 0x257 0xffffffa3ce75bc30 : 0xffffff7f9f1b8adb com.apple.kext.AMDRadeonX4000 : __ZN37AMDRadeonX4000_AMDGraphicsAccelerator17createHWInterfaceEP11IOPCIDevice + 0x7b 0xffffffa3ce75bc70 : 0xffffff7f9f1b64be com.apple.kext.AMDRadeonX4000 : __ZN37AMDRadeonX4000_AMDGraphicsAccelerator15configureDeviceEP11IOPCIDevice + 0x10a 0xffffffa3ce75bd00 : 0xffffff7f9f128534 com.apple.iokit.IOAcceleratorFamily2 : __ZN22IOGraphicsAccelerator25startEP9IOService + 0x21e 0xffffffa3ce75bd80 : 0xffffff7f9f1b488e com.apple.kext.AMDRadeonX4000 : __ZN37AMDRadeonX4000_AMDGraphicsAccelerator5startEP9IOService + 0x82 0xffffffa3ce75bde0 : 0xffffff801be1b216 mach_kernel : __ZN9IOService14startCandidateEPS_ + 0xf6 0xffffffa3ce75be40 : 0xffffff801be1adc1 mach_kernel : __ZN9IOService15probeCandidatesEP12OSOrderedSet + 0xb21 0xffffffa3ce75bef0 : 0xffffff801be1a10e mach_kernel : __ZN9IOService14doServiceMatchEj + 0x2ce 0xffffffa3ce75bf50 : 0xffffff801be1c8ad mach_kernel : __ZN15_IOConfigThread4mainEPvi + 0x15d 0xffffffa3ce75bfa0 : 0xffffff801b6e213e mach_kernel : _call_continuation + 0x2e Kernel Extensions in backtrace: com.apple.iokit.IOAcceleratorFamily2(438.3.1)[66992525-3204-3CB0-8F03-4B70031B1CF2]@0xffffff7f9f0f0000->0xffffff7f9f1b2fff dependency: com.apple.driver.AppleMobileFileIntegrity(1.0.5)[A243D030-19AC-30AA-AC70-6C786DF9E6CE]@0xffffff7f9c185000 dependency: com.apple.iokit.IOPCIFamily(2.9)[ADD485B5-3EF8-37C4-B3C5-F86326E497A4]@0xffffff7f9c2f8000 dependency: com.apple.iokit.IOSurface(269.6)[42377B3B-D14A-368E-820F-07E7EA666198]@0xffffff7f9d454000 dependency: com.apple.iokit.IOGraphicsFamily(569.4)[1F9B5D88-52DB-3A16-8373-4F608A3CB2D8]@0xffffff7f9df73000 dependency: com.apple.iokit.IOReportFamily(47)[988360A2-2E10-3014-A119-BE81BC045A10]@0xffffff7f9c228000 com.apple.kext.AMDRadeonX4000(3.0.5)[5FD7AE5F-C03C-34A1-803F-ACA9B68524D0]@0xffffff7f9f1b3000->0xffffff7f9f6f7fff dependency: com.apple.iokit.IOPCIFamily(2.9)[ADD485B5-3EF8-37C4-B3C5-F86326E497A4]@0xffffff7f9c2f8000 dependency: com.apple.iokit.IOSurface(269.6)[42377B3B-D14A-368E-820F-07E7EA666198]@0xffffff7f9d454000 dependency: com.apple.iokit.IOGraphicsFamily(569.4)[1F9B5D88-52DB-3A16-8373-4F608A3CB2D8]@0xffffff7f9df73000 dependency: com.apple.iokit.IOAcceleratorFamily2(438.3.1)[66992525-3204-3CB0-8F03-4B70031B1CF2]@0xffffff7f9f0f0000 BSD process name corresponding to current thread: kernel_task Boot args: debug=0x100 keepsyms=1 alcid=1 -v shikigva=128 Mac OS version: 19D76 Kernel version: Darwin Kernel Version 19.3.0: Thu Jan 9 20:58:23 PST 2020; root:xnu-6153.81.5~1/RELEASE_X86_64 Kernel UUID: A8DDE75C-CD97-3C37-B35D-1070CC50D2CE Kernel slide: 0x000000001b400000 Kernel text base: 0xffffff801b600000 __HIB text base: 0xffffff801b500000 System model name: MacPro7,1 (Mac-27AD2F918AE68F61) System shutdown begun: NO Panic diags file available: NO (0xe00002bc) System uptime in nanoseconds: 47565362999  
      Kernel Panic Report 2
      panic(cpu 10 caller 0xffffff801b8652fa): Kernel trap at 0xffffff7f9e629fe3, type 14=page fault, registers: CR0: 0x000000008001003b, CR2: 0xffffff83d25d2000, CR3: 0x0000000029068000, CR4: 0x00000000003406e0 RAX: 0xffffff83d25d2000, RBX: 0x0000000000005434, RCX: 0x0000000002000000, RDX: 0x0000000003000000 RSP: 0xffffff83d14c3b60, RBP: 0xffffff83d14c3b80, RSI: 0xffffff805f6adb80, RDI: 0x0000000000000000 R8: 0x0000000000000001, R9: 0x0000000000000026, R10: 0x00000000f8000000, R11: 0x0000000000000070 R12: 0xffffff805fba2580, R13: 0xffffff835b02e000, R14: 0x0000000000000000, R15: 0xffffff80631191e0 RFL: 0x0000000000010246, RIP: 0xffffff7f9e629fe3, CS: 0x0000000000000008, SS: 0x0000000000000010 Fault CR2: 0xffffff83d25d2000, Error code: 0x0000000000000002, Fault CPU: 0xa, PL: 0, VF: 1 Backtrace (CPU 10), Frame : Return Address 0xffffff83d14c35c0 : 0xffffff801b73bb2b mach_kernel : _handle_debugger_trap + 0x47b 0xffffff83d14c3610 : 0xffffff801b8734d5 mach_kernel : _kdp_i386_trap + 0x155 0xffffff83d14c3650 : 0xffffff801b864f4e mach_kernel : _kernel_trap + 0x4ee 0xffffff83d14c36a0 : 0xffffff801b6e2a40 mach_kernel : _return_from_trap + 0xe0 0xffffff83d14c36c0 : 0xffffff801b73b217 mach_kernel : _DebuggerTrapWithState + 0x17 0xffffff83d14c37c0 : 0xffffff801b73b5fb mach_kernel : _panic_trap_to_debugger + 0x21b 0xffffff83d14c3810 : 0xffffff801bed2aa9 mach_kernel : _panic + 0x61 0xffffff83d14c3880 : 0xffffff801b8652fa mach_kernel : _sync_iss_to_iks + 0x2aa 0xffffff83d14c3a00 : 0xffffff801b864ff8 mach_kernel : _kernel_trap + 0x598 0xffffff83d14c3a50 : 0xffffff801b6e2a40 mach_kernel : _return_from_trap + 0xe0 0xffffff83d14c3a70 : 0xffffff7f9e629fe3 com.apple.kext.AMDRadeonX4000 : __ZN29AMDRadeonX4000_AMDHWRegisters4readEj + 0x53 0xffffff83d14c3b80 : 0xffffff7f9e661795 com.apple.kext.AMDRadeonX4000 : __ZN28AMDRadeonX4000_AMDVIHardware19getRegisterAperSizeEv + 0x23 0xffffff83d14c3ba0 : 0xffffff7f9e629ef0 com.apple.kext.AMDRadeonX4000 : __ZN29AMDRadeonX4000_AMDHWRegisters4initEP11IOPCIDeviceP30AMDRadeonX4000_IAMDHWInterface + 0xfa 0xffffff83d14c3be0 : 0xffffff7f9e6495c1 com.apple.kext.AMDRadeonX4000 : __ZN26AMDRadeonX4000_AMDHardware4initEP11IOPCIDeviceP28AMDRadeonX4000_IAMDHWHandlerRjP16_GART_PARAMETERSP14_FB_PARAMETERS + 0x257 0xffffff83d14c3c30 : 0xffffff7f9e5cfadb com.apple.kext.AMDRadeonX4000 : __ZN37AMDRadeonX4000_AMDGraphicsAccelerator17createHWInterfaceEP11IOPCIDevice + 0x7b 0xffffff83d14c3c70 : 0xffffff7f9e5cd4be com.apple.kext.AMDRadeonX4000 : __ZN37AMDRadeonX4000_AMDGraphicsAccelerator15configureDeviceEP11IOPCIDevice + 0x10a 0xffffff83d14c3d00 : 0xffffff7f9e52a534 com.apple.iokit.IOAcceleratorFamily2 : __ZN22IOGraphicsAccelerator25startEP9IOService + 0x21e 0xffffff83d14c3d80 : 0xffffff7f9e5cb88e com.apple.kext.AMDRadeonX4000 : __ZN37AMDRadeonX4000_AMDGraphicsAccelerator5startEP9IOService + 0x82 0xffffff83d14c3de0 : 0xffffff801be1b216 mach_kernel : __ZN9IOService14startCandidateEPS_ + 0xf6 0xffffff83d14c3e40 : 0xffffff801be1adc1 mach_kernel : __ZN9IOService15probeCandidatesEP12OSOrderedSet + 0xb21 0xffffff83d14c3ef0 : 0xffffff801be1a10e mach_kernel : __ZN9IOService14doServiceMatchEj + 0x2ce 0xffffff83d14c3f50 : 0xffffff801be1c8ad mach_kernel : __ZN15_IOConfigThread4mainEPvi + 0x15d 0xffffff83d14c3fa0 : 0xffffff801b6e213e mach_kernel : _call_continuation + 0x2e Kernel Extensions in backtrace: com.apple.iokit.IOAcceleratorFamily2(438.3.1)[66992525-3204-3CB0-8F03-4B70031B1CF2]@0xffffff7f9e4f2000->0xffffff7f9e5b5fff dependency: com.apple.driver.AppleMobileFileIntegrity(1.0.5)[A243D030-19AC-30AA-AC70-6C786DF9E6CE]@0xffffff7f9c3f1000 dependency: com.apple.iokit.IOPCIFamily(2.9)[ADD485B5-3EF8-37C4-B3C5-F86326E497A4]@0xffffff7f9c4a6000 dependency: com.apple.iokit.IOSurface(269.6)[42377B3B-D14A-368E-820F-07E7EA666198]@0xffffff7f9e4c1000 dependency: com.apple.iokit.IOGraphicsFamily(569.4)[1F9B5D88-52DB-3A16-8373-4F608A3CB2D8]@0xffffff7f9c793000 dependency: com.apple.iokit.IOReportFamily(47)[988360A2-2E10-3014-A119-BE81BC045A10]@0xffffff7f9c09f000 com.apple.kext.AMDRadeonX4000(3.0.5)[5FD7AE5F-C03C-34A1-803F-ACA9B68524D0]@0xffffff7f9e5ca000->0xffffff7f9eb0efff dependency: com.apple.iokit.IOPCIFamily(2.9)[ADD485B5-3EF8-37C4-B3C5-F86326E497A4]@0xffffff7f9c4a6000 dependency: com.apple.iokit.IOSurface(269.6)[42377B3B-D14A-368E-820F-07E7EA666198]@0xffffff7f9e4c1000 dependency: com.apple.iokit.IOGraphicsFamily(569.4)[1F9B5D88-52DB-3A16-8373-4F608A3CB2D8]@0xffffff7f9c793000 dependency: com.apple.iokit.IOAcceleratorFamily2(438.3.1)[66992525-3204-3CB0-8F03-4B70031B1CF2]@0xffffff7f9e4f2000 BSD process name corresponding to current thread: kernel_task Boot args: debug=0x100 keepsyms=1 alcid=1 -v shikigva=128 Mac OS version: 19D76 Kernel version: Darwin Kernel Version 19.3.0: Thu Jan 9 20:58:23 PST 2020; root:xnu-6153.81.5~1/RELEASE_X86_64 Kernel UUID: A8DDE75C-CD97-3C37-B35D-1070CC50D2CE Kernel slide: 0x000000001b400000 Kernel text base: 0xffffff801b600000 __HIB text base: 0xffffff801b500000 System model name: MacPro7,1 (Mac-27AD2F918AE68F61) System shutdown begun: NO Panic diags file available: NO (0xe00002bc) System uptime in nanoseconds: 38416992755  
      Kernel Panic Report 3
      panic(cpu 8 caller 0xffffff801da652fa): Kernel trap at 0xffffff7fa084dfe3, type 14=page fault, registers: CR0: 0x000000008001003b, CR2: 0xffffff83d44cd000, CR3: 0x000000002b260000, CR4: 0x00000000003406e0 RAX: 0xffffff83d44cd000, RBX: 0x0000000000005434, RCX: 0x0000000002000000, RDX: 0x0000000003000000 RSP: 0xffffff83d319bb60, RBP: 0xffffff83d319bb80, RSI: 0xffffff8066659c00, RDI: 0x0000000000000000 R8: 0x0000000000000001, R9: 0x0000000000000026, R10: 0x00000000f8000000, R11: 0x0000000000000070 R12: 0xffffff8061f35280, R13: 0xffffff835d231000, R14: 0x0000000000000000, R15: 0xffffff806189db90 RFL: 0x0000000000010246, RIP: 0xffffff7fa084dfe3, CS: 0x0000000000000008, SS: 0x0000000000000000 Fault CR2: 0xffffff83d44cd000, Error code: 0x0000000000000002, Fault CPU: 0x8, PL: 0, VF: 1 Backtrace (CPU 8), Frame : Return Address 0xffffff83d319b5c0 : 0xffffff801d93bb2b mach_kernel : _handle_debugger_trap + 0x47b 0xffffff83d319b610 : 0xffffff801da734d5 mach_kernel : _kdp_i386_trap + 0x155 0xffffff83d319b650 : 0xffffff801da64f4e mach_kernel : _kernel_trap + 0x4ee 0xffffff83d319b6a0 : 0xffffff801d8e2a40 mach_kernel : _return_from_trap + 0xe0 0xffffff83d319b6c0 : 0xffffff801d93b217 mach_kernel : _DebuggerTrapWithState + 0x17 0xffffff83d319b7c0 : 0xffffff801d93b5fb mach_kernel : _panic_trap_to_debugger + 0x21b 0xffffff83d319b810 : 0xffffff801e0d2aa9 mach_kernel : _panic + 0x61 0xffffff83d319b880 : 0xffffff801da652fa mach_kernel : _sync_iss_to_iks + 0x2aa 0xffffff83d319ba00 : 0xffffff801da64ff8 mach_kernel : _kernel_trap + 0x598 0xffffff83d319ba50 : 0xffffff801d8e2a40 mach_kernel : _return_from_trap + 0xe0 0xffffff83d319ba70 : 0xffffff7fa084dfe3 com.apple.kext.AMDRadeonX4000 : __ZN29AMDRadeonX4000_AMDHWRegisters4readEj + 0x53 0xffffff83d319bb80 : 0xffffff7fa0885795 com.apple.kext.AMDRadeonX4000 : __ZN28AMDRadeonX4000_AMDVIHardware19getRegisterAperSizeEv + 0x23 0xffffff83d319bba0 : 0xffffff7fa084def0 com.apple.kext.AMDRadeonX4000 : __ZN29AMDRadeonX4000_AMDHWRegisters4initEP11IOPCIDeviceP30AMDRadeonX4000_IAMDHWInterface + 0xfa 0xffffff83d319bbe0 : 0xffffff7fa086d5c1 com.apple.kext.AMDRadeonX4000 : __ZN26AMDRadeonX4000_AMDHardware4initEP11IOPCIDeviceP28AMDRadeonX4000_IAMDHWHandlerRjP16_GART_PARAMETERSP14_FB_PARAMETERS + 0x257 0xffffff83d319bc30 : 0xffffff7fa07f3adb com.apple.kext.AMDRadeonX4000 : __ZN37AMDRadeonX4000_AMDGraphicsAccelerator17createHWInterfaceEP11IOPCIDevice + 0x7b 0xffffff83d319bc70 : 0xffffff7fa07f14be com.apple.kext.AMDRadeonX4000 : __ZN37AMDRadeonX4000_AMDGraphicsAccelerator15configureDeviceEP11IOPCIDevice + 0x10a 0xffffff83d319bd00 : 0xffffff7fa074e534 com.apple.iokit.IOAcceleratorFamily2 : __ZN22IOGraphicsAccelerator25startEP9IOService + 0x21e 0xffffff83d319bd80 : 0xffffff7fa07ef88e com.apple.kext.AMDRadeonX4000 : __ZN37AMDRadeonX4000_AMDGraphicsAccelerator5startEP9IOService + 0x82 0xffffff83d319bde0 : 0xffffff801e01b216 mach_kernel : __ZN9IOService14startCandidateEPS_ + 0xf6 0xffffff83d319be40 : 0xffffff801e01adc1 mach_kernel : __ZN9IOService15probeCandidatesEP12OSOrderedSet + 0xb21 0xffffff83d319bef0 : 0xffffff801e01a10e mach_kernel : __ZN9IOService14doServiceMatchEj + 0x2ce 0xffffff83d319bf50 : 0xffffff801e01c8ad mach_kernel : __ZN15_IOConfigThread4mainEPvi + 0x15d 0xffffff83d319bfa0 : 0xffffff801d8e213e mach_kernel : _call_continuation + 0x2e Kernel Extensions in backtrace: com.apple.iokit.IOAcceleratorFamily2(438.3.1)[66992525-3204-3CB0-8F03-4B70031B1CF2]@0xffffff7fa0716000->0xffffff7fa07d9fff dependency: com.apple.driver.AppleMobileFileIntegrity(1.0.5)[A243D030-19AC-30AA-AC70-6C786DF9E6CE]@0xffffff7f9e5f1000 dependency: com.apple.iokit.IOPCIFamily(2.9)[ADD485B5-3EF8-37C4-B3C5-F86326E497A4]@0xffffff7f9e6a6000 dependency: com.apple.iokit.IOSurface(269.6)[42377B3B-D14A-368E-820F-07E7EA666198]@0xffffff7fa06e5000 dependency: com.apple.iokit.IOGraphicsFamily(569.4)[1F9B5D88-52DB-3A16-8373-4F608A3CB2D8]@0xffffff7f9e993000 dependency: com.apple.iokit.IOReportFamily(47)[988360A2-2E10-3014-A119-BE81BC045A10]@0xffffff7f9e29f000 com.apple.kext.AMDRadeonX4000(3.0.5)[5FD7AE5F-C03C-34A1-803F-ACA9B68524D0]@0xffffff7fa07ee000->0xffffff7fa0d32fff dependency: com.apple.iokit.IOPCIFamily(2.9)[ADD485B5-3EF8-37C4-B3C5-F86326E497A4]@0xffffff7f9e6a6000 dependency: com.apple.iokit.IOSurface(269.6)[42377B3B-D14A-368E-820F-07E7EA666198]@0xffffff7fa06e5000 dependency: com.apple.iokit.IOGraphicsFamily(569.4)[1F9B5D88-52DB-3A16-8373-4F608A3CB2D8]@0xffffff7f9e993000 dependency: com.apple.iokit.IOAcceleratorFamily2(438.3.1)[66992525-3204-3CB0-8F03-4B70031B1CF2]@0xffffff7fa0716000 BSD process name corresponding to current thread: kernel_task Boot args: debug=0x100 keepsyms=1 alcid=1 -v shikigva=128 Mac OS version: 19D76 Kernel version: Darwin Kernel Version 19.3.0: Thu Jan 9 20:58:23 PST 2020; root:xnu-6153.81.5~1/RELEASE_X86_64 Kernel UUID: A8DDE75C-CD97-3C37-B35D-1070CC50D2CE Kernel slide: 0x000000001d600000 Kernel text base: 0xffffff801d800000 __HIB text base: 0xffffff801d700000 System model name: MacPro7,1 (Mac-27AD2F918AE68F61) System shutdown begun: NO Panic diags file available: NO (0xe00002bc) System uptime in nanoseconds: 27776834167  
      config.plist
×