0

Issue

When trying to use Finder, the window will freeze and become unresponsive. Trying to relaunch or force quit fails. The only thing that fixes it is a full restart of the computer.

When trying to use Spotlight, anytime I try to launch a program with it, it will get the Beach Ball of Death (BBOD). After a minute or so, it will crash, the program will have not launched, and it will successfully restart spotlight (I think).

When trying to use applications that access the filesystem, it will cause those applications to freeze for long periods of time before they become responsive again. This does not happen with every application, notably DaisyDisk has no problem whatsoever, and accessing things with shell (I use fish) works fine.

And this started to happen later, but my background is also freaking out, showing up 'sharded' or like it's got screen tearing where half the background is black. Same thing for the login screen. It's like it's in negative, where the mouse is blue, the entire background is black, and there's a weird box around the cursor. The password input is cyan (for the dots).

Steps I've taken

I've tried many things:

  • removing most login items
  • uninstalling a bunch of unused stuff
    • anytime I try to uninstall stuff it freezes due to trying to access the file system
  • I've tried removing the Finder and Spotlight plist files
  • I've tried using Disk Utility to verify all drives
  • I've tried Safe Mode and though it seems to work, the problem will come back if I stay in safe mode long enough
  • I've cleaned out caches using Onyx
  • I've looked through the Console.app and I quite a lot of errors, but that's not necessarily a bad thing, but one thing that does stick out to me is:
    • Bad volume: /Volumes/BOOTCAMP
  • I've tried reinstalling Ventura
    • I got the following error storage system verify or repair failed -69716
    • it seemed to work for Finder
    • but apps still are struggling to access files/create folders
    • spotlight still crashes

Other steps I've taken

/ on ☁️  (us-west-1)
❯ cat /etc/auto_nas
[bat error]: '/etc/auto_nas': No such file or directory (os error 2)

/ on ☁️ (us-west-1) ❯ cat /etc/auto_master ───────┬────────────────────────────────────────────────────────────────────────────────────────────────────────── │ File: /etc/auto_master ───────┼────────────────────────────────────────────────────────────────────────────────────────────────────────── 1 │ # 2 │ # Automounter master map 3 │ # 4 │ +auto_master # Use directory service 5 │ #/net -hosts -nobrowse,hidefromfinder,nosuid 6 │ /home auto_home -nobrowse,hidefromfinder 7 │ /Network/Servers -fstab 8 │ /- -static ───────┴──────────────────────────────────────────────────────────────────────────────────────────────────────────

/ on ☁️ (us-west-1) ❯

❯ diskutil info disk0 | grep SMART
   SMART Status:              Verified

/ on ☁️ (us-west-1) ❯

I tried removing the QuickLook folders as well, but only did the user folder to start. The other folders wanted sudo so wanted to check here first if that should be my next course of action.

rm -rf ~/Library/QuickLook/

I don't have Google Backup & Sync though I did at one point. Nothing in the sidebar. I do have Dropbox, but it's still installed, not removed, and it works fine.

I do see this in the Application Support directory though:

❯ ls ~/Library/Application\ Support/Google/Drive/
Permissions Size User  Date Modified Name
drwxr-xr-x     - tyler 20 Sep  2021  drive_fs_upgrade
.rw-r--r--@ 659k tyler 10 Oct  2022  finder_log.log
.rw-r--r--     0 tyler 11 Jul  2020  findextmp.lock
.rw-r--r--   20k tyler 11 Jul  2020  global.db
.rw-r--r--     0 tyler 10 Jul  2020  ip_lockfile
.rw-r--r--     0 tyler 10 Jul  2020  lockfile
drwxr-xr-x     - tyler 11 Jul  2020  user_default

I want to exhaust all resources before I nuke entirely and start over.

removed the plist files

well I really don't want it to be the sata cable or ssd, but I'm not sure how I'd rule those out.

not sure if I should do this? Not sure how to tbh.

System info

