Jump to content

Catalina randomly locking up


3 posts in this topic

Recommended Posts

Installed it the other day, sometimes it'll work for 4-5 hours before it locks up and I have to reboot.  Specs:

 

ASRock Z77E-ITX

Intel i5-3570k

Intel HD4000 GPU

1 8gb Crucial Ballistix stick

Samsung 128gb SSD

UEFI

Clover boot, still booting off the USB stick I made, haven't gotten around to installing an actual boot loader yet. Wanted to wait until I have the locking up issues fixed.

 

I did a stock Niresh Catalina install, the only thing I've modified was I injected a kext to get my ethernet working. With it working for 3+ hours I doubt it's overheating, plus it'll lock up even when I'm not doing anything, but I can run something CPU intensive for a good hour with no issue.  You'll have to excuse me I'm a life long DOS/Windows guy so I'm still very much trying to adjust to OSX.  I did look at the system logs and when it's locking up I see a fsck_apfs_error.log, so i thought it was maybe something to do with my SDD. But I'm not able to decipher the log file. Here's a few lines from the log, the rest looks the same just repeated.

 

dev= uuid=00000000-0000-0000-0000-000000000000 vers=1412.11.7 result=0 fp=0 fl=-1 repairs=0 time=0 iter=1
fsck_apfs completed at Sun Jan 24 01:29:19 2021
dev=/dev/rdisk1 uuid=00000000-0000-0000-0000-000000000000 vers=1412.11.7 result=65 pl=156:1 fp=2 fl=156 repairs=0 time=0 iter=1
fsck_apfs completed at Sun Jan 24 01:32:22 2021
dev= uuid=00000000-0000-0000-0000-000000000000 vers=1412.11.7 result=0 fp=0 fl=-1 repairs=0 time=0 iter=1
fsck_apfs completed at Sun Jan 24 01:32:22 2021
dev= uuid=00000000-0000-0000-0000-000000000000 vers=1412.11.7 result=0 fp=0 fl=-1 repairs=0 time=0 iter=1
fsck_apfs completed at Sun Jan 24 01:32:22 2021
 

 

 

 I did look on here for a FAQ on what to put in a post if you need help, I apologize if there is one and I was just unable to find it. I'm really tired from lack of sleep + trying to get this working so I'm running on fumes. If there is a posting protocol I'll look for it when I wake up and have brain energy.

 

I went thru my BIOS and disabled XMP and set my memory to a lower speed - seems to be something that came up a lot when I Googled potential reasons it'll lock up.  I know for anyone to help me they'll need logs or file lists, please let me know.  These are the files in my EFI/Clover/ktext/other

 

XHCI-unsupported

WhateverGreen

VoodooPS2Controller

USBInjectAll

NullCPUPowerManagement

Niresh's Extra

Lilu

GenericUSBXHCI

FakeSMC

FakePCIID

FakePCIID_XHCIMux

FakePCIID_Intel_HD_Graphics

AppleIntelKBLGraphicsFramebufferInjector_3e9x

 

 

When I did the install I didn't touch the section that lets you chose other kexts to install.

 

Edited by quebert
Link to comment
Share on other sites

Distro alert!

 

No support for distros here; they are troublesome, not to say evil. They always contains all sort of c r a p that cause problems as you currently experience. Your list of kexts is a perfect example: an injector for Kaby Lake HD/UHD 6x0 graphics (you have an Ivy Bridge platform with HD4000 graphics), NullCPUPowerManagement (meaning no turbo boost, no sleep or wake) or FakePCIID_Intel_HD_Graphics. :no:

 

Given that you somehow run Catalina, proceed with a full vanilla re-installation. You may proceed so on a separate partition on your disk to begin with, in order to experiment and work out all you need for a complete successful build. Good luck!

  • Like 1
Link to comment
Share on other sites

Thank you for replying, I suspected as much lol. I wanted to get my feet wet before I jumped into trying Opencore. I'm going to go read up and get crackin on building an Opencore installer.  I know that's what I should have done from the start. I'll format the  disk and start over,  from all my reading online Opencore would be the best route to go here.

Edited by quebert
Link to comment
Share on other sites

 Share

×
×
  • Create New...