25839 Views Previous 1 … 8 9 10 11 12 … Next 386 Replies Latest reply: May 11, 2007 7:54 AM by Talmage Cooley Go to original post
I like AMD too, but I'm not sure where the Intel hate is coming from.
As far as I know, the farthest that anyone has narrowed it down to is the logic board (and that's still a theory), and there's quite a few components on there -- really not enough evidence to point the finger at any specific set of manufacturers just yet.
I'd hardly call my post as Intel hatred, and I never pointed the finger at them in regards to who was to blame with my broken laptop. I said (or meant) that it was clear that the problems with the MBP is hardware related... whether it is the logic board, airport card, memory, or any combination there of... it is clear that something is amiss.
As far as AMD goes? I just prefer them. Does that mean I think Intel stinks? No... If I did I wouldn't have bought this lappy.
Thanks for playing though.
Thanks for this posting guys. It has been very helpful. I didn't even bother wasting my time trying to troubleshoot my 3 day old MBP. I brought it to the Apple Store immediatly and it was declared DOA on the spot for a return/refund. Unfortunately I couldn't do a straight exchange since it was a custom online order. Hopefully the next MBP I get will not have the same issue.
I get my replacement very soon tracking says its in NJ and I live East Coast and all that so .... man I am crossing my fingers.
Going to sound whiney but it should not be like this. Instead of happy to get my computer back I am nervous as **** wondering if I am going to get the same issue again.
Outside of the panics this was the best experience I ever had on a personal computer.
I am ready to get my mac back.
Well, AppleCare has been great - so far as being as helpful as they can be, they are much better than any other support service that I've ever used, but on solving the problem...they just haven't done it yet. Bringing in my MBP didn't help because my local store is NOT a Apple Store proper, just an authorized retailer/repairer, so they could not get it declared DOA. They said to bring it in for some more diagnostics on Monday, but I think I'm going to spend some more time with AppleCare and see that they won't just declare it over the phone. I really don't want to deal with exhaustive tests and repairs before turning mine in. We'll see...
I got my MBP 15" this past Thursday, from Shanghai. It's nice and quiet, not too hot, but from day one, I get the kernel panics after connecting via Airport to my network to grab files. In fact, after I get the files, other apps like iTunes, Mail, crash and won't open. Last night, I got a kernel panic when I tried to turn Airport off. I only got one the first day, probably one the second, and two yesterday. I've spoken to support three times, and they seem totally unaware that this is a problem, even though it's on their own site's discussion board. The two other guys were great but the guy today really wasn't, to the point that when I told him about this thread and some people's machines being declared DOA and replaced, he said mine couldn't be because it was a custom build. The only "customization" done, by them, I might add, is a glossy screen and an extra 512 ram. Is that correct, or do they just say what comes to mind without checking policy? I really love the machine otherwise and don't really want to be without one while I wait for a replacement, but I am wondering if it's just the Airport or some greater underlying problem that will eventually mean the whole thing stops working. I actually did a reinstall of the OS today, set the router (a linksys) to B only, and have decided not to transfer files wirelessly. Should I push the issue or be content is the big question I'm struggling with at the moment.
MacBook Pro 15" Mac OS X (10.4.6)
I am in the same place that you are...except for one thing: push the problem. I also bought my "customized" MBP online and have had the KP problem since day one. I've been on with AppleCare three times and today I reinstalled my OS to no avail. The problem only occurs with wireless - not Ethernet, and it is a hassle. We all paid well for our computers and I want all of our problems solved. It is the least that they can do to solve the problem, since we didn't cause it. I hope that if AppleCare continues to monitor this thread, all of our issues will be resolved. Don't give up!
This past weekend has been exceptionally bad for me with KP's.
This is a work computer and there is no way I can be without it for over a week. A couple days at max. I am holding out for some kind of soft fix for it. I guess they have me by the balls until we get an official statement and potential fix on the issue.
Thanks for they advice, I will push it but I'm still hoping it's somehow resolved itself because already me and the MBP have a bond :o) After the reinstall, I did a transfer of file , but I used ethernet. I then switched to airport and ran Safari, Mail, iTunes, and so far, no crash. I keep knocking on wood, because I truly love this MBP. It's almost too quiet (I'm wondering if there are fans in here) and doesn't run hot. But like I said, if it really is a logic board issue, and not Airport, I'm worried. I understand that it's a 14 day period in which to make the exchange, so I'm going to work this baby silly and see what happens. And I'll update as to what happens.
My experience was similar. I was using Netgear's latest MIMO Wireless G router via WEP/128 and all was well for several months... never saw a single kernel panic in OSX.
My Windows desktop PC on the other hand would kernel panic (STOP error / BSOD / IRQNOT_LESS_THAN_OREQUAL) and point at the netgear wireless card's driver...
Also, i couldn't get my wireless connection to work in the Windows half of my MacBook (via BootCamp). Hardwire LAN worked great, but wireless via WEP would never properly connect for some reason. Neither would my friend's Windows-only laptop (from Sager).
So about 3 or 4 days ago i switched over to WPA-PSK because i got tired of typing very long strings of gibberish in and i got tired of Windows not working with it (why, i dunno). All of a sudden, Windows started to work (hooray) but OSX began panicking over and over again, always while browsing the internet.
Took it to the Apple store and the Geniuses tortured it for an hour, tested the RAM, and generally couldn't get it to repro. Neither could I. I even re-installed OSX the night before and while it happened at home, it didn't happen at the store. They applied the Combo update over top of the Delta that i had installed and said that "might" have fixed it.
I figured maybe my Netgear access point was throwing junk data (considering it often crashes my pure-Windows PC, too) or something, so i took an AirPort Express home with me just in case. Within 10 minutes of being home, the Mac kernel panicked again. So i swapped out the Netgear WAP for the AirPort and (fingers crossed, knock on wood) i haven't had a single KP since.
Of course, there has been one downside. For reasons i can't fathom, my Xbox 360 refuses to even detect the AirPort's SSID (which is in the same room only 5' away) so i now have to hard-wire my 360 to the internet (not really a big loss, Xbox Live! works better over a hardwired connection anyway. still, it's annoying and befuddling).
I just hope the Windows side of my MacBook will still work with the new AirPort WAP... and that the KPs don't return!
Thanks for this testimony, however I would never say that the case has been solved.
By essence, the MBP is portable, which means it needs to support other AP than Apple's Airport Express.
We cannot require every hotel, airport, Starbucks to use only AA.
One point also to notice is that even if the Netgear AP is sending garbage, OSX should never crash.
I just sent back my second 15" MacBook Pro due to kernel panics primarily downloading updates, accessing safari, or any application that connects to the internet (i.e. itunes)- I was pretty satisfied the first go around -Apple declared the computer DOA quickly and replaced it-- however the second go around was more than disappointing- to receive a second MBP right out of the box malfunction so much so that it is unusable was maddening and the response I got from Apple Care was hit and miss- mostly miss depending on who you spoke with- one product specialist dimissed the discussion on this forum and tried to help put my situation in a better perspective --using the analogy that my MBP had the "flu"- and that apple is trying to figure out what is causing this "flu"- needless to say I was surprised a representative would describe a brand new -fairly expensive computer as having the "flu"
I ran a data capture and sent the information to apple -I waited over a week and heard nothing back- followed up and was told the information was never sent to engineering but would be sent immediately - and apple would contact me in a few days- Not willing to wait another week and go beyond the 14 day return limit-- Apple did declare the second MBP DOA after initially saying the same thing-- that typically they do not refund custom built machines-
The first MPB was built week 21 and the second 22 --from China-
At this point I am satisfied with a refund and not willing to try a third computer- because at this point it doesn't seem that apple knows what the problem is or is even willing to admit there may one--
MacBook Pro Mac OS X (10.4.6)
MacBook Pro Mac OS X (10.4.6)