Welcome to the MacNN Forums.

form.aat · 10:48 AM

Hi all

I�ve encountered an extremely weird unsettling problem: When logging onto the internet via modem, I got, for the second time in 2 weeks, a black screen with the following text SCROLLING down on the screen:

Exception state (SV=0x00336230)
PC= (here comes a row of figures like the one above) MSR= (another row of figures) DAR= (another row of figures) LR= (row of figures) R1= (row of figures) XCP= (row of figures) (Unknown code) <-- these words appear at the end of this line

Backtrace:
backtrace teminated unaligned frame access: 0x003362B8

Does anybody have seen this before? How can I avoid it and what is it? I�m on a 867 Mhz TiBook with 768 RAM, OS X.3.5, Motu 828 audio interface.

Thanks for you help
Form.aat

Catfish_Man · Sep 22, 2004, 11:40 AM

It's a kernel panic, which I guess one could describe as roughly the OSX equivalent to the windows blue screen o' death. Try googling for kpdecode, and see if you can run that and post the results here.

Millennium · Sep 22, 2004, 11:58 AM

That's a kernel panic all right, but something is strange: OSX hasn't displayed kernel panics like this since 10.2 Jaguar.

What version of OSX are you using?

Niakoro · Sep 22, 2004, 12:18 PM

New RAM lately? I ask becasue the only time I've seen the black scrolling screen was when I had a bad stick of RAM...

If you have installed new RAM, look for Rember or memtest on Macupdate, or run the Main Memeory test in TechTool Pro 4 if you've got it. If you see "FAILURE" then you have some bad RAM...

Another method is to try to boot from your hardware test CD that should have come with your Mac. If you've got bad RAM, it will fail to load properly.

form.aat · Sep 23, 2004, 02:44 AM

Thanks for your replies.

To answer your questions, I have OS X.3.5 installed and the only time I put some RAM is was when I bought it in January 2003. That's all. I'm scared stiff because I use the machine for playing music live on stage with Ableton Live, and wouldn't want to see this behaviour during my set.

OK, I will run the hardware test from my CD, and will run kpdecode and post results. So far, I think this has happened twice while connecting to the internet via modem, if I remember correctly. Could the modem be simply broke? That would then be the third repair to be necessary for a year-old laptop after a broken power adaptor and the broken-off monitor. I just switched from Windows and am not too pleased.

form.aat · Sep 25, 2004, 04:03 AM

Ok this is what kpdecode found, hope this says anything to some of you. The problem hasn't reoccured so far, I'm playing live tonight so I won't change anything until then; here's the report:

Last login: Sat Sep 25 11:00:02 on ttyp1
/Volumes/kpdecode-0.1/kpdecode; exit
-bash-2.05b$ /Volumes/kpdecode-0.1/kpdecode; exit
No logfile specified. Trying /Library/Logs/panic.log
Creating stack map... loading modules and nametables... sh: line 1: nm: command not found
sh: line 1: c++filt: command not found
sh: line 1: nm: command not found
sh: line 1: c++filt: command not found
sh: line 1: nm: command not found
sh: line 1: c++filt: command not found
sh: line 1: nm: command not found
sh: line 1: c++filt: command not found
sh: line 1: nm: command not found
sh: line 1: c++filt: command not found
sh: line 1: nm: command not found
sh: line 1: c++filt: command not found
Could not find loadable module with signature "com.apple.iokit.IOPCIFamily".
logout
[Prozess beendet]

This seems to suggest that nothing can be found, but really I don't have a clue.... many thanks in advance!

form.aat

form.aat · Sep 25, 2004, 04:36 AM

One more thing. This is what the Console file in Library/Logs says:

Sat May 22 11:46:21 2004

