i7-4930K - Asus Rampage IV Extreme - 32GB RAM - GTX 770 4GB [Success!!]

[neofusion]

I still run Yosemite on my main R4BE machine. I built up my old R4E/3930K hardware with a bunch of stuff I got on 2016 black friday sales. I use it for a HTPC (connected to a video projector) and plex media server, and also now for keeping this guide current. So I installed 10.12 on it. I tested the machine for a few days before updating the guide with new files. It hasn't seen much use but I haven't experienced any issues with audio on it. I will say that the clover audio patch method is NOT update proof and that you may need to run toleda's script after updates. I'm also pretty sure that his script modifies the OEM AppleHDA.kext in /S/L/E and if it does, it's no better than the old method of overwriting the OEM kext with a fully patched kext. Toleda is a genius I don't know what all he has going on with his new method, but if the OEM kext is modified in any way to make audio work, then it will break the kext signing and I don't see why it's better to patch the OEM kext and use another one in the EFI partition.

Thanks for the reply.
I gave 10.12 a new try and used PikerAlphas HDA-patch instead. It worked fine and I did not experience any issues what-so-ever with his method. It's possible I made a mistake when applying Toledas CloverHDA patch, but all in all I much prefer PikerAlphas dummy kext version. So that's good at least.

Video however has been nothing but problem after problem.
I have a multimonitor setup, perhaps that's reason why I am having so many issues where others do not;
It turned out that if I ran 10.12 with your SSDT-1 and Webdrivers installed, I got a black screen on bootup with one monitor connected using DisplayPort and the other with DVI. If I swapped the DP-cable with an HDMI-cable it booted successfully.

Having to use HDMI instead was disappointing but acceptable; until I realised that GPU power management wasn't working at all.
My GPU core was running at ~960MHz and GPU memory was running at 7GHz all the time, even when the computer was completely idle. That was a deal breaker for me.

In 10.10 the GPU works fine, it's unfathomable why it would break so spectacularly in 10.12. The GPU PM issue is possibly fixable with edits to AppleGraphicsPowerManagement.kext (or a dummy version of it) but as it stands I will probably not touch 10.12 again until post 10.12.3 update.

 

[blackgiwi]

I would guess that maybe your turbo isn't working. Can you run RunAppleIntelInfo.app (from my files for this guide) and post the results (Run the app, go to a couple different pages on the internet that you haven't visited and run Geekbench to stress the CPU to different levels, then click the OK button)?

These are from my R4E/3930K system @ stock speed:

64bit
View attachment 229953

32bit
View attachment 229954

Thank you again, its very nice of you. Here are my stats:

Settings:

------------------------------------

logMSRs............................: 1

logIGPU............................: 0

logIntelRegs.......................: 1

logCStates.........................: 1

logIPGStyle........................: 0

InitialTSC.........................: 0xe27896cb00

MWAIT C-States.....................: 135456


Model Specific Regiters

------------------------------------

MSR_CORE_THREAD_COUNT......(0x35) : 0x6000C

MSR_PLATFORM_INFO..........(0xCE) : 0xC0070012000

MSR_PMG_CST_CONFIG_CONTROL.(0xE2) : 0x1E000403

MSR_PMG_IO_CAPTURE_BASE....(0xE4) : 0x10414

IA32_MPERF.................(0xE7) : 0x14F4525167

IA32_APERF.................(0xE8) : 0x13FB6DD5B4

MSR_FLEX_RATIO.............(0x194) : 0xE0000

MSR_IA32_PERF_STATUS.......(0x198) : 0x288300002300

MSR_IA32_PERF_CONTROL......(0x199) : 0x2500

IA32_CLOCK_MODULATION......(0x19A) : 0x0

IA32_THERM_STATUS..........(0x19C) : 0x883F0000

IA32_MISC_ENABLES..........(0x1A0) : 0x850089

MSR_MISC_PWR_MGMT..........(0x1AA) : 0x400001

MSR_TURBO_RATIO_LIMIT......(0x1AD) : 0x2323232324252626

IA32_ENERGY_PERF_BIAS......(0x1B0) : 0x0

