Hi argh2xxx,

LOL ... OCZ-SSDs are good friends of mine. I’ve an Agility3 and a Vertex3. I had freezes, f4-BSODs and one Sudden Death of SSD. Three weeks ago I found a firmware that works with my system, but it’s not the new FW v2.13, but an older version. If you read the OCZ-threads, the situation is still very confusing.

O.k., back to topic!

Let’s hope it’s only software related, but I’ve some doubts. I think it is a hardware & software related issue. The big problem is the fact that there is no clear pattern what is causing the BSODs.

In this thread here most users are convinced that the problem is either the graphics driver or the OS itself, but - please do not beat me - I don’t think so. 

I’m not sure, but I think that Lion makes problems above all with new CPU-Generation (i5/i7) inside and for this reason I suspect that new CPUs in combination with certain hardware-layouts & software-settings lead to all these problems.

Let’s have a look at Sandy Bridge. These CPUs need BCLK (Baseclock) 100,0 MHz and nothing else. If you change it you have serious problems with SATA-Controllers, PCI-Slots, USB-Ports etc.. At the end you get bugs like dualboot, BSODs with sleep-modus, freezes and crashes! You can test this perfectly with a new ASUS-Mobo with i5 / i7 Sandy Bridge. I tried it and therefore I know, what I’m talking about.

The question I have to Apple-Techs would be:

Does LION (or LION-installation) change BCLK???

And I still have a second point, which makes me think regarding Sandy. The Power Control Unit only calculates three basic parameters for Sandy Bridge, the minimum voltage at idle, the voltage at nominal clock and that at maximum. This could be not enough. Probably therefore we get corrupt power-cycles in our systems.

I have read in an article that Ivy Bridge will change all this! The Power Control Unit will take significantly more points in order to calculate better the necessary voltage. And with Ivy Bridge you can change BCLK until 133,0 MHz without problems. I suppose that all these problems will dissappear with Ivy.

And don’t forget: Lion shows no problem with older Dual-Core-Macs. My old boy (iMac 24“) runs perfectly with Lion.

Hopefully, I’m wrong with my suspects and Apple can fix this problem with a simple Software-Update.

And just let me say again, if the problem is hardware related a non-disclosure agreement could make an official statement impossible for Apple.

Downgraded with clean install of 10.6, and Photobooth STILL creates BSOD.

dammit.

.....

double dammit.

Anyone tested 10.7.2? Does it fix the problem?

Well, many of the Macbooks that are having this problem, aren't Sandybridge based, the 2010 models are based on the Arrandale architecture. Any base clock changes would be done in the BIOS, and surely wouldn't be done during an OS install.

But yes, the problem isn't purely a hardware or software issue. Many are reporting needing multiple logic board replacements, many are reporting having this issue under SL and haven't even upgraded to Lion. The meat of teh issue resides somewhere in failing/malfunctioning sensors, which can be from hardware, software causing conflicts, bad firmware, or a combination of both.

The multiple logic board replacements some are going through on the 2010 models hints that Apple's inventory of parts is at fault if it is indeed a purely hardware/sensor problem, which in any case, should result in a recall of all affected systems as somewhere in the manufacturing process, someone goofed and produced a crappy part.

I just update my MacBook Pro mid 2010 to latest Mac OS X 10.7.2 patch, some minutes later (after restarting and beginning the latest update patch) during the opening up of iPhoto and then App Store, I got a black screen of death!  So, I don't think it's fixed yet!  Sadly to see BSOD even though the latest patch had been released.  Sigh!

My mbp mid 2010 with the same problem now is working fine...with snow leopard. The same cincumstances: final cut pro x and photo booth. Correct, everything is working now, but I repeat, with snow leopard.

Those who say that the problem is more than just lion, have to read this. I can´t understand it either, but it´s that way on my laptop. Lion doesn´t work, snow leopard, works.

More sad news

For most people like us with MBP 2010 that can't upgrade to Lion or either had to downgrade to SL we can't have ICloud too.

look at the system requirements: http://support.apple.com/kb/HT4759

So, now we have the newest upgrade from Apple but we need to switch to window to use ICloud or trash our macbrick and replace with an extra 3k $.

Last chance for mi is to see if 10.7.2 fix the problem oterwise my (2 MBPs) and Ipod are for sale !!!!!

We miss you Steve. I believe we lost a genius and got another commercial product like MS. Nothing last forever. I moved to mac only two years ago, I feel sorry I did or better say I was to late to enjoy enought.

