- Joined
- Jul 19, 2013
- Messages
- 6
- CPU
- 4700k
- Graphics
- Intel HD 4600
- Mac
- Classic Mac
- Mobile Phone
Hey folks.
I'm having some trouble with "0xdeadbeef".
As some of you may know, the infamous "0xdeadbeef" is actually a marker used by some Unices to mark regions of memory as safe for allocation. That is, any memory region containing "0xdeadbeefdeadbeefdeadbeef..." is fair game. Any memory not containing "0xdeadbeef" is unsafe to use, because it should only have a different value if had been already allocated; when the memory is freed, it is filled with "0xdeadbeef" again.
My first build was composed of a 4770k processor, 4x8gb of Corsair 1866 MHz memory (cmz32gx3m4x1866c10), a Corsair TX 750 PSU, and a Gigabyte Z87X-OC motherboard.
After some time on Mavericks, perhaps after updating to something ~10.9.2-ish, I started having stability problems. My system would crash about 5 minutes after login. Sometimes it wouldn't boot, giving me a kernel panic with a message like:
panic(cpu 6 caller 0xffff...): "a freed zone element has been modified: expected 0xdeadbeefdeadbeef but found 0xdeadbeef88098809, bits changed 0x56a436e6, at offset 16 of 32 in zone: kalloc.32"@/SourceCache/xnu/xnu-2422.110
I quickly whipped up an Unibeast installer from the latest Mavericks installer, and I couldn't boot from the USB stick without removing a dimm or doing "maxmem=4096". Even after an install, I couldn't boot without less than 32 GiB of RAM.
So I started a new build. I read online in various places that sometimes Gigabyte boards don't like all 4 slots filled. I wanted to downsize my pc, so I opted this time for an Asus mATX board, the ROG Maximus VII Gene. Others here have had some success with it (although it is Z97).
Same problem. I have tried the XMP profile. I have tried relaxing the timings. I have tried lowering the frequency. I have tried upping the DRAM voltage, and VCCSA. No love. I even tried a couple of the n00b overclocking wizards on the Gene. Nothing worked.
Now at this point, you have to say to yourself, it's probably the RAM. Well, I'm currently reproducing the same results with a similar kit of GSkill 1866 MHz memory with the same timings.
The interesting part is the error is always "kalloc." + "32" or "64" + "''@/SourceCache/xnu/xnu-2422.110". Furthermore, it is always "at offset 48 of 64" or "at offset 16 of 32". And I have only had it report erroneous values of "88098809" or "00000000". (Another forum user reported a similar error with "88098809" on the forum).
If I manage to install OS X (ie. by using "maxmem=4096"), and boot with just "-x IGPEnabler=No", then I can make it to login, but the moment after password entry, I get the same type of panic (with no previous stack trace showing, even if I have booted with "-v").
Can anyone shed some light on this? I've seen others on the forums claim their problems are solved with "maxmem=4096", but we can't run on only 1/4 of our memory day to day :'(
I'm having some trouble with "0xdeadbeef".
As some of you may know, the infamous "0xdeadbeef" is actually a marker used by some Unices to mark regions of memory as safe for allocation. That is, any memory region containing "0xdeadbeefdeadbeefdeadbeef..." is fair game. Any memory not containing "0xdeadbeef" is unsafe to use, because it should only have a different value if had been already allocated; when the memory is freed, it is filled with "0xdeadbeef" again.
My first build was composed of a 4770k processor, 4x8gb of Corsair 1866 MHz memory (cmz32gx3m4x1866c10), a Corsair TX 750 PSU, and a Gigabyte Z87X-OC motherboard.
After some time on Mavericks, perhaps after updating to something ~10.9.2-ish, I started having stability problems. My system would crash about 5 minutes after login. Sometimes it wouldn't boot, giving me a kernel panic with a message like:
panic(cpu 6 caller 0xffff...): "a freed zone element has been modified: expected 0xdeadbeefdeadbeef but found 0xdeadbeef88098809, bits changed 0x56a436e6, at offset 16 of 32 in zone: kalloc.32"@/SourceCache/xnu/xnu-2422.110
I quickly whipped up an Unibeast installer from the latest Mavericks installer, and I couldn't boot from the USB stick without removing a dimm or doing "maxmem=4096". Even after an install, I couldn't boot without less than 32 GiB of RAM.
So I started a new build. I read online in various places that sometimes Gigabyte boards don't like all 4 slots filled. I wanted to downsize my pc, so I opted this time for an Asus mATX board, the ROG Maximus VII Gene. Others here have had some success with it (although it is Z97).
Same problem. I have tried the XMP profile. I have tried relaxing the timings. I have tried lowering the frequency. I have tried upping the DRAM voltage, and VCCSA. No love. I even tried a couple of the n00b overclocking wizards on the Gene. Nothing worked.
Now at this point, you have to say to yourself, it's probably the RAM. Well, I'm currently reproducing the same results with a similar kit of GSkill 1866 MHz memory with the same timings.
The interesting part is the error is always "kalloc." + "32" or "64" + "''@/SourceCache/xnu/xnu-2422.110". Furthermore, it is always "at offset 48 of 64" or "at offset 16 of 32". And I have only had it report erroneous values of "88098809" or "00000000". (Another forum user reported a similar error with "88098809" on the forum).
If I manage to install OS X (ie. by using "maxmem=4096"), and boot with just "-x IGPEnabler=No", then I can make it to login, but the moment after password entry, I get the same type of panic (with no previous stack trace showing, even if I have booted with "-v").
Can anyone shed some light on this? I've seen others on the forums claim their problems are solved with "maxmem=4096", but we can't run on only 1/4 of our memory day to day :'(
