- Joined
- Feb 28, 2015
- Messages
- 32
- Motherboard
- GA-H97M-D3H
- CPU
- Intel i5-4690
- Graphics
- EVGA GTX 960 SSC
- Mac
- Classic Mac
- Mobile Phone
Yosemite "deadbeef" error
Hi guys! I have successfully installed Yosemite with Unibeast on my first Hackintosh (my first user-built computer, in fact) largely thanks to help in these forums. Now I'm encountering a couple of other weird issues. The road so far...
Hardware is as follows:
Gigabyte GA-H97M-D3H
Intel i5-4690
Crucial Ballistix Sport 16GB (2x8GB)
Using Intel graphics (I have an EVGA GTX 960 SSC, but had to take it out for the Unibeast installer to run.)
Boot flags -v -x -no-zp got Yosemite to install successfully.
First a side question: Before installing MultiBeast drivers, Yosemite would boot with -v but not without. I thought -v just displays on the screen in text what the boot process is doing anyway (hence "verbose"). Does it actually change something?
Now the real question: I keep getting KPs from "Error: freed zone element. Expected 0xdeadbeefdeadbeef but found 0xdeadbeef00000000." I can't find any perceptible pattern in how/why/when it happens. I have booted multiple times with the same boot flags and performed the same tasks, and that error happens at different points or not at all until I shut down. I have also tried different combinations of -v, -x, and GraphicsEnabler, but the error seems just as random. Any ideas?
Hi guys! I have successfully installed Yosemite with Unibeast on my first Hackintosh (my first user-built computer, in fact) largely thanks to help in these forums. Now I'm encountering a couple of other weird issues. The road so far...
Hardware is as follows:
Gigabyte GA-H97M-D3H
Intel i5-4690
Crucial Ballistix Sport 16GB (2x8GB)
Using Intel graphics (I have an EVGA GTX 960 SSC, but had to take it out for the Unibeast installer to run.)
Boot flags -v -x -no-zp got Yosemite to install successfully.
First a side question: Before installing MultiBeast drivers, Yosemite would boot with -v but not without. I thought -v just displays on the screen in text what the boot process is doing anyway (hence "verbose"). Does it actually change something?
Now the real question: I keep getting KPs from "Error: freed zone element. Expected 0xdeadbeefdeadbeef but found 0xdeadbeef00000000." I can't find any perceptible pattern in how/why/when it happens. I have booted multiple times with the same boot flags and performed the same tasks, and that error happens at different points or not at all until I shut down. I have also tried different combinations of -v, -x, and GraphicsEnabler, but the error seems just as random. Any ideas?