Unresolved kernel trap(cpu 0): 0x200 - Machine check DAR=0x0000000002A8A000 PC=0x000000000062793C
Latest crash info for cpu 0:
Exception state (sv=0x1FCEBC80)
PC=0x0062793C; MSR=0x00149030; DAR=0x02A8A000; DSISR=0x42000000; LR=0x00622D4C; R1=0x11FABC20; XCP=0x00000008 (0x200 - Machine check)
Backtrace:
0x015FB340 0x00622D4C 0x00419328 0x004191E8 0x204B472C 0x204B3C30 0x00035590 0x00035470
Kernel loadable modules in backtrace (with dependencies):
com.motu.driver.FireWireAudio(1.0.7)@0x204a6000
dependency: com.apple.iokit.IOAudioFamily(1.4.4b1)@0x554000
dependency: com.apple.iokit.IOFireWireFamily(1.7.2)@0x414000
com.apple.driver.AppleFWOHCI(2.1.3)@0x61e000
dependency: com.apple.iokit.IOPCIFamily(1.4)@0x484000
dependency: com.apple.iokit.IOFireWireFamily(1.7.2)@0x414000
com.apple.iokit.IOFireWireFamily(1.7.2)@0x414000
Proceeding back via exception chain:
Exception state (sv=0x1FCEBC80)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x20128500)
PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)

Kernel version:
Darwin Kernel Version 7.3.0:
Fri Mar 5 14:22:55 PST 2004; root:xnu/xnu-517.3.15.obj~4/RELEASE_PPC

panic(cpu 0): 0x200 - Machine check
Latest stack backtrace for cpu 0:
Backtrace:
0x000834B8 0x0008399C 0x0001EDA4 0x000909C0 0x00093C8C
Proceeding back via exception chain:
Exception state (sv=0x1FCEBC80)
PC=0x0062793C; MSR=0x00149030; DAR=0x02A8A000; DSISR=0x42000000; LR=0x00622D4C; R1=0x11FABC20; XCP=0x00000008 (0x200 - Machine check)
Backtrace:
0x015FB340 0x00622D4C 0x00419328 0x004191E8 0x204B472C 0x204B3C30 0x00035590 0x00035470
Kernel loadable modules in backtrace (with dependencies):
com.motu.driver.FireWireAudio(1.0.7)@0x204a6000
dependency: com.apple.iokit.IOAudioFamily(1.4.4b1)@0x554000
dependency: com.apple.iokit.IOFireWireFamily(1.7.2)@0x414000
com.apple.driver.AppleFWOHCI(2.1.3)@0x61e000
dependency: com.apple.iokit.IOPCIFamily(1.4)@0x484000
dependency: com.apple.iokit.IOFireWireFamily(1.7.2)@0x414000
com.apple.iokit.IOFireWireFamily(1.7.2)@0x0
*********

Wed Aug 11 15:55:04 2004

Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x0000000000000150 PC=0x00000000002502C0
Latest crash info for cpu 0:
Exception state (sv=0x00922C80)
PC=0x002502C0; MSR=0x00009030; DAR=0x00000150; DSISR=0x40000000; LR=0x00250288; R1=0x12143970; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x00250288 0x00251168 0x0024CA08 0x0024C870 0x005116D4 0x006E465C 0x006E43A0 0x00250914
0x002506EC 0x00251168 0x002517DC 0x00241994 0x00241958
Kernel loadable modules in backtrace (with dependencies):
com.apple.driver.AppleUSBComposite(2.0.5)@0x6e3000
dependency: com.apple.iokit.IOUSBFamily(2.0.8)@0x502000
com.apple.iokit.IOUSBFamily(2.0.8)@0x502000
Proceeding back via exception chain:
Exception state (sv=0x00922C80)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x201D3500)
PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)

Kernel version:
Darwin Kernel Version 7.3.0:
Fri Mar 5 14:22:55 PST 2004; root:xnu/xnu-517.3.15.obj~4/RELEASE_PPC

