Firmtek SeriTek/2SM2-E eSATA ExpressCard/34 - Deep Sleep issues / problems

Hi There,
Has anyone had experience with these cards? I've emailed FirmTek twice over the past 2 weeks but haven't heard back.
The card and drive work as expected until the computer sleeps for more than 20min or so (I can't be sure of the exact time). When you wake the computer the drive is on the desktop and you can browse previously viewed directories but if you go to a new directory, the Finder locks up.
Turning the drive off and restarting works until the computer sleeps.
I have a new 17" Macbook Pro running 10.5.7 connected to a Western Digital Mybook Studio edition enclosure.
I checked with FirmTek before purchasing the card to ensure compatibility with my existing drive (I'd heard Lacie & Sonnet both have issues) so I'm not sure what the problem is.
Any help or suggestions would be most appreciated.
Cheers

Dear Ben,
My guess is that you may have some type of Spam filter that prevents the FirmTek response from reaching you. If you live outside the US it can be difficult for companies to call you when this occurs. You may want to check your spam filter, call FirmTek or email them your phone number.
It is possible that you may have another extension loaded that is causing the issue. This is what I would do.
1. Look for WDBMService in Macintosh HD//Library/StartupItems/WDBMService. If it exists I would remove it. This startup item can cause the ExpressCard driver problems. Restart and see if this corrects the issue.
2. If this does not correct the issue you can install an alternative driver. Here are the directions.
A. Uninstall the existing driver by removing the following files (if they exist)
Macintosh HD/System/Library/Extensions/FTATASil3132EC.kext
Macintosh HD//System/Library/Extensions.mkext
Macintosh HD/System/Library/Caches (folder)
Restart the MacBook Pro
B. Download the SiI 3132 32-bit universal Mac OS X 10.4.9, 10.4.10, & 10.5.1 BASE Driver found 1/4 of the way down the page here: http://www.siliconimage.com/support/searchresults.aspx?pid=32&cat=3
C. Install the SiI3132 1.1.9u driver downloaded in B above. Restart.
Now try the WD enclosure.
The beauty of the SeriTek/2SM2-E is that it will work with the FirmTek driver or this Silicon Image driver which provides another option for certain applications. Just don't install both drivers together
Have fun!

Similar Messages

Deep Sleep issue after SSD upgrade

I recently upgraded my Macbook Pro mid-2012 13" Intel Core i5 laptop to a SSD. I purchased a OWC Mercury Electra 6G model for this machine. Everything seems to run fine except when I leave my notebook with the lid closed to induce sleep mode and its been running off of battery power for well over an hour. This issue occurs : https://www.dropbox.com/s/rghjwckw07m59ea/IMG_0866.MOV Have anyone who have done a similar upgrade to this model experiencenced this specific isue ? Thanks.

Open terminal.app, enter the following bolded command. What value is returned? 3 should be the default for your machine:
pmset -g | grep hibernatemode
hibernatemode = 0 (binary 0000) by default on supported desktops. The system will not back memory up to persistent storage. The system must wake from the contents of memory: the system will lose context on power loss. This is, historically, plain old sleep.
hibernatemode = 3 (binary 0011) by default on supported portables. The system will store a copy of memory to persistent storage (the disk), and will power memory during sleep. The system will wake from memory, unless a power loss forces it to restore from disk image.
hibernatemode = 25 (binary 0001 1001) is only settable via pmset. The system will store a copy of memory to persistent storage (the disk), and will remove power to memory. The system will restore from disk image. If you want "hibernation" - slower sleeps, slower wakes, and better battery life, you should use this setting.
pmset(1) Mac OS X Manual Page - Apple Developer

Reccomendations for eSATA expresscard please!

Hi,
I've just installed Snow Leopard and my 2 port esata express card no longer works. During the install process OSX stated that my SIL3132-based card is not supported and the software has been removed and placed in a folder.
I have had problems all week trying to get this thing to work in Bootcamp with Windows XP (the attached drive would never show in Explorer) although it did work perfectly in Leopard.
That's all by the by anyway. I'm pretty much over this cheap and nasty card so i've decided to bin it and buy another one in the hope that it'll be less troublesome.
So my question is can anyone tell me a brand/model of *2 port* esata expresscard that they have got working both in OSX Snow Leopard AND Bootcamp with Windows XP please?
If i can't find one I will be forced to use Firewire 800, but i am unsure if this is quick enough for multi-track audio recording and video editing.
Any help will be greatly appreciated.
Cheers
John

A bit of research shows that your card uses the very same chipset as the Firmtek card. Therefore you may be able to get their driver to work with your card instead of spending your hard earned cash on a new card. I will be testing this over the weekend when I install Snow Leopard myself and try to get things up and running. I, however, will be doing a clean install (shame on Apple for requiring a wipe for this option to appear) and dual booting with either Tiger or Leopard so that I may use some programs that likely will not work with SL (and possibly in this case, eSATA). If you insist on getting a new card, I suggest the Sonnet Tempo Pro, which uses the Marvel chipset. May as well upgrade performance at the same time as making it work with a new OS that all cards should work with anyway.
On the driver front, while I am not suggesting that you break any EULA's which Firmtek may have on its drivers, most cards based on the Sil-3132 chip use Silicon Image's reference design. Thus the driver should work without any modification. At the very most you may have to modify a plist file to get it to accept your card and install it. Kudo's to Firmtek for going above and beyond the (lack there of) work that Silicon Image puts into their drivers. If I knew what I know now I would have gladly paid more for a card from a company that writes their own drivers.
I'll update once I get SL up and running and (attempt to) get my eSATA card working with it.

FirmTek SeriTek/2ME4-E bootability

My question is about Firmtek's SeriTek/2ME4-E esata adapter card.
Manufacturer claims Powermac G5 bootability - http://www.firmtek.com/seritek/seritek-2me4-e/spec/
I tried to boot from external and then from internal hard drive, using this card, but the only thing I get is a question mark on start up.
Has anyone tried to boot using this card?

Question for Mariusz12..
How is your system working so far? I am running a G5 Quad Mac OS X(10.5.8) same as you I believe
I too have installed the Seritek/2ME4-E SATA controller card , so far all is well.
I ran a SATA - eSATA cable from just outside the PCIe slot looped back thru to connect to the SATA HDD in drive bay "A". Once selected ( thru "Startup Disk" pref) it now always boots from the selected disk.
I replaced the ATA100 DVD drive with a newer SATA model (connected to the G5's onboard SATA controller) as SeriTek claims their card will not support optical drives.
My next test is to purchase a SSD and see if it will take advantage of the SeriTek's faster SATA speed.

ESata Expresscard 34 - how do I use it?

An Addonics eSata expresscard that I inserted into the expresscard slot on my Macbook Pro is not being recognized because I see a little item appearing on the menu bar. However, I have on idea on how to get it to recognize the hard disk it is connected to. Also, the lights on the eSata do not light up - I assume that this will happen once the hard disk is recognized?
Message was edited by: mapexvenus

I finally got it working, but am somewhat disappointed with the results. I find that it takes longer to transfer a file from my external drive to the internal drive via eSata than Firewire 800. Do I need to configure the eSata expresscard? I thought data transfer was supposed to go much faster than FW 800.

MacBook Pro 17' (2010) don't want eSATA expresscard/34

Hi
each time I connect the eSATA expresscard/34 Griffin in the macbook pro
it start a kernel panic, grey screen, etc.
or, a message : HD not readable, Do you want to erase and initialize your HD?
And there is no new update in the Griffin website.
I've try to reboot in 64 bits... same result.
Please, someone know some issue?
thank you
jem

Try to find out who the original chipset manufacturer is and then go to their web site and see if they have updated drivers for 10.6.x. I have a card which uses the Siliconlmage chip set and found a 64-bit compatible driver for 10.6.3 for the dual port system. If you have a SiliconImage chipset try this link:
http://www.siliconimage.com/products/family.aspx?id=3#24
Zarbs

Lion 10.7 - Proper driver for Dynex eSATA Expresscard adapter?

I just upgraded to OS X Lion today, and I'm having trouble talking to my external drive with my eSATA expresscard adapter. (see link below)
http://reviews.bestbuy.com/3545/8682393/dynex-2-port-esata-ii-expresscard-adapte r-reviews/reviews.htm
The adapter is detected as a "Mass Storage Controller," but I can't get any connectivity with my external drive. Has anyone had success with this/any expresscard adapter? Back to good ol' USB 2.0 for the time being I guess...
Thanks in advance!

I can confirm that this driver (SLI 3132 ver. 1.2.5.0) is working for my Dynex 2 port e-SATA II ExpressCard Adapter.
(Link to Mac specific driver page)
I haven't done any super heavy lifting with it yet, but so far so good.
Will report back if I see any issues over the next couple days of use.

ESATA ExpressCard Problem

I bought a new eSATA ExpressCard.
One of the new ones that are smaller and don't need a special driver.
When I plug in a drive and start it up, it causes a kernel panic.
I know that the card is fine, I'm pretty sure it's a software conflict.
The strange thing is, that if the disk is plugged in and running before I start the computer, everything is fine. That is, no kernel panic.
Does anyone have any suggestions on how to figure out what's causing the conflict?

It's from Other World Computing.
Brand: Best Connectivity (?)
It's replacing a LaCie SATA II ExpressCard 34, which had a driver. I tried with LaCie tech support to remove all the driver parts but I can't be sure I got all of them.
I know that I works just fine because I have a bootable external drive that I use for maintenance.
When I boot from this drive, which is bare bones (just a few utility programs like Diskwarrior), it works beautifully.
My gut feeling is that it might be one of my startup programs, because if I boot from my internal drive with the card and hard drive plugged in and running, it works.
Go figure.

GX630 boot from esata expresscard adapter

Hi,
i have GX630 with non functional sata ports (sata working for 5min and after that not).
Now i booting from USB, but this is little slowly.
I read many topics about booting ssd card from expresscard slot, and it works, but its much expensive for me.
Can i boot from esata expresscard adapter (adapter supports booting)?
Can bios in GX630 recognize this sata adapter?
Thanks for reply

Hi and welcome to Discussions,
the EFI and SMC updates are specific for each Mac model.
Therefor trying to apply an EFI update made for the newer MBP to an older one would either not work (because the Installer checks the model) or, if it installs, surely crash your MBP.
Don't try it !!
Since the newer MBPs uses a different (newer) Intel-chipset on the logic board, it is most likely that the ability to boot from eSATA Express Card is not implemented on the chipset that is in your 'older' MBP.
Sorry
Stefan

Pcmcia eSATA ExpressCard and Yosemite upgrade?

When I upgraded to Mavericks the pcmcia eSATA ExpressCard in my 17" MacbookPro stopped working, and I had to go through an involved process to restore the libraries that were removed from that OS upgrade.
Does anyone know if pcmcia eSATA ExpressCard drives work under Yosimite, or will the upgrade break that drive again?
The ExpressCard on this laptop is dedicated to the Aperture library which won't fit on the hard drive and it is critical to keep it functional.
thanks all!

Same Problem here. No warning no nothing. I am using this card to connect my backup disk and now - nada. @Apple: This is bad policy not telling in advance that there ist unsupported Hard/Software on a system _BEFORE_ upgrading. This software is there for a reason!

W530 eSata expresscard 34 recommendation

Hi,
I need to get an eSata port on a W530 and I would like to get a card that's fully compatible with full bandwidth and no BSOD.
Could anyone recommend card(s)?
Thank you

I'm also in the market for a reputable brand of SATAIII eSATA ExpressCard. Glad I ran into this thread. I just looked through this Addonics Card recommended but I could not find indication of its port-multiplier support on the following official web page.
I have a 5-day eSATA external HDD enclosure and I'm dying for a true SATAIII ExpressCard with port-multiplier support.
Could any current owner of the Addonics Card confirm this does support port-multiplier? BTW could someone recommend some real SATAIII eSATA cable as well?
6G 2-port eSATA ExpressCard 34:
http://www.addonics.com/products/adexsa6g-2e.php
Thank you for advising!
W520 (4270CTO), i7-2720QM, BIOS 1.42, 1920x1080 FHD, 16 GB RAM, 2000M NVIDIA GPU, Sandisk Extreme Pro 240GB SSD (planned), Hitachi 1TB 7200rpm HDD, ThinkPad Mini Dock Plus Series 3 (170W) eSATA edition, & eSATA ExpressCard/34 w/ port-multiplier support

MobileSTOR MS2UT + esata + USB + mac pro = never-ending problems

Hey gang,
I seemed to have entered a perfect storm here:
I had purchased the *MobileSTOR MS2UT 2 Bay SATA to eSATA/USB 2.0 RAID 0/1* Enclosure initially for a *dual 800 quicksilver G4* mac that I had, looking for a hardware-based Raid solution for back ups and to not burden the G4 processor. I have replaced the G4 with an early *2008 2.8 dual quad core mac pro*. After two machines and two different PCI sata cards, I've had no luck....
(website for the above enclosure)
http://www.sansdigital.com/mobilestor/ms2ut.html
For starters, in the G4, I had a quality Seritek/1ve2+2 controller that had no problem with two other single drive enclosures, but failed with the MS2UT.
http://www.firmtek.com/seritek/seritek-1ve2plus2/
A glib response from Seritek support says that I should use their enclosure. Digging around I find that I need a controller card that can handle a port multiplier enclosure rather than just any serial ata enclosure. Seems silly to me that the user has to dig for this. I mean the USB & FIREWIRE interfaces don't seem to care: it says USB/FIREWIRE on the effing box of both the controller and on the drive, badda-bing, badda boom: it works. Whats with this high maintenance of esata. Well you get roughly 2-3x the performance so Ok, maybe its worth it.
Well, with the macpro on the horizon,, I give up on the G4, close that unsolved mystery. For the mac pro I figure PCIe, a modern computer, no problem. I get the computer, fish around the internet for an esata PCIe card, then I come across this review of the WiebeTech SilverSATA II which appears to be similar to that of the MobileSTOR:
http://www.amug.org/amug-web/html/amug/reviews/articles/wiebetech/silver2/
It appears that the unit has specific tastes as far as having the right card to make it bootable, multiport aware, etc... (the Sonnet Tempo 4+4 card works but its a PCIx card, not PCIe)
Like I said: install a bootable Mac OS on any USB/firewire drive, plug it into any card, and it works... estata... its russian roulette...
Ok so I round up some vendors, (firmtek, sonnet, Highpoint) send them emails to see what they think: if their latest cards will work with the MS2UT... They are all over the place.. they think it may work, they dunno... it should work, they haven't tested it... then they try to push their own enclosure hardware on me. I mean see an astrologist or have your palm read.. it seems more likely you'll get a more accurate answer from them, rather than vendors... props to Sonnet, though, they list compatibility right on the page with their controller.
then 10.6 comes out... and you email vendors about compatibility on that OS, and they don't even email you back.
So I find this review of the highpoint rocket raid for the mac on the great sight: Barefeats.com
http://www.barefeats.com/hard119.html
to make a long story short:
+KEY FEATURES of the "eSATA for Mac"+
+1. Dual eSATA ports+
+2. 32 and 64-bit EFI onboard+
+3. Able to boot Mac OS X+
+4. Plug and Play for (Oxford and Silicon Image chipset) external storage+
enclosures
+5. 4x PCIe rating+
+6. Support for Direct Attached and Port Multiplied enclosures+
+7. RAID 0, 1, 5, and JBOD support using browser-based manager+
+8. Native support for Snow Leopard+
+9. Compatible with 2006 - 2009 Mac Pro+
I should be set, right? WRONG!
I email highpoint, detailing that I planned to mix both Port multiplied (PM) and direct access (DA) enclosures on the same card at the same time. They say maybe (only describing the PM enclosure, not even mentioning the DA enclosure compatibility as I specified), since its a raid card and I intended to use it with an enclosure with its own raid hardware, however they say they see no issues. Well it shows they don't even know their own hardware: Their docks say that the card supports PM enclosures as well as DA (direct access) enclosures. Their web based software even shows the two as separate categories. What is buried in the manual and not cleared up by tech support or their product page is that YOU CAN'T MIX PM AND DA ENCLOSURES ON THE CARD AT THE SAME TIME!!! I explained more in the paragraph above than any tech support from any company. Unbelievable where support has gone these days.
I discover the above because I found the card at Fry's believe it not and since they have a generous return policy I tried it out and learned the above the hard way. No dice on the MS2UT with what is perhaps the most forgiving esata card for the mac.
So more hunting on the web, this time the enclosure's manufacture site: sans digital.
http://www.sansdigital.com/mobilestor/ms2ut.html
...clicking on the accessories tab I find several esata adapter cards... funny that they include ones that don't appear to support PM enclosures... Anyway, I study two that state they supports port multipliers:
http://www.sansdigital.com/adapters/ha-san-4espcix2.html:
http://www.sansdigital.com/adapters/ha-dat-4espcie.html
Ok, I may not get a bootable enclosure.. I just want to get this thing working in esata since cloning my internal raid on the mac pro takes 8 hours using usb, and my main purpose is to maintain a clone so I make my compromise.
I should be set, right? WRONG!
reading the fine print on both cards it says:
*(Please note that the host adapter card is based on Silicon Image chipset, which currently only support up to MAC OS 10.5.1 by Silicon Image.)*
I do more research, it seems any manufacturer using chips by Silicon Image will have an issue with 10.6 macs! On some websites it says Silicon Image will never release a driver. On firmtek it says they make their own driver and swears that it works. At the Silicon Image website they say they are an OEM provider so don't bother them, and that its up to the vendor to make a compatible driver. Sheesh!!
I don't get it.. whats the point in having an esata sticker if it appears to come in more flavors than an ice cream shop!
Oh and it gets better: I go to the sonnet site, thinking they have to have something that works, looking at their latest tempo SATA E4P:
http://www.sonnettech.com/product/temposatae4p.html
well, the fine print is EXHAUSTIVE, but again props to Sonnet for making it crystal clear:
(4) Sonnet Tempo cards are compatible with most external SATA storage. However, external hard drives with USB 2.0/eSATA dual interface based on the Oxford Semiconductor OXU931DS storage controller chip may not be compatible with Mac OS X when connected via SATA. Known issues are kernel panics occurring when the drive is connected, or the drive not being recognized by the operating system.
+Summary of external SATA storage+
+• Storage with eSATA alone +
Compatible
+• Storage with triple interfaces +
Compatible
+• Storage with eSATA plus Firewire 400 and/or 800 +
Compatible
+• Storage with port multiplier support (multiple drives) +
Compatible
+• Storage with RAID 0, 1, or 5 (multiple drives) +
Compatible
+• Storage with eSATA plus USB (based on JMicron 20366) +
Compatible
+ these compatible drives include, but are not limited to:+
+- OWC Mercury On-the-Go USB 2.0/eSATA 2.5" portable+
+• Storage with eSATA plus USB (based on Oxford OXU931DS) +
+not compatible+
+ these incompatible drives include, but are not limited to:+
+- Western Digital My Book™ Premium ES Edition™+
+- Seagate Technology FreeAgent™ Pro+
+Advanced users note that this card is not yet compatible in full 64-bit boot. Snow Leopard default boots in 32-bit mode, except in an Xserve.+
So in short: if you have an enclosure that has both USB and esata, but does not use the JMicron 20366, then it will not be recognized by the card. If you have an enclosure with three interfaes: USB, FW and esata, you're fine. Keep in mind too: most manufacturers don't put the source manufacturer of their chipsets on the box. So I ask..
*HOW IS THE CONSUMER SUPPOSED TO KNOW!*
I swear, a perfect analogy is if I go to best buy, buy a toshiba DVD player only to discover it doesn't play DVD's that contain movies produced by Sony Pictures..because its not a a Sony/columbia House movie. You think consumers would put up with that crap? UNBELIEVABLE...
So now I have this really versatile enclosure that apparently can't run on Mac 10.6 with ANY esata controller for the mac. I really like the design of the enclosure, with its hardware based raid that is hot swappable and has a small footprint. However there seems to be no way to get a controller card for this device that will work on a 10.6 mac.
I guess whats inferred is that you should get an enclosure with the fewest variety of ports, i.e. esata/fw/usb... ironically if it has all three, you are ok, but not if it has usb/esata. Being that USB is the most popular, thats not easy. I'm looking to contact Sans Digital to see if they will exchange it for me, possible for a model with esata/fw800 or an esata only model, if it exists. My last resort is to just use it as a USB drive (my intention was to use it as a clone of my system, with the added security that the enclosure makes a copy of a copy in raid 1), however its like 3x as time consuming than esata.
If anyone has a working MobileSTOR MS2UT/wiebetech SilverSATA II in a 10.5 mac pro, please respond to me with your config. Thanks for reading!

Thank you hatter for your reply.
I'm familiar with OWC, as I've done business with them since 2001, as well as XLR8.
I have a 2008 mac pro so the 2009 model related problems are not an issue in my situation
As I stated above I go to reputable vendors for my hardware who have specific mac experience. I look specifically for hardened compatibility so that there is support for things like deep sleep. The Sans Digital enclosure was over $200..it was not cheap. The USB/Esata combo is the most common interface for the enclosure storage market. Having a compatibility issue is a vendor fault, not the buyer. Having minutiae flavors of esata compatability based on chipsets roulette wheel is inexcusable. The enclosure needs that I have is for the medium to be removable and be able to be rebuilt at the hardware level, i.e. at the enclosure's control panel. To the mac its just a drive. The hotswap and back up is transparent to the OS and mac hardware, and allows me to change from raid 0/1 and do back up right from the enclosure interface.
So far I haven't had problems with USB/Firewire. Meanwhile Esata to me has been nothing but beta testing for vendors and seeing how the chipset manufacturers have gone loosey-goosey on following spec and just dump cheap chinese crap into the market with no pride.
for comparison:
USB/FW, PATA, SATA, SCSI
1) industry standard
2) native drivers
3) bootable. Period.
4) buy a controller card/raid card, plug it in, format, it works even through major OS upgrades.
5) USB/FW: Hot-swapable. Yes it really does work.
Esata:
1) Multiple standards (again, look at the Sonnet website to see the minefield one has to walk through to mate a controller card to an enclosure)
2) non native drivers. Buying an esata card is like marrying into the vendors family. Plus if you manage to get things working and do an OS upgrade, you are playing russian roulette. If you system boots off it, then get life insurance because you may kill yourself.
3)Not bootable and no one seems to care to explain why. Whats odd is that some earlier PCIx cards were bootable (like sonnet Temp 4x4) but their PCIe successors aren't. Not sure if this has to do with the host computer BIOS and/or the current chipsets from SI which rely on custom drivers from the vendors. Another lovely example of this are the ODD_SATA ports on the Mac pro: storage only, not bootable. Sure it makes sense now that I've learned it the hard way, however to users of FW/USB and even IDE, one would think that motherboard ports are bootable. Yes I know this is a mac bios thing and its not even considered as part of the feature set of the computer
4) As I've shown, each controller card seems to be unique, even if its from the same vendor. Even the drivers vary from card to card! Heck even the vendors are unsure as to how compatible their controller cards are with various enclosures. That is proprietary, not industry standard. OS upgrades doesn't seem to provide native driver support for Direct access and/or port multiplying interfaces. The problem with this is that film/video users like myself like to build bullet proof systems, and with raids that I've built from IDE, FW, or USB, I've never had the minutiae of compatibility issues as I've had with esata. I installed an Acard raid controller in my dual 800 back in 2001, installed the drives and forgot about it. it just worked through multiple OS upgrades. Not sure whats gong on with esata.
5) Can't call it hot swappable if I can't get the **** thing to wok in the first place.
My analysis is this: Esata is basically a proprietary format to the vendor that sells the hardware, while USB/FW is an industry standard. I bought a quality enclosure that said "esata", I bought a quality controller that said "esata", it didn't work. I had to learn the hard way about DA and PM enclosures and now about chipset conflicts. I've built computers since the late 80's amiga days, hot-rodding that computer well beyond spec and with custom cooling. SCSI terminators and IDE master/slave issues were easy-cheesey because they followed straightforward rules. This esata stuff is just plain sloppy work on the part of vendors and as Danny Glover said I'm getting to old for this **** as far as being a beta tester for hardware.

