"a freed zone element has been modified: expected 0xdeadbeefdeadbeef but found 0

[HackInBuild]

I just build my first hackintosh and everything was going great until I got this strange error message while at the apple screen on boot up.

Most of the first line is in the title, but here is some other information I think might be helpful:

System uptime in nanoseconds: 9507200668
panic cpu 1 caller
Mac OS version: 13E20
Darwin Kernal Version 13.3.0

I am a pretty big noob at this whole hackintosh thing, so any information (Preferably dummy proof) would be very nice.

 

[TooSwede]

I have the same issue

 

[wangerman69]

Have either of you tried booting safe mode using the -x boot flag at the bootloader screen.Just type this in before the bar counts all the way down.

Also double check all of your bios settings are correct

Also a full list of hardware would help

 

[rixmeister]

I'm almost certain that this problem is caused by an incompatibility with the intel gigabit networking driver from multibeast and the 10.10.2 and 10.10.3 since I took the update just fine and rebooted in and then added this driver and got the error when I rebooted. Do you by chance have the intel gigabit network card on your system? I haven't solved it yet but I think a different driver will fix the problem so you'll need to delete the current driver first either by booting into another working partition or by command line after booting with -i

 

[Going Bald]

I'm almost certain that this problem is caused by an incompatibility with the intel gigabit networking driver from multibeast and the 10.10.2 and 10.10.3 since I took the update just fine and rebooted in and then added this driver and got the error when I rebooted. Do you by chance have the intel gigabit network card on your system? I haven't solved it yet but I think a different driver will fix the problem so you'll need to delete the current driver first either by booting into another working partition or by command line after booting with -i

In which case you would be wrong - it is caused by memory error and is a known issue. Did you bother to search before you posted per the rules?
See http://www.tonymacx86.com/search.php?googleSearch=0xdeadbeef

 

[adizrox]

tried nv_disable=1 gave me the same error..

later it was solved by using -v -x boot arguments....
-no-zp also solved the issue.