-
All replies
-
Helpful answers
first
Previous
Page
50
of 115
last
Next
-
Jun 23, 2010 9:55 AM in response to Kevin MacLeodby mgcharlie,Thanks for summarize the 3 kinds of freeze, Kevin. I think those are the main types. In 32 days of owning my macbook pro, I've experienced type 1 three or four times, type 2 two times and type 3 one time. Still hoping it's a software issue.
Everyone should report to apple:
http://www.apple.com/feedback/macbookpro.html -
Jun 23, 2010 3:51 PM in response to Artitronby monsterkruemel,We had my dad´s new mbp (i5, 2,4 GHz, 320 GB Hitachi) freeze too and i finally found the cause!
I noticed that the macbook would only freeze when i was logged in to my dad´s WLAN.
He runs a Speedport W 503 V Router.
The freeze would occur at no other time other then. I found out because when i was at my dad´s house my own (different) macbook pro would freeze too as soon as i was logged in to his WLAN.
Hope this will help. -
Jun 23, 2010 9:44 PM in response to Artitronby Darthob,So, I just sent this little rant to Apple via the "Crash Report"...
"I don't know what causes the problem, but the computer will freeze and be completely unresponsive. All I can hear is a repeated clicking sound that sounds like it's coming from my speakers. Whatever the problem is it is constant and frequent and soon, the bigger problem will be the $3000 computer I've ripped apart and lit on fire on my floor setting off my fire alarm. I'm serious. This thing is ******* me off but apparently if I want anything done about it I need to pay Apple an additional arm and leg(Thus leaving me limbless after buying this computer) to even get this thing looked at.
Now, I would like some sort of response from Apple just to make sure this report was actually received because I'm aware of how few companies actually look through these "Crash Reports". It reads "You will not be contacted in response to this report" which probably means you guys are just going to trash it upon receipt anyway and this entire rant is completely useless.. So what is the point of this problem report at all? Why does it exist? Is it to make us Mac users feel like you actually care? I mean, your protection plan is called "Apple Care" right? Does that mean "Apple Cares as long as you pay enough?". Don't get me wrong. I (used to) LOVE Macs and their support. I think they are great machines with a simple OS that makes life easier. However, lately a chain of stupid events has led me to nearly hate Apple. I literally convinced 7 people to step away from Windows and buy Macs because of how easy and enjoyable I found them to be. Now I am regretting that decision. Seriously, you would think Apple would try to make liking Macs easier, but with these prices and this tech support, all I can do is look at the computer, wonder where all that extra money is and try to imagine how deep Steve Job's pockets have grown.
On that note... Anyone know if Apple shares stock? I mean that way I could have invested my money wisely and bought the stock instead of investing my money into this computer that I have been trying to love for 2 years now. Atleast doing that would yield me something that isn't a $3000 fire. (Which is funny because this computer gets so hot pretty much all I need is to drop some twigs behind the vents and the fire'll pretty much start itself).
Oh well, here goes nothing. I won't be expecting that reply I'm asking for. ****, I'm not even expecting anyone to read this. $20 says no one does. I'm serious. I'll Paypal you the money right then and there if I hear back from any body.
BTW, I'm not contacting your Support line. I've spent too much time talking to your automated voice and spent too much time listening to the bad music that you blast. Seriously, trying to play this "Hip/Cool" music just makes mad callers more angry. And don't try to kid me, I know people calling your support lines aren't happy. They're probably pretty ****** at the fact that they are paying who knows how much just to TALK to someone, or the are ****** that they payed that much 3 years ago.
CHEERS! Hope I described the steps needed to trigger the problem appropriately.
- Sincerely, 12 year faithful Mac user gone Pyro."
All of that aside, my computer is crashing at least 4 times a day. Hard crashes. She just freezes up in all ways possible minus a clicking sound I hear coming from beneath the keyboard. Granted she is running a game + music + ventrilo + system preferences... but isn't that what the "Pro" is for in Macbook PRO?
I'm getting really sick of this.
What I am also sick of is Apple not offering any solutions or even a response to anything. I guess they are happy with taking your money and sending you on your way. I didn't go through all 50 pages of this thread, but can anyone who has tell me if Apple has acknowledged anyone here at all? -
Jun 24, 2010 12:36 AM in response to Darthobby rdbowden,You could alway email that response to directly to Steve Job's as he seem to be more responsive on emails these days -
Jun 24, 2010 12:58 AM in response to monsterkruemelby Espen Vestre,monsterkruemel wrote:
We had my dad´s new mbp (i5, 2,4 GHz, 320 GB Hitachi) freeze too and i finally found the cause!
I noticed that the macbook would only freeze when i was logged in to my dad´s WLAN.
He runs a Speedport W 503 V Router.
Hi! How long did these freezes last? Some weeks ago I noticed my i7 was hanging every time I was reconnecting to the WLAN at home, but that typically lasted for perhaps no more than 15 seconds. The problem disappeared after a reboot of the router (a TimeCapsule), but clearly, there may be something in the wireless driver of the new Intel chipsets that's locking up the kernel more than it really should be allowed to.
The graphic-freezes-for-several-minutes-while-computer-keeps-on-running problem that many in this thread have experienced is different though. On my machine it happened while on a wired network (and I'm almost certain that I had turned AirPort off). -
Jun 24, 2010 11:47 PM in response to Darthobby JK09,No offense, but this is a really dumb way to go about getting a problem solved. Assuming you're talking about a newer MBP, your unit should be under warranty, so no payment will be required for Apple to take a look at it.
Regardless, if you've read any of this thread, you'll see that, while people are frustrated with this issue, Apple has exchanged units quite liberally. Expecting to get your problem solved via a self-described "rant" in a crash report is beyond silly. Apple has a very well-regarded Customer Support unit. Try calling them -- without jumping into full-rant mode from the get-go. Good luck. -
Jun 25, 2010 2:03 AM in response to Espen Vestreby monsterkruemel,Hi! How long did these freezes last?
The freezes would not just last temporarily but permanently.
Only long pressing the power button would turn the MBP off but restarting would not solve the problem, the freezes came back almost immediately.
Sometimes we were able to move the cursor with the trackpad but the dock would not react an no keyboard shortcuts would work. The right-click on the trackpack would not work; instead of that the left-klick on the trackpad would result in a right-klick, so we were able to start programs by that workaround. I would not take long though before even that trick would not work anymore an everything was totally frozen.
I took the machine to my house a couple of days ago an since then it works just fine with no freezes at all.
My Router at home is a Vodafone DSL-EasyBox A-601. -
Jun 25, 2010 6:20 AM in response to Darthobby Rod Hagen,Darthob wrote:
So, I just sent this little rant to Apple ...
Sigh!
Which model of MBP do you have, what OS are you running when the problem occurs, what is the "game" you mention, and what steps have you taken to resolve the issue so far? If you really want to find an answer you will need to provide more specific information than you have so far.
You use phrases like "your" here as if you believe you are actually talking to Apple. You are not. You are simply posting in a user to user support board.
As far as Apple "not offering any solutions" goes, I'd suggest you take a look at http://www.apple.com/support/ where you will find many hundreds of "solutions" to a very wide range of problems. If you need help with finding material relevant to your own issue then post back with less rant and more description of your own problem and the circumstances in which it occurs and I'm sure we will be able to point you in the right direction.
Cheers
Rod -
-
Jun 25, 2010 9:45 AM in response to Artitronby SKEL_73,Just got off the phone with Applecare -
They said engineering is aware of the issue, is working on troubleshooting, and that they will likely issue a software update that will resolve the issue (don't know if that statement was based on reality, as the rep I spoke with was of course not an engineer himself and no intimately familiar with the issue)
At least we know they are acknowledging the issue and working on it. -
Jun 25, 2010 11:04 AM in response to Engenhartby Engenhart,Hello Everybody! For me the problem seemes to be solved! I got back my i7/17" mbp. In the progress of the installation of standard system by the installation dvd (10.6.3) I skipped the migration step. Then I installed the Mac OSX Update 10.6.4.
- When finished I migrated with the »Migration-Assistant« my old MBP 15" with 10.6.4.
- I updated the system again, and checked the Creative Suite for Updates
- I rebooted the system via DVD and repaired the harddisk via harddisk assistant.
Till now the MBP is fast and stable...
Yours,
Engenhart -
Jun 26, 2010 1:13 AM in response to Artitronby Darthob,Obviously the wall of text I wrote was on the sarcastic side. I was not expecting it to solve my problems... I think you took it just a tad bit too seriously. It was me venting more than anything. I've been having problems with a $3000 piece of equipment I purchased to be reliable. I am currently living in the middle of nowhere (the reason I wanted the reliable computer) and getting to "The nearest Mac store" is a pretty costly thing to do, especially if I'm not guaranteed that it's going to fix things.
About the Tech support... One morning, I had this repeated freezing problem + a problem where my airport randomly turned off and would not turn back on. I tried calling Apple but was told that they wouldn't have anyone there till 6a.m. PST ( I think it was, I can't remember exactly.) Well, I called back at that time only to get the same response telling me to call back at 6a.m. PST. I had to wait another hour and a half before there was someone alive on the other end of the phone to talk with and all she had to tell me was that I was going to have to pay up if I wanted any more assistance from Apple.
$3000 is a lot of money for a foreign college student. I thought I was buying a computer that could complete all the tasks I would require of it but that's not the case. There is something wrong when a $3000 computer isn't doing what it was built to do, and the company that sold it to you wants more money just to have it looked again. They won't give you a single hint as to how to fix it yourself unless you pay them more.
Now I've talked to the Apple employees tons. They are great people to talk to, I have no problem with them. They are simply following company policy, I know that. It's the company policy I have a problem with.
Sorry, I guess I'm still kinda irked at the whole situation because while typing this my airport decided to die again.
Looking at things technically:
- When the airport shuts off it goes off and when I try to turn it back on it is unresponsive. It doesn't look for any signals and freeze, it just stays off. The only way I've found to fix the problem is a PRAM reset when restarting. Once, when I didn't PRAM reset, my computer told me I had no airport card connected.
Now this is odd considering I had just had my computer looked at thoroughly by my "Apple Authorized Service Provider". My logic board had just died and my battery was swollen to a point of near explosion when I took it in to him. The trip to take it in to him already cost me $100, but luckily Apple replaced all the problems with the computer before they had another case of exploding products on their hands.
So I don't know if the problem is hardware or not. I tried running the Extended Test that came with my installation CDs but they said there was nothing wrong with the computer at all, which is most definitely not the case.
- My other problem is the Freezing + Clicking sounds that accompany it. It happens randomly. Temperature does not seem to affect it as it's happened when my computer is at 70° or at 30°. It's happened when I have 6 applications running or none running. Running on battery power or plugged in don't matter either. I haven't tried letting the computer sit for hours, maybe 10 minutes at most. When I close the lid the screen stays the same, it doesn't power down at all. In order to get anything done I need to force shut down by holding down the power button. I've looked for answers but have yet to find any anywhere.
P.S. The game I've been playing is DotA (Warcraft 3: The Frozen Throne). -
Jun 26, 2010 11:34 AM in response to Artitronby Watcher_as,Minutes later I had one more freeze but this time the pointer was moving and after some minutes it became spinning beach ball. I have to say that the display became dimmer and when I closed the lid to put my mb p in sleep, it actually slept!! But when I opened the lid again the same spinning beach ball.. I track down in console and I found this and I don't know if it could help but it looks like suspicious to me;
Jun 26 20:51:19 Watchers-MacBook-Pro kernel[0]: le CONSTANTBUFFER_addr_offsetdisable memsyncenable TLB_Invalidate forwardprogressdisable
Jun 26 20:51:19 Watchers-MacBook-Pro kernel[0]: masks = 0x0000
Jun 26 20:51:19 Watchers-MacBook-Pro kernel[0]: PGTBL_CTL2:
Jun 26 20:51:19 Watchers-MacBook-Pro kernel[0]: 0x00000000PGTBL_STR2: 0x00000000
Jun 26 20:51:19 Watchers-MacBook-Pro kernel[0]: Set:
Jun 26 20:51:19 Watchers-MacBook-Pro kernel[0]: Clear: render_cache sampler_cache vertex_buffer indirectstatebuffer renderbatchbuffer
Jun 26 20:51:19 Watchers-MacBook-Pro kernel[0]: write_enable = 0x000000MIDISPLAYPOWER 0x00000000
Jun 26 20:51:19 Watchers-MacBook-Pro kernel[0]: enable = 0
Jun 26 20:51:19 Watchers-MacBook-Pro kernel[0]: MIARBSTATE: 0x00000044
Jun 26 20:51:19 Watchers-MacBook-Pro kernel[0]: Set:
Jun 26 20:51:19 Watchers-MacBook-Pro kernel[0]: Clear: priority_select page_size suppress_indicator TLBrequestpriority
Jun 26 20:51:19 Watchers-MacBook-Pro kernel[0]: time_slice = 0x02, mask_bits = 0x0000
Jun 26 20:51:19 Watchers-MacBook-Pro kernel[0]: MIRDRETSTATE: 0x00000000
Jun 26 20:51:19 Watchers-MacBook-Pro kernel[0]: Set:
Jun 26 20:51:19 Watchers-MacBook-Pro kernel[0]: Clear: displayAread displayBread displayCread CursorA_and_Bread sampler_read color_z overlay vertex_fetch HVM_enable
Jun 26 20:51:19 Watchers-MacBook-Pro kernel[0]: mask_bits = 0x0000
Jun 26 20:51:19 Watchers-MacBook-Pro kernel[0]: CACHEMODE0: 0x00006924
Jun 26 20:51:19 Watchers-MacBook-Pro kernel[0]: Set:
Jun 26 20:51:19 Watchers-MacBook-Pro kernel[0]: Clear: renderflushenable samplerL2_TLB_prefetchenable samplerL2disable
Jun 26 20:51:19 Watchers-MacBook-Pro kernel[0]: samplerL2_requestarb = 0x0, pagegatherlimit = 0x2, samplerL2_fifomodes = 0x3, mask_bits = 0x0000
Jun 26 20:51:19 Watchers-MacBook-Pro kernel[0]: CACHEMODE1: 0x00004180
Jun 26 20:51:19 Watchers-MacBook-Pro kernel[0]: Set:
Jun 26 20:51:19 Watchers-MacBook-Pro kernel[0]: Clear: instructionL1disable instructionstate_L2disable instructionstate_L2_fill_buffersdisable instructionL1_queuedisable instructionstateinvalidate indirectloadenable
Jun 26 20:51:19 Watchers-MacBook-Pro kernel[0]: dataset_XORselection = 0x0, samplerset_XORselection = 0x3, mask_bits = 0x0000
Jun 26 20:51:19 Watchers-MacBook-Pro kernel[0]: UHPTR: 0x00000000
Jun 26 20:51:19 Watchers-MacBook-Pro kernel[0]: valid = 0, address = 0x00000000
Jun 26 20:51:19 Watchers-MacBook-Pro kernel[0]: BB_ADDR: 0x0000000006764f03 valid = 1, address = 0x019d93c0
Jun 26 20:51:19 Watchers-MacBook-Pro kernel[0]: BB_STATE: 0x00000000
Jun 26 20:51:19 Watchers-MacBook-Pro kernel[0]: Buffer Security Indicator = 0
Jun 26 20:51:19 Watchers-MacBook-Pro kernel[0]: GFXFLSHCNTL: 0x00000000
Jun 26 20:51:19 Watchers-MacBook-Pro kernel[0]: PRCTRCTL: 0x00000001
Jun 26 20:51:19 Watchers-MacBook-Pro kernel[0]: Counter logic op = 0x1
Jun 26 20:51:19 Watchers-MacBook-Pro kernel[0]: PRCTRTHRSH: 0x00145855
Jun 26 20:51:19 Watchers-MacBook-Pro kernel[0]: Counter logic op = 0x145855
Jun 26 20:51:19 Watchers-MacBook-Pro kernel[0]: CCID: 0x0438c10d
Jun 26 20:51:19 Watchers-MacBook-Pro kernel[0]: valid = 1, extendedstate_restoreenable = 1, extendedstate_saveenable = 1, context_address = 0x008718
Jun 26 20:51:19 Watchers-MacBook-Pro kernel[0]: PR_CTR: 0x00000000
Jun 26 20:51:19 Watchers-MacBook-Pro kernel[0]: Counter logic op = 0x0
Jun 26 20:51:19 Watchers-MacBook-Pro kernel[0]: IA Vertices Count Report: 0x0
Jun 26 20:51:19 Watchers-MacBook-Pro kernel[0]: IA Primitives Count Report: 0x0
Jun 26 20:51:19 Watchers-MacBook-Pro kernel[0]: VS Invocation Count: 0x0
Jun 26 20:51:19 Watchers-MacBook-Pro kernel[0]: GS Invocation Count: 0x0
Jun 26 20:51:19 Watchers-MacBook-Pro kernel[0]: GS Primitives Count: 0x0
Jun 26 20:51:19 Watchers-MacBook-Pro kernel[0]: CL Invocation Count Report: 0x0
Jun 26 20:51:19 Watchers-MacBook-Pro kernel[0]: CL Primitives Count: 0x0
Jun 26 20:51:19 Watchers-MacBook-Pro kernel[0]: PS Invocation Count: 0x0
Jun 26 20:51:19 Watchers-MacBook-Pro kernel[0]: CXT_SIZE: 0x0000002d
Jun 26 20:51:19 Watchers-MacBook-Pro kernel[0]: size = 0x0e * 64B
Jun 26 20:51:19 Watchers-MacBook-Pro kernel[0]: CXTSIZENOEXT: 0x00000007
Jun 26 20:51:19 Watchers-MacBook-Pro kernel[0]: size = 0x08 * 64B
Jun 26 20:51:19 Watchers-MacBook-Pro kernel[0]: ECOSKPD: 0x00000307
Jun 26 20:51:19 Watchers-MacBook-Pro kernel[0]: enable = 0, constantbuffer_save_restoredisable = 0, mask_bits = 0x0000
Jun 26 20:51:19 Watchers-MacBook-Pro kernel[0]: CSFLFSM: 0x00000002
Jun 26 20:51:19 Watchers-MacBook-Pro kernel[0]: CSFLFLAG: 0x00000420
Jun 26 20:51:19 Watchers-MacBook-Pro kernel[0]: CSFLTRK: 0x000004c4
Jun 26 20:51:19 Watchers-MacBook-Pro kernel[0]: CSCMDOP: 0x3ab985e3
Jun 26 20:51:19 Watchers-MacBook-Pro kernel[0]: CSCMDVLD: 0x00000001
Jun 26 20:51:19 Watchers-MacBook-Pro kernel[0]: TIMESTAMP_LO: 0x2458e33e00000000
Jun 26 20:51:19 Watchers-MacBook-Pro kernel[0]: CLKCMP: 0x0000000000000000
Jun 26 20:51:19 Watchers-MacBook-Pro kernel[0]: VFDC: 0x00000000
Jun 26 20:51:19 Watchers-MacBook-Pro kernel[0]: VFSKPD: 0x00000000
Jun 26 20:51:19 Watchers-MacBook-Pro kernel[0]: status[ISR]: 46d28000
Jun 26 20:51:19 Watchers-MacBook-Pro kernel[0]: status[PRB0_HEAD]: 42003c48
Jun 26 20:51:19 Watchers-MacBook-Pro kernel[0]: status[SRB0_HEAD]: 00000000
Jun 26 20:51:19 Watchers-MacBook-Pro kernel[0]: status[SRB1_HEAD]: 00000000
Jun 26 20:51:19 Watchers-MacBook-Pro kernel[0]: status[HWB_HEAD]: 00000000
Jun 26 20:51:19 Watchers-MacBook-Pro kernel[0]: status[STAMP]: 00013aba
Jun 26 20:51:19 Watchers-MacBook-Pro kernel[0]: ******** Dumping SVG Debug Registers ********
Jun 26 20:51:19 Watchers-MacBook-Pro kernel[0]: General state base address = 0x00000000
Jun 26 20:51:19 Watchers-MacBook-Pro kernel[0]: Surface state base address = 0x00000000
Jun 26 20:51:19 Watchers-MacBook-Pro kernel[0]: Indirect object base address = 0x00000000
Jun 26 20:51:19 Watchers-MacBook-Pro kernel[0]: Generate state address upper bound = 0x00000000
Jun 26 20:51:19 Watchers-MacBook-Pro kernel[0]: Indirect indirect object access = 0x00000000
Jun 26 20:51:19 Watchers-MacBook-Pro kernel[0]: System instruction pointer = 0x00000000
Jun 26 20:51:24 Watchers-MacBook-Pro kernel[0]: ********* Gen575::debuggraphicsengine() called ***********
Jun 26 20:51:54: --- last message repeated 5 times ---
Jun 26 20:51:56 Watchers-MacBook-Pro kernel[0]: ********* Gen575::debuggraphicsengine() called ***********
Jun 26 20:52:26: --- last message repeated 5 times ---
Jun 26 20:52:28 Watchers-MacBook-Pro kernel[0]: ********* Gen575::debuggraphicsengine() called ***********
Jun 26 20:52:58: --- last message repeated 5 times ---
Jun 26 20:53:00 Watchers-MacBook-Pro kernel[0]: ********* Gen575::debuggraphicsengine() called ***********
Jun 26 20:53:30: --- last message repeated 5 times ---
Jun 26 20:53:32 Watchers-MacBook-Pro kernel[0]: ********* Gen575::debuggraphicsengine() called ***********
Jun 26 20:54:02: --- last message repeated 5 times ---
Jun 26 20:54:03 Watchers-MacBook-Pro kernel[0]: ********* Gen575::debuggraphicsengine() called ***********
Jun 26 20:54:33: --- last message repeated 5 times ---
Jun 26 20:54:35 Watchers-MacBook-Pro kernel[0]: ********* Gen575::debuggraphicsengine() called ***********
Jun 26 20:55:05: --- last message repeated 5 times ---
Jun 26 20:55:07 Watchers-MacBook-Pro kernel[0]: ********* Gen575::debuggraphicsengine() called ***********
Jun 26 20:55:37: --- last message repeated 5 times ---
Jun 26 20:55:39 Watchers-MacBook-Pro kernel[0]: ********* Gen575::debuggraphicsengine() called ***********
Jun 26 20:56:09: --- last message repeated 5 times ---
Jun 26 20:56:12 Watchers-MacBook-Pro kernel[0]: ********* Gen575::debuggraphicsengine() called ***********
I don't know if these messages are relative but if someone can understand them please let me know! -
Jun 26, 2010 6:58 PM in response to JK09by Kevin MacLeod,JK09-Now that is spot on. Customer Support and AppleCare have been good for me and my family/friends on nearly a dozen occasions. This is probably one area Apple still beats all other PC makers in. Yes--call them. -