panic(cpu 0): 0x300 - Data access
Latest stack backtrace for cpu 0:
Backtrace:
0x000834B8 0x0008399C 0x0001EDA4 0x000909C0 0x00093C8C
Proceeding back via exception chain:
Exception state (sv=0x00922C80)
PC=0x002502C0; MSR=0x00009030; DAR=0x00000150; DSISR=0x40000000; LR=0x00250288; R1=0x12143970; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x00250288 0x00251168 0x0024CA08 0x0024C870 0x005116D4 0x006E465C 0x006E43A0 0x00250914
0x002506EC 0x00251168 0x002517DC 0x00241994 0x00241958
Kernel loadable modules in backtrace (with dependencies):
com.apple.driver.AppleUSBComposite(2.0.5)@0x6e3000
dependency: com.apple.iokit.IOUSBFamily(2.0.8)@0x502000
com.apple.iokit.IOUSBFamily(2.0.8)@0x502000
Exception state (sv=0x201D3500)
PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)

Kernel version:
Darwin Kernel Version 7.3.0:
Fri Mar 5 14:22:55 PST 2004; root:xnu/xnu-517.3.15.obj~4/RELEASE_PPC

*********

Help much appreciated!

Catfish_Man · Sep 25, 2004, 11:56 AM

Originally posted by form.aat:
One more thing. This is what the Console file in Library/Logs says:

Sat May 22 11:46:21 2004

Unresolved kernel trap(cpu 0): 0x200 - Machine check DAR=0x0000000002A8A000 PC=0x000000000062793C
Latest crash info for cpu 0:
Exception state (sv=0x1FCEBC80)
PC=0x0062793C; MSR=0x00149030; DAR=0x02A8A000; DSISR=0x42000000; LR=0x00622D4C; R1=0x11FABC20; XCP=0x00000008 (0x200 - Machine check)
Backtrace:
0x015FB340 0x00622D4C 0x00419328 0x004191E8 0x204B472C 0x204B3C30 0x00035590 0x00035470
Kernel loadable modules in backtrace (with dependencies):
com.motu.driver.FireWireAudio(1.0.7)@0x204a6000
dependency: com.apple.iokit.IOAudioFamily(1.4.4b1)@0x554000
dependency: com.apple.iokit.IOFireWireFamily(1.7.2)@0x414000
com.apple.driver.AppleFWOHCI(2.1.3)@0x61e000
dependency: com.apple.iokit.IOPCIFamily(1.4)@0x484000
dependency: com.apple.iokit.IOFireWireFamily(1.7.2)@0x414000
com.apple.iokit.IOFireWireFamily(1.7.2)@0x414000
Proceeding back via exception chain:
Exception state (sv=0x1FCEBC80)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x20128500)
PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)

Kernel version:
Darwin Kernel Version 7.3.0:
Fri Mar 5 14:22:55 PST 2004; root:xnu/xnu-517.3.15.obj~4/RELEASE_PPC

panic(cpu 0): 0x200 - Machine check
Latest stack backtrace for cpu 0:
Backtrace:
0x000834B8 0x0008399C 0x0001EDA4 0x000909C0 0x00093C8C
Proceeding back via exception chain:
Exception state (sv=0x1FCEBC80)
PC=0x0062793C; MSR=0x00149030; DAR=0x02A8A000; DSISR=0x42000000; LR=0x00622D4C; R1=0x11FABC20; XCP=0x00000008 (0x200 - Machine check)
Backtrace:
0x015FB340 0x00622D4C 0x00419328 0x004191E8 0x204B472C 0x204B3C30 0x00035590 0x00035470
Kernel loadable modules in backtrace (with dependencies):
com.motu.driver.FireWireAudio(1.0.7)@0x204a6000
dependency: com.apple.iokit.IOAudioFamily(1.4.4b1)@0x554000
dependency: com.apple.iokit.IOFireWireFamily(1.7.2)@0x414000
com.apple.driver.AppleFWOHCI(2.1.3)@0x61e000
dependency: com.apple.iokit.IOPCIFamily(1.4)@0x484000
dependency: com.apple.iokit.IOFireWireFamily(1.7.2)@0x414000
com.apple.iokit.IOFireWireFamily(1.7.2)@0x0
*********

