Contribute
Register

Stork's Zorro Build: Z68X-UD3H - i7-2600K - HD3000

Status
Not open for further replies.
So the crash just seems a little random. Again, not like a specific driver is barfing (though that one did have Nvidia in it, so you could try installing the Nvidia Web drivers if you like).

You should set XMPDetection to <string>YES</string> or <true /> in config.plist since you have XMP enabled in BIOS.

Clover Configurator is a GUI for editing config.plist. You run it, do a File/Open and select your config.plist, make any changes you want, and then File/Save and it will write out an updated config.plist. You never have to use it -- you can make all the same changes by hand -- I'm guessing that Patch APIC checkbox corresponds to this PatchAPIC setting.

Thanks.

Changing XMPDetection to YES actually made things worse. Basically just took me into a bootloop.

I'm trying the PatchAPIC thing this time around. I'll let you know. Here is the latest crash report (only the top part):

Anonymous UUID: 54D1706A-C2DA-9019-8A98-1F265D34BA40

Sun Nov 29 13:39:23 2015

*** Panic Report ***
panic(cpu 3 caller 0xffffff8025dd6bba): Kernel trap at 0xffffff7fa6c99229, type 14=page fault, registers:
CR0: 0x000000008001003b, CR2: 0x0000000000000000, CR3: 0x000000002e894000, CR4: 0x00000000000626e0
RAX: 0x0000000000000000, RBX: 0x0000000000000000, RCX: 0xffffff81c8bee2a0, RDX: 0x0000000000000020
RSP: 0xffffff9215aabbc0, RBP: 0xffffff9215aabc20, RSI: 0x0000000003000000, RDI: 0xffffff81c8bee008
R8: 0x0000000000000004, R9: 0xffffff80264e0b78, R10: 0xffffff80264e0b78, R11: 0xffffff7fa6f6531b
R12: 0x0000000000000000, R13: 0xffffff804bac8008, R14: 0x0000000000000000, R15: 0x0000000000000464
RFL: 0x0000000000010246, RIP: 0xffffff7fa6c99229, CS: 0x0000000000000008, SS: 0x0000000000000010
Fault CR2: 0x0000000000000000, Error code: 0x0000000000000000, Fault CPU: 0x3, PL: 0

Backtrace (CPU 3), Frame : Return Address
0xffffff9215aab850 : 0xffffff8025ce5307
0xffffff9215aab8d0 : 0xffffff8025dd6bba
0xffffff9215aabab0 : 0xffffff8025df4313
0xffffff9215aabad0 : 0xffffff7fa6c99229
0xffffff9215aabc20 : 0xffffff7fa6c99398
0xffffff9215aabc80 : 0xffffff7fa6ce9f91
0xffffff9215aabcc0 : 0xffffff7fa6ce9773
0xffffff9215aabd30 : 0xffffff7fa6ce9371
0xffffff9215aabd70 : 0xffffff7fa6e5d2c2
0xffffff9215aabdc0 : 0xffffff7fa6fe4318
0xffffff9215aabe20 : 0xffffff7fa6dcb805
0xffffff9215aabe40 : 0xffffff7fa6ce14be
0xffffff9215aabef0 : 0xffffff80262b7536
0xffffff9215aabf40 : 0xffffff80262b53a1
0xffffff9215aabf80 : 0xffffff80262b5496
0xffffff9215aabfb0 : 0xffffff8025dd15d7
Kernel Extensions in backtrace:
com.apple.nvidia.driver.NVDAResman(10.0.6)[E177026A-B6F5-30AB-BF87-8ADC4D102278]@0xffffff7fa6c83000->0xffffff7fa6f05fff
dependency: com.apple.iokit.IOPCIFamily(2.9)[8E5F549E-0055-3C0E-93F8-E872A048E31B]@0xffffff7fa651e000
dependency: com.apple.iokit.IONDRVSupport(2.4.1)[814A7F4B-03EF-384A-B205-9840F0594421]@0xffffff7fa6c6d000
dependency: com.apple.iokit.IOGraphicsFamily(2.4.1)[48AC8EA9-BD3C-3FDC-908D-09850215AA32]@0xffffff7fa6c26000
dependency: com.apple.AppleGraphicsDeviceControl(3.11.33b1)[2BA0BB49-9DFD-3851-984F-8816AE3A1964]@0xffffff7fa6c7d000
com.apple.nvidia.driver.NVDAGK100Hal(10.0.6)[8CE64377-C546-33CF-B016-B343A4F7E20E]@0xffffff7fa6f11000->0xffffff7fa70c0fff
dependency: com.apple.nvidia.driver.NVDAResman(10.0.6)[E177026A-B6F5-30AB-BF87-8ADC4D102278]@0xffffff7fa6c83000
dependency: com.apple.iokit.IOPCIFamily(2.9)[8E5F549E-0055-3C0E-93F8-E872A048E31B]@0xffffff7fa651e000