MSR_POWER_CTL..............(0x1FC) : 0x2504005B

MSR_RAPL_POWER_UNIT........(0x606) : 0xA1003

MSR_PKG_POWER_LIMIT........(0x610) : 0x69F40005A9F40

MSR_PKG_ENERGY_STATUS......(0x611) : 0x1C429172

MSR_PKG_POWER_INFO.........(0x614) : 0x1A80410

MSR_PP0_CURRENT_CONFIG.....(0x601) : 0x141494800007F8

MSR_PP0_POWER_LIMIT........(0x638) : 0x0

MSR_PP0_ENERGY_STATUS......(0x639) : 0xDABFEB7

MSR_PP0_POLICY.............(0x63a) : 0x0

MSR_PKGC6_IRTL.............(0x60b) : 0x0

MSR_PKGC7_IRTL.............(0x60c) : 0x0

MSR_PKG_C2_RESIDENCY.......(0x60d) : 0x4194B5E600

MSR_PKG_C3_RESIDENCY.......(0x3f8) : 0x149C0A7C0

MSR_PKG_C6_RESIDENCY.......(0x3f9) : 0x43AA0B27C0

MSR_PKG_C7_RESIDENCY.......(0x3fa) : 0x0

IA32_TSC_DEADLINE..........(0x6E0) : 0xE27B172156

PCH device.................: 0x1D418086


CPU Ratio Info:

------------------------------------

CPU Low Frequency Mode.............: 1200 MHz

CPU Maximum non-Turbo Frequency....: 3200 MHz

CPU Maximum Turbo Frequency........: 3800 MHz

CPU P-States [ (12) 22 ]

CPU C3-Cores [ 3 8 9 11 ]

CPU C6-Cores [ 2 3 7 8 9 10 11 ]

CPU C3-Cores [ 2 3 4 8 9 10 11 ]

CPU C6-Cores [ 2 3 4 5 7 8 9 10 11 ]

CPU C3-Cores [ 2 3 4 7 8 9 10 11 ]

CPU C6-Cores [ 0 1 2 3 4 5 6 7 8 9 10 11 ]

CPU C3-Cores [ 2 3 4 6 7 8 9 10 11 ]

CPU C3-Cores [ 1 2 3 4 5 6 7 8 9 10 11 ]

CPU P-States [ 12 22 (37) ]

CPU C3-Cores [ 0 1 2 3 4 5 6 7 8 9 10 11 ]

CPU P-States [ 12 22 (36) 37 ]

CPU P-States [ 12 22 (35) 36 37 ]

CPU P-States [ 12 22 35 36 37 (38) ]

CPU P-States [ 12 22 (32) 35 36 37 38 ]

CPU P-States [ 12 22 (27) 32 35 36 37 38 ]

Settings:

------------------------------------

logMSRs............................: 1

logIGPU............................: 0

logIntelRegs.......................: 1

logCStates.........................: 1

logIPGStyle........................: 0

InitialTSC.........................: 0xe27896cb00

MWAIT C-States.....................: 135456


Model Specific Regiters

------------------------------------

MSR_CORE_THREAD_COUNT......(0x35) : 0x6000C

MSR_PLATFORM_INFO..........(0xCE) : 0xC0070012000

MSR_PMG_CST_CONFIG_CONTROL.(0xE2) : 0x1E000403

MSR_PMG_IO_CAPTURE_BASE....(0xE4) : 0x10414

IA32_MPERF.................(0xE7) : 0x14F4525167

IA32_APERF.................(0xE8) : 0x13FB6DD5B4

MSR_FLEX_RATIO.............(0x194) : 0xE0000

MSR_IA32_PERF_STATUS.......(0x198) : 0x288300002300

MSR_IA32_PERF_CONTROL......(0x199) : 0x2500

IA32_CLOCK_MODULATION......(0x19A) : 0x0

IA32_THERM_STATUS..........(0x19C) : 0x883F0000

IA32_MISC_ENABLES..........(0x1A0) : 0x850089

MSR_MISC_PWR_MGMT..........(0x1AA) : 0x400001

