Jump to content
InsanelyMac Forum

computergek80

Members
  • Content count

    32
  • Joined

  • Last visited

About computergek80

  • Rank
    InsanelyMac Protégé

Profile Information

  • Gender
    Male
  • Location
    Rotterdam, The Netherlands
  1. computergek80

    GTX 970 Dual monitor on Sierra fails

    Is there always only one output that's working? Or are you getting glitches on the others? Which port layout does your card have? My GTX 970 won't output a correct signal over DP1.2. At least not at 3840x2160@60. I haven't tried any other displays yet, or any forced resolutions. I'm hoping our issues are related.
  2. Could you let us know how you managed it? I'm still having the same problems, and I can't find a clue in my BIOS. Any help would be appreciated.
  3. Hi darthsian, Oh, I'm sorry, I got the user names mixed up. That's weird. It's stable for you with VoodooTSCSync.kext? Or are the systems rebooting frequently? My problem is that I can't patch it, because the issue doesn't seem to be present. I must be dealing with a different problem. Kind regards, Pieter
  4. Hello everyone. I'm glad a few of you managed to solve your problems! I thought my system was stable, but it doesn't seem to be after all. It still crashes randomly (usually not long after sleep), just much less often. But it's still annoying when it does. So I just examined my BIOS following your guide, thorton, but all I found was "mov ecx, 0xc0000080". No 0x10. There were a few other modules that seemed to have something to do with S3, but none of them contained a wrmsr call. What else can I try? Is my issue unrelated to all of yours? Kind regards, Pieter Edit: Sorry, it's thorton's guide!
  5. That's disappointing. Maybe it's one of the built-in PCIe devices in the board that is misbehaving, like the NIC or a USB controller. I suppose you could try disabling certain things in the BIOS. I'm still getting TSCSync messages, and I haven't tried removing the Voodoo kext, so not everything is how I'd like it. But at least it's stable.
  6. Great news (for me at least)! I've managed to get rid of the kernel panics that were seemingly the result of the TSCSync issue. Ever since I got my new board, I've been using an Apple BCM94360CD with a PCIe 1x adapter. But the Asrock OC Formula wasn't detecting the PCIe device. But the Bluetooth was working using the USB header connection. I had found out that some motherboards get the wiring wrong for combined USB and PCIe devices and the stated solution would be to get an adapter with all four USB lines connected to the motherboard header. So, to get WiFi to work (I wasn't expecting our problem to be related), I was looking at a really expensive adapter that is only sold with the card, the wdxxfu version. And I was looking at the most expensive BCM943602CDP option as well. The purchasing agent somehow wouldn't place the order, so I had to wait for my money to get back to me. In the meantime I decided to just take the €12 risk and I bought this adapter from aliexpress.com. The cheap adapter arrived in record time, and it seems to have solved the problem. After noticing that there were no more crashes (not only launchd, but the other processes that would crash were no longer doing so), I changed some other things. I went back to letting Clover generate the P and C states, and I set a darkwake=9 bootflag. I hope this helps everyone else with this problem. I'd be interested to know wether you too have a PCIe device that is plugged in, but isn't detected by the motherboard.
  7. Have you checked your logs for the kernel panic? And as for darkwake, have you tried darkwake=9? It works great for me.
  8. I was getting those memory errors on my GA-Z87MX-D3H. I found a thread over at the other site where others with Gigabyte boards were having the same problem with memory corruption after longer sleep. I'd be interested in a solution that doesn't involve replacing the board, because I just did that and I'm having problems with the new one that are possibly unfixable.
  9. Ah, so there is a difference between the Haswell and Skylake systems. But yes, VoodooTSCSync.kext doesn't eliminate the log messages, it just tries to synchronise the cores when they occur.
  10. computergek80

    Reboot after wake problem

    I created a new thread, it's over here. And I'm sorry I can't help with the HDMI audio problem. Have you had any luck? Are there more people with the same problem?
  11. computergek80

    Wake up from sleep and USB issues (10.11.2)

    I found someone else with the crash after wake problem, so I've compiled everything we've already found out and created a new thread to keep the conversation centralised. It's over here.
  12. computergek80

    OS X reboots after wake

    I found someone else with the same problem, so I've compiled all we've already found out and created a new thread to keep the conversation centralised. It's over here.
  13. Hello everyone, I'm posting a new thread on behalf of myself and a few other members here (konrad11901, blackswords and Dmitry R). We've been experiencing an unstable system after wake. My system is ab Asrock Z97M OC Formula with an i5-4670k, konrad11901 has an MSI B85-G43 Gaming with an i5-4460, blackswords has an MSI PC Mate Z97 with an i5-4690k and Dimitry R has an Asrock Z170M-ITX ac with an i3-6100. I recently got my Z97M OC Formula to replace a GA-Z87MX-D3H which suffered from corrupted memory after long sleep. I'm booting using Clover, with a patched DSDT, and an SSDT generated with PikerAlpha's ssdtPRGen.sh. I've attached the files of my configuration. Soon after wake, the log shows messages such as: 2016-03-29 11:23:21,000 kernel[0]: Unsynchronized TSC for cpu 1: 0x0000000193273184, delta 0x18e0a1aca 2016-03-29 11:23:21,000 kernel[0]: Unsynchronized TSC for cpu 2: 0x0000000193428ced, delta 0x18e0a1aed 2016-03-29 11:23:21,000 kernel[0]: Unsynchronized TSC for cpu 3: 0x00000001935de52f, delta 0x18e0a1aed followed by process crashes, usually culminating in a launchd crash, causing a kernel panic and a reboot: *** Panic Report ***panic(cpu 1 caller 0xffffff800cb9aaa4): launchd exited (signal 8, exit status 0 ) … Thread 3 crashed … We have noticed that the output of pmset -g log | grep -i failure points to various PCIe devices, most notably the graphics card. Here's my output at the moment: 2016-03-29 13:11:50 +0200 Failure Drivers Failure panic during wake due to PEG0(NVDA NVDA NVDA NVDA NVDA NVDA),IGPU(): 2016-03-29 22:45:40 +0200 Failure Drivers Failure panic during wake due to PEG0(NVDA NVDA NVDA NVDA NVDA NVDA),IGPU(): With VoodooTSCSync.kext, we've noticed launchd crashes less often, meaning waking from sleep works, apart from the other processes that do crash. My theory is that there's something wrong with the firmware of our boards, or an issue with the DSDT or with CPU power management. This underlying problem is causing a TSC sync issue, which causes problems with PCIe devices as well as processes. Does anyone know the cause? Are there more people with this issue? And can anyone explain the relationship between the TSC, the HPET and the RTC? Thanks in advance to anyone who can shed any light on this issue. Kind regards, Pieter Edit: I forgot to mention that konrad11901 discovered that when using hibernation (hibernatemode=25) in stead of sleep there are no crashes, but of course, this isn't an ideal solution. Z97M OC Formula.zip
  14. computergek80

    Reboot after wake problem

    Hello Dmitry, Do you have a generated SSDT from toleda's scripts? That enabled HDMI audio for me. As for where to continue with the TSC sync problem, it might be good to have everyone with this issue in the same thread so we can all share what we discover. Also, other people can have one thread to come to with solutions. At the moment, I'm commenting in three threads, and there's a risk of redundant information. Good luck, Pieter
  15. computergek80

    Wake up from sleep and USB issues (10.11.2)

    Yes, the output of "pmset -g log | grep -i failure" for me is: 2016-03-26 00:07:04 +0100 Failure Drivers Failure panic during wake due to HDAU(),SATA(AppleAHCI): 2016-03-26 11:00:06 +0100 Failure Drivers Failure panic during wake due to HDAU(),SATA(AppleAHCI): 2016-03-26 13:38:58 +0100 Failure Drivers Failure panic during wake due to PEG0(NVDA NVDA NVDA NVDA NVDA NVDA),IGPU(): 2016-03-26 15:38:52 +0100 Failure Drivers Failure panic during wake due to HDAU(),SATA(AppleAHCI): 2016-03-26 17:38:53 +0100 Failure Drivers Failure panic during wake due to PEG0(NVDA NVDA NVDA NVDA NVDA NVDA),IGPU(): 2016-03-27 15:39:17 +0200 Failure Drivers Failure panic during wake due to HDAU(),SATA(AppleAHCI): 2016-03-27 17:11:31 +0200 Failure Drivers Failure panic during wake due to PEG0(NVDA NVDA NVDA NVDA NVDA NVDA),IGPU(): 2016-03-27 17:42:20 +0200 Failure Drivers Failure panic during wake due to PEG0(NVDA NVDA NVDA NVDA NVDA NVDA),IGPU(),HDEF(): 2016-03-27 22:01:20 +0200 Failure Drivers Failure panic during wake due to PEG0(NVDA NVDA NVDA NVDA NVDA NVDA),IGPU(),HDEF(AppleHDAController): This is with my GTX 970 set as initial display. But you'll notice SATA also shows up. My theory here is that the TSC sync issue in the processor is also affecting PCIe devices, and these are just a side-effect of the more central problem. I've found threads where the solution was to modify the firmware of their board, or even update the microcode of their processor (for Haswell-E). I'm really hoping it doesn't come to that. Blackswords, could you let us know wether the settings konrad11901 suggests help in any way?
×