I don't understand why there isn't more of a consumer outcry about this. I have the same problem mid 2010 MBP with Nvidia 330 graphics card, and crashes started with Lion. I have my computer now at an authorized mac dealer who said he "can't reduplicate the crash" after running my mac for 6 days. I just think he had it sitting on the shelf and probably wasn't running any programs. The crash log on my computer is probably over a page long, but still "he can't reduplicate the crash". He deleted some old temporary internet files and called it good. So sounds like he isn't going to do anything. Why isn't this in the media?? There are over 100 pages on this post, it has been on CNET reviews. This is very disappointing to me as I am a first time Mac user with this computer. Mac's are supposed to be the option of quality. I really like my Mac, but I cannot afford another top of the market priced computer, nor do I have time to deal with this. I am a medical student and need my computer for school everyday. There are tons of people in this discussion with the same problem, same computer, same specs......and this isn't in the news??? I would think Apple would take some serious heat for this. Why hasn't this made bigger headlines? I am looking at getting my faulty computer back from a Mac dealer with only old temp files deleted??? Gimme a break. I am very angry at Apple for this.

More sad news

For most people like us with MBP 2010 that can't upgrade to Lion or either had to downgrade to SL we can't have ICloud too.

look at the system requirements: http://support.apple.com/kb/HT4759

So, now we have the newest upgrade from Apple but we need to switch to windows to use ICloud or trash our macbrick and replace with an extra 3k $ machine.

Last chance for mi is to see if 10.7.2 fix the problem otherwise my (2 MBPs) and Ipod are for sale !!!!!

We miss you Steve. I believe we lost a genius and got another commercial product like MS. Nothing last forever. I moved to mac only two years ago, I feel sorry I did it or, better say, I was to late to enjoy enough.

Has anyone daring tried out the Lion update yet? I'm back at SN, and it's 'somewhat stable', from 'rather unstable' in Lion.

It still happens with 10.7.2

It took more time for me to get a test case (and now ashamed I see that it was mentioned already here before) but with Photo Booth it still happens 100% of the times. Other cases that some times make it happen now appear to work, but still, it is still broken.

i would suggest you back track on this post a bit and follow some of the advice posted. I had the same issues with my mac and got mac to listen after much hard ache they didn't solve the problem but they replaced it. They gave me a new 2011 mac book pro. So you could try being persistent about the issue you're having and then if it seems you're not getting through then probably you might wanna take legal actions about the problem you're having. I'd also document everything when you're dealing with them to make your case stronger.

Just to add to those above posted, 10.7.2 did not fix the BSOD of my mid-2010 macbook pro either. Just as Topher Kessler on MacFixit predicted. I have talked with apple telephone support 4 times, 2 times in the genius bar for total 6 times. It is now 90 days since Lion release and I waited patiently for 10.7.2 as suggested by the Apple folks. It appears that Apple has officially decided not to support any macbook pro with nVidia cards with Lion. I also am surprised that there has been no  discussion about this on any of the mac sites, except Macfiixt. This is exactly what Apple vilified Microsoft for in the Vista debacle. To not support an expensive top of the line macbook pro which is barely a year old is shocking. I have scheduled an telephone call tomorrow, looks like it is either a logic board or a new computer. Will post what I find out tomorrow. Currently finally got system running after nearly 7 BSODs in a row at start up - limping along with gfxCardStatus in integrated only. If it wasn't for the the guy who wrote and release that utility, we would have lost much work.

I have 3 MBP 17" models all different years, the MID 2010 unit which is the middle unit sporting the NVIDIA 330 (one is older and one is newer) are all running Lion 10.7.1  with no obvious issues.   The MacMini Early 2009 - no issues with 10.7.1.   The 27" iMac (Mid 2010) loads and loads of problems with 10.7.1. was just updated to 10.7.2 and so far seems better (time will tell)

Mid 2010 MBP, i7. Nvidia 330- 512 MB, 8 Gigs of Ram

Just upgraded to 10.7.2, and also upgraded Aperture and IPhoto...also migrated to iCloud

Everything is working great...the computer seems faster and works smoothly under the upgraded Lion OS. iCloud handles email, contacts, etc without a problem as well.

damienfromarmadale wrote:

 

Has anyone daring tried out the Lion update yet? I'm back at SN, and it's 'somewhat stable', from 'rather unstable' in Lion.