MSR_TURBO_RATIO_LIMIT......(0x1AD) : 0x2323232324252626

IA32_ENERGY_PERF_BIAS......(0x1B0) : 0x0

MSR_POWER_CTL..............(0x1FC) : 0x2504005B

MSR_RAPL_POWER_UNIT........(0x606) : 0xA1003

MSR_PKG_POWER_LIMIT........(0x610) : 0x69F40005A9F40

MSR_PKG_ENERGY_STATUS......(0x611) : 0x1C429172

MSR_PKG_POWER_INFO.........(0x614) : 0x1A80410

MSR_PP0_CURRENT_CONFIG.....(0x601) : 0x141494800007F8

MSR_PP0_POWER_LIMIT........(0x638) : 0x0

MSR_PP0_ENERGY_STATUS......(0x639) : 0xDABFEB7

MSR_PP0_POLICY.............(0x63a) : 0x0

MSR_PKGC6_IRTL.............(0x60b) : 0x0

MSR_PKGC7_IRTL.............(0x60c) : 0x0

MSR_PKG_C2_RESIDENCY.......(0x60d) : 0x4194B5E600

MSR_PKG_C3_RESIDENCY.......(0x3f8) : 0x149C0A7C0

MSR_PKG_C6_RESIDENCY.......(0x3f9) : 0x43AA0B27C0

MSR_PKG_C7_RESIDENCY.......(0x3fa) : 0x0

IA32_TSC_DEADLINE..........(0x6E0) : 0xE27B172156

PCH device.................: 0x1D418086


CPU Ratio Info:

------------------------------------

CPU Low Frequency Mode.............: 1200 MHz

CPU Maximum non-Turbo Frequency....: 3200 MHz

CPU Maximum Turbo Frequency........: 3800 MHz

CPU P-States [ (12) 22 ]

CPU C3-Cores [ 3 8 9 11 ]

CPU C6-Cores [ 2 3 7 8 9 10 11 ]

CPU C3-Cores [ 2 3 4 8 9 10 11 ]

CPU C6-Cores [ 2 3 4 5 7 8 9 10 11 ]

CPU C3-Cores [ 2 3 4 7 8 9 10 11 ]

CPU C6-Cores [ 0 1 2 3 4 5 6 7 8 9 10 11 ]

CPU C3-Cores [ 2 3 4 6 7 8 9 10 11 ]

CPU C3-Cores [ 1 2 3 4 5 6 7 8 9 10 11 ]

CPU P-States [ 12 22 (37) ]

CPU C3-Cores [ 0 1 2 3 4 5 6 7 8 9 10 11 ]

CPU P-States [ 12 22 (36) 37 ]

CPU P-States [ 12 22 (35) 36 37 ]

CPU P-States [ 12 22 35 36 37 (38) ]

CPU P-States [ 12 22 (32) 35 36 37 38 ]

CPU P-States [ 12 22 (27) 32 35 36 37 38 ]
:
Settings:

------------------------------------

logMSRs............................: 1

logIGPU............................: 0

logIntelRegs.......................: 1

logCStates.........................: 1

logIPGStyle........................: 0

InitialTSC.........................: 0xe27896cb00

MWAIT C-States.....................: 135456


Model Specific Regiters

------------------------------------

MSR_CORE_THREAD_COUNT......(0x35) : 0x6000C

MSR_PLATFORM_INFO..........(0xCE) : 0xC0070012000

MSR_PMG_CST_CONFIG_CONTROL.(0xE2) : 0x1E000403

MSR_PMG_IO_CAPTURE_BASE....(0xE4) : 0x10414

IA32_MPERF.................(0xE7) : 0x14F4525167

IA32_APERF.................(0xE8) : 0x13FB6DD5B4

MSR_FLEX_RATIO.............(0x194) : 0xE0000

MSR_IA32_PERF_STATUS.......(0x198) : 0x288300002300

MSR_IA32_PERF_CONTROL......(0x199) : 0x2500

IA32_CLOCK_MODULATION......(0x19A) : 0x0

IA32_THERM_STATUS..........(0x19C) : 0x883F0000

IA32_MISC_ENABLES..........(0x1A0) : 0x850089

