Monterey crashes - kernel panic

[Bicyclegroup]

New Monterey installation went smoothly. Now random crashes - but regularly on 'shutdown' or 'restart'. Attached log seems to reveal kernel panic. Not sure how to proceed 

GB z490 Vision D, i7 10700, Rx580

 

panic.doc

Edited November 8, 2021 by Bicyclegroup

[eSaF]

Hi - See if you can find a system as close as possible to your specs here - https://github.com/topics/hackintosh?o=desc&s=updated - and download their EFI Folder and compare it to yours to see the difference, or if you do find one, use the EFI Folder to see if you can boot/install OS X. Good luck.

[Cyberdevs]

@Bicyclegroup

 

Take a look at this topic it might help you

 

[Bicyclegroup]

Thank you. I've tried several EFI folders - some I've made myself, others borrowed from successful builds with specs very similar to my own. I always get a kernel panic when I select 'shutdown' or 'restart' no matter what folder I use.

I am running Big Sur on another (nvme) drive on the same machine with an EFI folder I generated myself. I have never had a kernel panic with Big Sur - the issue seems to be specific to Monterey.

I used the same EFI folder (from the Big Sur installation using OC 7.5) to prepare the bootloader for Monterey. The installation of Monterey proceeded normally. I didn't have a problem until I transferred the folder to the installed drive and rebooted.

[eSaF]

Maybe I am clutching at straws here but check your BIOS settings again against a known working example also what Drive is Monterey on as it's been reported some manufacturer's drives are proving problematic with Monterey i.e Samsung. There is a list some where of makes of drives to avoid installing Monterey on. Good luck, hope you get to solve the problem.

[Bicyclegroup]

Thank you Cyberdevs. I installed my own USBPorts.kext and platform info and tried the Hackbeast EFI. Monterey continues to crash with a kernel panic.

When I installed Monterey, I migrated everything from my functioning Big Sur drive. Now I wonder if there is a conflict with something from the migration?

[Cyberdevs]

Basically the same EFI works for both OSes and the only way to find out if the data transfer might cause the issue is to do a clean install with all the latest kext files available and with the kexts files specific to your build and this time don't transfer your data.

 

Usually migrating data from one OS to another OS won't affect the system files but a clean install is the best way to narrow down issue.

The panic log points to com.apple.iokit.IOPCIFamily kext along side with lilu and weg. So in conclusion try a clean install and before doing that rest the NVRAM and as @eSaF stated double check the BIOS settings.

I don't have Z490 system at my disposal other wise i would have tested your EFI folder.

 

AND please update your signature with your hardware specs and as detailed as possible for future reference.

[eSaF]

32 minutes ago, Cyberdevs said:

Usually migrating data from one OS to another OS won't affect the system files but a clean install is the best way to narrow down issue.

Very good point indeed, I proved that the other day when I updated to the latest Monterey update which was running perfect before the update. At the end of the update I ran a 'First Aid' check on the disk and it threw up a Bunch of warnings so as long winded as it is, I did a clean install and at the end ran 'First Aid' again and the disk was error or warning free. Sometime updates will carry forward anomalies from previous installation that will manifest them selves in the new one that may or may not cause glitch operation, for me knowing about the warnings was a bug bear I couldn't live with. 

[miliuco]

@Bicyclegroup

Please complete your signature (account settings >> signature).

[MaLd0n]

remove fakepciid kexts

use folder from this topic for comet lake

https://www.olarila.com/topic/5676-hackintosh-efi-folders-for-all-chipsets-clover-and-opencore/

 

[devwithu]

MaLdOn ' s link is very good, simple and clean, i will use that comet lake EFI,

[arsradu]

Hi guys,

 

I've been struggling with this issue ever since I upgraded to Monterey and I couldn't figure out what was the cause. The KP message was pointing to Lilu and WEG... But they were fine. So I was stuck not knowing what could be the culprit.

I was having the exact same symptoms. Random freezes during regular operation (even in standby, while the machine was not doing anything in particular), but most of the times when trying to shut down or restart. That always caused a crash.

 

In my case, the only thing I had to remove (and now I'll have to figure out another way to fix my USB issue, but that's something I'm planning to do some other time) was FakePCIID.kext and FakePCIID_XHCIMux.kext. Removed them, updated OC config to reflect that, and that fixed it. Now some of my USBs are no longer working, but at least I can use the computer. :))

 

I wish I found this before deciding to wipe the partition and revert to Big Sur from Time Machine backup (while testing potential solutions on a test partition). In the end, I managed to upgrade again to Monterey, but this time everything's working fine.

 

So, I just wanted to post this in case there are other people with the same issue.

 

Thank you very much guys for your hard work and dedication! You guys are awesome!

Edited September 6, 2022 by arsradu

[STLVNUB]

@arsradu

Try Legacy_USB3.kext

Get RID of Anything To Do With USB

59 minutes ago, arsradu said:

Now some of my USBs are no longer working, but at least I can use the computer. :))

 

 

[Cyberdevs]

@arsradu

Hi, how are you?

Im curious to know what happens of you map the USB ports with tools like hackintool or USBTooBox? do you still need to use FakePCIID_XHCIMux.kext (I assume you are using these kexts because of an unsupported USB controller?) 

[arsradu]

3 hours ago, STLVNUB said:

@arsradu

Try Legacy_USB3.kext

Get RID of Anything To Do With USB

 

 

Thank you! Will definitely check it out.

 

3 hours ago, Cyberdevs said:

@arsradu

Hi, how are you?

Im curious to know what happens of you map the USB ports with tools like hackintool or USBTooBox? do you still need to use FakePCIID_XHCIMux.kext (I assume you are using these kexts because of an unsupported USB controller?) 

Hi Cyber!

 

Good, good! Thank you! Hope you're well, too!  It's been a while since my last post here.

 

I actually tried using Hackintool for that before...but either I don't know how to do it right, or...something else is happening. Basically I couldn't get those USBs to work. I don't think I ever tried the other tool. But yeah, that's why I was using those kexts.

To be honest, I don't really know which controllers are supported/unsupported. I found USB mapping really confusing. I was using these kexts cause they offered an easy and (as far as I could tell) accurate mapping of my ports. Yes, they were not the recommended way to do things, but it was good while it lasted.

 

Edited September 6, 2022 by arsradu

[jpz4085]

10 hours ago, arsradu said:

In my case, the only thing I had to remove (and now I'll have to figure out another way to fix my USB issue, but that's something I'm planning to do some other time) was FakePCIID.kext and FakePCIID_XHCIMux.kext. Removed them, updated OC config to reflect that, and that fixed it. Now some of my USBs are no longer working, but at least I can use the computer. :))

I encountered the same issue recently and was able to recompile FakePCIID for use with Monterey. See my GitHub page below.

 

https://github.com/jpz4085/OS-X-Fake-PCI-ID/releases

[Cyberdevs]

@arsradu

Yeah It's been so long! and it's good to see you back

I'm doing fine thanks.

IMHO the easiest way to map the USB ports is using USBoolBox which you can run it under windows and map the ports almost without any issues and once you do it you're set! no more 3rd party kexts are needed. All you need to use id the USBToolBox.kext and the USBMap.kext which will be generate with USBToolBox.

 

Give it a try and I hope it resolves the USP port issues.

https://github.com/USBToolBox/tool

[PippoX0]

USBToolBox , nice tool

I will give a try , too