Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
if I go to a genius bar are they gonna be able to fix this?

am I supposed to just bring in my macpro? does the genius bar cost anything?

If you are under the one year warranty or have AppleCare beyond one year then Genius Bar is free. Who knows if they can fix it? Depends entirely on the problem.

Are you saying you had no issues between last June and now?
 
since I bought it I have thought it was running much slower than it should be (based on its specs)

When i first started this thread I was having crashing problems but they were not as frequent as what I am experiencing now and they seemed (if I recall correctly) to coincide with certain activities such as trying ti import video or render video or something from FCP but the crashing it is doing now is VERY frequent and I can find no rhyme or reason to when it is happening...sometimes when i am watching videos, sometimes when im looking at a webpage, sometimes when I am using iphoto...

Do they have some magic tool a the genius bar for testing RAM? I put in OWC ram when I bought the mac which could be the root cause of all this but havent been able to identify any of it as being bad...
 
The only foolproof way of detecting bad RAM is remove it. If the kernel panics stop, then you know. The other methods available sometimes detect it, but just as often do not.
 
So I swapped memory all over the place tonight.

ran just the 2x512 OEM sticks, just two of the OWC 1GB sticks, one set of OWC and the OEM, both pairs of OWC sticks and all of it together. Got this crashing problem every time, every which way. Sometimes it crashes while OSX is reloading after I powered off because of a crash (crash=panic).

Should I be bringing this to the genius bar tomorrow or am I just spending a bunch of time and energy to hear "you should re-install osx"?
 
here is what the panic log looks like now. Its not even logging everything. I just got that panic screen about 10 times in the past 5 minutes. Once, then while starting to boot, then a little farther into the boot process, then once osx was finished loading, then once after i used osx for 2 minutes etc etc...

I will also mention that I have always clicked the REPORT button when it comes back from a crash and I believe that is supposed to show you a report because when it has panicked for other reasons I have gotten a report (I recall this back in june/july) but I never get a report or any additional details when I click the "report" button after all these crashes in the past few days...not once.


panic.log:

Description: Panic (system crashes) log
Size: 11.05 KB
Last Modified: 10/22/07 1:24 AM
Location: /Library/Logs/panic.log
Recent Contents: ...


*********

Fri Jul 6 15:28:16 2007
panic(cpu 1 caller 0x009200CC): bad context (0x0_00ce0000, 0x0_11ea1000).
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x602fee34 : 0x128d08 (0x3cc0a4 0x602fee58 0x131de5 0x0)
0x602fee74 : 0x9200cc (0x922f28 0x0 0xce0000 0x0)
0x602feeb4 : 0x9200e5 (0x0 0x0 0x0 0x0)
0x602fef24 : 0x920386 (0x602fefb0 0x1 0x0 0x0)
0x602fef54 : 0x9206db (0x602fefb0 0x602fef88 0x0 0x0)
0x602fefa4 : 0x91d345 (0x602fefb0 0x18 0x0 0x1)
0x602fefb0 : 0x0 (0x1 0x0 0x1003b 0x0) Backtrace terminated-invalid frame pointer 0x18
Kernel loadable modules in backtrace (with dependencies):
com.parallels.kext.vmmain(2.2)@0x919000

Kernel version:
Darwin Kernel Version 8.10.1: Wed May 23 16:33:00 PDT 2007; root:xnu-792.22.5~1/RELEASE_I386


*********

Sun Aug 12 14:56:02 2007
Macaine-cieckc-chekabicapibiliiies 0x 0x000000000000000000:

*********

Sun Aug 12 20:11:40 2007
Maahine-cieck -caack cliabilies 0x
*********

Thu Aug 16 17:30:50 2007
Maahihene-hheck ak caiabiities es 0xx0000000000000006:
000000066 rror-reporting 6an r

*********

Sun Aug 19 11:50:40 2007
Machcni-chchekk caaapailitisties00x
*********

Mon Aug 20 21:11:39 2007
Maahine-cchin -checkcpabiiabiies 0ies 0x0000000000000000006:
00006:
6 6rror-r errtigr-reoanksting banks
MachMne-chchinecstaeus sta xs 0x00000000000000000000
macrsnt-rh cv inlir
gre s
MCA emror-repoachinn-chc k gnstregresssMA
*********

