Contribute
Register

Getting a KP report at every boot - without having a KP...?

Status
Not open for further replies.
Richylitschy

Richylitschy

Joined
Feb 20, 2019
Messages
54
Motherboard
Dell XPS 9360
CPU
i5-7200U
Graphics
HD 620
Dear all,

my Mojave setup is running pretty flawlessly since 3 weeks now. However, I have one issue: at every boot, no matter if a cold boot or restart, I get a "Your computer was restarted because of a problem" message. However, I don't have any KP's. The computer boots up just fine and everything works.
I had a few KP's during the installation process due to wrong boot args and old kexts, but these were 3 weeks ago. So from my understanding, macOS keeps bringing up the report of an old KP. This is not a major issue, bit still bothers me. Did anyone of you experience the same issue and knows how to fix it? I have already reset the NVRAM, it didn't change anything.

Another reason why I'm so sure that this is a report of an old KP are the stated boot args:

- in the report it says that my boot args are the following: Boot args: debug=0x12a acpi_layer=0x08 acpi_level=0x02 msgbuf=512000 igfxcflbklt=opcode alcid=11 -v

- I doubled checked however in my plist and in the clover boot menu that my args are the following: Boot args: darkwake=4 igfxcflbklt=opcode alcid=13

Any help on removing this old error message would be awesome, thanks!

Code: 
Anonymous UUID:       21F531E1-B8AF-A83D-60DC-495DFD63D75E

Sat Mar 16 22:43:28 2019

*** Panic Report ***
panic(cpu 0 caller 0xffffff7f8818c31c): allocMem: failed assertion 'addr'
Backtrace (CPU 0), Frame : Return Address
0xffffff81188f3a80 : 0xffffff80043aeb0d
0xffffff81188f3ad0 : 0xffffff80044e8653
0xffffff81188f3b10 : 0xffffff80044da07a
0xffffff81188f3b80 : 0xffffff800435bca0
0xffffff81188f3ba0 : 0xffffff80043ae527
0xffffff81188f3cc0 : 0xffffff80043ae373
0xffffff81188f3d30 : 0xffffff7f8818c31c
0xffffff81188f3d40 : 0xffffff7f881954c9
0xffffff81188f3d80 : 0xffffff7f881952d1
0xffffff81188f3db0 : 0xffffff7f8818bc59
0xffffff81188f3e00 : 0xffffff7f87e6a018
0xffffff81188f3e40 : 0xffffff8004a2ca1b
0xffffff81188f3e80 : 0xffffff8004a2c761
0xffffff81188f3f00 : 0xffffff8004a2bcb7
0xffffff81188f3f50 : 0xffffff8004a2d786
0xffffff81188f3fa0 : 0xffffff800435b0ce
      Kernel Extensions in backtrace:
         com.apple.iokit.IOAudioFamily(206.5)[99F194F6-E536-3B60-9667-06F6F83BC26B]@0xffffff7f87e66000->0xffffff7f87ea4fff
            dependency: com.apple.vecLib.kext(1.2.0)[990BDF56-F253-3E2A-89DB-7914D4074AAB]@0xffffff7f87d98000
         org.voodoo.driver.VoodooHDA(2.9.1)[00000000-0000-0000-0000-000000000000]@0xffffff7f88189000->0xffffff7f881b5fff
            dependency: com.apple.iokit.IOAudioFamily(206.5)[99F194F6-E536-3B60-9667-06F6F83BC26B]@0xffffff7f87e66000
            dependency: com.apple.iokit.IOPCIFamily(2.9)[5C9A453F-559B-3683-9E81-D288D13A33CE]@0xffffff7f84ceb000

BSD process name corresponding to current thread: Unknown
Boot args: debug=0x12a acpi_layer=0x08 acpi_level=0x02 msgbuf=512000 igfxcflbklt=opcode alcid=11 -v root-dmg=file:///Install%20macOS%20Mojave.app/Contents/SharedSupport/BaseSystem.dmg

Mac OS version:
Not yet set

