Mac OS X on x86 Hardware 2008–2024 Technical Archive
InfiniteMac OSx86 › Leopard 10.5 › exc_bad_access (sigbus)
7,468 reads · 2009-05-23 – 2009-07-06
Report Leopard 10.5 Voodoo / XNU Kernel AMD OSx86

exc_bad_access (sigbus)

I just installed xXx Osx86 10.5.6 with the Voodoo Kernel and I can't seem to run the majority of the applications. I got ahold of iLife 09 and every time I go to burn a dvd from iDVD the program crashes and I get that error. Programs such…

Primary Author
@daoliverio Published 2009-05-23
Collection
Leopard 10.5
Archival Footprint
7,468 historical reads · 1 curated field notes (from 9 dispatches) · 2009-05-23 – 2009-07-06
Credited Voices (2)
@daoliverio (8)@Voyn1x

I just installed xXx Osx86 10.5.6 with the Voodoo Kernel and I can't seem to run the majority of the applications. I got ahold of iLife 09 and every time I go to burn a dvd from iDVD the program crashes and I get that error. Programs such as DIVX don't even get to load before they cras and give me the same error. I tried the rosetta fix and that didn't solve anything. My RAM is fine and i turned down the overclock that I had and that didn't fix anything either. I am going to download iPC 10.5.6 and see if that distro works and i'm also going to try zephyroth's AMD Patcher…any other suggestions?

xXx Osx86 10.5.6
2x - Kingston 1GB 240-Pin DDR2 SDRAM DDR2 800 (PC2 6400)
ASUS M2A-VM
AMD Athlon 64 X2 4400+
1 TB SATA HDD
40 GB IDE (with SATA converter) (OSX installed here)

Author Updates & Technical Revisions

Follow-up dispatches by @daoliverio

Author Update #1 @daoliverio 2009-05-24

I just had Ubuntu installed last week and everything worked just fine so I don't believe it's the RAM. I put in uname -a and it spit out the correct kernel and version. I'm really at a loss...could it be the voodoo kernel? I'm going to try a different distro and see if that works

Author Update #2 @daoliverio 2009-05-26

here is the error that I'm getting. This is when trying to run Divx 7 for mac

Process: DivX Player [794]
Path: /Applications/DivX Player.app/Contents/MacOS/DivX Player
Identifier: com.divx.DivX_Player
Version: 7.0.1 (build 1_0_1_8) (1.0)
Code Type: X86 (Native)
Parent Process: launchd [567]

Date/Time: 2009-05-25 20:06:07.640 -0400
OS Version: Mac OS X 10.5.6 (9G66)
Report Version: 6

Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000000
Crashed Thread: 3

Thread 0:
0 ? 0x022b320e 0 + 36385294
1 ? 0x022bace5 0 + 36416741
2 ? 0x13c1395f 0 + 331430239
3 ? 0x13bf7ca0 0 + 331316384
4 ? 0x13bec4ae 0 + 331269294
5 ? 0x00231caa 0 + 2301098
6 ? 0x00231ef0 0 + 2301680
7 ? 0x07b8442d 0 + 129516589
8 ? 0x017bea0e 0 + 24898062
9 ? 0x07b81ba6 0 + 129506214
10 ? 0x017772cf 0 + 24605391
11 ? 0x0177923c 0 + 24613436
12 ? 0x0045cd31 0 + 4574513
13 ? 0x004600f1 0 + 4587761
14 ? 0x017d8b3b 0 + 25004859
15 ? 0x0045c2f1 0 + 4571889
16 ? 0x0045c3bd 0 + 4572093
17 ? 0x00460361 0 + 4588385
18 ? 0x000046eb 0 + 18155
19 ? 0x00002b5e 0 + 11102
20 ? 0x00002a85 0 + 10885

Thread 1:
0 ? 0x022b32e6 0 + 36385510
1 ? 0x0232a3ad 0 + 36873133
2 ? 0x0232a26d 0 + 36872813
3 ? 0x007018db 0 + 7346395
4 ? 0x00348cac 0 + 3443884
5 ? 0x00700f45 0 + 7343941
6 ? 0x022e4095 0 + 36585621
7 ? 0x022e3f52 0 + 36585298