2.4 GHz 8-Core Intel Core i9
Intel UHD Graphics 630 1536 MB
32 GB 2667 MHz DDR4
Macintosh HD
13.3.1 (a) (22E772610a)
snowe2010
  • 103
  • To be candid, this is much to lengthy and broad to follow. When you get the wait cursor (the spinning beachball of death), it means that the system is waiting for something before it can move on. It could be from either RAM or your disk or another application. Before you start taking drastic steps, boot into Safe Mode and see if the problem persists. – Allan May 17 '23 at 02:50
  • I clearly laid out all the things I've tried. There's no such thing as "too broad" when you're detailing out the problems you've tried. I gave as much information as possible that is 100% relevant to the problem at hand. If you had actually read to literally the fifth bullet point you would have seen that. – snowe2010 May 17 '23 at 05:27
  • Is this a Mini or a MBP? – nohillside May 17 '23 at 05:46
  • @nohillside it's a MBP. 2019 16" – snowe2010 May 17 '23 at 05:51
  • I've seen dust in the vents causing issues like the ones you describe, but not sure how much cleaning you can do on a 2019 MBP. – nohillside May 17 '23 at 07:37
  • Booting into safe mode would negate all the software manipulation and installation. It points to hardware. – Allan May 17 '23 at 12:16
  • @nohillside I'll see if I can open it up and look for that – snowe2010 May 17 '23 at 18:36
  • @Allan yep, and I've run Disk Utility, but that's about all I know about debugging hardware. So how would I go about testing which piece is broken? – snowe2010 May 17 '23 at 18:37
  • 2
    I would start with a cleaning as @nohillside suggested. Too much heat will cause the CPU to limit performance. Unfortunately, the MBP of that vintage is no longer user upgradable - all components are soldered. You could try booting into Diagnostics (Hold D while booting) and see what it reports. You don’t need to wipe the drive to try a reinstall, just install macOS to an external drive (even a flash drive will work; > 32GB). If the problem goes away there, it’s your drive. If not, it’s narrowed down to memory or CPU – Allan May 17 '23 at 18:44
  • Fantastic. I'll try all those things. Currently I'm running a Time Machine backup to my unraid server and it's 1.75 terabytes, but I'll do this all after it's done. Thank you – snowe2010 May 17 '23 at 20:28
  • Ok, so I opened up my mbp, pulled the logic board, cleaned everything (wasn't really that dirty), then pulled the heatsink and saw the horror that was the thermal compound. I cleaned and replaced the compound, and it significantly improved the situation, the computer hardly has the fans turn on at all now, which is quite nice, and it's running much cooler. But it didn't solve the problem.

    So then I booted into Diagnostics, and ran that, but it also didn't find anything.

    I tried installing macos onto an external ssd, but met problem after problem...

    – snowe2010 May 19 '23 at 23:06
  • (cont.) First problem, I was not able to install it to the ssd on my computer that is having problems. I kept getting errors saying there was a problem during the install. Then I installed it using my work mac, which is an m2, plugged it into my intel, and tried to start it there. I had to turn off the startup disk security. But I kept getting messages saying my system must be updated in order to start the disk. Found some blog posts on it, and then decided to turn the security all the way down. Now when I try to start from the ssd it crashes my computer (log https://pastebin.com/T7G5qCx2) – snowe2010 May 19 '23 at 23:10
  • (cont.) Finally I tried running MemTest86 from a usb, but it too failed. I think because I don't have a usb-c key, only usb-a and so had to use a hub to connect it, and I don't think mac can boot like that.

    At this point I'm at a loss. It seems like there is something wrong, but I cannot figure out what.

    – snowe2010 May 19 '23 at 23:11
  • for good measure I followed all the steps in this article, except the reinstall, which I did the other day. https://www.easeus.com/computer-instruction/software-update-is-required-to-use-this-startup-disk.html#Fix_4

    at this point I think I might have to wipe the system before I know if it's the logic board...

    – snowe2010 May 19 '23 at 23:19

0 Answers0