Wed Aug 11 15:55:04 2004

Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x0000000000000150 PC=0x00000000002502C0
Latest crash info for cpu 0:
Exception state (sv=0x00922C80)
PC=0x002502C0; MSR=0x00009030; DAR=0x00000150; DSISR=0x40000000; LR=0x00250288; R1=0x12143970; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x00250288 0x00251168 0x0024CA08 0x0024C870 0x005116D4 0x006E465C 0x006E43A0 0x00250914
0x002506EC 0x00251168 0x002517DC 0x00241994 0x00241958
Kernel loadable modules in backtrace (with dependencies):
com.apple.driver.AppleUSBComposite(2.0.5)@0x6e3000
dependency: com.apple.iokit.IOUSBFamily(2.0.8)@0x502000
com.apple.iokit.IOUSBFamily(2.0.8)@0x502000
Proceeding back via exception chain:
Exception state (sv=0x00922C80)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x201D3500)
PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)

Kernel version:
Darwin Kernel Version 7.3.0:
Fri Mar 5 14:22:55 PST 2004; root:xnu/xnu-517.3.15.obj~4/RELEASE_PPC

panic(cpu 0): 0x300 - Data access
Latest stack backtrace for cpu 0:
Backtrace:
0x000834B8 0x0008399C 0x0001EDA4 0x000909C0 0x00093C8C
Proceeding back via exception chain:
Exception state (sv=0x00922C80)
PC=0x002502C0; MSR=0x00009030; DAR=0x00000150; DSISR=0x40000000; LR=0x00250288; R1=0x12143970; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x00250288 0x00251168 0x0024CA08 0x0024C870 0x005116D4 0x006E465C 0x006E43A0 0x00250914
0x002506EC 0x00251168 0x002517DC 0x00241994 0x00241958
Kernel loadable modules in backtrace (with dependencies):
com.apple.driver.AppleUSBComposite(2.0.5)@0x6e3000
dependency: com.apple.iokit.IOUSBFamily(2.0.8)@0x502000
com.apple.iokit.IOUSBFamily(2.0.8)@0x502000
Exception state (sv=0x201D3500)
PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)

Kernel version:
Darwin Kernel Version 7.3.0:
Fri Mar 5 14:22:55 PST 2004; root:xnu/xnu-517.3.15.obj~4/RELEASE_PPC

*********

Help much appreciated!

Well... all of those are firewire or USB related. Got anything odd plugged in related to that?

form.aat · Sep 25, 2004, 07:06 PM

Well FW and USB-wise, I have:

MOtu 828 Firewire audio interface
FW hard drive, 120 GB
USB hub (make: Typhoon)
mouse
XS Key (Logic authorisation)
usb stick
Midiman Oxygene keyboard controller

--- that's about it. could it be to do with any of these? They all seem to do their job.

form.aat

Turnpike · Sep 26, 2004, 03:10 AM

Originally posted by Millennium:
That's a kernel panic all right, but something is strange: OSX hasn't displayed kernel panics like this since 10.2 Jaguar.

I've received these under 10.3.5 as well. RAM/motherboard related.

sounds to me like a bad modem if it only happens when connecting via modem... perhaps the USB/FW things in the console log are actually more generalized I/O messages with cryptic names, or perhaps there is some I/O conflict caused by one of your devices when the modem looks for instructions?

Good luck with it... don't be too worried about things going wrong at a critical time... as long as you avoid making a modem connection during a show, you should be cool.

msuper69 · Sep 26, 2004, 07:35 AM

Might I suggest you have a backup system just in case your primary Mac goes belly-up during a live show? This would seem prudent even if you weren't having this particular problem. I'm sure you have backup amps and such so an important piece of equipment like your Mac should also have a backup. Just in case.

I would hate to think how horrible it would be to have a live performance crap out and not be able to get things going again.

