{"id":1153,"date":"2012-07-06T23:07:40","date_gmt":"2012-07-06T22:07:40","guid":{"rendered":"http:\/\/dpscomputing.com\/wordpress\/?p=1153"},"modified":"2012-07-29T13:33:21","modified_gmt":"2012-07-29T12:33:21","slug":"dps-computing-uncovers-solution-to-os-x-superbug","status":"publish","type":"post","link":"https:\/\/www.dpscomputing.com\/blog\/2012\/07\/06\/dps-computing-uncovers-solution-to-os-x-superbug\/","title":{"rendered":"DPS Computing Uncovers Solution to OS X ‘Superbug’"},"content":{"rendered":"

[adrotate banner=”45″]<\/p>\n

\"Apple\"<\/p>\n

Following numerous hours of investigation by DPS Computing into the OS X ‘superbug’, which causes repeated kernel panics over and over again with apparently no common cause, we have uncovered a solution that, in testing, has proved to work and correct the critical bug in the OS X operating system, which Apple have been attempting to deal with for the past 18 months.<\/p>\n

Now firstly, there’s a couple of points that we need to make. \u00a0One, it’s doubtful that this is the only solution, or necessarily the best, however, our tests have shown that it should work in a lot of circumstances, if not the majority.<\/p>\n

As some of you will remember, we reported two days ago on the plight of MacBook Pro users<\/a> experiencing kernel panics persistently out of the blue. \u00a0Following in depth research into this issue, we discovered that Apple initially for six months denied that the problem was cause by Apple hardware or software, instead indicating that it must be third party software and hardware that users are adding to their machines. \u00a0Around 12 months ago, Apple appear to have finally conceded that there was a problem with the aptly named ‘Black Screen of Death’ (silent kernel panics) was due to a low level hardware and OS X bug.<\/p>\n

It was initially indicated that a fix for the bug would be available in the 10.7.2 update to the OS X operating system. \u00a0Users eagerly anticipated this update, to free them of this catastrophic ailment of their once mighty machine, however disappointment was to come. \u00a010.7.2 was released, everybody updated and……… nothing changed.<\/p>\n

Many users vented further frustration in the Apple community on their support forums and again another announcement was made by Apple on the support forums that this was likely being caused by a firmware issue, which it was promptly announced would be upgraded in the near future. \u00a0Firmware update 2.6 was this time supposed to be the saviour of the MacBook Pros all over the country experiencing this weird and disabling bug in Apples flagship operating system. \u00a0But….. you guessed it. \u00a0Firmware update 2.6 came, and it went. \u00a0And still, things were no better.<\/p>\n

As mentioned in our previous article<\/a>\u00a0a solution, albeit temporary, that seemed to work was the use of the freeware program gfxCardStatus, which, when used to stop the dynamic switching of the graphics card, seemed to work. \u00a0The main issue with this fix was that, to have a chance of temporarily fixing the issue, you had to restrict the Macs capabilities to using on the integrated Intel graphics card, which is the least powerful of the two graphics cards shipped with the MacBook Pro (the other external card being the nVidea card). \u00a0Many users were however, happy to take a performance hit as they were absolutely desperate to stop the excessive kernel panics, which rendered their \u00a32,500 Macs into little more use than a \u00a32 paper weight.<\/p>\n

This temporary solution, which of the many shared in the community support forums provided by Apple is without doubt the one with the highest success rate.<\/p>\n

We tested out the gfxCardStatus fix on one of our machines and low and behold, it worked. \u00a0OK, so it wasn’t perfect, but we knew that we’d all be able to wait a little while for Apple to sort the problem out.<\/p>\n

However, when we continued testing this solution over the following two days, there appeared to be a flaw in the solution which would render it useless, at least in some cases – it is not clear whether what we experienced would happen in all the other cases, but it is a safe bet to say that it is not an isolated phenomena.<\/p>\n

\"\"<\/a>After 24 hours of uptime, with the gfxCardStatus solution implemented, we rebooted the MacBook Pro. \u00a0OK, so nothing drastic about that. \u00a0The Mac booted up fine and we logged in as per usual. \u00a0gfxCardStatus had reverted to dynamic switching, so we changed it back to the ‘Integrated only’ option, as it had been previously set prior to the reboot. \u00a0And then, the display went ‘crazy’. \u00a0Remember the slider puddles you used to play with as a kid? \u00a0Well that’s exactly what OS X did with our screen. \u00a0It was cut up into tiny pieces, mixed up, and put back together. \u00a0And as if that wasn’t enough, the OS decided to throw in some ‘interference’ for good measure – the kind that you used to see on Analogue TV when you weren’t quite tuned into the channel correctly.<\/p>\n

So a couple of reboots later and lots of tinkering we finally manage to get back on to the ‘Discrete only’ option using the Nvidea card and the display returns to normal – great, except we’re back to where we started now. \u00a0But the problems are much worse. \u00a0The integrated graphics card plays havoc with the display, rendering it useless. \u00a0And the discrete graphics card works perfectly in 5 minute intervals before promptly and timely causing a kernel panic and the Black Screen of Death (similar to the Blue Screen of Death in Windows – apart from this one doesn’t have any text!)<\/p>\n

Hmmm, so we we’re a bit unhappy at this stage as you can imagine. \u00a0Rather than settling for this temporary solution, which although good, was by no means good enough for any machine that would be used in a production environment, we decided to set about finding a more temporary solution – seen as though Apple are showing few signs that they are any closer to solving the problem than they were 18 months ago.<\/p>\n

One recommendation from Apple was to run the AHT – Apple Hardware Test. \u00a0This would indeed be useful as it would allow us to identify whether the panics are being caused by hardware or software – and in this case, software referring to OS X. \u00a0Great, we started to follow the recommendation. \u00a0So, firstly we are informed that we need to shut down (and it must be a shut down) followed by a power up (not, I repeat not a reboot!). \u00a0Before the Apple logo appears we were told to hold down D. \u00a0This would start the AHT for us.<\/p>\n

\"Apple<\/a><\/p>\n

So, I followed these instructions and I did it. \u00a0While waiting for the magic to happen, I did question what holding the ‘D’ key would do. \u00a0Normally there is another key used to create a interrupt signal or similar to the OS to tell it we don’t want a normal boot. \u00a0So I was sat there holding the ‘D’ key with one finger while using my other hand to read more on the issue on an iPad.<\/p>\n

5 minutes passed and we’ve gone from a black screen to an off white screen. \u00a0I’m still holding the ‘D’ key. \u00a0And I’m still reading about the problem on the iPad. \u00a0A couple more minutes passed, by which stage my finger had turned a shade of bright red and my arm was crying out for a rest.<\/p>\n

Another couple of minutes, and we’ve got a log in screen. \u00a0The same old login screen as normal. \u00a0Not the special 16bit lookalike computer icon that was indicated in the instructions. \u00a0So we tried a couple more times, same result. \u00a0Changing how and when the key was pressed each time.<\/p>\n

Convinced that this advice seemed a little bit woeful, we tried Cmd-D upon boot. \u00a0Same effect, nothing. \u00a0We do a little more (soul) searching on the iPad and I discover an excellent piece of information, which works for any users of Lion (10.7.x). \u00a0Excellent, so this isn’t the AHT test via your own hard drive or DVD, this time you hold Option (Alt) + D which boots the online AHT from Apple.<\/p>\n

We follow through the same steps using the new key combination and ta-da!! \u00a0It starts to load the AHT. \u00a0Just before I can crack a smile…… we gather around the MacBook and inspect the stop error that has just been displayed saying ‘AHT cannot run on this system’.<\/p>\n

Great, normal reboot is initiated and I plan to use my 5 minutes of uptime to read a bit more advice from Apple. \u00a0The reasons for this error are a) out of date version of OS X – i.e. you need to upgrade to 10.7.4 and b) out of date firmware – i.e. you need to upgrade to 2.6. \u00a0The only problem with this advice and reasoning for the error is that the machine was running both OS X 10.7.4 and the 2.6 firmware update. \u00a0Two pieces of advice from Apple, and two dead ends.<\/p>\n