ESATA sleep issues

I just purchased a Seagate eSATA 300Gb external drive. Everything seems to work fine, but I am having the deep sleep problem. I have read about this with external USB and firewire drives. I currently have to disconnect my iPod and external firewire drive and power them down to avoid the sleep issue. Now with this new eSATA drive, I still have the problem after unmounting and powering down the drive. Anyone else had this problem with a eSATA drive?

Same issue here - controller installed on PCI-X slot 4 no problem and drive
works fine but fans stay on and no heartbeat indicator. Not sure if drives
spin down and wake does not require the normal mouse click to activate.
I'm sure the controller card on PCI-X bus has changed the environment
enough where the normal sleep mode no longer funcions. I have read
other messages posted on these boards that indicate this is a common
problem.

HELP...   Since last week, I can not awake from sleep. After reading a review I downloaded Deep Sleep, but after the first deep sleep, my MBP (late 2011 with Mountain Lion), developed a problem restarting from sleep.

HELP...   Since last week, I can not awake from sleep. After reading a review I downloaded Deep Sleep, but after the first deep sleep, my MBP (late 2011 with Mountain Lion), developed a problem restarting from sleep. I straight away uninstalled Deep Sleep, but the problem has increased.
Now when I try to awake from sleep, a grey screen with the apple logo appears with a progress bar underneath it, which slowly moves to the forelast indicator, then it stops and a audio signal starts. Three bleeps and pause.
Then when I press the on/off botton and restart the system, the underneath error reports appears with the heading RAPPORTD unexpectedly failed.
Can any one help?
Process:         rapportd [235]
Path:            /Library/Rapport/*/rapportd
Identifier:      rapportd
Version:         ???
Code Type:       X86 (Native)
Parent Process: launchd [196]
User ID:         501
Date/Time:       2012-08-27 11:38:13.723 +0200
OS Version:      Mac OS X 10.8.1 (12B19)
Report Version: 10
Interval Since Last Report:          8281 sec
Crashes Since Last Report:           5
Per-App Crashes Since Last Report:   5
Anonymous UUID:                      F7A70155-2067-4184-A500-CECB394A71B3
Crashed Thread: 5
Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000920
VM Regions Near 0x920:
--> __PAGEZERO             0000000000000000-0000000000001000 [    4K] ---/--- SM=NUL /Library/Rapport/*
    __TEXT                 0000000000001000-0000000000065000 [ 400K] r-x/rwx SM=COW /Library/Rapport/*
Thread 0:: Dispatch queue: com.apple.main-thread
0   libsystem_c.dylib                       0x991479c9 szone_free_definite_size + 3565
1   libsystem_c.dylib                       0x99141cdc free + 217
2   rapportd                                0x00022a80 refree + 43
3   rapportd                                0x0001dc09 dictionary_free + 97
4   RapportUtil1.dylib                      0x001893ea CLocalSection::~CLocalSection() + 40
5   RapportUtil1.dylib                      0x0018e17b CSimplePersistentSection::~CSimplePersistentSection() + 97
6   RapportUtil1.dylib                      0x00186e07 counted_ptr<IConfigurationSection>::release() + 57
7   RapportUtil1.dylib                      0x00186512 SectionSynchronizer::~SectionSynchronizer() + 54
8   RapportUtil1.dylib                      0x00186e07 counted_ptr<IConfigurationSection>::release() + 57
9   RapportUtil1.dylib                      0x001885d8 std::pair<std::string const, counted_ptr<IConfigurationSection> >::~pair() + 26
10 RapportUtil1.dylib                      0x00188628 __gnu_cxx::hashtable<std::pair<std::string const, counted_ptr<IConfigurationSection> >, std::string, __gnu_cxx::hash<std::string>, std::_Select1st<std::pair<std::string const, counted_ptr<IConfigurationSection> > >, std::equal_to<std::string>, std::allocator<counted_ptr<IConfigurationSection> > >::_M_delete_node(__gnu_cxx::_Hashtable_node<std::pair<std::string const, counted_ptr<IConfigurationSection> > >*) + 44
11 RapportUtil1.dylib                      0x00188994 __gnu_cxx::hashtable<std::pair<std::string const, counted_ptr<IConfigurationSection> >, std::string, __gnu_cxx::hash<std::string>, std::_Select1st<std::pair<std::string const, counted_ptr<IConfigurationSection> > >, std::equal_to<std::string>, std::allocator<counted_ptr<IConfigurationSection> > >::clear() + 62
12 RapportUtil1.dylib                      0x001889eb __gnu_cxx::hashtable<std::pair<std::string const, counted_ptr<IConfigurationSection> >, std::string, __gnu_cxx::hash<std::string>, std::_Select1st<std::pair<std::string const, counted_ptr<IConfigurationSection> > >, std::equal_to<std::string>, std::allocator<counted_ptr<IConfigurationSection> > >::~hashtable() + 23
13 RapportUtil1.dylib                      0x00186791 CConfigurationManager::~CConfigurationManager() + 77
14 RapportUtil1.dylib                      0x0019a8e3 counted_ptr<CConfigurationManager>::release() + 57
15 RapportUtil1.dylib                      0x0019b348 configuration::~configuration() + 54
16 RapportUtil1.dylib                      0x0019a113 counted_ptr<configuration>::release() + 57
17 libsystem_c.dylib                       0x99161edb __cxa_finalize + 184
18 libsystem_c.dylib                       0x99164dd5 exit + 23
19 rapportd                                0x00002317 start + 63
Thread 1:: Dispatch queue: com.apple.libdispatch-manager
0   libsystem_kernel.dylib                  0x98a8b9ae kevent + 10
1   libdispatch.dylib                       0x99223cc5 _dispatch_mgr_invoke + 993
2   libdispatch.dylib                       0x992237fd _dispatch_mgr_thread + 53
Thread 2:
0   libsystem_kernel.dylib                  0x98a8b0ee __workq_kernreturn + 10
1   libsystem_c.dylib                       0x9912a04c _pthread_workq_return + 45
2   libsystem_c.dylib                       0x99129e19 _pthread_wqthread + 448
3   libsystem_c.dylib                       0x99111cca start_wqthread + 30
Thread 3:
0   libsystem_kernel.dylib                  0x98a8b0ee __workq_kernreturn + 10
1   libsystem_c.dylib                       0x9912a04c _pthread_workq_return + 45
2   libsystem_c.dylib                       0x99129e19 _pthread_wqthread + 448
3   libsystem_c.dylib                       0x99111cca start_wqthread + 30
Thread 4:
0   libsystem_kernel.dylib                  0x98a8b0ee __workq_kernreturn + 10
1   libsystem_c.dylib                       0x9912a04c _pthread_workq_return + 45
2   libsystem_c.dylib                       0x99129e19 _pthread_wqthread + 448
3   libsystem_c.dylib                       0x99111cca start_wqthread + 30
Thread 5 Crashed:
0   rapportd                                0x0002c66c threaded_service::main(void*) + 208
1   libsystem_c.dylib                       0x99127557 _pthread_start + 344
2   libsystem_c.dylib                       0x99111cee thread_start + 34
Thread 5 crashed with X86 Thread State (32-bit):
eax: 0x00000900 ebx: 0x0002c5a7 ecx: 0xbffff894 edx: 0xbffff88c
edi: 0xbffff898 esi: 0x00012868 ebp: 0xb030af98 esp: 0xb030af40
   ss: 0x00000023 efl: 0x00010202 eip: 0x0002c66c   cs: 0x0000001b
   ds: 0x00000023   es: 0x00000023   fs: 0x00000023   gs: 0x0000000f
cr2: 0x00000920
Logical CPU: 0
Binary Images:
    0x1000 -    0x64fef +rapportd (???) <322EF040-125E-3D79-4A2F-01BB8B1415E9> /Library/Rapport/*/rapportd
   0xaf000 -   0x147ff7 +RapportWR.dylib (1) <A50472EA-F9E8-3C45-E173-216263532AEC> /Library/Rapport/*/RapportWR.dylib
0x16e000 -   0x2faffb +RapportUtil1.dylib (1) <087D94DE-7376-A5E6-C000-2895F7D0AA60> /Library/Rapport/*/RapportUtil1.dylib
0x3f8000 -   0x420fef +librooksbas.dylib (1) <75079BEF-ED76-12F6-5973-3B4584AFA1E4> /Library/Rapport/*/librooksbas.dylib
0x718000 -   0x725ffb com.apple.Librarian (1.1 - 1) <C8D82AA3-AE5E-3B6D-A8D1-847856057186> /System/Library/PrivateFrameworks/Librarian.framework/Versions/A/Librarian
0x732000 -   0x733fff +com.ecamm.pluginloader (Ecamm Plugin Loader v1.0.5 - 1.0.5) /Library/InputManagers/*/Ecamm Plugin Loader.bundle/Contents/MacOS/Ecamm Plugin Loader
0x8fe77000 - 0x8fea9e57 dyld (210.2.3) <23516BE4-29BE-350C-91C9-F36E7999F0F1> /usr/lib/dyld
0x9000e000 - 0x9001bff7 com.apple.AppleFSCompression (49 - 1.0) <166AA1F8-E50A-3533-A3B5-8737C5118CC3> /System/Library/PrivateFrameworks/AppleFSCompression.framework/Versions/A/Apple FSCompression
0x90135000 - 0x90135fff libkeymgr.dylib (25) <D5E93F7F-9315-3AD6-92C7-941F7B54C490> /usr/lib/system/libkeymgr.dylib
0x90294000 - 0x90294fff libSystem.B.dylib (169.3) <4F99C03B-BBFF-3BF8-8CC2-2DA764447446> /usr/lib/libSystem.B.dylib
0x90295000 - 0x90295fff com.apple.Carbon (154 - 155) <604ADD9D-5835-3294-842E-3A4AEBCCB548> /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon
0x90296000 - 0x90296fff com.apple.Accelerate (1.8 - Accelerate 1.8) <4EC0548E-3A3F-310D-A366-47B51D5B6398> /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate
0x90297000 - 0x90679ff7 com.apple.HIToolbox (2.0 - 624) <04C20B6A-FE3D-396E-BCAF-AC4DBAB3747E> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.fra mework/Versions/A/HIToolbox
0x90acc000 - 0x90b30ff3 libstdc++.6.dylib (56) <F8FA490A-8F3C-3645-ABF5-78926CE9C62C> /usr/lib/libstdc++.6.dylib
0x90b3f000 - 0x90db9ff3 com.apple.RawCamera.bundle (3.14.2 - 644) <3A5383AC-F30A-3674-88F4-DF82ADE8D73E> /System/Library/CoreServices/RawCamera.bundle/Contents/MacOS/RawCamera
0x90dba000 - 0x90dc7fff libGL.dylib (8.5) <B411046C-3068-3A22-B3F1-9E78C5888232> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib
0x90dc8000 - 0x90e5affb libvMisc.dylib (380.6) <6DA3A03F-20BE-300D-A664-B50A7B4E4B1A> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libvMisc.dylib
0x90e5b000 - 0x90f05ff7 com.apple.LaunchServices (539 - 539) <4C026504-5420-35D7-912E-A584C6F9FFC6> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchS ervices.framework/Versions/A/LaunchServices
0x90f06000 - 0x90f4bff7 com.apple.NavigationServices (3.7 - 200) <F6531764-6E43-3AF3-ACDD-8A5551EF016A> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/NavigationSer vices.framework/Versions/A/NavigationServices
0x9114e000 - 0x91158fff com.apple.speech.recognition.framework (4.1.5 - 4.1.5) <B855E8B4-2EE3-3BFF-8547-98A0F084F9AF> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SpeechRecogni tion.framework/Versions/A/SpeechRecognition
0x91159000 - 0x911b6fff com.apple.audio.CoreAudio (4.1.0 - 4.1.0) <9549B81F-4425-34EE-802B-F462068DC0C5> /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio
0x911c3000 - 0x911cafff liblaunch.dylib (442.21) <349330F8-1BBF-3B78-AFB2-4F32413CE971> /usr/lib/system/liblaunch.dylib
0x911cb000 - 0x91219ffb com.apple.SystemConfiguration (1.12 - 1.12) <5859B368-4118-3755-A197-0A8172514ADA> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfi guration
0x9121a000 - 0x9121effe libcache.dylib (57) <834FDCA7-FE3B-33CC-A12A-E11E202477EC> /usr/lib/system/libcache.dylib
0x9121f000 - 0x91220fff libsystem_sandbox.dylib (220) <4E42390B-25EC-3530-AF01-337E430C16EB> /usr/lib/system/libsystem_sandbox.dylib
0x91223000 - 0x91279ff3 com.apple.HIServices (1.20 - 416) <C52A00FD-76D6-34F3-95D1-7EDB857EC5E5> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ HIServices.framework/Versions/A/HIServices
0x912b7000 - 0x913afff2 libsqlite3.dylib (138) <AA00F27E-B72D-31DE-8EE4-985227CC9912> /usr/lib/libsqlite3.dylib
0x913b0000 - 0x913b2ffb libRadiance.dylib (843) <6C2B92DB-A537-3618-9E68-F006DF427D2F> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libRadiance.d ylib
0x913b3000 - 0x913f7fff libGLU.dylib (8.5) <DC69992A-2547-38FF-ABD1-BDE19EA75C08> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLU.dylib
0x91428000 - 0x9144aff3 libc++abi.dylib (24.2) <4C064BFE-B8B4-35CA-AB3C-F6A47D47A0F2> /usr/lib/libc++abi.dylib
0x91571000 - 0x91571ffd com.apple.audio.units.AudioUnit (1.8 - 1.8) <B688A998-93B5-3D9B-BAE4-E49947AA82B4> /System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit
0x91572000 - 0x915b3ff7 libcups.2.dylib (327) <F46F8703-FEAE-3442-87CB-45C8BF98BEE5> /usr/lib/libcups.2.dylib
0x915b4000 - 0x915c2fff com.apple.opengl (1.8.5 - 1.8.5) <8EB6DEE7-7248-3644-B840-35174755C356> /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL
0x915c3000 - 0x91625fff libc++.1.dylib (65.1) <C0CFF9FF-5D52-3EAE-B921-6AE1DA00A135> /usr/lib/libc++.1.dylib
0x91651000 - 0x91a09ffa libLAPACK.dylib (1073.3) <0F813868-D84F-365D-8A7B-67FDA169F19C> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libLAPACK.dylib
0x91a0d000 - 0x91e2aff3 FaceCoreLight (2.0.1) <3EF03B25-C361-31A6-8704-3FBFFBD0E10B> /System/Library/PrivateFrameworks/FaceCoreLight.framework/Versions/A/FaceCoreLi ght
0x91e30000 - 0x91e54fff libJPEG.dylib (843) <04383F74-067F-3E98-882F-21F5B9578984> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJPEG.dylib
0x91f89000 - 0x92087ff7 libFontParser.dylib (84.5) <B3006327-7B2D-3966-A56A-BD85F1D71641> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ATS.framework/Versions/A/Resources/libFontParser.dylib
0x92088000 - 0x9208cffc libGIF.dylib (843) <355B672B-D07D-36FE-B6B9-142406ACFBA2> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libGIF.dylib
0x9219e000 - 0x9245bff3 com.apple.security (7.0 - 55178.0.1) <EB90D52E-27EC-3874-BA15-C69976F1067A> /System/Library/Frameworks/Security.framework/Versions/A/Security
0x9249f000 - 0x924fafff com.apple.htmlrendering (77 - 1.1.4) <5C0C669F-AE07-3983-B38F-EB829B5CE609> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HTMLRendering .framework/Versions/A/HTMLRendering
0x924fb000 - 0x9253aff7 com.apple.bom (12.0 - 192) <0637E52C-D151-37B3-904F-8656B2FD44DD> /System/Library/PrivateFrameworks/Bom.framework/Versions/A/Bom
0x9253b000 - 0x92589ffb libFontRegistry.dylib (100) <3B8350C2-4D8F-38C4-A22E-2F855D7E83D1> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ATS.framework/Versions/A/Resources/libFontRegistry.dylib
0x9258a000 - 0x925bbff7 com.apple.DictionaryServices (1.2 - 184) <9199E88F-2477-3596-9F56-B8E317A7164D> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Diction aryServices.framework/Versions/A/DictionaryServices
0x925bc000 - 0x92745ff7 com.apple.vImage (6.0 - 6.0) <1D1F67FE-4F75-3689-BEF6-4A46C8039E70> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.fr amework/Versions/A/vImage
0x92746000 - 0x92750fff libsystem_notify.dylib (98.5) <7EEE9475-18F8-3099-B0ED-23A3E528ABE0> /usr/lib/system/libsystem_notify.dylib
0x92751000 - 0x92771ff7 com.apple.ChunkingLibrary (2.0 - 132) <172C3F7F-CB49-323F-932F-35340999979E> /System/Library/PrivateFrameworks/ChunkingLibrary.framework/Versions/A/Chunking Library
0x92772000 - 0x92a77fff com.apple.CoreServices.CarbonCore (1037 - 1037) <92494ADA-2ED1-3141-81B9-23F2C27E779C> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonC ore.framework/Versions/A/CarbonCore
0x92fbb000 - 0x92fbffff com.apple.OpenDirectory (10.8 - 151.10) <A1858D81-086F-3BF5-87E3-9B70409FFDF6> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/OpenDirectory
0x93003000 - 0x930c1ff3 com.apple.ColorSync (4.8.0 - 4.8.0) <EFEDCB37-4F20-3CEC-A185-5D2976E11BAC> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ColorSync.framework/Versions/A/ColorSync
0x930c2000 - 0x93162ff7 com.apple.QD (3.42 - 285) <1B8307C6-AFA8-312E-BA5B-679070EF2CA1> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ QD.framework/Versions/A/QD
0x93163000 - 0x931affff libcorecrypto.dylib (106) <FAAD1A30-0D84-3A17-AC40-288EF0F529AA> /usr/lib/system/libcorecrypto.dylib
0x93208000 - 0x93dc1fff com.apple.AppKit (6.8 - 1187) <5E13B150-4096-3B61-9DC0-6ABA48F6515B> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
0x93dc2000 - 0x93e04ff7 libauto.dylib (185.1) <B2B5B639-6778-352A-828D-FD8B64A3E8B3> /usr/lib/libauto.dylib
0x94492000 - 0x94501ffb com.apple.Heimdal (3.0 - 2.0) <1ABF438B-30E6-3165-968C-E2EA1A9DF1FD> /System/Library/PrivateFrameworks/Heimdal.framework/Versions/A/Heimdal
0x94502000 - 0x9461dff7 com.apple.desktopservices (1.7.1 - 1.7.1) <0039FBAA-BB0B-36B7-962F-BDAC8E3D1C58> /System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/Desk topServicesPriv
0x94994000 - 0x94994fff com.apple.ApplicationServices (45 - 45) <677C4ACC-9D12-366F-8A87-B898AC806DD9> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Application Services
0x949cb000 - 0x949ceffb com.apple.TCC (1.0 - 1) <C1B2A1EB-9EA2-3340-8611-F788C87A951F> /System/Library/PrivateFrameworks/TCC.framework/Versions/A/TCC
0x9524c000 - 0x952b2fff com.apple.print.framework.PrintCore (8.0 - 387) <84DFC4F0-3186-3C59-9EBD-9EF2C3561A43> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ PrintCore.framework/Versions/A/PrintCore
0x952b3000 - 0x952b3fff com.apple.Accelerate.vecLib (3.8 - vecLib 3.8) <908B8D40-3FB5-3047-B482-3DF95025ECFC> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/vecLib
0x952b4000 - 0x952f9ff5 com.apple.opencl (2.1.17 - 2.1.17) <921C1549-637A-33D7-A891-834FB9F582C7> /System/Library/Frameworks/OpenCL.framework/Versions/A/OpenCL
0x952fa000 - 0x9531efff com.apple.PerformanceAnalysis (1.16 - 16) <18DE0F9F-1264-394D-AC56-6B2A1771DFBE> /System/Library/PrivateFrameworks/PerformanceAnalysis.framework/Versions/A/Perf ormanceAnalysis
0x9531f000 - 0x95497ff5 com.apple.QuartzCore (1.8 - 304.0) <0B0EC55A-9084-3E28-9A84-1813CE3FAA9B> /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore
0x95498000 - 0x9549bffd libCoreVMClient.dylib (24.4) <C54E8FD0-61EC-3DC8-8631-54288AC66AC8> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreVMClien t.dylib
0x95516000 - 0x95958ff3 com.apple.CoreGraphics (1.600.0 - 322) <2E04AAAD-8403-3819-BD6C-9836D42F58B1> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/CoreGraphics
0x95959000 - 0x9595bfff com.apple.securityhi (4.0 - 55002) <15E9B9BC-108F-3416-A0A7-A321A85081F7> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SecurityHI.fr amework/Versions/A/SecurityHI
0x95d59000 - 0x95d5cfff com.apple.help (1.3.2 - 42) <AD7EB1F0-A068-3A2C-9D59-38E59CEC0D96> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Help.framewor k/Versions/A/Help
0x95d5d000 - 0x95d6bfff libxar.1.dylib (105) <343E4A3B-1D04-34A3-94C2-8C7C9A8F736B> /usr/lib/libxar.1.dylib
0x95d6c000 - 0x95d6dffd com.apple.TrustEvaluationAgent (2.0 - 23) <E42347C0-2D3C-36A4-9200-757FFA61B388> /System/Library/PrivateFrameworks/TrustEvaluationAgent.framework/Versions/A/Tru stEvaluationAgent
0x95d78000 - 0x95dedff7 com.apple.ApplicationServices.ATS (332 - 341) <EC79D064-1399-3F33-BACC-6D93A5BE04E6> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ATS.framework/Versions/A/ATS
0x95e03000 - 0x95e5aff7 com.apple.ScalableUserInterface (1.0 - 1) <2B5E454B-BC49-3E85-B54D-1950397C448C> /System/Library/Frameworks/QuartzCore.framework/Versions/A/Frameworks/ScalableU serInterface.framework/Versions/A/ScalableUserInterface
0x95e5b000 - 0x95e5bfff libsystem_blocks.dylib (59) <3A743C5D-CFA5-37D8-80A8-B6795A9DB04F> /usr/lib/system/libsystem_blocks.dylib
0x95eb3000 - 0x95f66ff7 com.apple.coreui (2.0 - 181) <4F071012-F857-367D-B0B8-EAD088A05740> /System/Library/PrivateFrameworks/CoreUI.framework/Versions/A/CoreUI
0x95faf000 - 0x95fbdff7 libz.1.dylib (43) <245F1B61-2276-3BBB-9891-99934116D833> /usr/lib/libz.1.dylib
0x95fbe000 - 0x962dbfff com.apple.Foundation (6.8 - 945) <B6F00754-C3F7-3E33-B708-CCEA2AA3E969> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
0x962dc000 - 0x962e4fff com.apple.DiskArbitration (2.5 - 2.5) <E49427B0-5317-3DFD-B12E-117402BB19CB> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration
0x962e5000 - 0x962f3ff3 libsystem_network.dylib (77.10) <7FBF5A15-97BA-3721-943E-E77F0C40DBE1> /usr/lib/system/libsystem_network.dylib
0x969fc000 - 0x96bb8ffd libicucore.A.dylib (491.11.1) <DB04A8FD-9BBE-3CBC-869F-8FA855FB43D2> /usr/lib/libicucore.A.dylib
0x96bb9000 - 0x96bc9ff2 com.apple.LangAnalysis (1.7.0 - 1.7.0) <875363E7-6D02-3229-A9DD-E5A5568A7D61> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ LangAnalysis.framework/Versions/A/LangAnalysis
0x96bca000 - 0x96bd3ffd com.apple.audio.SoundManager (4.0 - 4.0) <ABC5FE40-B222-36EB-9905-5C8C4BFD8C87> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CarbonSound.f ramework/Versions/A/CarbonSound
0x96eeb000 - 0x96f01fff com.apple.CFOpenDirectory (10.8 - 151.10) <56C3F276-BD1F-3031-8CF9-8F4F481A534E> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/Frameworks/CFOpen Directory.framework/Versions/A/CFOpenDirectory
0x96f02000 - 0x96f02fff com.apple.CoreServices (57 - 57) <956C6C6D-A5DD-314F-9C57-4A61D41F30CE> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
0x96f34000 - 0x96f35fff liblangid.dylib (116) <E13CC8C5-5034-320A-A210-41A2BDE4F846> /usr/lib/liblangid.dylib
0x96f36000 - 0x9708dff7 com.apple.audio.toolbox.AudioToolbox (1.8 - 1.8) <6856CA9B-BF08-341B-AEE9-91CC258D4534> /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox
0x970b4000 - 0x970b8fff com.apple.CommonPanels (1.2.5 - 94) <6B3E7E53-7708-3DA2-8C50-59C2B4735DE1> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CommonPanels. framework/Versions/A/CommonPanels
0x970b9000 - 0x970bbfff libCVMSPluginSupport.dylib (8.5) <A91DC66E-5A16-31AC-9B6A-605292573281> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCVMSPluginS upport.dylib
0x97107000 - 0x97113ff7 com.apple.NetAuth (4.0 - 4.0) <4983C4B8-9D95-3C4D-897E-07743326487E> /System/Library/PrivateFrameworks/NetAuth.framework/Versions/A/NetAuth
0x97114000 - 0x97199ff7 com.apple.SearchKit (1.4.0 - 1.4.0) <454E950F-291C-3E95-8F35-05CA0AD6B327> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchK it.framework/Versions/A/SearchKit
0x9719a000 - 0x9719affd libOpenScriptingUtil.dylib (148) <6B34E8E4-EE31-3E2B-AEB3-8714C3102AED> /usr/lib/libOpenScriptingUtil.dylib
0x9719b000 - 0x97249ff3 com.apple.CoreText (260.0 - 275.14) <3CC31B7F-5560-364A-ADFC-31861C3C2328> /System/Library/Frameworks/CoreText.framework/Versions/A/CoreText
0x97264000 - 0x9729affb com.apple.DebugSymbols (98 - 98) <9A9ADA0A-E487-3C8F-9998-286EE04C235A> /System/Library/PrivateFrameworks/DebugSymbols.framework/Versions/A/DebugSymbol s
0x9729b000 - 0x972eaff6 libTIFF.dylib (843) <AA81BA16-8026-35DA-8193-2C8715ACD435> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libTIFF.dylib
0x972ef000 - 0x972f0fff libquarantine.dylib (52) <D526310F-DC77-37EA-8F5F-83928EFA3262> /usr/lib/system/libquarantine.dylib
0x972f1000 - 0x97388fff com.apple.ink.framework (1.4 - 110) <C01F2572-E7E4-3A6C-B4F2-2F97B4AD43D5> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Ink.framework /Versions/A/Ink
0x9738d000 - 0x9738effd libunc.dylib (25) <58599CBF-E262-3CEA-AFE1-35560E0177DC> /usr/lib/system/libunc.dylib
0x9738f000 - 0x97393fff com.apple.IOSurface (86.0.2 - 86.0.2) <BDF93CE4-9F14-3747-9CD5-FFE71D488BDA> /System/Library/Frameworks/IOSurface.framework/Versions/A/IOSurface
0x97394000 - 0x973c1ffb com.apple.CoreServicesInternal (153 - 153) <DB105788-CCF5-3678-88C5-65A7267DC581> /System/Library/PrivateFrameworks/CoreServicesInternal.framework/Versions/A/Cor eServicesInternal
0x973ce000 - 0x973d1ff7 libcompiler_rt.dylib (30) <CE5DBDB4-0124-3E2B-9105-989DF98DD108> /usr/lib/system/libcompiler_rt.dylib
0x973d2000 - 0x973d2fff com.apple.vecLib (3.8 - vecLib 3.8) <83160DD1-5614-3E34-80EB-97041016EF1F> /System/Library/Frameworks/vecLib.framework/Versions/A/vecLib
0x97435000 - 0x97635ffb com.apple.CoreData (106 - 407.5) <B4386286-5C67-3134-A5BD-852447DA696E> /System/Library/Frameworks/CoreData.framework/Versions/A/CoreData
0x97636000 - 0x9763dff3 com.apple.NetFS (5.0 - 4.0) <1F7041F2-4E97-368C-8F5D-24153D81BBDB> /System/Library/Frameworks/NetFS.framework/Versions/A/NetFS
0x97680000 - 0x976a4ff2 com.apple.framework.familycontrols (4.0 - 400) <A313D83E-5A03-3174-A213-1F7D379040D1> /System/Library/PrivateFrameworks/FamilyControls.framework/Versions/A/FamilyCon trols
0x976a5000 - 0x976a6fff libdnsinfo.dylib (453.16) <6441AEC9-3916-3BF6-BE54-9C25E2BE61E1> /usr/lib/system/libdnsinfo.dylib
0x976a7000 - 0x97938ffb com.apple.CoreImage (8.0.17 - 1.0.1) <CE54EC11-1C41-3857-B82D-F8B7D1798F42> /System/Library/Frameworks/QuartzCore.framework/Versions/A/Frameworks/CoreImage .framework/Versions/A/CoreImage
0x97939000 - 0x9794bfff libbsm.0.dylib (32) <DADD385E-FE53-3458-94FB-E316A6345108> /usr/lib/libbsm.0.dylib
0x97996000 - 0x97aa315f libobjc.A.dylib (532) <9663A040-F232-3E2A-8318-AA40B940AF6F> /usr/lib/libobjc.A.dylib
0x97aa4000 - 0x97b95ffc libiconv.2.dylib (34) <B096A9B7-83A6-31B3-8D2F-87D91910BF4C> /usr/lib/libiconv.2.dylib
0x97b9d000 - 0x97ca8ff7 libJP2.dylib (843) <D8FE1E1C-D4DC-3465-95C4-AEADD6C2611C> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJP2.dylib
0x97d41000 - 0x97d58fff com.apple.GenerationalStorage (1.1 - 132.1) <4E0F0C47-7796-3152-A77D-F6456287498A> /System/Library/PrivateFrameworks/GenerationalStorage.framework/Versions/A/Gene rationalStorage
0x97d59000 - 0x97d65ff8 libbz2.1.0.dylib (29) <7031A4C0-784A-3EAA-93DF-EA1F26CC9264> /usr/lib/libbz2.1.0.dylib
0x97da9000 - 0x97e03fff com.apple.Symbolication (1.3 - 93) <D327EEFF-F2F5-39C4-B1EC-32E259DC04F1> /System/Library/PrivateFrameworks/Symbolication.framework/Versions/A/Symbolicat ion
0x97e04000 - 0x97e10ffd com.apple.CrashReporterSupport (10.8.1 - 412) <9BBEBED1-DEDD-3258-A8CC-F46EC5CDD4F7> /System/Library/PrivateFrameworks/CrashReporterSupport.framework/Versions/A/Cra shReporterSupport
0x97e14000 - 0x97e27ff9 com.apple.MultitouchSupport.framework (235.27 - 235.27) <75D9C0FD-6A40-3A9E-8861-C74DBE137CF3> /System/Library/PrivateFrameworks/MultitouchSupport.framework/Versions/A/Multit ouchSupport
0x97e82000 - 0x97e9ffff com.apple.openscripting (1.3.5 - 148) <3460338D-B686-3C33-B322-DC8391668F8A> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/OpenScripting .framework/Versions/A/OpenScripting
0x97ea0000 - 0x97eacffc libkxld.dylib (2050.9.2) <301804CB-55F1-3A9B-BC45-DEB020C22C6F> /usr/lib/system/libkxld.dylib
0x97eb7000 - 0x97ec1ffc com.apple.bsd.ServiceManagement (2.0 - 2.0) <D3112172-D3A7-3C9A-825D-5630D47327D1> /System/Library/Frameworks/ServiceManagement.framework/Versions/A/ServiceManage ment
0x97ef4000 - 0x97f11fff libCRFSuite.dylib (33) <C9D72D0C-871A-39A2-8AFB-682D11AE7D0D> /usr/lib/libCRFSuite.dylib
0x97f8f000 - 0x97fabff7 libPng.dylib (843) <43C3DD20-4BB2-3429-A40A-7FF9BC50E5FB> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libPng.dylib
0x97fac000 - 0x98095ff7 libxml2.2.dylib (22.3) <015A4FA6-5BB9-3F95-AFB8-B9281E22685B> /usr/lib/libxml2.2.dylib
0x98096000 - 0x9809aff7 libmacho.dylib (829) <5280A013-4F74-3F74-BE0C-7F612C49F1DC> /usr/lib/system/libmacho.dylib
0x9809b000 - 0x980a4ff9 com.apple.CommonAuth (3.0 - 2.0) <A1A6CC3D-AA88-3519-A305-9B5D76C5D63B> /System/Library/PrivateFrameworks/CommonAuth.framework/Versions/A/CommonAuth
0x980f1000 - 0x9810efff libxpc.dylib (140.37) <F61095FA-B2CF-3CD8-9088-9D9FC18B38BC> /usr/lib/system/libxpc.dylib
0x9810f000 - 0x9824aff7 libBLAS.dylib (1073.3) <804B5AF7-2646-31D1-8875-FCCF158476D4> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libBLAS.dylib
0x9824b000 - 0x982e3ff7 com.apple.CoreServices.OSServices (557 - 557) <F7CDD65A-3D2E-3AAE-BD55-4C604C9D1709> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServi ces.framework/Versions/A/OSServices
0x982e4000 - 0x982e5fff libDiagnosticMessagesClient.dylib (7) <B2BC685E-C129-3F6B-9222-AF3CF4F186AC> /usr/lib/libDiagnosticMessagesClient.dylib
0x982e6000 - 0x98313ffe libsystem_m.dylib (3022.6) <9975D9C3-3B71-38E3-AA21-C5C5F9D9C431> /usr/lib/system/libsystem_m.dylib
0x98314000 - 0x98315fff libremovefile.dylib (23.1) <98622D14-DAAB-3AD8-A5D9-C322BF572A98> /usr/lib/system/libremovefile.dylib
0x985a8000 - 0x985cdff7 com.apple.CoreVideo (1.8 - 99.0) <7A90C337-4493-3393-9C56-75EB52112D75> /System/Library/Frameworks/CoreVideo.framework/Versions/A/CoreVideo
0x985fd000 - 0x98665fe7 libvDSP.dylib (380.6) <55780308-4DCA-3B10-9703-EAFC3E13A3FA> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libvDSP.dylib
0x98784000 - 0x9879dfff com.apple.Kerberos (2.0 - 1) <9BDE8F4D-DBC3-34D1-852C-898D3655A611> /System/Library/Frameworks/Kerberos.framework/Versions/A/Kerberos
0x9879e000 - 0x988eaff3 com.apple.CFNetwork (596.1 - 596.1) <DE5FA267-6E01-388E-9ADA-8764BE469C35> /System/Library/Frameworks/CFNetwork.framework/Versions/A/CFNetwork
0x988ec000 - 0x98909ff7 libresolv.9.dylib (51) <B9742A2A-DF15-3F6E-8FCE-778A58214B3A> /usr/lib/libresolv.9.dylib
0x9890a000 - 0x98911fff libsystem_dnssd.dylib (379.27.1) <B5CD3F39-7039-30CF-877D-FDF38A659E46> /usr/lib/system/libsystem_dnssd.dylib
0x98912000 - 0x98912fff com.apple.Cocoa (6.7 - 19) <354094F0-F36B-36F9-BF5F-FD60590FBEB9> /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa
0x98913000 - 0x98946ff3 com.apple.GSS (3.0 - 2.0) <B1D719C1-B000-3BE3-B747-329D608585DD> /System/Library/Frameworks/GSS.framework/Versions/A/GSS
0x98947000 - 0x989a0ff7 com.apple.AE (645 - 645) <D4919967-EF16-36BA-9E8A-DA110DE8BB4A> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.fram ework/Versions/A/AE
0x989a1000 - 0x98a1dffb com.apple.Metadata (10.7.0 - 707.1) <E18350AD-CAA9-3323-BDE9-63A688792C6C> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadat a.framework/Versions/A/Metadata
0x98a1e000 - 0x98a26fff com.apple.CommerceCore (1.0 - 26) <AF0D1990-8CBF-3AB4-99DF-8B7AE14FB0D5> /System/Library/PrivateFrameworks/CommerceKit.framework/Versions/A/Frameworks/C ommerceCore.framework/Versions/A/CommerceCore
0x98a27000 - 0x98a62fe7 libGLImage.dylib (8.5) <D2589E82-41ED-383D-9254-6D12A3A20644> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLImage.dyl ib
0x98a63000 - 0x98a6efff libcommonCrypto.dylib (60026) <A6C6EDB8-7E69-3827-81F3-9A74D0935461> /usr/lib/system/libcommonCrypto.dylib
0x98a6f000 - 0x98a75fff libGFXShared.dylib (8.5) <7022CE54-70E9-33D3-B679-9A9BB6B2AABF> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGFXShared.d ylib
0x98a76000 - 0x98a90ffc libsystem_kernel.dylib (2050.9.2) <C6BA5A9F-08BB-3544-9A36-070DEDE92279> /usr/lib/system/libsystem_kernel.dylib
0x98a91000 - 0x98b0bff7 com.apple.securityfoundation (6.0 - 55115.4) <7F614418-F853-3FED-B265-0EA47F309A49> /System/Library/Frameworks/SecurityFoundation.framework/Versions/A/SecurityFoun dation
0x98b0c000 - 0x98b21fff com.apple.speech.synthesis.framework (4.1.10 - 4.1.10) <20E394D6-D9BA-3C1D-993A-533B60EF3B63> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ SpeechSynthesis.framework/Versions/A/SpeechSynthesis
0x98b22000 - 0x98bbcfff com.apple.CoreSymbolication (3.0 - 87) <6A27BBE5-6EF0-3D5D-A485-2145826B9796> /System/Library/PrivateFrameworks/CoreSymbolication.framework/Versions/A/CoreSy mbolication
0x98bd5000 - 0x98ce2ffb com.apple.ImageIO.framework (3.2.0 - 843) <4BFEFB05-3EE3-36A7-891D-CE03D1DF8125> /System/Library/Frameworks/ImageIO.framework/Versions/A/ImageIO
0x98dc7000 - 0x98e9bff7 com.apple.backup.framework (1.4 - 1.4) <12123FB8-B42D-38B0-8463-6BA375C3C643> /System/Library/PrivateFrameworks/Backup.framework/Versions/A/Backup
0x98e9c000 - 0x98ea4fff libcopyfile.dylib (89) <4963541B-0254-371B-B29A-B6806888949B> /usr/lib/system/libcopyfile.dylib
0x98ea5000 - 0x98eacffb libunwind.dylib (35.1) <E1E8D8B3-3C78-3AB1-B398-C180DC6DCF05> /usr/lib/system/libunwind.dylib
0x98ead000 - 0x98f11fff com.apple.datadetectorscore (4.0 - 269.1) <4D155F09-1A60-325A-BCAC-1B858C2C051B> /System/Library/PrivateFrameworks/DataDetectorsCore.framework/Versions/A/DataDe tectorsCore
0x98f12000 - 0x98f15ffc libpam.2.dylib (20) <FCF74195-A99E-3B07-8E49-688D4A6F1E18> /usr/lib/libpam.2.dylib
0x98f16000 - 0x990fdffb com.apple.CoreFoundation (6.8 - 744) <A2BB4949-264A-302B-897E-713860894FE6> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
0x99111000 - 0x991ceffb libsystem_c.dylib (825.24) <7D90CAC5-EC98-35F8-A52E-81B54F0C7DCC> /usr/lib/system/libsystem_c.dylib
0x991cf000 - 0x991d1fff libdyld.dylib (210.2.3) <05D6FF2A-F09B-309D-95F7-7AF10259C707> /usr/lib/system/libdyld.dylib
0x991d2000 - 0x99214ff7 com.apple.RemoteViewServices (2.0 - 80.3) <EE36AF6C-E574-3F48-9AC3-E8C8295739FF> /System/Library/PrivateFrameworks/RemoteViewServices.framework/Versions/A/Remot eViewServices
0x99215000 - 0x9921bfff com.apple.print.framework.Print (8.0 - 258) <12AEAD24-6924-3923-9E4A-C5D21231E639> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Print.framewo rk/Versions/A/Print
0x9921f000 - 0x99231ff7 libdispatch.dylib (228.18) <833C83BE-278C-353E-AC6D-9B85FAC50A1D> /usr/lib/system/libdispatch.dylib
0x99232000 - 0x99247fff com.apple.ImageCapture (8.0 - 8.0) <B8BD421F-D5A9-3FB4-8E89-AD5CFC0D4030> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/ImageCapture. framework/Versions/A/ImageCapture
0x994c5000 - 0x994eefff libxslt.1.dylib (11.3) <0DE17DAA-66FF-3195-AADB-347BEB5E2EFA> /usr/lib/libxslt.1.dylib
0x995e7000 - 0x9964eff7 com.apple.framework.IOKit (2.0 - 755.9.7) <CB976A7C-2601-3054-BC41-C3AD6896327C> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
0x9964f000 - 0x9967bff7 libsystem_info.dylib (406.17) <AA5611DB-A944-3072-B6BE-ACAB08689547> /usr/lib/system/libsystem_info.dylib
0x9a61f000 - 0x9a63dffb com.apple.Ubiquity (1.2 - 234.2) <BEFF43DE-CF72-3E66-90C8-CAECAFD5F3ED> /System/Library/PrivateFrameworks/Ubiquity.framework/Versions/A/Ubiquity
External Modification Summary:
Calls made by other processes targeting this process:
    task_for_pid: 2
    thread_create: 0
    thread_set_state: 0
