pastrychef's Asus ROG Strix Z370-G Gaming (WI-FI AC) build w/ i9-9900K + AMD 6600 XT

[dclive]

Yes.

FYI, I think everyone is referencing https://www.tonymacx86.com/threads/mac-os-mojave-died-after-installing-intel-power-gadget.284270/. I'm not sure if 3.7 still causes the issue; I vaguely remember having a problem with the app; may have been 3.6.

 

[pastrychef]

FYI, I think everyone is referencing https://www.tonymacx86.com/threads/mac-os-mojave-died-after-installing-intel-power-gadget.284270/. I'm not sure if 3.7 still causes the issue; I vaguely remember having a problem with the app; may have been 3.6.

I never had any issues like that... I just installed it and iStat Menus is now able to display CPU frequency.

 

[dclive]

Can confirm - 3.7 still does a hard hang shortly after login. I have iStat Menus 6.40, and I can log in, and shortly after (but before iState Menus appears) I get a hard OS hang, lose mouse/key functionality, and I am forced to reboot. Safe boot is able to boot, so I was able to fix fairly quickly by simply uninstalling the app.

 

[Nicoras]

FYI, I think everyone is referencing https://www.tonymacx86.com/threads/mac-os-mojave-died-after-installing-intel-power-gadget.284270/. I'm not sure if 3.7 still causes the issue; I vaguely remember having a problem with the app; may have been 3.6.

Removing EnergyDriver.kext still results in this.

panic(cpu 2 caller 0xffffff800044aa3a): Kernel trap at 0xffffff7f8711f0c7, type 13=general protection, registers:
CR0: 0x0000000080010033, CR2: 0x000000010768b000, CR3: 0x0000000ba866019b, CR4: 0x00000000003626e0
RAX: 0xffffff7f87120070, RBX: 0x0000000000000000, RCX: 0x0000000000000771, RDX: 0xffffff80b6498610
RSP: 0xffffff8727f73aa0, RBP: 0xffffff8727f73aa0, RSI: 0x0000000000000771, RDI: 0xffffff80b6498610
R8:  0x0000000000000015, R9:  0x0000000000000000, R10: 0xffffff80ab6eca44, R11: 0xffffff80b649860c
R12: 0x0000000000000009, R13: 0x00000000e00002e2, R14: 0x0000000000000000, R15: 0x0000000000000001
RFL: 0x0000000000010202, RIP: 0xffffff7f8711f0c7, CS:  0x0000000000000008, SS:  0x0000000000000010
Fault CR2: 0x000000010768b000, Error code: 0x0000000000000000, Fault CPU: 0x2, PL: 0, VF: 0

Backtrace (CPU 2), Frame : Return Address
0xffffff8000152220 : 0xffffff800031f5cd mach_kernel : _handle_debugger_trap + 0x49d
0xffffff8000152270 : 0xffffff8000458b05 mach_kernel : _kdp_i386_trap + 0x155
0xffffff80001522b0 : 0xffffff800044a68e mach_kernel : _kernel_trap + 0x4ee
0xffffff8000152300 : 0xffffff80002c5a40 mach_kernel : _return_from_trap + 0xe0
0xffffff8000152320 : 0xffffff800031ec97 mach_kernel : _DebuggerTrapWithState + 0x17
0xffffff8000152420 : 0xffffff800031f087 mach_kernel : _panic_trap_to_debugger + 0x227
0xffffff8000152470 : 0xffffff8000ac27cc mach_kernel : _panic + 0x54
0xffffff80001524e0 : 0xffffff800044aa3a mach_kernel : _sync_iss_to_iks + 0x2aa
0xffffff8000152660 : 0xffffff800044a738 mach_kernel : _kernel_trap + 0x598
0xffffff80001526b0 : 0xffffff80002c5a40 mach_kernel : _return_from_trap + 0xe0
0xffffff80001526d0 : 0xffffff7f8711f0c7 com.intel.driver.EnergyDriver : __ZN29com_intel_driver_EnergyDriver7readMSREjPy + 0x9
0xffffff8727f73aa0 : 0xffffff7f8711fc8f com.intel.driver.EnergyDriver : __ZN35com_intel_driver_EnergyDriverClient15executeCommandsEPKvjPyj + 0x19f
0xffffff8727f73b10 : 0xffffff8000a54a8e mach_kernel : __ZN12IOUserClient14externalMethodEjP25IOExternalMethodArgumentsP24IOExternalMethodDispatchP8OSObjectPv + 0x1de
0xffffff8727f73b60 : 0xffffff8000a5dcb3 mach_kernel : _is_io_connect_method + 0x223
0xffffff8727f73ca0 : 0xffffff80004082b2 mach_kernel : _iokit_server_routine + 0x4e72
0xffffff8727f73db0 : 0xffffff8000325328 mach_kernel : _ipc_kobject_server + 0x238
0xffffff8727f73e10 : 0xffffff80002fbcc5 mach_kernel : _ipc_kmsg_send + 0x135
0xffffff8727f73e70 : 0xffffff8000312aa2 mach_kernel : _mach_msg_overwrite_trap + 0x2d2
0xffffff8727f73f00 : 0xffffff8000430d05 mach_kernel : _mach_call_munger64 + 0x205
0xffffff8727f73fa0 : 0xffffff80002c6226 mach_kernel : _hndl_mach_scall64 + 0x16
      Kernel Extensions in backtrace:
         com.intel.driver.EnergyDriver(3.6)[CF3549FA-B79E-34E2-BF25-6C5FEF5EF262]@0xffffff7f8711e000->0xffffff7f87123fff