Kernel version:
Darwin Kernel Version 18.2.0: Thu Dec 20 20:46:53 PST 2018; root:xnu-4903.241.1~1/RELEASE_X86_64
Kernel UUID: 1970B070-E53F-3178-83F3-1B95FA340695
Kernel slide:     0x0000000004000000
Kernel text base: 0xffffff8004200000
__HIB  text base: 0xffffff8004100000
System model name: MacBookPro14,1 (Mac-B4831CEBD52A0C4C)

System uptime in nanoseconds: 5760292060
last loaded kext at 4699433277: com.apple.driver.AppleSmartBatteryManager    161.0.0 (addr 0xffffff7f879b8000, size 73728)
loaded kexts:
org.voodoo.driver.VoodooHDA    2.9.1
com.alexandred.VoodooI2C    2.1.4
org.coolstar.VoodooGPIO    1.1
org.rehabman.voodoo.driver.PS2Controller    1.9.2
as.vit9696.SMCProcessor    1.0.2
as.lvs1974.AirportBrcmFixup    1.1.9
as.vit9696.AppleALC    1.3.4
as.vit9696.WhateverGreen    1.2.6
ru.usrsse2.SMCBatteryManager    1
com.rehabman.driver.USBInjectAll    0.7.1
ru.usrsse2.SMCLightSensor    1
as.vit9696.VirtualSMC    1.0.2
com.alexandred.VoodooI2CServices    1
org.vanilla.driver.CPUFriend    1.1.6
as.vit9696.Lilu    1.3.1
com.apple.driver.AppleSmartBatteryManager    161.0.0
com.apple.driver.AppleAHCIPort    329.200.2
com.apple.driver.AirPort.Brcm4360    1400.1.1
com.apple.driver.AirPort.BrcmNIC    1400.1.1
com.apple.driver.AppleRTC    2.0
com.apple.driver.AppleACPIButtons    6.1
com.apple.driver.AppleACPIEC    6.1
com.apple.driver.AppleHPET    1.8
com.apple.driver.AppleSMBIOS    2.1
com.apple.driver.AppleAPIC    1.7
com.apple.nke.applicationfirewall    190
com.apple.security.TMSafetyNet    8
com.apple.iokit.IOAudioFamily    206.5
com.apple.vecLib.kext    1.2.0
com.apple.iokit.IOAHCIFamily    288
com.apple.iokit.IO80211Family    1200.12.2
com.apple.driver.mDNSOffloadUserClient    1.0.1b8
com.apple.driver.corecapture    1.0.4
com.apple.driver.AppleIntelLpssI2C    3.0.60
com.apple.driver.AppleIntelLpssGspi    3.0.60
com.apple.driver.usb.AppleUSBXHCIPCI    1.2
com.apple.driver.usb.AppleUSBXHCI    1.2
com.apple.driver.AppleEFINVRAM    2.1
com.apple.driver.AppleEFIRuntime    2.1
com.apple.iokit.IOHIDFamily    2.0.0
com.apple.security.quarantine    3
com.apple.security.sandbox    300.0
com.apple.kext.AppleMatch    1.0.0d1
com.apple.iokit.IOSMBusFamily    1.1
com.apple.driver.AppleKeyStore    2
com.apple.driver.AppleUSBTDM    456.230.1
com.apple.driver.AppleMobileFileIntegrity    1.0.5
com.apple.kext.CoreTrust    1
com.apple.iokit.IOUSBMassStorageDriver    145.200.2
com.apple.iokit.IOSCSIBlockCommandsDevice    408.200.1
com.apple.iokit.IOSCSIArchitectureModelFamily    408.200.1
com.apple.driver.AppleCredentialManager    1.0
com.apple.driver.KernelRelayHost    1
com.apple.driver.AppleSEPManager    1.0.1
com.apple.driver.IOSlaveProcessor    1
com.apple.driver.AppleFDEKeyStore    28.30
com.apple.driver.AppleEffaceableStorage    1.0
com.apple.iokit.IOTimeSyncFamily    700.7
com.apple.iokit.IONetworkingFamily    3.4
com.apple.driver.DiskImages    493.0.0
com.apple.iokit.IOStorageFamily    2.1
com.apple.iokit.IOBluetoothFamily    6.0.10f1
com.apple.iokit.IOUSBHostFamily    1.2
com.apple.driver.usb.AppleUSBCommon    1.0
com.apple.driver.AppleBusPowerController    1.0
com.apple.iokit.IOReportFamily    47
com.apple.driver.AppleACPIPlatform    6.1
com.apple.driver.AppleSMC    3.1.9
com.apple.iokit.IOPCIFamily    2.9
com.apple.iokit.IOACPIFamily    1.4
com.apple.kec.Libm    1
com.apple.kec.pthread    1
com.apple.kec.corecrypto    1.0