Calls made by this process:
    task_for_pid: 0
    thread_create: 0
    thread_set_state: 0
Calls made by all processes on this machine:
    task_for_pid: 318
    thread_create: 0
    thread_set_state: 0
VM Region Summary:
ReadOnly portion of Libraries: Total=120.4M resident=73.0M(61%) swapped_out_or_unallocated=47.4M(39%)
Writable regions: Total=92.1M written=1476K(2%) resident=1836K(2%) swapped_out=0K(0%) unallocated=90.3M(98%)
REGION TYPE                      VIRTUAL
===========                      =======
CG shared images                     96K
CoreServices                       1472K
MALLOC                             81.3M
MALLOC guard page                    48K
Memory tag=35                      7256K
Stack                              66.5M
VM_ALLOCATE                          56K
__DATA                             5584K
__DATA/__OBJC                       160K
__IMAGE                             528K
__IMPORT                              8K
__LINKEDIT                         32.4M
__OBJC                             1492K
__PAGEZERO                            4K
__TEXT                             88.0M
__UNICODE                           544K
mapped file                        99.4M
shared memory                       308K
===========                      =======
TOTAL                             384.8M
Model: MacBookPro8,2, BootROM MBP81.0047.B27, 4 processors, Intel Core i7, 2.4 GHz, 16 GB, SMC 1.69f3
Graphics: Intel HD Graphics 3000, Intel HD Graphics 3000, Built-In, 512 MB
Graphics: AMD Radeon HD 6770M, AMD Radeon HD 6770M, PCIe, 1024 MB
Memory Module: BANK 0/DIMM0, 8 GB, DDR3, 1333 MHz, 0x859B, 0x43543130323436344246313333392E4D3136
Memory Module: BANK 1/DIMM0, 8 GB, DDR3, 1333 MHz, 0x859B, 0x43543130323436344246313333392E4D3136
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0xD6), Broadcom BCM43xx 1.0 (5.106.98.81.21)
Bluetooth: Version 4.0.9f8 10405, 2 service, 11 devices, 1 incoming serial ports
Network Service: Ethernet, Ethernet, en0
Serial ATA Device: TOSHIBA MK7559GSXF, 750.16 GB
Serial ATA Device: HL-DT-ST DVDRW GS31N
USB Device: FaceTime HD Camera (Built-in), apple_vendor_id, 0x8509, 0xfa200000 / 3
USB Device: hub_device, 0x0424 (SMSC), 0x2513, 0xfa100000 / 2
USB Device: Apple Internal Keyboard / Trackpad, apple_vendor_id, 0x0253, 0xfa120000 / 5
USB Device: BRCM2070 Hub, 0x0a5c (Broadcom Corp.), 0x4500, 0xfa110000 / 4
USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x821a, 0xfa113000 / 8
USB Device: hub_device, 0x0424 (SMSC), 0x2513, 0xfd100000 / 2
USB Device: IR Receiver, apple_vendor_id, 0x8242, 0xfd110000 / 3

