From a review of the config.plist attached in post #1 I would comment as follows:
You don't say which motherboard you are using so I have no idea if you require any additional or alternative entries for the more problematical boards such as the TRX40, B550 or A520 etc.
Do you need the Kernel > Emulate > DummyPowerManagement entry set as True, when you are using the AMDRyzenCPUPowerManagement.kext?
The Kernel > Quirks > ProvideCurrentCPUInfo entry is set as False, this should be set as True.
If you are installing a version of macOS Big Sur 11.3 or newer you should not be enabling the Kernel > Quirks > XhciPortLimit patch, as it is not functioning in the newer releases of macOS.
UEFI > APFS > MinDate and MinVersion are bot set as 0. This is fine if you are installing Big Sur or Monterey. If you are installing High Sierra, Mojave or Catalina these entries need to be changed to the options shown below.
As you don't state which version of OpenCore you are using I tested the config.plist against ocvalidate for 0.7.7, 0.7.6 and 0.7.5.
The only one to have no errors was ocvalidate for OC 0.7.5.
ocvalidate for OC 0.7.6 contained 3 errors.
ocvalidate for OC 0.7.7 contained 14 errors.
Assumption is that your config.plist is part of an OC 0.7.5 setup.
Thanks @Edhawk for your replies.
I am using Msi b450m pro m2 max mobo.
I had installed Monterey,after updating to 12.2 the problem started.
I am using opencore 0.7.7
It is a random kernel panic.
Sometimes pc boots,sometimes doesn't with the same kernel panic.
When ı unclick dummypowermanagement,system gives me kernel panic:
kernel Extensions in backtrace:
I used Mikigal's updated efi,edited core count,for sleep ı remapped usb ports.System works fine.Also sleeps works fine.
Using someone else’s EFI setup is fine as long as their setup is correct, the one you are using obviously isn’t correct given the errors shown in the ocvalidate screenshot above.
If you are using OC 0.7.7 then you need to fix the 14 issues shown in the Terminal window from the ocvalidate check screenshot. Plus dealing with the other issues I mentioned such as XhciPortLimit quirk.
Post a copy of your whole EFI folder, so we can see what you are using.
I take it the EFI linked above is the EFI you based your setup on. As that folder bears little resemblance to the config.plist I reviewed previously.
It contains entries for an SSDT-UIAC.aml and a USBPorts.kext. Neither would work in your setup if they were configured for the ASUS B350 Plus board used by the creator of the folder. Plus the two should never be used together, it is a case of either or, never both.
There is a statement in the Readme.md file, in the Software Compatibility section, which states the following:
There were some reports about issues that occur while using MSI motherboards on Monterey Beta 3. The only possible solution to this problem as of right now is to downgrade to Monterey Beta 2 and wait for a confirmed workaround.
Have you read through and made the changes recommended in the Readme.md file that accompanied the EFI folder, specifically those that mention your B450 Series motherboard?
The MSI & Monterey issue has not been fixed, as far as I am aware. So if you are looking to install macOS Monterey, then you need to change tack and install Big Sur instead, as MSI boards currently have major issues with macOS Monterey.
@Edhawk thanks again for your time.
I had two kernel panics even on this efi before posting this.
I have installed xcode etc,ı don't want to start from scratch.
I am on 12.2 Monterey.
Is there any workaround for these kernel panics?
Assuming the two kernel panics were not caused by the EFI folder you have put together, then yes there is a workaround. But not one you would want. Install macOS Big Sur.
Until someone confirms what exactly is causing the kernel panics on the MSI boards and comes up with a fix for the issue(s) there is little anyone can do, bar downgrading to Big Sur.
Patience is required in this instance, it is the same for all MSI board owners.
The only other option you have is to buy a new motherboard, but not an MSI board. I know a few members here have gone down this route. Usually buying an Asus board, as they are fairly resilient and run macOS Monterey, at the moment.