\"Mac<\/a>So with a bit more digging on AHT we discover its convoluted and apparently unnecessary complexity. \u00a0AHT has been included in the past few major versions of OS X. \u00a0There is also a version on all new MacBooks over the past few years. \u00a0However, if at any time during your ownership of your MacBook Pro, you have upgraded to a new version of OS X (a new major version), then AHT won’t be there any more. \u00a0But if you’ve got your copy of OS X on DVDs AHT will be present on Disc 1, that is unless you have Snow Leopard in which case it’ll be on Disc 2. \u00a0Keeping up so far? \u00a0We’re not done yet. \u00a0However, if say for example you upgraded online (via the AppStore) to Lion, and your using your original Snow Leopard discs, it’ll probably still work, however some Snow Leopard files will be copied across during the AHT process, which is completely unnecessary and it may make Lion go wonky. \u00a0And finally, the logical solution to the previously mentioned problem would be to use the AHT included in Lion on the disc. \u00a0Well, no, as you can see from this entire situation, absolutely nothing is following logic. \u00a0If you have the Lion DVD, great, but you don’t have AHT on it. \u00a0And if you downloaded it from the App Store, you definitely don’t have AHT on it. \u00a0One solution to ‘burn the image to a disc’ was evidently never going to work as the App Store version of OS X isn’t provided as an image, it’s an application. \u00a0Next, the reason why Lion doesn’t include AHT is because its all changed to exclusively the online AHT from Lion onwards. \u00a0So, if you haven’t got an Internet connection, you would probably start crying at this point. \u00a0But don’t worry, many more of us will be crying along with you now as we then discover the revelation that the online AHT online works if your MacBook Pro\u00a0originally<\/strong> shipped with Lion, upgrades don’t count.<\/p>\n