MSR_MISC_PWR_MGMT..........(0x1AA) : 0x400001

MSR_TURBO_RATIO_LIMIT......(0x1AD) : 0x2323232324252626

IA32_ENERGY_PERF_BIAS......(0x1B0) : 0x0

MSR_POWER_CTL..............(0x1FC) : 0x2504005B

MSR_RAPL_POWER_UNIT........(0x606) : 0xA1003

MSR_PKG_POWER_LIMIT........(0x610) : 0x69F40005A9F40

MSR_PKG_ENERGY_STATUS......(0x611) : 0x1C429172

MSR_PKG_POWER_INFO.........(0x614) : 0x1A80410

MSR_PP0_CURRENT_CONFIG.....(0x601) : 0x141494800007F8

MSR_PP0_POWER_LIMIT........(0x638) : 0x0

MSR_PP0_ENERGY_STATUS......(0x639) : 0xDABFEB7

MSR_PP0_POLICY.............(0x63a) : 0x0

MSR_PKGC6_IRTL.............(0x60b) : 0x0

MSR_PKGC7_IRTL.............(0x60c) : 0x0

MSR_PKG_C2_RESIDENCY.......(0x60d) : 0x4194B5E600

MSR_PKG_C3_RESIDENCY.......(0x3f8) : 0x149C0A7C0

MSR_PKG_C6_RESIDENCY.......(0x3f9) : 0x43AA0B27C0

MSR_PKG_C7_RESIDENCY.......(0x3fa) : 0x0

IA32_TSC_DEADLINE..........(0x6E0) : 0xE27B172156

PCH device.................: 0x1D418086


CPU Ratio Info:

------------------------------------

CPU Low Frequency Mode.............: 1200 MHz

CPU Maximum non-Turbo Frequency....: 3200 MHz

CPU Maximum Turbo Frequency........: 3800 MHz

CPU P-States [ (12) 22 ]

CPU C3-Cores [ 3 8 9 11 ]

CPU C6-Cores [ 2 3 7 8 9 10 11 ]

CPU C3-Cores [ 2 3 4 8 9 10 11 ]

CPU C6-Cores [ 2 3 4 5 7 8 9 10 11 ]

CPU C3-Cores [ 2 3 4 7 8 9 10 11 ]

CPU C6-Cores [ 0 1 2 3 4 5 6 7 8 9 10 11 ]

CPU C3-Cores [ 2 3 4 6 7 8 9 10 11 ]

CPU C3-Cores [ 1 2 3 4 5 6 7 8 9 10 11 ]

CPU P-States [ 12 22 (37) ]

CPU C3-Cores [ 0 1 2 3 4 5 6 7 8 9 10 11 ]

CPU P-States [ 12 22 (36) 37 ]

CPU P-States [ 12 22 (35) 36 37 ]

CPU P-States [ 12 22 35 36 37 (38) ]

CPU P-States [ 12 22 (32) 35 36 37 38 ]

CPU P-States [ 12 22 (27) 32 35 36 37 38 ]

 

[ggeorge]

I am getting a lockup as well. It's fine for some period of time after I have booted the computer under 10.12.2, but then it just locks up and I have to reboot it.

I've gotten as far as Step 10. I've done the post install stuff.

Well I completely removed the NVME SSD and booted off the new sata and it still locked up the same. So it doesn't seem like the NVME should be the issue. I haven't installed/done anything on the new drive to install that, but this was the one panic log I could find.

\Library\Logs\DiagnosticReports\Kernel_2017-01-10-003450_Thes-Mac-Pro.panic

My primary boot drive is an NVME I was using the generic kext for it.