BSD process name corresponding to current thread: Intel Power Gadg
Boot args: -alcbeta -lilubetaall debug=0x100 keepsyms=1 -wegbeta -vsmcbeta

Mac OS version:
19F101

Kernel version:
Darwin Kernel Version 19.5.0: Tue May 26 20:41:44 PDT 2020; root:xnu-6153.121.2~2/RELEASE_X86_64
Kernel UUID: 54F1A78D-6F41-32BD-BFED-4381F9F6E2EF
__HIB  text base: 0xffffff8000100000
System model name: iMac19,1 (Mac-AA95B1DDAB278B95)
System shutdown begun: NO
Panic diags file available: YES (0x0)

System uptime in nanoseconds: 10751109856175

 

[dclive]

Removing EnergyDriver.kext still results in this.

panic(cpu 2 caller 0xffffff800044aa3a): Kernel trap at 0xffffff7f8711f0c7, type 13=general protection, registers:
CR0: 0x0000000080010033, CR2: 0x000000010768b000, CR3: 0x0000000ba866019b, CR4: 0x00000000003626e0
RAX: 0xffffff7f87120070, RBX: 0x0000000000000000, RCX: 0x0000000000000771, RDX: 0xffffff80b6498610
RSP: 0xffffff8727f73aa0, RBP: 0xffffff8727f73aa0, RSI: 0x0000000000000771, RDI: 0xffffff80b6498610
R8:  0x0000000000000015, R9:  0x0000000000000000, R10: 0xffffff80ab6eca44, R11: 0xffffff80b649860c
R12: 0x0000000000000009, R13: 0x00000000e00002e2, R14: 0x0000000000000000, R15: 0x0000000000000001
RFL: 0x0000000000010202, RIP: 0xffffff7f8711f0c7, CS:  0x0000000000000008, SS:  0x0000000000000010
Fault CR2: 0x000000010768b000, Error code: 0x0000000000000000, Fault CPU: 0x2, PL: 0, VF: 0