So after a couple of hours of a fruitless AHT search we give up on that. \u00a0It might not even necessarily give us any answers, so we move on.<\/p>\n

Now we start investigating tools…… no, not that kind of tools (although you could be forgiven for thinking that with the runaround Apple is giving the community), software tools.<\/p>\n

As experienced Mac users will know, there isn’t the plethora of free software maintenance and utilities tools that there is available for Windows. \u00a0The apparent reasoning behind this is that Macs don’t break, well at least not until now. \u00a0There’s a few paid for tools, some of which tease you into a ‘free download’, perform a scan, declare you MacBook a write off and offer to fix all your problems with 10 minutes and a click of a button – after you pay them \u00a350-\u00a375.<\/p>\n

So theres, ToolKit, ToolTip, Tool….. something anyway. \u00a0I can’t quite remember the exact name off the top of my head now but it’s the $99 pro version we were looking at (the cheaper sister product, the Deluxe version is given to AppleCare customers free of charge, apparently because it’s ‘that good’). \u00a0One of the Pro versions selling points is that it goes ‘much further than Apples Hardware Test’. \u00a0Great, no need to worry about the AHT saga now! \u00a0But, the price tag… well we’ll keep this in reserve in case we get even more desperate than we already are.<\/p>\n

Free system utilities, well there isn’t many. \u00a0The only one that we found to be of any potential use in this situation was OnyX<\/a>, which has many positive reviews and endorsements across the Internet.<\/p>\n

In my complete an utter desperation at this point, I concede that I’ll just have to go through the 5 minute kernel panics for the next 25 years (or at least until we replace the affected MacBook Pro) and decide the system could do with a bit of a general major cleanup anyway, after all, what more harm can it do?<\/p>\n

And now…..<\/p>\n

The Solution!<\/strong><\/span><\/p>\n

I thought’d I’d make that stand out for the non techie users who just want it fixed and don’t care why, how or the amazing adventure we embarked upon to get to this point.<\/p>\n