Good luck!

Millennium · Sep 26, 2004, 11:36 AM

Originally posted by Turnpike:
I've received these under 10.3.5 as well. RAM/motherboard related.

I have too; it was on 10.2.8, but it was a TiBook not unlike the one the original poster is using (though mine is an earlier model). Don't get me wrong; I'm not denying that they happen. I should have been more clear in my wording, however. They shouldn't happen. They do seem to be happenning with these older-model TiBooks. I had missed the fact that he was using a TiBook before, though.

A question for the poster: how old is your machine? The TiBooks I've seen with this issue -including my own- all seem to have died around 30 months (two years and four months) from their original purchase. I'm beginning to wonder if this phenomenon isn't caused by some bad part which only has a lifetime of about that long.

form.aat · 02:30 PM

Originally posted by Millennium:
I have too; it was on 10.2.8, but it was a TiBook not unlike the one the original poster is using (though mine is an earlier model). Don't get me wrong; I'm not denying that they happen. I should have been more clear in my wording, however. They shouldn't happen. They do seem to be happenning with these older-model TiBooks. I had missed the fact that he was using a TiBook before, though.

A question for the poster: how old is your machine? The TiBooks I've seen with this issue -including my own- all seem to have died around 30 months (two years and four months) from their original purchase. I'm beginning to wonder if this phenomenon isn't caused by some bad part which only has a lifetime of about that long.

Now this is frightening... bought mine in January 2003, it's a 867Mhz ti with 768 RAM. What happened to yours? Did you have to throw it away or was it just a re-install?
Please let me know.

{edit} sometimes my PB refuses to connect via mode, saying there's a modem error, but I always attributed it to server-provider problems or my old cable...

Xeo · Sep 26, 2004, 02:02 PM

I apologize for hijacking, but I'm having panics recently too on my B&W G3 running OS X Server 10.3.

Code:
Sun Sep 12 00:19:02 2004:
        Backtrace 1:
                0x0020b1f4: _kevent
                0x002452b4: _unix_syscall
                0x00094200: _shandler
                0x7fffffff: _libsa_builder
        Backtrace 2:
                0x000836e4: _print_backtrace
                0x00083bc8: _Debugger
                0x0001eda4: _panic
                0x00090c60: _trap
                0x0009406c: _thandler
        Backtrace 3:
                0x0020b1f4: _kevent
                0x002452b4: _unix_syscall
                0x00094200: _shandler
                0x7fffffff: _libsa_builder

Thu Sep 23 00:33:38 2004:
        Backtrace 1:
                0x0020b1f4: _kevent
                0x002452b4: _unix_syscall
                0x00094200: _shandler
                0x79db64ff: _libsa_builder
        Backtrace 2:
                0x000836e4: _print_backtrace
                0x00083bc8: _Debugger
                0x0001eda4: _panic
                0x00090c60: _trap
                0x0009406c: _thandler
        Backtrace 3:
                0x0020b1f4: _kevent
                0x002452b4: _unix_syscall
                0x00094200: _shandler
                0x79db64ff: _libsa_builder

Fri Sep 24 10:08:59 2004:
        Backtrace 1:
                0x0002b144: _thread_invoke
                0x0020b1f4: _kevent
                0x002452b4: _unix_syscall
                0x00094200: _shandler
                0x7fff7fff: _libsa_builder
        Backtrace 2:
                0x000836e4: _print_backtrace
                0x00083bc8: _Debugger
                0x0001eda4: _panic
                0x00090c60: _trap
                0x0009406c: _thandler
        Backtrace 3:
                0x0002b144: _thread_invoke
                0x0020b1f4: _kevent
                0x002452b4: _unix_syscall
                0x00094200: _shandler
                0x7fff7fff: _libsa_builder