*** Panic Report ***
panic(cpu 2 caller 0xffffff80155ce6fa): Kernel trap at 0xffffff80155c0f01, type 14=page fault, registers:
CR0: 0x000000008001003b, CR2: 0x0000000000000429, CR3: 0x000000002a9f0000, CR4: 0x00000000000626e0
RAX: 0x0000000000000200, RBX: 0x0000000000000429, RCX: 0xffffff80b176edb0, RDX: 0x0000000000000080
RSP: 0xffffff9779e73dc8, RBP: 0xffffff9779e73de0, RSI: 0x00000000bebb47a0, RDI: 0x0000000000000429
R8: 0xffffff80b0f86000, R9: 0x0000000000000001, R10: 0x0000000000000000, R11: 0x0000000000000001
R12: 0x0000000000000000, R13: 0x0000000000000001, R14: 0x0000000000000421, R15: 0x0000000000000421
RFL: 0x0000000000010002, RIP: 0xffffff80155c0f01, CS: 0x0000000000000008, SS: 0x0000000000000010
Fault CR2: 0x0000000000000429, Error code: 0x0000000000000000, Fault CPU: 0x2, PL: 1

Backtrace (CPU 2), Frame : Return Address
0xffffff9779e73a50 : 0xffffff80154dab52
0xffffff9779e73ad0 : 0xffffff80155ce6fa
0xffffff9779e73cb0 : 0xffffff80155ec563
0xffffff9779e73cd0 : 0xffffff80155c0f01
0xffffff9779e73de0 : 0xffffff80154fb15c
0xffffff9779e73e20 : 0xffffff80154fb45e
0xffffff9779e73e40 : 0xffffff7f97c96abc
0xffffff9779e73e70 : 0xffffff7f97c97f5b
0xffffff9779e73eb0 : 0xffffff7f97c97d90
0xffffff9779e73ef0 : 0xffffff8015ab5146
0xffffff9779e73f40 : 0xffffff8015ab2fb1
0xffffff9779e73f80 : 0xffffff8015ab30a6
0xffffff9779e73fb0 : 0xffffff80155c9117
Kernel Extensions in backtrace:
com.MinnowStor.NVMeGeneric(1.0)[27312503-CF2F-3E2B-8D8D-6E79177410C9]@0xffffff7f97c92000->0xffffff7f97c9efff
dependency: com.apple.iokit.IOPCIFamily(2.9)[F51AA3D6-EC2F-3AD3-A043-06DB79027AA2]@0xffffff7f95c50000
dependency: com.apple.iokit.IOStorageFamily(2.1)[DC1AAB7C-F417-3238-BB3F-2A5B84D67B90]@0xffffff7f95e89000

BSD process name corresponding to current thread: kernel_task
Boot args: npci=0x2000 darkwake=8 nvda_drv=1

 

[shilohh]

Thank you again, its very nice of you. Here are my stats:

CPU Ratio Info:

CPU Low Frequency Mode.............: 1200 MHz

CPU Maximum non-Turbo Frequency....: 3200 MHz

CPU Maximum Turbo Frequency........: 3800 MHz

CPU P-States [ 12 22 (27) 32 35 36 37 38 ]

Based on your info, it looks like you are reaching you max turbo pstate. What speed is your ram running at?

 

[shilohh]

I am getting a lockup as well. It's fine for some period of time after I have booted the computer under 10.12.2, but then it just locks up and I have to reboot it.

I've gotten as far as Step 10. I've done the post install stuff.

Well I completely removed the NVME SSD and booted off the new sata and it still locked up the same. So it doesn't seem like the NVME should be the issue. I haven't installed/done anything on the new drive to install that, but this was the one panic log I could find.

\Library\Logs\DiagnosticReports\Kernel_2017-01-10-003450_Thes-Mac-Pro.panic

My primary boot drive is an NVME I was using the generic kext for it.

*** Panic Report ***
panic(cpu 2 caller 0xffffff80155ce6fa): Kernel trap at 0xffffff80155c0f01, type 14=page fault, registers:
CR0: 0x000000008001003b, CR2: 0x0000000000000429, CR3: 0x000000002a9f0000, CR4: 0x00000000000626e0
RAX: 0x0000000000000200, RBX: 0x0000000000000429, RCX: 0xffffff80b176edb0, RDX: 0x0000000000000080
RSP: 0xffffff9779e73dc8, RBP: 0xffffff9779e73de0, RSI: 0x00000000bebb47a0, RDI: 0x0000000000000429
R8: 0xffffff80b0f86000, R9: 0x0000000000000001, R10: 0x0000000000000000, R11: 0x0000000000000001
R12: 0x0000000000000000, R13: 0x0000000000000001, R14: 0x0000000000000421, R15: 0x0000000000000421
RFL: 0x0000000000010002, RIP: 0xffffff80155c0f01, CS: 0x0000000000000008, SS: 0x0000000000000010
Fault CR2: 0x0000000000000429, Error code: 0x0000000000000000, Fault CPU: 0x2, PL: 1