For anybody whomay stumble across this post- it is an addendum to the originalpost
Just to be sure it is an APPLE SOFTWARE ISSUE - ProbablySafari---I used my mac mini ( with mountain lion ) and-- it too drops wifi-- and the end result is
SAFARI CANNOT CONNECT TO SERVER lol
the app store hangs and hangs and hangs
as it does my macbook pro -- they BOTH have to be restarted-- then it is okay for a little while
THIS IS SO ANNOYING ha ha-- in this instance caps does mean I am yelling lol

Battery, Power, Deep Sleep and Spotlight problems after 10.9.4 update

Hi, I have a Macbook Pro 8,1 13in (Late 2011). I updated to the latest version of Mavericks (10.9.4) and iTunes on Sunday, right after that my macbook started to goes into Deep Sleep after closing the lid, even when the battery was 80% of charge. My battery normally lasts for almost 5 hours. After it went to deep sleep, the power bottom does not respond. Also, I have noticed that spotlight process in Monitor was consuming so huge amount of resources. This problem persists in Boot Camp. There is no way to turn the machine up without plugging it to the power cord. Sometimes it charges the battery as usual, sometimes it does not recognize the battery. Suddenly, the mac goes into sleep mode while I'm using it.
I have researching and troubleshooting in order to fix this but no solution. I have reset the PRAM and SMC. I made a backup of my files and installed Mavericks from the ground with external storage in order to erase the entire disk, no solution. I made an Internet Recovery and downgraded it to Lion, it worked for 2 hours and then I upgraded again to Mavericks (10.9.0) and the same problem came again, the upgraded to 10.9.4 and no solution at all.
I have searched on internet and there are other people experiencing this problem but nobody is able to bring a valid solution.
This is my battery's health:
Battery Information:
Model Information:
Serial Number: 9G1450LRJD3MA
Manufacturer: DP
Device Name: bq20z451
Pack Lot Code: 0
PCB Lot Code: 0
Firmware Version: 201
Hardware Revision: 2
Cell Revision: 158
Charge Information:
Charge Remaining (mAh): 3204
Fully Charged: No
Charging: Yes
Full Charge Capacity (mAh): 4859
Health Information:
Cycle Count: 931
Condition: Normal
Battery Installed: Yes
Amperage (mA): 2406
Voltage (mV): 12273
System Power Settings:
AC Power:
System Sleep Timer (Minutes): 10
Disk Sleep Timer (Minutes): 10
Display Sleep Timer (Minutes): 10
Wake on AC Change: No
Wake on Clamshell Open: Yes
Wake on LAN: Yes
Current Power Source: Yes
Display Sleep Uses Dim: Yes
PrioritizeNetworkReachabilityOverSleep: 0
Standby Delay: 4200
Standby Enabled: 0
Battery Power:
System Sleep Timer (Minutes): 10
Disk Sleep Timer (Minutes): 10
Display Sleep Timer (Minutes): 2
Wake on AC Change: No
Wake on Clamshell Open: Yes
Display Sleep Uses Dim: Yes
Reduce Brightness: Yes
Standby Delay: 4200
Standby Enabled: 0
Hardware Configuration:
UPS Installed: No
AC Charger Information:
Connected: Yes
ID: 0x0100
Wattage (W): 60
Revision: 0x0000
Family: 0x0085
Serial Number: 0x008d9c78
Charging: Yes

Reseting the NVRAM/PRAM doesn't solve my problems.
Hi, since you have performed NVRAM /PRAM reset, try:
Intel-based Macs: Resetting the System Management Controller (SMC)
and if still issues persist, try: OS X: What is Safe Boot, Safe Mode?
Cheers

Firmtek SeriTek/2SM2-E eSATA ExpressCard/34 - Deep Sleep issues / problems

Similar Messages

Maybe you are looking for