So, reboot, hold down the shift key on the keyboard, and we get it into ‘Safe Boot’ (similar to Windows Safe Mode). \u00a0And yes, most of your things will be disabled, including all non Apple start up items. \u00a0But on the plus side, the system runs a lot faster.<\/p>\n

So, we then start OnyX. \u00a0You’ll be greeted by a dialog asking you to check S.M.A.R.T status, which it highly recommends. \u00a0And so do we. \u00a0It should only take a few seconds, and then we’re onto the next stage, assuming there is no problems. \u00a0If you do encounter problems at this point, follow the repair instructions given by OnyX.<\/p>\n

\"OS<\/a><\/p>\n

\"OS<\/a><\/p>\n

All being well and good, you’ll be greeted by a second dialog box. \u00a0This time its to verify the integrity of the start up volume. \u00a0Again this highly recommended by OnyX and by us. \u00a0This is the same process that ‘Disk Utility’ follows to check the start up volume integrity. \u00a0If any errors are shown, it’s best to reboot into the recovery area, run Disk Utility and repair the start up volume and permissions. \u00a0Not doing so, when errors are shown, and then using the tools in OnyX can, for want of a better term, ‘brick’ your system, and believe me, that is not good. \u00a0Assuming everything is fine, we can then carry on.<\/p>\n

\"OS<\/a><\/p>\n

We’re then greeted by an Administration authorisation dialog box. \u00a0This allows us to give OnyX permission to do its magic. \u00a0Enter your username and password.<\/p>\n

\"OS<\/a><\/p>\n

Then we arrive at the main menu:<\/p>\n

\"OS<\/a><\/p>\n

Click on the cleaning option, at which point you should be presented with a screen similar to the following:<\/p>\n

\"OS<\/a><\/p>\n

On this first tab, the system tab (shown above) ensure that all the options are ticked in this ‘Delete the cache’ section. \u00a0By default some are left unticked. \u00a0Tick them all. \u00a0Don’t worry, a cache is just temporary files that can speed up common tasks and applications after you’ve used them a few times. \u00a0Their removal will not harm your system. \u00a0Click execute and wait for the function to complete.<\/p>\n

Then move onto the User tab:<\/p>\n

\"OS<\/a><\/p>\n

Select everything again. \u00a0As above, nothing bad is going to happen (lets be honest, things can’t really get any worse can they). \u00a0Click execute and wait for the function to complete.<\/p>\n

Move onto the Internet tab:<\/p>\n

\"OS<\/a><\/p>\n

Now some people are attached to their cookies, browser history etc. \u00a0If you are, then don’t worry, you don’t have to do anything on this tab. \u00a0But equally, you could also take this opportunity to sort out the thousands of temporary files for your different browsers, a good many of which won’t be used any more. \u00a0Either way, if you decided to delete them, your system is going to be fine. \u00a0Click execute and wait for the function to complete or move onto the next tab.<\/p>\n

Move onto the Fonts tab:<\/p>\n

\"OS<\/a><\/p>\n

Again, tick all the options and delete all the font caches. \u00a0Ignore the doomsday warning bout Apps taking usually long to load the first time after clearing all these caches. \u00a0Yes, Apps will take a bit longer to load the first few times…. however, if we don’t follow these steps, the chances of us ever using any of our Apps productively again is minimal. \u00a0Click execute and wait for the function to complete.<\/p>\n

Close OnyX and empty the trash. \u00a0Don’t worry at the amount of files that are getting junked now. \u00a0We had over 100,000 – this is normal if you’ve been using your MacBook a long time and \/ or you haven’t cleared your caches recently (or ever).<\/p>\n

Reboot out of ‘Safe Boot’.<\/p>\n

The boot and log on will take a little longer than usual. \u00a0As will the loading of your different apps for the first few times. \u00a0But…… the good old persistent kernel panics should now have resolved. \u00a0No need to set the gfxCardStatus settings, feel free to have dynamic switching on – you shouldn’t have any more problem and this setting does give the best performance and power consumption for your system.<\/p>\n

Conclusion.<\/strong><\/span><\/p>\n