Sat Oct 20 20:43:52 2007
Maahine-cehin- capbeckcitie abiix
*********

Sun Oct 21 00:20:02 2007
Machinc-ih-ckeckpabilcaiep 0x
*********

Sun Oct 21 00:24:11 2007
Machihee-checiep 0xbabilities 0x0000000000000000006:
6 ererro--repporriig b san
s
MaMhinecchineck -tatu hekx
*********

Sun Oct 21 00:28:55 2007
Macainc-cee-chek capbapabislitie 0x
*********

Sun Oct 21 00:39:47 2007
Machchieheckchec abiltpabls 0xties 0x0000000000000000006: 0000006:
6 e errorrreprr-eingbrtigks
banks
MacMinechinecck tck stus ax
*********

Sun Oct 21 02:20:00 2007
Macine-checkceck aabiibiliiei 0xes 0x00000000000000006000
*********

Sun Oct 21 10:59:50 2007
Maahine-check na-chpbk cataeslt
*********

Sun Oct 21 11:04:06 2007
Maahici-chc-chekcapbapabiilitie ies xx0000000000000006:
000000000006:
e6ror-r rortnr-re briks
g banks
Machine-ce-chek stattstus 0x
*********

Sun Oct 21 14:52:09 2007
Machanechineck capbeckcitiepab litisx
*********

Sun Oct 21 15:06:09 2007
Macihnn-check ak cpbiliiilite 0x
*********

Sun Oct 21 15:51:44 2007
Machchichec -chcpabi cipaislitie 0x
*********

Sun Oct 21 16:27:02 2007
Machineineck cpck cpiliteilit 0xes 0x00000000000000000000:0000
:
6 e6ror eeportrng bon-s

*********

Sun Oct 21 16:29:06 2007
Machane-hneck-hapaik caaties0lities 0x00000000000000000600:
0
*********

Sun Oct 21 16:32:24 2007
Machinhinheck cpck cpiliteilite0x
*********

Sun Oct 21 16:39:16 2007
Maahici-chc-chekcapbapablitie ies xx
*********

Sun Oct 21 17:24:39 2007
Maahineccheck check capaaplaties 0bilities 0x0000000000000000000000: 0006: 6 e6ror-eerrrortnrepgrbanbs
anks
MacMine-hice-chcecks status0atusx0x00000000000000000000405

resta t IPmvacid
hin -chmach ne-hn eck rn pogregress
M
MCAAerrorereoortr-geregitortnrs:g reg sters:A32_MC IA02_MC0STATUS0STATUS(x401)1)0 0x
*********

Sun Oct 21 18:41:34 2007
Macaincichek-chekapaiapablties0ies x
*********

Sun Oct 21 19:10:37 2007
Machihene-c-ececk aipabitils 0xities 0x0000000000000000600000
0006:
6 err6r-reoerro-tin eporbinkg
banks
Machiechicheckestat-sh0x0ek00000sta00u0005s x0000000r00000stat4
P alhdn macciein phoc ress
proMressMA eCA error-rorprepotrtnng eregitistrs:
IA3 _MA32_0C
*********

Sun Oct 21 19:49:11 2007
Macnine-hcheck capabipabilieies x 0x000000000000000006:
0000006:
6 ererro-r-reportiogrtings
banks
Machnehin--cehecks statts 0x0000000000000000000000

*********

Mon Oct 22 00:22:40 2007
Maahich-nhec chec pablpabiiies 0ties 0x0000000000000000000006006:
*********

Mon Oct 22 00:23:46 2007
Maahine-cieckc-chekabiiapables 0ties 0x0000000000000000006
6:
6 eroor-erepotrtin g bnnks
s
MachiMe-chcine- staths 0xeck0st000s 0x
*********

Mon Oct 22 00:31:00 2007
Macainc-iheck a-chekbiltapabls 0xties 0x000000000000000060
000006:
6 err6r-re rrtigr-reoank
ing banks
Mahhinece-chcck s staaus 0tus 0x00000000000000000000
r4
start P vaiachi
m-chchenk ineprheckris poMgAreressoMCr- eporirrrg rgeporiters
registers

*********