BSD process name corresponding to current thread: kernel_task
Boot args: dart=0

Mac OS version:
15B42

Kernel version:
Darwin Kernel Version 15.0.0: Sat Sep 19 15:53:46 PDT 2015; root:xnu-3247.10.11~1/RELEASE_X86_64
Kernel UUID: AB5FC1B4-12E7-311E-8E6F-9023985D8C1D
Kernel slide: 0x0000000025a00000
Kernel text base: 0xffffff8025c00000
__HIB text base: 0xffffff8025b00000
System model name: MacPro3,1 (Mac-F42C88C8)

System uptime in nanoseconds: 3272108583
last loaded kext at 2771184471: com.apple.driver.AppleGraphicsDevicePolicy 3.7.7 (addr 0xffffff7fa8451000, size 49152)
loaded kexts:
com.logmein.driver.LogMeInSoundDriver 4.1.52f59
jp.plentycom.driver.SteerMouse 4.1.4
org.hwsensors.driver.GPUSensors 1394
com.insanelymac.RealtekRTL8111 2.0.0
org.hwsensors.driver.LPCSensors 1394
org.hwsensors.driver.ACPISensors 1394
org.hwsensors.driver.CPUSensors 1394
org.netkas.driver.FakeSMC 1394
com.apple.driver.AppleGraphicsDevicePolicy 3.7.7
com.apple.filesystems.autofs 3.0
 
Did the PatchAPIC thing through Clover Configurator. I did a successful shut down and restart after that, but now, with nothing changed, I'm back to a crash every other time. Going to start removing hardware next.
 
FIXED!

The fix was to install the NVIDIA Web Drivers! Now I can shut down and reboot without issue.

I had removed my TPLink airport card, my firewire card, a SATA card, and had decided I would try removing the graphics card, but thought, well since ammulder mentioned installing the NVIDIA Web Drivers, why don't I try that first. So glad I did!

Thanks everyone for all your help!

Now to get iMessage working.... ;)
 
Also got iMessage totally working by following this:

https://www.******.com/r/hackintosh/comments/2wohwn/getting_imessage_working_on_10102_generating/

and then this to link my iPhone number:

https://support.apple.com/en-us/HT201349
 
Well that was short lived.

All of a sudden the only way I can boot up is by using my Unibeast stick.

The problem is when I start in verbose mode without the stick, I get all kinds of different stopping points. The latest one is:

utun_start: ifnet_disable_output returned error 12

And the problem with booting from my USB stick is that it changes my system definition, etc. causing problems with iMessage, iCloud, etc.
 
Got it working again for now...

Also removed my secondary installation that was on a spare SSD. Evidently Clover shouldn't be on more than one drive in the system...is that so?
 
Got it working again for now...

Also removed my secondary installation that was on a spare SSD. Evidently Clover shouldn't be on more than one drive in the system...is that so?
Weird. But, we're (as you're finding out) the 6-Series motherboards are prone to problems. 5, 7, 8 and 9 series motherboards don't seem to have the same problems.

Hang in there. You're pressing into new ground.
 
I was using the secondary installation to work in Final Cut Pro because the current NVIDIA drivers cause it to crash. I had installed a previous version of the drivers in the secondary installation and it was working fine. But something about booting into two different installations was messing things up. So I rolled back the NVIDIA drivers on my main boot drive and unhooked the secondary installation. I'm hoping everything will be hunky dory from here. :)
 
Hallo EddyMac, I wish I could help you: my ga-z68x-ud3h-b3, I7, Geforce GT640, Geekbench today 14071, works well. After years with chimera and F12 BIOS I upgraded to UEFI and Clover. I disconnnected 2 drives with system backup according to http://www.tonymacx86.com/general-h...os-boot-entries-prevent-further-problems.html
Greetings from Germany

Thank you ibaiba. Like you, I've had this system for several years (since 2011 I believe) and upgraded through every OS with Chimera. I updated to UEFI last year.

The problems I was having today led me to that exact thread you linked, about extra boot entries, etc. However, when I listed boot entries, I wasn't really seeing anything problematic. It does seem, though, that since I took out the second El Capitan install, my problems have ceased.

I really want this to work because I don't want to have to update to a new board/processor/RAM until this time next year.
 
Status
Not open for further replies.
Back
Top