Basically, corruption can occur in caches (especially system and kernel caches, although it can be others) which can cause persistent kernel panics. \u00a0Cleaning your caches every once in a while is a good idea to maintain performance anyway. \u00a0Delete the cache, and you delete the corruption. \u00a0Our test machine that we used has stopped having 5 minute kernel panics and, touch wood, there hasn’t been any since.<\/p>\n

This particular problem seems to be particularly affecting mid 2010 MacBook Pro 15″ models (manufactured between April 2010 and February 2011) running OS X Lion (10.7.x). \u00a0It isn’t clear why this very specific model (6.2) would be affected in particular, maybe it is just coincidence.<\/p>\n

Either way, this fix should work if you are experiencing the same problem, irregardless of model.<\/p>\n

The only one, very minor, temporary downside, is that due to the caches being cleared the first boot and the first few times starting each application are going to be a bit slower. \u00a0But it’s a price worth paying for actually turning your MacBook Pro back from being a paper weight into being the excellent productive machine that it should be! \u00a0This is by the far the best and most permanent solution to the problem out there currently.<\/p>\n

At one point, David, our Managing Director, was so disheartened he was contemplating replacing all the office Macs with PCs (perish the thought!). \u00a0But crisis averted, with next to no help from Apple ;). \u00a0Reading the community forums you can see that Apple support and the ‘Genius’ bar weren’t much help to users who accessed their services.<\/p>\n

Faith in Macs restored, lets continue with the productivity! \u00a0Hopefully it’ll be at least another 20 years at least before another critical bug occurs in Mac OS!<\/p>\n","protected":false},"excerpt":{"rendered":"

[adrotate banner=”45″] Following numerous hours of investigation by DPS Computing into the OS X ‘superbug’, which causes repeated kernel panics over and over again with apparently no common cause, we have uncovered a solution...<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","enabled":false},"version":2}},"categories":[55,8,29],"tags":[26,611,599,521,520,616,30,405,612,605,535,508,603,602,524,525,609,610,608,600,615,604,517,613,614,606,522,601,607,577],"class_list":["post-1153","post","type-post","status-publish","format-standard","hentry","category-articles","category-news","category-tutorials","tag-apple","tag-apple-bug","tag-article","tag-black-screen-of-death","tag-bsod","tag-cache","tag-dps-computing","tag-dps-computing-limited","tag-dps-david","tag-firmware-update","tag-gfxcardstatus","tag-kernel-panic","tag-mac-os-x-lion","tag-mac-os-x-superbug","tag-macbook","tag-macbook-pro","tag-macbook-pro-mid-2010-model","tag-macbook-pro-mid-2010-model-15","tag-multiple-kernel-panics","tag-news-2","tag-onyx","tag-os-x-10-7","tag-os-x-bug","tag-os-x-bug-solution","tag-os-x-bug-solved","tag-os-x-firmware","tag-os-x-lion","tag-os-x-superbug","tag-persistent-kernel-panics","tag-tutorial"],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/p3nsfA-iB","jetpack_sharing_enabled":true,"jetpack_likes_enabled":true,"_links":{"self":[{"href":"https:\/\/www.dpscomputing.com\/blog\/wp-json\/wp\/v2\/posts\/1153","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.dpscomputing.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dpscomputing.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dpscomputing.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dpscomputing.com\/blog\/wp-json\/wp\/v2\/comments?post=1153"}],"version-history":[{"count":3,"href":"https:\/\/www.dpscomputing.com\/blog\/wp-json\/wp\/v2\/posts\/1153\/revisions"}],"predecessor-version":[{"id":1167,"href":"https:\/\/www.dpscomputing.com\/blog\/wp-json\/wp\/v2\/posts\/1153\/revisions\/1167"}],"wp:attachment":[{"href":"https:\/\/www.dpscomputing.com\/blog\/wp-json\/wp\/v2\/media?parent=1153"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dpscomputing.com\/blog\/wp-json\/wp\/v2\/categories?post=1153"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dpscomputing.com\/blog\/wp-json\/wp\/v2\/tags?post=1153"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}