Sun Sep 26 13:49:00 2004:
        Backtrace 1:
                0x0011c294: _tcp_mssopt
                0x0020b1f4: _kevent
                0x002452b4: _unix_syscall
                0x00094200: _shandler
                0x7fff7fff: _libsa_builder
        Backtrace 2:
                0x000836e4: _print_backtrace
                0x00083bc8: _Debugger
                0x0001eda4: _panic
                0x00090c60: _trap
                0x0009406c: _thandler
        Backtrace 3:
                0x0011c294: _tcp_mssopt
                0x0020b1f4: _kevent
                0x002452b4: _unix_syscall
                0x00094200: _shandler
                0x7fff7fff: _libsa_builder

Can anyone tell me what these are related to?

form.aat · Oct 21, 2004, 02:08 AM

Originally posted by Millennium:
I have too; it was on 10.2.8, but it was a TiBook not unlike the one the original poster is using (though mine is an earlier model). Don't get me wrong; I'm not denying that they happen. I should have been more clear in my wording, however. They shouldn't happen. They do seem to be happenning with these older-model TiBooks. I had missed the fact that he was using a TiBook before, though.

A question for the poster: how old is your machine? The TiBooks I've seen with this issue -including my own- all seem to have died around 30 months (two years and four months) from their original purchase. I'm beginning to wonder if this phenomenon isn't caused by some bad part which only has a lifetime of about that long.

I would like to bump this and ask again: What exactly happened?

theolein · Oct 21, 2004, 09:32 AM

Originally posted by Xeo:
I apologize for hijacking, but I'm having panics recently too on my B&W G3 running OS X Server 10.3.

Code:
Sun Sep 12 00:19:02 2004: Backtrace 1: 0x0020b1f4: _kevent 0x002452b4: _unix_syscall 0x00094200: _shandler 0x7fffffff: _libsa_builder Backtrace 2: 0x000836e4: _print_backtrace 0x00083bc8: _Debugger 0x0001eda4: _panic 0x00090c60: _trap 0x0009406c: _thandler Backtrace 3: 0x0020b1f4: _kevent 0x002452b4: _unix_syscall 0x00094200: _shandler 0x7fffffff: _libsa_builder Thu Sep 23 00:33:38 2004: Backtrace 1: 0x0020b1f4: _kevent 0x002452b4: _unix_syscall 0x00094200: _shandler 0x79db64ff: _libsa_builder Backtrace 2: 0x000836e4: _print_backtrace 0x00083bc8: _Debugger 0x0001eda4: _panic 0x00090c60: _trap 0x0009406c: _thandler Backtrace 3: 0x0020b1f4: _kevent 0x002452b4: _unix_syscall 0x00094200: _shandler 0x79db64ff: _libsa_builder Fri Sep 24 10:08:59 2004: Backtrace 1: 0x0002b144: _thread_invoke 0x0020b1f4: _kevent 0x002452b4: _unix_syscall 0x00094200: _shandler 0x7fff7fff: _libsa_builder Backtrace 2: 0x000836e4: _print_backtrace 0x00083bc8: _Debugger 0x0001eda4: _panic 0x00090c60: _trap 0x0009406c: _thandler Backtrace 3: 0x0002b144: _thread_invoke 0x0020b1f4: _kevent 0x002452b4: _unix_syscall 0x00094200: _shandler 0x7fff7fff: _libsa_builder Sun Sep 26 13:49:00 2004: Backtrace 1: 0x0011c294: _tcp_mssopt 0x0020b1f4: _kevent 0x002452b4: _unix_syscall 0x00094200: _shandler 0x7fff7fff: _libsa_builder Backtrace 2: 0x000836e4: _print_backtrace 0x00083bc8: _Debugger 0x0001eda4: _panic 0x00090c60: _trap 0x0009406c: _thandler Backtrace 3: 0x0011c294: _tcp_mssopt 0x0020b1f4: _kevent 0x002452b4: _unix_syscall 0x00094200: _shandler 0x7fff7fff: _libsa_builder

Can anyone tell me what these are related to?