Backtrace (CPU 2), Frame : Return Address
0xffffff9779e73a50 : 0xffffff80154dab52
0xffffff9779e73ad0 : 0xffffff80155ce6fa
0xffffff9779e73cb0 : 0xffffff80155ec563
0xffffff9779e73cd0 : 0xffffff80155c0f01
0xffffff9779e73de0 : 0xffffff80154fb15c
0xffffff9779e73e20 : 0xffffff80154fb45e
0xffffff9779e73e40 : 0xffffff7f97c96abc
0xffffff9779e73e70 : 0xffffff7f97c97f5b
0xffffff9779e73eb0 : 0xffffff7f97c97d90
0xffffff9779e73ef0 : 0xffffff8015ab5146
0xffffff9779e73f40 : 0xffffff8015ab2fb1
0xffffff9779e73f80 : 0xffffff8015ab30a6
0xffffff9779e73fb0 : 0xffffff80155c9117
Kernel Extensions in backtrace:
com.MinnowStor.NVMeGeneric(1.0)[27312503-CF2F-3E2B-8D8D-6E79177410C9]@0xffffff7f97c92000->0xffffff7f97c9efff
dependency: com.apple.iokit.IOPCIFamily(2.9)[F51AA3D6-EC2F-3AD3-A043-06DB79027AA2]@0xffffff7f95c50000
dependency: com.apple.iokit.IOStorageFamily(2.1)[DC1AAB7C-F417-3238-BB3F-2A5B84D67B90]@0xffffff7f95e89000

BSD process name corresponding to current thread: kernel_task
Boot args: npci=0x2000 darkwake=8 nvda_drv=1

Based on your report, your nvme kext (com.MinnowStor.NVMeGeneric) is panicking your system. Just using a non nvme drive may not stop the kext from loading. Look for a update, go back to a non nvme drive or revert to a older os. If you really want to test it, you'll need to remove the kext and rebuild the caches.

 

[ggeorge]

Based on your report, your nvme kext (com.MinnowStor.NVMeGeneric) is panicking your system. Just using a non nvme drive may not stop the kext from loading. Look for a update, go back to a non nvme drive or revert to a older os. If you really want to test it, you'll need to remove the kext and rebuild the caches.

It was a clean install on the SATA drive. I never installed the kext on the new drive to begin with and didn't copy anything other than world of warcraft on to the new drive (no migration). I can't find that kext on the new drive either. I booted the computer from the drive without the NVME installed and it still locked up. So I'm not sure how I'm getting the panic.

 

[shilohh]

I booted the computer from the drive without the NVME installed and it still locked up and I never installed the kext on the new drive to begin with and didn't copy anything other than world of warcraft on to the new drive. I can't find that kext on the new drive either. Only the old NVME drive. So I'm not sure how I'm getting the panic.

If the kext wasn't loaded, it wouldn't be listed in the backtrace you posted

 

[blackgiwi]

Based on your info, it looks like you are reaching you max turbo pstate. What speed is your ram running at?

I have G.skill 2x4gb DDR3 on stock frequency (F3-10600CL9D-8GBNT):

• DDR3 1333 (PC3 10600)

• Timing 9-9-9-24

• Cas Latency 9

• Voltage 1.5V

 

[pdrufo]

Thank you for your help. We are up and running now!

 

[ggeorge]

If the kext wasn't loaded, it wouldn't be listed in the backtrace you posted

I understand that, I'm just not convinced that I was looking at the right log for the lockup.

It was dated from 2 days previously and the panic log hasn't been updated with a current date, when I've tried booting from the new OS drive since then.

I only mentioned it because I wasn't sure WHERE I should be looking for the correct log.