Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Random crashes after big sur
- Thread starter biggie!
- Start date
- Sort by reaction score
Not had any reboots at all, I'm about to hit day 5 on Big Sur without rebooting, just putting the machine to sleep - and have been using it as my daily driver...been absolutely fine for me.
Take it you've tried all the SMC and PRAM resets?
What's the machine you're running this on?
The only crashes I've had have been with Safari and Preview...
Take it you've tried all the SMC and PRAM resets?
What's the machine you're running this on?
The only crashes I've had have been with Safari and Preview...
2019 Macbook Pro 4 thunderbolt 3 ports
[automerge]1593413904[/automerge]
Is it different cause to me beta is beta lol😂
[automerge]1593413910[/automerge]
[automerge]1593413938[/automerge]
Apple community forums are reporting that the Kernel Panics that exist in 10.15.5 are present in 11.0 Dev beta 1. Threads are being removed by apple apparently so you need to subscribe if you want to catch them. It probably makes sense as issues existed in the baseline.
Yes, I have had random crashes every day since I updated my 2016 MacBook Pro 2.7 GHz Quad-Core Intel Core i7 with 16 Gbs of ram and just when I came onto this forum and was about to write this down it crashed....real pain in the neck. I am hoping Apple address this in their next update. I had heard that Apple changed the bios when they updated to Big Sur....If this true why on earth are they messing about with the bios where they could potentially brick machines. Not a bit pleased with this Big Sur update and now wished I had held back from updating. I know a lot of people had problems with Catalina but I must say everything ran smoothly for me but this crashing is annoying.....there is no warning it's going to happen like fans running or anything like that....just a big black blank screen and then it restarts again. Anybody, got any ideas of how to fix this bug or any suggestions what I can do to report it to Apple (would they be interested in trying to fix it???