Thread 2:
0 ? 0x022b320e 0 + 36385294
1 ? 0x022e5206 0 + 36590086
2 ? 0x0232a539 0 + 36873529
3 ? 0x13c0ef8f 0 + 331411343
4 ? 0x13bd8cef 0 + 331189487
5 ? 0x13becf99 0 + 331272089
6 ? 0x13c12df1 0 + 331427313
7 ? 0x022e4095 0 + 36585621
8 ? 0x022e3f52 0 + 36585298

Thread 3 Crashed:
0 ? 0x022bbe70 0 + 36421232
1 ? 0x13a7c23c 0 + 329761340
2 ? 0x13a821a7 0 + 329785767
3 ? 0x005a926f 0 + 5935727
4 ? 0x005adf8d 0 + 5955469
5 ? 0x005a86d7 0 + 5932759
6 ? 0x13bf9767 0 + 331323239
7 ? 0x13bfa7b8 0 + 331327416
8 ? 0x13bfeb04 0 + 331344644
9 ? 0x13c02a06 0 + 331360774
10 ? 0x13bebda2 0 + 331267490
11 ? 0x13bec058 0 + 331268184
12 ? 0x13c12df1 0 + 331427313
13 ? 0x022e4095 0 + 36585621
14 ? 0x022e3f52 0 + 36585298

Thread 4:
0 ? 0x022ba3ae 0 + 36414382
1 ? 0x022e4d0d 0 + 36588813
2 ? 0x06e31b32 0 + 115546930
3 ? 0x022e4095 0 + 36585621
4 ? 0x022e3f52 0 + 36585298

Thread 3 crashed with X86 Thread State (32-bit):
eax: 0xffffffff ebx: 0x13a7c165 ecx: 0x00000000 edx: 0x00000000
edi: 0x13833f50 esi: 0x00000000 ebp: 0xb018da18 esp: 0xb018d9fc
ss: 0x0000001f efl: 0x00010286 eip: 0x022bbe70 cs: 0x00000017
ds: 0x0000001f es: 0x0000001f fs: 0x0000001f gs: 0x00000037
cr2: 0x00000000

Binary Images:
0x8fe00000 - 0x8fe298a3  dyld 0.0 (?) <d1092af4e89e77aa121dd5fb0c855cd9> /usr/lib/dyld
Author Update #3 @daoliverio 2009-05-26

Ok. I downloaded iPC 10.5.6 and i'm getting the "still waiting for root device" after . However, I grabbed the memtest application that comes with that dvd and ran the tests. The test came out fine. So, apparently, it's not my memory. I'm going to reinstall xXx with a different chipset driver and see how that works out…anybody got any ideas?

Author Update #4 @daoliverio 2009-05-28

OK, I got iPC 10.5.6 installed but still no luck with the programs. I installed with the voodoo kernel first and then did an install with the XNU Universal kernel and got the same error. Anybody got any ideas?

Author Update #5 @daoliverio 2009-05-30

I'm not sure, but could this be due to voodoo being 10.5.5 and the osx being 10.5.6?

Author Update #6 @daoliverio 2009-06-01

*BUMP*

Anybody? The voodoo kernel documentation says it is to be used with 10.5.5...I have iPC os x 10.5.6...although my system is 9.5 and my voodoo is 9.5.

Author Update #7 @daoliverio 2009-07-06

Ok...I just installed Win 7 RC and all programs work just fine...so...it's not a memory problem. Can anybody offer up a solution?

Synthesized Community Field Notes

1 technical responses curated from 9 original dispatches

Field Note #1 @Voyn1x 2009-05-24

Hmm it does sound like it's either your ram or related to the kernel. This reminds me of the 4gb+ ram bug but as you've only got 2gb, that shouldn't be the problem unless one stick has gone bad. Have you run any tests on the ram?

Also are you sure you installed the voodoo kernel? The AMD patcher shouldn't be needed when using this.

Enter in the terminal:

uname -a

This will tell the kernel version you are using.

Sources & Contributor Provenance (2 credited usernames · Thread #2959)
UsernameDossier ContributionDispatchesActive Window
@daoliverioPrimary Author82009-05-23 → 2009-07-06
@Voyn1xContributor12009-05-24