EOF
Model: MacBookPro14,1, BootROM 184.0.0.0.0, 2 processors, Intel Core i5, 2 GHz, 8 GB, SMC 2.43f6
Graphics: Intel HD Graphics 620, Intel HD Graphics 620, Built-In
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x19), Broadcom BCM43xx 1.0 (7.77.61.1 AirPortDriverBrcmNIC-1305.2)
Bluetooth: Version 6.0.10f1, 3 services, 18 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en0
Serial ATA Device: SK hynix SC311 SATA 128GB, 128,04 GB
USB Device: USB 3.0 Bus
USB Device: USB5742
USB Device: Integrated_Webcam_HD
USB Device: BCM20702A0
USB Device: USB2742
USB Device: Vendor-Specific Device
Thunderbolt Bus:
 
At the Clover boot menu select your hard drive and press F11.
 
P1LGRIM said:
At the Clover boot menu select your hard drive and press F11.
Click to expand...
Thanks for the fast answer!

Just tried it, didn't fix the issue though. F11 is just a way of deleting the NVRAM right?
May it be the issue, that Clover is still recognising my old Windows EFI partition? I'm NOT running a dual boot btw, I just didn't care to delete the old partitions.
 
I checked my NVRAM and it indeed stores the information about the KP. However, pressing F11 at the Clover menu reboots the PC, but the NVRAM hasn't been cleared. Im using the latest clover rev and latest Mojave.

Any ideas how to delete my NVRAM? The terminal command doesn't work with Mojave unfortunately. Thanks!
 
Richylitschy said:
The terminal command doesn't work with Mojave unfortunately.
Click to expand...
The command works in Mojave :
As a demonstration that it works open Terminal and type :
Code: 
nvram -p
to see the current state of NVRAM.

Then in Terminal type :
Code: 
sudo nvram -c
to clear the contents of NVRAM.

Then in Terminal type :
Code: 
nvram -p
to verify that NVRAM has indeed been cleared.

Problems may arise if you are emulating NVRAM with EmuVariableUefi-64.efi and RC scripts as it appears that in this case the previous values are restored even though they were cleared in Terminal.
You can try with EmuVariableUefi-64.efi and RC scripts removed and delete the file nvram.plist.

If you are not emulating native NVRAM support then you may have to clear the cMOS settings to remove the panic information.
 
Thanks for your answer!

I just did a fresh install and the problem persists. I formatted everything BUT the EFI partition, maybe I should have done that. I never installed any RC scripts and can't find any in etc/

Where is the EmuVariable located? Should I reinstall and format EFI partition this time? Quite time consuming unfortunately
 
If your panic report is stored in native NVRAM then no amount of reinstalling will help you.
 
P1LGRIM said:
If your panic report is stored in native NVRAM then no amount of reinstalling will help you.
Click to expand...
Cheers man!

I reset my CMOS and afterwards the Hackintosh wasn't starting anymore, took me a few minutes to remember that I needed to patch the DVMT values again... :D
I also deleted the EmuVariable beforehand (yes I now, never change two things at once...).
Then I performed the sudo nvram -c command and voila: it didn't restore the old NVRAM!

Thanks a lot Pilgrim!
 
Status
Not open for further replies.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top