iMac keeps crashing after Catalina upgrade

Glad that helped you... I would guess this feature is triggering some deeper issue though... if it's your only "trigger" for the crash then that's great. I however seem to see the same crash even sometimes before I've finished typing my password to log in so I don't think such a preference would even be relevant by then? But who knows maybe Apple does some weird complicated pre-loading of preferences etc.

I'm curious if anyone has experienced the crashing and then downgraded to Mojave and then still experienced the crashing? That is the boat I'm in. I'm now currently restoring way back to macOS Sierra which came with my mac. Fingers crossed.

We were having the same "Crash Problems" as most other folks on both of our 2012 iMacs after "upgrading?" to Catalina. But did not have the crash problems on our 2015 MacBook Pro or our Mac Mini. I unhooked all the external devices and Thunderbolt docs from the iMacs. Then starting plugging things back in one a a time and shutting down & restarting between each change. On one iMac the crashes stopped after relocating the USB connection to a LG Blu-Ray Burner from the doc to a direct connection on the back of the iMac. On the other iMac the crashes stopped after just unplugging all the external devices and plugging them back in. I doubt this will solve everyones problems, but it worked for us, and my help some folks.

I have the same exact problem and even took my iMac into the Apple store with the same exact crash report. Apple claims they fixed it but when I brought it home and started it up it continues to unexpectedly crash problems and report. On phone support Apple recommended unplugging the computer then re-booting in recover mode (command R) and then reinstalling the OS. I did that and the problem continues - Apple please help!!!

Two weeks of crashes, thirteen pages worth of complaints in only ONE of similar threads and no fix in sight. This is absolutely disgusting. My mac crashes in the middle of preparing production releases and I need to constantly keep typing in a blank TextEdit document or move the mouse to prevent a crash. I've got all idle timeouts switched off, all screensavers turned off, all power saving features off YET it crashes after two minutes of idling.

GW1921 wrote:

I need to constantly keep typing in a blank TextEdit document or move the mouse to prevent a crash.

If you've got actual work to do, and your machine is unreliable, you need to drop back to Mojave. Maybe do it on another partition so you can check if they've fixed anything with the next release.

That's what I initially did, wasted two days restoring back to Mojave, got excited about the supplementary update and took the plunge.

Sadly, I require Catalina-specific features to develop and test on top, and it's non-productive for me to be switching between a VM and a Mojave development machine. I'm just weeping inside, hoping this is over soon.

After all the crashes and no help from Apple Tech Support, one must wonder why none of this showed up in the Beta Testing stage? Are there any Beta Testers here that can answer that? What is very apparent to us all is Catalina was not ready for release and in fact, it was delayed for a while. My suspecion is Apple knew of this issue, but because they had a drop dead date, they released it anyway. I would bet all of would have gladly waited until a error free system could be released.

If Apple is watching our posting, could someone at a high level tell us what is being done to correct all these issues and to restore our faith as users of the Mac OSX? Please?

I think it is clear now from these responses that the common point between all these issue including:

connecting to external monitors and

black screen and

crashing suddenly and crash report details which shows clearly GPU panic is

an update related to display card and/or gpu and I guess it impacts the firmware too.

any interaction with those parts are resulting in the failure we are facing

Another point that proved this to me is that it is working on safe mode with no crash or black screen. Never! Which i guess because safe mode is disabling this kind of interaction with some software components related to the previous infected ones

I've lost faith. Between this and the keyboard dust issues I don't know why I keep supporting them and their expensive products. No need to keep experimenting with these workhorse tools! Experiment with the mobile devices if they have to. I'd move to Windows straight away if it wasnt for my last 10 years of work being wrapped up in Apple software. Still... considering the change at some point. Especially if they try and charge me a huge amount to fix this (as it's entirely possible their cruddy update has damaged the hardware in some way?)

@MahmoudAlabgy. I think you're absolutely right... I was looking for a way to only use integrated graphics so I could put this theory to the test. But I can't find any modern software that would enable this

Just another note: I installed the 10.15.1 beta2 update and it didnt fix anything either :(

Try cold booting the iMac several times - I had the identical issue. There has been a recent update to Catalina too, that might help, not sure, Apple are secretive in disclosing the details of what is being fixed in the release.

Hi all,

I am also seeing very frequent crashes after I updated my Catalina installation especially after with the supplemental update from Oct 15. And only with my MacBook Pro 13inch 2016. My MacMini seems fine so far.

I must have sent over 20 crash reports, and in most of my reports I see this problem:

panic(cpu 0 caller 0xffffff80149beec7): "vm_compressor_pager_put: out of range"@/BuildRoot/Library/Caches/com.apple.xbs/Sources/xnu/xnu-6153.11.26/osfmk/vm/vm_compressor_pager.c:746

The other times it is a kernel panic with a dump of the registers(not sure if it is worth posting here).

Today I decided to make a fresh install

on a separate partition and now I notice every time my fan spins up during the reinstall of my software that the crashes come back.

So I am left with a fresh install without much software and every time I start to install my software I have to pray that it works... just to repeat what everyone said here so far, very frustrating.

Cheers

Duc

might be a odd theory but there is something else really strange going on. I just noticed that when I setup a touch ID finger print... the computer keeps says "oops you pressed too hard" when registering a fingerprint. I'm doing the most delicate touch possible. Can anyone else see if this happens to them in Catalina? It could explain my frequent random shutdowns if the computer think I'm holding that button down! Seriously just another stupid design flaw by Apple trying to be fancy. Just make a proper power button like everyone else.

It's so weird... my computer was humming along fine all morning after ANOTHER fresh install... but as soon as one shutdown occurred, they started happening wildly. This is so frustrating!

I'm having this issue also.. Of course I'm livid since this was a 'recommended update' and I don't want to be a beta tester while I'm on a business trip with a tight deadline.

If I boot normally, it goes to login prompt. As soon as I enter password, it takes about 15-30 seconds and then displays that 'Your computer restarted because of a problem' screen. This will happen over and over - I tried it 5 times just to see what would happen - same thing every time. If I boot into recovery mode and select 'Macintosh HD', it takes a long time for the decryption prompt to pop up - but it finally asks for password. Then I select Macintosh HD and restart - and it boots fine after I type in the password. It looks like I have a working install. But then, if I restart, I get the same annoying error message.

Also, it would be nice if the OS told me the actual amount of free space I have on my hard drive - and it would be nice if Apple told me they were going to repartition the hard drive on update. Also, the report has 'BSD process name corresponding to current thread: airportd' in it.. But then where do I troubleshoot?