- Joined
- Jan 24, 2017
- Messages
- 53
- Motherboard
- GA-Z170X-Designare
- CPU
- i7-6700K
- Graphics
- RX 580
- Mac
- Mobile Phone
I have a Hackintosh-build based off of the January 2017 recommended Customac Pro build descriptions running Sierra 10.12.2.
It has been rock solid until recently, but now, increasingly, I have been having issues.
Most notably, I now have to reboot almost every morning when I return to my Hack, as it has grown unbearably slow after a full night of inactivity. The same often applies if I go away for an extended period during the day and return. Often most or all apps have been paused because they're out of memory, and I have to force quit them. Still, the machine often remains unresponsive and unbearably slow, and I end up restarting when I can't take it anymore.
I have always had my Hack set to "Never sleep" in the power saving panel as I have loads of peripherals connected that don't agree with the Hack while booting, so I have to go through a tedious process of disconnecting and reconnecting lots of stuff during boot, and I also have loads of backups running overnight, which is another reason going to sleep isn't a good idea for me. So in theory, problems related to the Hack going to sleep shouldn't be the issue. It seems like it is whenever I return and my monitors have gone to sleep and I need to wake those (not the Hack itself as that is set to never sleep, right?) that the issues arise. I have set my monitors to remain active for 45 minutes (I do a lot of colour critical work on calibrated monitors so I don't want them to turn on and off as warm-up time affects colours).
At one point I also had this one popping up: "com.apple.PressAndHold (not responding)".
I would really appreciate any ideas about what may be causing this, as it is driving me insane currently. I'm in the middle of a big project, so don't really have time to go through a complete reinstall, although that will of course be last resort if I can't figure out what is the culprit and fix this problem in a more effortless way.
This morning I went through a series of processes in Onyx clearing caches, repairing permissions etc., and I restarted the Finder, and it is behaving well for the moment without a restart, so I'm cautiously optimistic - until next extended period of inactivity, that is.
I'd really like to find out the cause and fix it once and for all, rather than treating symptoms like I seemingly just did.
Edit: The small fixes above didn't last, as soon as I began launching apps again the beach ball started spinning and apps began to run out of memory again, have to reboot now...
FYI I also had a stubborn issue recently where the Hack refused to boot at all, it would crash when the progress bar on the black boot screen with the progress bar had reached about 90-95% every time, no matter what. In the end I managed to get around it thanks to advice some other place on this excellent forum which offered a solution using Diskwarrior on the original Hackintosh install/boot/restore memory stick, and that allowed me to run Diskwarrior and fix the corrupt directory structure that seemed to be the cause of the booting issue. But the slowness after periods of inactivity syndrome preceded that booting issue, just FYI.
Advance thanks for any help or advice - it would be most appreciated!
It has been rock solid until recently, but now, increasingly, I have been having issues.
Most notably, I now have to reboot almost every morning when I return to my Hack, as it has grown unbearably slow after a full night of inactivity. The same often applies if I go away for an extended period during the day and return. Often most or all apps have been paused because they're out of memory, and I have to force quit them. Still, the machine often remains unresponsive and unbearably slow, and I end up restarting when I can't take it anymore.
I have always had my Hack set to "Never sleep" in the power saving panel as I have loads of peripherals connected that don't agree with the Hack while booting, so I have to go through a tedious process of disconnecting and reconnecting lots of stuff during boot, and I also have loads of backups running overnight, which is another reason going to sleep isn't a good idea for me. So in theory, problems related to the Hack going to sleep shouldn't be the issue. It seems like it is whenever I return and my monitors have gone to sleep and I need to wake those (not the Hack itself as that is set to never sleep, right?) that the issues arise. I have set my monitors to remain active for 45 minutes (I do a lot of colour critical work on calibrated monitors so I don't want them to turn on and off as warm-up time affects colours).
At one point I also had this one popping up: "com.apple.PressAndHold (not responding)".
I would really appreciate any ideas about what may be causing this, as it is driving me insane currently. I'm in the middle of a big project, so don't really have time to go through a complete reinstall, although that will of course be last resort if I can't figure out what is the culprit and fix this problem in a more effortless way.
This morning I went through a series of processes in Onyx clearing caches, repairing permissions etc., and I restarted the Finder, and it is behaving well for the moment without a restart, so I'm cautiously optimistic - until next extended period of inactivity, that is.
I'd really like to find out the cause and fix it once and for all, rather than treating symptoms like I seemingly just did.
Edit: The small fixes above didn't last, as soon as I began launching apps again the beach ball started spinning and apps began to run out of memory again, have to reboot now...
FYI I also had a stubborn issue recently where the Hack refused to boot at all, it would crash when the progress bar on the black boot screen with the progress bar had reached about 90-95% every time, no matter what. In the end I managed to get around it thanks to advice some other place on this excellent forum which offered a solution using Diskwarrior on the original Hackintosh install/boot/restore memory stick, and that allowed me to run Diskwarrior and fix the corrupt directory structure that seemed to be the cause of the booting issue. But the slowness after periods of inactivity syndrome preceded that booting issue, just FYI.
Advance thanks for any help or advice - it would be most appreciated!
Last edited: