David, I went through similar scenario for couple months ,until finally finding a bad stick of (Memory-toGo) RAM. This would not show up under Apple hardware test nor did Apple authorized service ($185.00) find the problem. It wasn't until I pulled one RAM stick at a time and used my G5 for a day or so did I find the culprit. This was also after I reinstalled OSX,Logic and the 50 odd third party plugs I had installed, extremely time consuming! Also have you added any new software or hardware that may have brought this on or reconfiged any of the stuff you already had? Hope this helps and best of luck! Hayes

On Feb 26, 2007, at 2:13 PM, King Klang wrote: > I went through similar scenario for couple months ,until finally > finding a bad stick of (Memory-toGo) RAM. Same here: stable system, sudden crashes from out of no where. Tried everything, and 6 weeks later, someone suggested the same thing: remove ram 2X 2 and see what happens. Finally found the pair, and replaced. No more issues. The funny thing: the same 2 sticks work fine in my Windows machine. The Mac needs better ram I guess. George Leger III ________________________________________________________ http://www.myspace.com/georgelegeriii http://www.utopiaparkwaymusic.com Mac AND PC: The only way to fly 8-}

Thanks very much for your suggestion. Months ago, I bought some memory from ramjet.com, which is a specialty shop featuring memory for macs. Of course that doesn't mean you can't get a bad one. It would seem odd that it wouldn't fail until now, but I'll definitely try the experiment and see if removing the RAM makes a difference. To answer your question, it had been weeks since I altered the machine's configuration before the crash happened, however, I was working on the most RAM-intensive project I had ever worked on when it happened. I still can't guess why other apps don't crash, and why Logic always crashes, even when loading a blank project and no plug-ins. Anyway I really appreciate all the responses, and I'll post what I learn along the way. I sure like making music more than fixing computers! David

Well, at this point I don't think RAM is to blame. Here are the things I've tried so far: 1. Upgraded OS to 10.4.8 and Logic to 7.2.3. 2. Reinstalled Logic 7.2 from disc, then reupgraded from the net, trying it at each stage. 3. Removed half the RAM, then the other half. 4. Started Logic with control key down to get audio out of the equation. 5. Moved all contents from Components folder to a temporary directory somewhere else. 6. Upgraded BFD, since it was there. (Note: the other Plug-In I have is Ivory, in case that matters.) 7. Started Logic by double-clicking on a near-empty project file, rather than just starting the app. In no case did the behavior ever change: it boots up normally, right up to the point where the arrange window is up there looking like it should. Then a dialog box appears indicating the crash. I've read the crash logs but I don't know what I'm looking at. Since the crash text is long, I've uploaded it to the web and anyone who knows how to interpret it can see it here: http://dt.prohosting.com/work/crash.txt I did do something new and different (for me) in between the last successful exit and the first failed startup, but I'm not sure it's relevant: I noticed my project was getting too big to fit on a DVD-R, so I right-clicked the project folder and started creating an archive (ZIP file). Logic was *not* running at the time, though I think ITunes was, and it was playing a file imported from the Logic project in question. Anyway the progress indicator made it look like it was going to take a long time to make the archive, so I clicked the (X) to abandon the task for the time being. Logic hasn't run since. So, are there any good clues here? I'm puzzled. The machine otherwise seems healthy as can be, getting through multiple download/upgrade cycles flawlessly. David

--- In logic-users@yahoogroups.com, "David B. Thomas" <dt@...> wrote: > > Well, at this point I don't think RAM is to blame. Here are the things I've tried so far: > > 1. Upgraded OS to 10.4.8 and Logic to 7.2.3. > 2. Reinstalled Logic 7.2 from disc, then reupgraded from the net, trying it at each stage. > 3. Removed half the RAM, then the other half. > 4. Started Logic with control key down to get audio out of the equation. > 5. Moved all contents from Components folder to a temporary directory somewhere else. > 6. Upgraded BFD, since it was there. (Note: the other Plug-In I have is Ivory, in case that > matters.) > 7. Started Logic by double-clicking on a near-empty project file, rather than just starting > the app. Hi David, does Logic crash before, during or after it loads the project manager. Yesterday I had big problems loading logic (crashed at arrange page continuously) so I did some testing and found that if I forced logic to create a new project manager folder + contents (by dragging the old one to the desktop) it booted fine. The Project manager database folder is called 'PM Data' and is located in; users>'yourusername'>library>preferences>Logic. If this doesn't help you can always move the folder back again to restore the previous settings, Hope this helps, Mike P.S the project manager status bar appears (for me on my G4 1.5 PB) after the logic boot screen and immediately after the arrange page appears. It is a database of files used within logic and what helps logic to keep track of the contents of a song.

mt100uk (Mike) said: > does Logic crash before, during or after it loads the project manager. [...] 'PM Data' [...] Excellent tip!! After it started behaving, I went back and substituted the files one at a time. The actual naughty one ended up being PM Data/LogicProject7, weighing in at about 1MB. So, what, if anything, is likely to go wrong now that I'll be using a new LogicProject7 file? By the way, did it help that I reported that the program appeared to have started completely before the error appeared ... i.e. did that make you think of the project manager? Thank you *so* much! Now I can get back to the music. David

Hi Dave, --- In logic-users@yahoogroups.com, "David B. Thomas" <dt@...> wrote: > > > mt100uk (Mike) said: > > does Logic crash before, during or after it loads the project manager. [...] 'PM Data' [...] > > Excellent tip!! After it started behaving, I went back and substituted the files one at a time. > The actual naughty one ended up being PM Data/LogicProject7, weighing in at about 1MB. > > So, what, if anything, is likely to go wrong now that I'll be using a new LogicProject7 file? > Glad to help. This file holds data about file positions etc., so destroying it (or removing it) shouldn't have any devastating effects. You may need to go to the project manager window and get it to re-scan your hard drives (window menu) Functions>scan. The downside is that this can take some time for larger systems. Although it does run as a 'background task' ie you can do other things in logic while its doing this, on my PB it makes tracking impossible! maybe do it before you leave the studio tonight. > By the way, did it help that I reported that the program appeared to have started completely > before the error appeared ... i.e. did that make you think of the project manager? Yes! The first time i saw this problem was only a few days ago, and at first i was somewhat confused. Normally if logic (on startup) is going to crash it'll do it on either 'starting core audio' or when it loads preferences, ie when its showing its splash screen. Mike