pastrychef's Asus ROG Strix Z370-G Gaming (WI-FI AC) build w/ i9-9900K + AMD 6600 XT

[Azimuth1]

If it had been working well for about a week, then I doubt there's anything wrong with the EFI.

How does the system behave when you boot in the Recovery partition? Have you tried a clean install?

When I go to Recovery the system is responsive... I don't have any issue. No, I haven't tried a clean install because the main Mac disc is about 2TB with a lot of music, photos and personal stuff. I have an internal SATA HDD that works as TM but many things are not backupped, so I'm too afraid to clean everything! ...

 

[pastrychef]

When I go to Recovery the system is responsive... I don't have any issue. No, I haven't tried a clean install because the main Mac disc is about 2TB with a lot of music, photos and personal stuff. I have an internal SATA HDD that works as TM but many things are not backupped, so I'm too afraid to clean everything! ...

Try doing a clean install on a different drive or external drive. You should be able to copy whatever stuff you have from your current drive after you boot from the new clean install.

 

[Azimuth1]

Try doing a clean install on a different drive or external drive. You should be able to copy whatever stuff you have from your current drive after you boot from the new clean install.

UPDATE: I've been able to enter to a NEW profile and - after a long while with spinning wheel - now everything is working smoothly under this user profile.
So now... why the main profile has been freezing ? any ideas?

 

[pastrychef]

UPDATE: I've been able to enter to a NEW profile and - after a long while with spinning wheel - now everything is working smoothly under this user profile.
So now... why the main profile has been freezing ? any ideas?

I'm almost 100% sure it's software related. Disable login items, background processes, and launchdaemons.

 

[Azimuth1]

I'm almost 100% sure it's software related. Disable login items, background processes, and launchdaemons.

I've tried "Safe Mode" and the issue is still there. Safe mode is supposed to be at a minimum of background processes, and launchdaemons, isn't it?

Now I've been able to login in the main profile and I launched Utility Disk: Mac drive is perfectly ok but I see TWO instances of it in finder's left column. Isn't weird? Can this issue be related to some APFS thing? Another "suspect" is that as soon as I open DriveDx, it opens and then quits with unknown error. Or the main SSD (Samsung EVO 860 2TB) is going to die?

 

[pastrychef]

I've tried "Safe Mode" and the issue is still there. Safe mode is supposed to be at a minimum of background processes, and launchdaemons, isn't it?

Now I've been able to login in the main profile and I launched Utility Disk: Mac drive is perfectly ok but I see TWO instances of it in finder's left column. Isn't weird? Can this issue be related to some APFS thing? Another "suspect" is that as soon as I open DriveDx, it opens and then quits with unknown error. Or the main SSD (Samsung EVO 860 2TB) is going to die?

I've never seen two instances of my system drive... Maybe something is wrong or corrupt...

 

[Azimuth1]

I've never seen two instances of my system drive... Maybe something is wrong or corrupt...

Thanks ... I must say that TRIM was NOT enabled and maybe this has deteriorated the SSD (Samsung 860 EVO with 4 years of life now)... I've ordered a new disc and in the weekend I will make a fresh installation of Monterey and then a restore from the previous SSD of what I can read properly.

 

[jabro23]

Hello, Maybe there are some new ideas why the booting up might not go? Still trying to fix it without success. Empirically, I found out that MacOS is updated normally up to 13.2.1 / 13.3 beta 3. But if I update to 13.3 beta 4 and 13.3 RC, I get a kernel panic, with the same lines described in my previous messages.
RecoveryHD also stops booting.

All the same lines before the panic:
com.apple.securityd.xpc, requestor = bluetoothd(189), error = 3: No such process
com.apple.analyticsd, flags = 0x8, requestor = bluetoothd(189), error = 3: No such process
com.apple.private.corewifi-xpc, flags = 0x8, requestor = bluetooth(189), error =159: Sandbox restriction

After that, the apple logo and progress bar appear for a few seconds, then reboot.
OC 090 from post#1
Thanks anyway.

UPD: on 13.3 RC, loading takes a little further. Of course, I'm not very good at it, but it seems that MacOS cannot complete the update normally.

 

[pastrychef]

Hello, Maybe there are some new ideas why the booting up might not go? Still trying to fix it without success. Empirically, I found out that MacOS is updated normally up to 13.2.1 / 13.3 beta 3. But if I update to 13.3 beta 4 and 13.3 RC, I get a kernel panic, with the same lines described in my previous messages.
RecoveryHD also stops booting.

All the same lines before the panic:
com.apple.securityd.xpc, requestor = bluetoothd(189), error = 3: No such process
com.apple.analyticsd, flags = 0x8, requestor = bluetoothd(189), error = 3: No such process
com.apple.private.corewifi-xpc, flags = 0x8, requestor = bluetooth(189), error =159: Sandbox restriction

After that, the apple logo and progress bar appear for a few seconds, then reboot.
OC 090 from post#1
Thanks anyway.

UPD: on 13.3 RC, loading takes a little further. Of course, I'm not very good at it, but it seems that MacOS cannot complete the update normally.

Can you try config.plist > Kernel > Quirks > ProvideCurrentCpuInfo = Enabled and see if it works?

Edit:
You can also try adding the "-no-compat-check" boot-arg.

 

[jabro23]

Can you try config.plist > Kernel > Quirks > ProvideCurrentCpuInfo = Enabled and see if it works?

Edit:
You can also try adding the "-no-compat-check" boot-arg.

Unfortunately, the above did not help