Backtrace (CPU 2), Frame : Return Address
0xffffff8000152220 : 0xffffff800031f5cd mach_kernel : _handle_debugger_trap + 0x49d
0xffffff8000152270 : 0xffffff8000458b05 mach_kernel : _kdp_i386_trap + 0x155
0xffffff80001522b0 : 0xffffff800044a68e mach_kernel : _kernel_trap + 0x4ee
0xffffff8000152300 : 0xffffff80002c5a40 mach_kernel : _return_from_trap + 0xe0
0xffffff8000152320 : 0xffffff800031ec97 mach_kernel : _DebuggerTrapWithState + 0x17
0xffffff8000152420 : 0xffffff800031f087 mach_kernel : _panic_trap_to_debugger + 0x227
0xffffff8000152470 : 0xffffff8000ac27cc mach_kernel : _panic + 0x54
0xffffff80001524e0 : 0xffffff800044aa3a mach_kernel : _sync_iss_to_iks + 0x2aa
0xffffff8000152660 : 0xffffff800044a738 mach_kernel : _kernel_trap + 0x598
0xffffff80001526b0 : 0xffffff80002c5a40 mach_kernel : _return_from_trap + 0xe0
0xffffff80001526d0 : 0xffffff7f8711f0c7 com.intel.driver.EnergyDriver : __ZN29com_intel_driver_EnergyDriver7readMSREjPy + 0x9
0xffffff8727f73aa0 : 0xffffff7f8711fc8f com.intel.driver.EnergyDriver : __ZN35com_intel_driver_EnergyDriverClient15executeCommandsEPKvjPyj + 0x19f
0xffffff8727f73b10 : 0xffffff8000a54a8e mach_kernel : __ZN12IOUserClient14externalMethodEjP25IOExternalMethodArgumentsP24IOExternalMethodDispatchP8OSObjectPv + 0x1de
0xffffff8727f73b60 : 0xffffff8000a5dcb3 mach_kernel : _is_io_connect_method + 0x223
0xffffff8727f73ca0 : 0xffffff80004082b2 mach_kernel : _iokit_server_routine + 0x4e72
0xffffff8727f73db0 : 0xffffff8000325328 mach_kernel : _ipc_kobject_server + 0x238
0xffffff8727f73e10 : 0xffffff80002fbcc5 mach_kernel : _ipc_kmsg_send + 0x135
0xffffff8727f73e70 : 0xffffff8000312aa2 mach_kernel : _mach_msg_overwrite_trap + 0x2d2
0xffffff8727f73f00 : 0xffffff8000430d05 mach_kernel : _mach_call_munger64 + 0x205
0xffffff8727f73fa0 : 0xffffff80002c6226 mach_kernel : _hndl_mach_scall64 + 0x16
      Kernel Extensions in backtrace:
         com.intel.driver.EnergyDriver(3.6)[CF3549FA-B79E-34E2-BF25-6C5FEF5EF262]@0xffffff7f8711e000->0xffffff7f87123fff

BSD process name corresponding to current thread: Intel Power Gadg
Boot args: -alcbeta -lilubetaall debug=0x100 keepsyms=1 -wegbeta -vsmcbeta

Mac OS version:
19F101

Kernel version:
Darwin Kernel Version 19.5.0: Tue May 26 20:41:44 PDT 2020; root:xnu-6153.121.2~2/RELEASE_X86_64
Kernel UUID: 54F1A78D-6F41-32BD-BFED-4381F9F6E2EF
__HIB  text base: 0xffffff8000100000
System model name: iMac19,1 (Mac-AA95B1DDAB278B95)
System shutdown begun: NO
Panic diags file available: YES (0x0)

System uptime in nanoseconds: 10751109856175

Your posted dump indicates to me you still have v3.6 installed. Suggest removing that then retrying. Use the install located in /Applications/Intel Power Gadget to get rid of all remnants.

 

[Nicoras]

I never had any issues like that... I just installed it and iStat Menus is now able to display CPU frequency.

Can confirm - 3.7 still does a hard hang shortly after login. I have iStat Menus 6.40, and I can log in, and shortly after (but before iState Menus appears) I get a hard OS hang, lose mouse/key functionality, and I am forced to reboot. Safe boot is able to boot, so I was able to fix fairly quickly by simply uninstalling the app.

Yep dclive you're right! pastry, you're using 3.5.5 at most. I just switched to that and i'm fine now. Need to warn users that 3.6.0 results in kernel panic.

 

[pastrychef]

Yep dclive you're right! pastry, you're using 3.5.5 at most. I just switched to that and i'm fine now. Need to warn users that 3.6.0 results in kernel panic.

kextstat shows:



Get Info shows:

 

[dclive]

#Shouldn'tWork.

I have Clover 5118, in a setup very, very similar to your Clover starting point from roughly Jan 2020.

 

[pastrychef]

#Shouldn'tWork.

I have Clover 5118, in a setup very, very similar to your Clover starting point from roughly Jan 2020.

I'm on OpenCore on my Z370 and Z390. Intel Power Gadget 3.7.0 works.

I'm on Clover on my laptop. Intel Power Gadget 3.7.0 works.

 

[Nicoras]

Your posted dump indicates to me you still have v3.6 installed. Suggest removing that then retrying. Use the install located in /Applications/Intel Power Gadget to get rid of all remnants.

Don't worry, got that sorted!

Here's 3.5.5

Intel Developer Zone

Find software and development products, explore tools and technologies, connect with other developers and more. Sign up to manage your products.

software.intel.com