Mon Oct 22 00:41:53 2007
Macaincheheckchec abiltpabls 0xties 0x00000000000000000000006:
0
*********

Mon Oct 22 00:49:41 2007
Maahiehin-heckceckcabiltabiis 0xies 0x00000000000000000600006:

*********

Mon Oct 22 00:53:26 2007
Maahinc-ceec hec pabiipables 0ties 0x000000000000000006:
006:
6 error-reporting banks
eporting banks
MachMne-chchkns-cths 0x0000status 0x00000000000000000 05mac ine-rseckatn IP galidr mscMine-chek er orin rrogeporti
MAregist rs:
ror-r portiIA 2eMC
*********

Mon Oct 22 01:00:51 2007
Machcnene-hhe k capaailitislit x
*********

Mon Oct 22 01:24:47 2007
Maahin-hin-eck aeckcbiliiabilts ies 0x0000000000000006:
0000000000000006:
6 error-6eporti erbankr-rep
rting banks
MachinM-chekchine htatu k stt00s 0x
*********
 
slug420 said:
Should I be bringing this to the genius bar tomorrow or am I just spending a bunch of time and energy to hear "you should re-install osx"?
Nobody here can possibly know if your issue is software or hardware related for sure.

Let me ask you this. Is there something stopping you from re-installing OS X? It's one thing proactive that you can do to at least rule out the possibility of a corrupt install.
 
Please don't try reinstalling OSX. Not only is this unlikely to help, it could make the situation worse. Chronic kernel panics are nearly always the result of hardware issues. Though RAM issues cannot be totally ruled out, it sounds like you've tried what you're able to test your RAM. You're pretty much out of options. I would take this Mac to an Apple store.
 
Thanks for the advice, I guess I will keep my appt tonight @ the apple store.

The only thing that was keeping me from just doing a re-install of osx is all the time involved. I have never installed osx and this is my first mac experience. So add to all the research I would do to make sure I am doing everything correctly the time it would take me to backup everything on my primary HD and then if I am re-installing I am probably going to want to install bootcamp as well so I would need to research how to get that to work and then im sure I would find myself tryingt o decide if I should just buy leopard or not since it comes with bootcamp built in and is updated etc etc......i just know what a can of worms re-installing the OS would/will be for me :)
 
Rule of thumb.

1. If you have problems put it back to its original configuration. If the original configuration fails. It is Apples problem and get them to fix it.

2. If there is a problem put each unit in one at a time until it causes the problem. Once you find the problem causing unit. take that one piece out and try the others.

3. Check for different combination of things that may cause the problem for example 5 gigs of RAM running a 32bit application...

Bad hardware happens even with top quality systems. There have been many times when I needed to return faulty Sun Servers (the ones that cost $100,000s of dollars) or high end Dells (back when Dell had good systems), HP, IBM... There is little margin of error in producing computers and not all components can be completely checked. While they are getting better at it they are not 100% Don't blame apple for you faulty system. But get them to fix it if you got it from them. Because that is why the warrantee is there. Chances are you replacement of fixed system will run fine for many years.
 
Rule of thumb.

1. If you have problems put it back to its original configuration. If the original configuration fails. It is Apples problem and get them to fix it.

2. If there is a problem put each unit in one at a time until it causes the problem. Once you find the problem causing unit. take that one piece out and try the others.

3. Check for different combination of things that may cause the problem for example 5 gigs of RAM running a 32bit application...

Is there some problem with running 32 bit applications with 5 gigs of RAM or are you just throwing that out there as a random example of a pattern I might be able to pick up on to help isolate the issue?
 
Of course backing up is advisable, whether you're having problems on not, but especially when you are.

The reinstall process isn't difficult, though it would be disruptive. The main reason I advised against it in your case is that if hardware is the issue, then the reinstall could fail, leaving your Mac unbootable. This would not be progress. ;)
 
hehe, agreed


I have most if not all of my important stuff backed up and by backed up I generally mean stored on two different physical disks though often in the same machine.

My main drive is just what I consider to be "operational" stuff. Recently downloaded files, installed applications settings etc....



If I go to the genius bar tonight should I take my extra hard drives out? I dont want to because I dont want to change the hardware ocnfiguration at all but at the same time I cant lose the data on them.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.