Contribute
Register

High Sierra Random Freezing

Status
Not open for further replies.
Joined
Jun 30, 2014
Messages
20
Motherboard
Asus H87
CPU
Intel Core i7 4770 3.4GHz
Graphics
Intel HD4600
I recently updated my El Capitan system directly to High Sierra. No issues during upgrade process, but after upgrade I have had intermittent freezing issues with my machine. This happens 2-3 times/day - the display locks up and any audio output ceases. Fixable only via restart. As far as I can tell, there are no kernel messages that show up at the restart. Here is an example:

Code:
$ log show --predicate "processID == 0" --start 2018-01-15
...
2018-01-15 09:06:12.223376-0500 0x18b      Default     0x0                  0      0    kernel: (CoreStorage) CoreStorageGroup::handleOpen(<private>) called, client <private>, access 3, state 5, client is a lv = n.
2018-01-15 09:15:15.000000-0500 0x0        Timesync    0x0                  0      0    === system boot: 7E926235-A715-4BEB-B612-6F9DF8F5EE02
...

With the freeze occurring at ~09:15:00. Doesn't seem to be messages in system.log that correspond either. Here's the most recent:

Code:
Jan 15 09:11:40 iMac Google Chrome[312]: BUG in libdispatch client: kevent[mach_recv] monitored resource vanished before the source cancel handler was invoked
Jan 15 09:11:46 iMac FinderSyncAPIExtension[370]: Pipe path is a symbolic link, connecting to target.
Jan 15 09:11:46 iMac FinderSyncAPIExtension[370]: /Users/exark/Library/Application Support/Google/Drive/GoogleDriveIpcPipe is a symbolic link to /Users/exark/Library/Group Containers/google_drive/tmpd9R88u, connecting to link target.
Jan 15 09:12:12 iMac Dock[335]: DEPRECATED USE in libdispatch client: Setting timer interval to 0 requests a 1ns timer, did you mean FOREVER (a one-shot timer)?
Jan 15 09:14:09 iMac GoogleSoftwareUpdateAgent[60812]: 2018-01-15 09:14:09.859 GoogleSoftwareUpdateAgent[60812/0x7fff9e369340] [lvl=2] -[KSAgentApp(PrivateMethods) setUpLoggerOutputForVerboseMode:] Agent default/global settings: <KSAgentSettings:0x100449bd0 bundleID=com.google.Keystone.Agent lastCheck=2018-01-15 12:13:23 +0000 lastServerCheck=2017-10-13 03:57:29 +0000 lastCheckStart=2018-01-15 12:13:20 +0000 checkInterval=18000.000000 uiDisplayInterval=604800.000000 sleepInterval=1800.000000 jitterInterval=900 maxRunInterval=0.000000 isConsoleUser=1 ticketStorePath=/Users/exark/Library/Google/GoogleSoftwareUpdate/TicketStore/Keystone.ticketstore runMode=3 daemonUpdateEngineBrokerServiceName=com.google.Keystone.Daemon.UpdateEngine daemonAdministrationServiceName=com.google.Keystone.Daemon.Administration alwaysPromptForUpdates=0 lastUIDisplayed=(null) alwaysShowStatusItem=0 updateCheckTag=(null) printResults=NO userInitiated=NO>
Jan 15 09:15:15 localhost bootlog[0]: BOOT_TIME 1516025715 0

I've attached my list of current kexts in use, and my Clover config. Any assistance would be greatly appreciated, please let me know if there's any more information I could include!
 

Attachments

  • config.plist
    7.1 KB · Views: 473
  • list_of_kexts.txt
    18.6 KB · Views: 596
One more try - any ideas?

I've also noticed that some apps are taking longer to startup than before - they hang on a spinning beach ball for about 20s after drawing the user interface. Wondering if maybe this is an issue with reading/writing to storage? I'm using a DIY fusion drive setup, with TRIM turned off on the SSD and am using a clover hotpatch to change SAT0 to SATA in the DSDT.
 
I've had something very similar if not the same.

I'm fairly sure that the problem is not hardware. I've run memtest and burn-in for many hours and all was ok.

And I don't think I screwed up the HS install. Initially I had upgraded from Sierra. Then, trying to resolve the freeze issue, I got a new SSD and installed fresh HS on that. I also cut back the number of SATA devices from 8 to 4 (it's now 2xSSD and 2xHDD).

Today it froze again and I am very unhappy about that.
 
Glad to hear I'm not alone, but sorry for your pain. In my case, it seems to at least be partially related to use - I was able to leave the system up all weekend without incident but when I came to work on Monday it froze within 20 minutes of me starting to use it.

I'm at a loss for where to look for errors - if it's not showing up in kernel errors or system.log, I really don't know what else could be going on...
 
Hi,

I have the same problem. I have a HD300 igpu instead of a HD4600. If possible test this, enable ssh access to your hackintosh, and the next time it hangs try login trough ssh and reboot or halt the system. I think the problem is with the graphic susbsytem, and that the system stills runs, but the screen is completely frozen.
 
I'll give that a shot the next time it freezes, but I'm skeptical that's the case since when the machien freezes, there's a large gap in the (otherwise very noisy) system.log between the freeze and when I restart.

FWIW, I have Lilu and IntelGraphicsFixup kexts installed...
 
Yeah, it's definitely a hard freeze for me - the looping audio happens when the machine freezes and it's not accessible via network access.

I've further tried cleaning my kernel extensions (updating to the most recent of Rehabman's FakeSMC, removing lspcidrv that I had lying around from a long time ago) but still no luck - two freezes today :(
 
Hi,

I have the same problem. I have a HD300 igpu instead of a HD4600. If possible test this, enable ssh access to your hackintosh, and the next time it hangs try login trough ssh and reboot or halt the system. I think the problem is with the graphic susbsytem, and that the system stills runs, but the screen is completely frozen.

I have the same problem, the hardware configuration is the same as yours (Z68MA-D2H, 2500K, HD3000), but running on Sierra 10.12.6. (The screen was frezzed, but I can still move the mouse cursor around.)

This machine was running fine on High Sierra 10.13.x for a couple of months, the only difference in hardware configuration is the GPU was GT-640 instead of HD3000 and never experienced random freeze.

I also think that the problem is graphics subsystem related.
 
Last edited:
Status
Not open for further replies.
Back
Top