The last one looks like it's related to a network problem. Perhaps a network device driver?

theolein · Oct 21, 2004, 09:35 AM

Originally posted by form.aat:
Well FW and USB-wise, I have:

MOtu 828 Firewire audio interface
FW hard drive, 120 GB
USB hub (make: Typhoon)
mouse
XS Key (Logic authorisation)
usb stick
Midiman Oxygene keyboard controller

--- that's about it. could it be to do with any of these? They all seem to do their job.

form.aat

The problem is probably a device driver (sorry for being pedantic). My gues would be either the MOTu, the XS key, the usb stick or the Midiman. If you can try uninstalling those devices and reinstalling all those devices one by one. Before you do that however, make sure you have the newest drivers and/or firmware updates from the manufacturers sites.

form.aat · Oct 21, 2004, 10:00 AM

Ok thanks, I'll try that --- the weird thing is that the modem sometimes doesn't work (quite often actually...) when I want to connect to the internet (it says Modem error...) .... so could it be faulty? considering that this kernel panic occurred when I tried to log on while sound was running

Millennium · Oct 21, 2004, 10:28 AM

Originally posted by form.aat:
Now this is frightening... bought mine in January 2003, it's a 867Mhz ti with 768 RAM. What happened to yours? Did you have to throw it away or was it just a re-install?
Please let me know.

Target Disk Mode still worked, so I backed up everything and attempted a format/reinstall. This failed, however.

I haven't thrown the machine away yet, because I plan to take it into a repair shop and see what they can do with it. It's still possible that the machine might be able to be repaired. However, I'm not entirely sure how well that will go.

form.aat · Oct 21, 2004, 11:17 AM

Originally posted by Millennium:
Target Disk Mode still worked, so I backed up everything and attempted a format/reinstall. This failed, however.

I haven't thrown the machine away yet, because I plan to take it into a repair shop and see what they can do with it. It's still possible that the machine might be able to be repaired. However, I'm not entirely sure how well that will go.

This sounds scary.... :-(

theolein · Oct 21, 2004, 12:14 PM

Originally posted by form.aat:
Ok thanks, I'll try that --- the weird thing is that the modem sometimes doesn't work (quite often actually...) when I want to connect to the internet (it says Modem error...) .... so could it be faulty? considering that this kernel panic occurred when I tried to log on while sound was running

If it's a consolation, I had, until three weeks ago, a TiBook 667Mhz. It was the original November 2001 667, i.e. the VGA one, not the DVI one, which came later, and it worked absolutely fantastically for the one and a half years I had it. I never had one single crash through jaguar and Panther.There's no guarantee that older TiBooks will have problems.

The problems you have might well be related to your modem, either the hardware itself, or the driver. If it only happens when sound is running, then the problem probably lies with the sound software or one of your drivers. If you hadn't changed anything or installed any new software or hardware and the problem started happening it could be that one of the hardware devices is no longer working. I would try logging onto the net without any of your sound devices attached or software running and then see if still crashes. If it does then it might well be the modem. If you can't get it repaired you could still simply deactivate the device and use a PC card modem, for instance, or use this opportunity to get ADSL or cable.

Millennium · Oct 21, 2004, 01:07 PM

Originally posted by theolein:
If it's a consolation, I had, until three weeks ago, a TiBook 667Mhz. It was the original November 2001 667, i.e. the VGA one, not the DVI one, which came later, and it worked absolutely fantastically for the one and a half years I had it. I never had one single crash through jaguar and Panther.There's no guarantee that older TiBooks will have problems.

Why did you get rid of the machine? I note that it would have been about 30 months old; the same age my machine was when it died.

Person Man · Oct 21, 2004, 01:22 PM

The modem in the machine is actually USB based (it's like that in Power Macs as well as PowerBooks)... so it could be the modem itself, or it could be 10.3.5, as I remember reading somewhere that 10.3.5 broke modem connectivity on PowerBooks... can't remember where I saw it, though.