Aperture importing Results in System Crash

Launch Aperture 3, create new library, create a handful of Project names, start importing photos into Projects. Generates a system crash after about 150 photos imported resulting in system rebooting with Question Folder in center display.
I have been running Aperture 2 for well over 18 months with great results on a 4gb iMac 3.0.6G 1 TB system, 32 bit mode, Aperture library on internal boot drive, no external referenced files.
With a few days after installing Aperture 3, major problems began:
1. Thumbnail photos did not match the photo titles, clicking on thumbnail displayed yet a different photo. Some Projects, Albums appears just fine, but others gave every increasing problems. Some previously fine thumbnails now appear as moving vertical lines. Files sizes enormous. Very unstable.
2. Performing Command+Option on launch and selecting repair database resulted in over 7000+ plus photos in recovery folders. After spending 5 days performing tasks like: A.)Verifying and Repair the HD, b.) Repairing Permissions, Repairing the database, c.) Finally exporting every possible Master for safe keeping (a monumental task).
3. Starting over from scratch with volumes of duplicate photo files (some from export, some from recovery folders, etc. just to be sure nothing is lost (and I have no way to be sure).
4. Re-installed Aperture 3, ran software upgrade to ensure I have the latest 3.0.1 version. Turned off Face detection and created new library on the boot drive.
5. Stopped using Aperture 3 (for over a week) with no system problems.
6. Hand verified several hundred RAW Nikon image files using preview, Photoshop -all view and appear fine. Now I will attempt to import these same RAW image files into Aperture 3 as a test.
6. Started using Aperture 3 - and within 30 minutes my system is down again - so I called Apple support. Very frustrated. 2 Crashes within 1 hour. Hung during importing, dial at the 7 o'clock position, Finder locked unable to Shutdown waiting for crash to prevent causing more problems.
7. I need to give time for Apple to correct these Aperture problems. How could this major upgrade go out from Apple without extensive testing?
Other suggestions?

I have the same problem with my ipad with ios 7.1, there aren't other updates for ios, so how can i resolve the problem? Every time that i try to desabling the sim pin the system crash and the settings app closes
Thanks

Similar Messages

System Crash resulting in lost work...HELP with data recovery!

I need help. I was working on some art for an event and had a system crash. I was 95% complete with this particular project and am now back to square one unless I can recover all of the data or some of the data. Does anyone know how to recover data in Photoshop CS? I'm desperate!!!

howdy,
Usually it happens wen system crashes then it results into loss of all dat work...
But there are certains recovery tool that are used to recover lost data.
I think if u follow the following steps den u'll definately get a sol to this problem..
1.Install a recovery tool on some other system.
2.Place ur hard disc as secondry disc on this system
3.select ur crashed disc
4.Scan it through the recovery tool
5.and recover the lost data
u can use any of recovery tools like Advanced Disk Recovery,i found it worth...u can also try this....it is available on tucows

Aperture Import Settings Panels crashes.

The Aperture Import Settings panel crashes and it show you only info from the moment
you choose a location on a server called "Pictures" (same Name as the "Pictures" folder in the user folder in my case). The choose options stays on "choose" and if you click "Import Selected" you loose from now on all the option on the import on the next start of the app and even after reboot you will never have any options on the import panel. If i choose any other folder not named "Pictures" all works fine.
It seemed to me like a bug.

http://www.apple.com/feedback/aperture.html or if you have a (free) developer account you can use http://bugreport.apple.com

ITunes V6.0.0.18 - Total system crash whole importing CDs

Since installing V6.0.0.18 system crashes when importing CD. When I say crash I mean total system crash and automatic re-boot. The hard disk check reports truncated files in iTunes library (no surprise there the PC just crashed). When this happens is very variable sometimes at the start of a CD import sometimes on the last track and occasionally the import goes fine.
There is nothing wrong with my PC or CD/DVD drive, it has run happily with every other version of iTunes from V4.x onwards and continues to be very stable with the exception of this import problem
Any Idrea?

Hi Martin,
Sorry I can't help you, but you may get better help in the iTunes for Windows forum.
Regards,
CR

Leopard 10.5.8 or 10.5.4 System Crashes?

I need some help. I must have a corrupted file in my "User Library". How do I find it? I've tried to do a Restore and I get a message after 3 hours that says 'error cannot complete operation' or something like that. I have Time Capsule and managed to recover all my files by individually importing the proper folders, but when I tried to import my iTunes Library or my iPhoto Library (9GB- 4000 photos), it would 'Copy' the file very slowly and about half way through it would hang (the 'file count left to be copied' would stop changing and if I wait too long to try and 'Cancel Coping' the whole system crashes (I think the problem is with very, very large Folders) and I am forced to do a hard reboot with the power button. Then I am in real trouble, because it corrupts the System and I need to do a complete Restore and now it is full circle again.
I did some research with 'Apple Discussions' and discovered that the problem is most likely in my 'User Library'. I figure during 'Restore' the System sees some corrupt file(s) and refuses to copy it, and that file probably is the cause of the System Crashes. Is there anything out there that can scan my User Library for files that are corrupted or could cause problems?
I have plenty of memory (2GB). I've used 'System Profiler' and it shows that the memory is good. I've tried Restore 3 or 4 different ways with always the same result as above. I've discovered that with Time Machine, if I keep the Folder small enough (less than 4 or 5 GB) it will copy OK. But if the folder is above that limit then 'All H... Breaks Loose'.
Any help would be greatly appreciated.

ocsdmac wrote:
Hi, and welcome to the forums.
I need some help. I must have a corrupted file in my "User Library". How do I find it? I've tried to do a Restore
What kind of restore? From the Time Machine interface (the "Star Wars" display)? Restoring your entire system by booting from your Leopard Install disc and using the +Restore from Backups+ option?
and I get a message after 3 hours that says 'error cannot complete operation' or something like that.
Sorry, but we're going to need the exact message.
I have Time Capsule and managed to recover all my files by individually importing the proper folders, but when I tried to import my iTunes Library or my iPhoto Library (9GB- 4000 photos), it would 'Copy' the file very slowly and about half way through it would hang (the 'file count left to be copied' would stop changing and if I wait too long to try and 'Cancel Coping' the whole system crashes (I think the problem is with very, very large Folders) and I am forced to do a hard reboot with the power button. Then I am in real trouble, because it corrupts the System and I need to do a complete Restore and now it is full circle again.
Do you mean copying from your backups via the Finder?
I did some research with 'Apple Discussions' and discovered that the problem is most likely in my 'User Library'. I figure during 'Restore' the System sees some corrupt file(s) and refuses to copy it, and that file probably is the cause of the System Crashes. Is there anything out there that can scan my User Library for files that are corrupted or could cause problems?
If the problem is something corrupted, it's probably something in your backups, not your user folder (on your internal HD). Try repairing the sparse bundle:
Open the Disk Utility app (in your Applications/Utilities folder).
Mount the sparse bundle by opening the TM drive in finder and double-click on the sparse bundle.
Drag the sparse bundle into Disk Utility's sidebar and do a +*Repair Disk+* (not permissions) on it.
Also, any time you do a forced-power off, you can corrupt your internal HD. So use Disk Utility to do a +*Verify Disk+* (not permissions) on it. If that shows errors, you'll have to boot from your Leopard Install disk and use it's copy of DU to repair them. Post back if you need to do this but need help.
I have plenty of memory (2GB). I've used 'System Profiler' and it shows that the memory is good.
No. System Profiler doesn't test your computer's memory. It just shows what's installed.
Do the +*Repair Disk+* and report back with the results and answers to the questions.

Lightroom 4 importing causing program to crash.

Lightroom 4 will not import files. Windows 7 pop-up states; "there is a problem with this program that is preventing it from running correctly will check for solution". "Windows failed to find a solution must shut down program now".
This prevents the import page from loading or working and no images can be imported using usb or SATA connections. Was able to use computer's built-in card-reader to read from Sd and compact cards, those were able to run in the import window only because of preference setting. "when a Memory card is installed import files" (preference-setting). Any other means of importing files, the out-come is the program crashing and being shut down. All other functions outside the import menu seem to be working. Deleting all catalogs and then using the default catalog setting, failed to clear issue.
System info: Windows 7 64-bit, Intel i7 cpu, 16 gigs of ram, 4 one terabyte hard-drives.
Solutions tried. Removing Lightroom 4, all catalogs, then running defrag, registry cleaner, before attempting to re-installing lightroom 4. Removing lightroom 4 and installing lightroom 3.6 fails to fix issue. Removing all Lightroom products from hardrive,Including the windows program folder, windows programs data folder. Then rebooting re-running defrag, registry cleaner and re-installing lightroom 4 fails to fix importing issue. No way to contact support and links to user group fail to take me to correct user group. Question with the lead as lightroom 4 importing causes program to crash. Takes me to everything but lightroom solutions! Now this takes me to photoshop user group which has nothing to do with lightroom. With lightroom 4 in the question itself, I get everything but lightroom solutions!

Camera raw is built into Lightroom. It is the engine that makes the corrections within an image. You might not see as a seperate program, like earlier versions of Lightroom. Or having to launch it in a new window to work in camera raw. In version 4 of Lightroom it was made seamless and built into Lightroom.
Lightroom 4 was installed in the admin log-in window. I have all useage rights to any file lightroom creates or adjusts. I am thinking that the Photoshop CS6 beta created some working problem within Lightroom 4. Now that the beta-test program is over, I think the problem is a result of removing Photoshop's last build, before the public beta was released. I do hope, Adobe is working on a solution for people experiencing importing problems with Lightroom 4. I am just grabbing at straws here, trying to find something that will work. I think the problem will go away once computer has the new camera raw build 7.0 that ships in Photoshop CS6. With so many versions of camera raw installed on the computer, I think Lightroom is having issues as a result. Let's hope a patch is in the works, Lightroom 4 is useless if importing files doesn't work correctly.
B&H photo is taking pre-orders for the creative suites, right now. The only way to get support is by purchasing a subscription. Otherwise it is a $35.00 per issue fee. So, I am not sure of what upgrade path I will take. Not loving the cloud at all, with this year of Hackers, I seriously doubt that any cloud will prove to be safe to use. Why would, I want to post my hard work to a cloud where anyone can steal it? But that is a different topic.
For right now the only way to import is by creating an empty folder on the same hard-drive that Lightroom resides on. Setting up auto-import in Lightroom Pref. file to check that empty folder. Folder has to be empty to set up. Then dragging image files into that empty folder. I discovered that Lightroom 4 will not open or look in sub-folders for images. Which means you lose keeping a day's worth of shooting seperate from other folders. Where Lightroom version 3.6 you could.There was a second auto-import that worked, with my built-in memory-card reader. Where in the Lightroom pref.file you can tell Lightroom to auto-import, when a memory-card is detected. ( this is the least viable option, because more memory card become damaged removing and reinstalling them). These were the only two methods, I could get images into Lightroom 4 and prevent Lightroom from crashing. Might have to go back to using Nikon NX to import my images and using Bridge to catalog them.

System Crash in Mac OS 10.5.5: How to restore my data?

A system crash left me unable to log in to my computer, so I had no choice but to archive and reinstall. My Paml desktop ap is now gone, but this left my Palm user data file intact in user/document/palm/users/myname/files to install. I need contacts on my computer, but not in the field, so I haven't used my old Visor handheld in years, and it's uncharged and empty, thus I cna't simply sync. When I reinstall Palm desktop, is there danger of overwriting my user data? Also, once I finish, how do I import the old data?
Thanks.
Post relates to: Visor Platinum

Thanks, I've made my copies. Now I've run into this, which I've put on a separate post too:
When I run the installer, it gets to 758 of 791 items, then stops and puts up a box saying "Installation did no complete successfully. Do you wish to attempt to reinstall the software or to quit?"
Repeated attempts bring identical results. Any thoughts?
Post relates to: Visor Platinum

Please help: fail to recover after system crash

Hi all,
I tried to start our directory server after system crash due to hardware failure. Error log shows:
[17/Apr/2010:01:35:15 +0800] - WARNING<20488> - Backend Database - conn=-1 op=-1 msgId=-1 - Detected Disorderly Shutdown last time Directory Server was running, recovering database.
However, the recover process seems never ends (I waited overnight...). While CPU usage of ns-slapd grows continuously, the server has no response (e.g. ldapsearch waits forever). I make copies of db before starting ns-slapd and thus I tried several attempts:
1. start as it is.
2. remove db/log* and start
3. remove db/log* and db/__db* and start
4. remove db/* except db/NetscapeRoot and start
All attempts have the same result - recovery goes on continuously.
Then I tried to remove db/* and run restoreconfig with an old configuration backup. Then ns-slapd can be started. However, when I do ldapsearch testing:
ldapsearch -h localhost -v -D"cn=directory manager" -b "" -s base objectclass= namingContexts
ldap_init( localhost, 389 )
Bind Password:
ldap_simple_bind_s: Invalid credentials
I'm sure the password is correct, and also tried modifying nsslapd-rootpw in config/dse.ldif and corresponding userPassword in configuration file created by saveconfig before restoreconfig.
Again, all attempts have the same result - invalid credentials. I can see BIND cn=directory manager attempts in logs/access, but also see following line in logs/errors:
[17/Apr/2010:21:59:08 +0800] - INFORMATION - conn=-1 op=-1 msgId=-1 - get_entry: entry cn=directory manager not found (error 32)
I'd like to know:
* if there any other method to make recovery process complete successfully?
* if there is anything missed/wrong in the restoreconfig process?
I tried several days but can't make it. Would anyone please help?
Sorry that we're still using old versions 5.2 patch 5 on Solaris 5.9 on v440 machines...
Thank you very much.
/ST Wong ([email protected])

I hope you have a export of LDAP data backup in LDIF format, if so, please stop the instance and remove all the files from your db directory which includes .db3 and log.* and __db* and then do a ldif2db.
Once import is complete, start the slapd process.

Event recovery after system crash?

My system crashed yesterday when I was viewing some recently imported videos in iPhoto. When I rebooted, the videos were gone. I found them in my iPhoto Library (in the folders with yesterday's date) but they're not showing up as an event in iPhoto itself.
Any idea how to re-import them?

You have a corrupted library - do NOT import anything into it - you will compound the corruption - you need to fix it - Back up your iPhoto library, Depress and hold the option (alt) and command keys and launch iPhoto - from the resulting first aid window repair permissions and if necessary rebuild your database
LN

System crash OS 10.10.2

My system frequently crashes after installing OS10.10.1. I was quite fine with OS10.10 except wifi drop. Now I am really suffering since my system crashes everyday. Can anyone help?

The short answer is, never install any anti-virus software. The long answer is below.
Mac users often ask whether they should install "anti-virus" software. The answer usually given on ASC is "no." The answer is right, but it may give the wrong impression that there is no threat from what are loosely called "viruses." There is a threat, and you need to educate yourself about it.
1. This is a comment on what you should—and should not—do to protect yourself from malicious software ("malware") that circulates on the Internet and gets onto a computer as an unintended consequence of the user's actions. It does not apply to software, such as keystroke loggers, that may be installed deliberately by an intruder who has hands-on access to the computer, or who has been able to take control of it remotely. That threat is in a different category, and there's no easy way to defend against it.
The comment is long because the issue is complex. The key points are in sections 5, 6, and 10.
OS X now implements three layers of built-in protection specifically against malware, not counting runtime protections such as execute disable, sandboxing, system library randomization, and address space layout randomization that may also guard against other kinds of exploits.
2. All versions of OS X since 10.6.7 have been able to detect known Mac malware in downloaded files, and to block insecure web plugins. This feature is transparent to the user. Internally Apple calls it "XProtect."
The malware recognition database used by XProtect is automatically updated; however, you shouldn't rely on it, because the attackers are always at least a day ahead of the defenders.
The following caveats apply to XProtect:
☞ It can be bypassed by some third-party networking software, such as BitTorrent clients and Java applets.
☞ It only applies to software downloaded from the network. Software installed from a CD or other media is not checked.
As new versions of OS X are released, it's not clear whether Apple will indefinitely continue to maintain the XProtect database of older versions such as 10.6. The security of obsolete system versions may eventually be degraded. Security updates to the code of obsolete systems will stop being released at some point, and that may leave them open to other kinds of attack besides malware.
3. Starting with OS X 10.7.5, there has been a second layer of built-in malware protection, designated "Gatekeeper" by Apple. By default, applications and Installer packages downloaded from the network will only run if they're digitally signed by a developer with a certificate issued by Apple. Software certified in this way hasn't necessarily been tested by Apple, but you can be reasonably sure that it hasn't been modified by anyone other than the developer. His identity is known to Apple, so he could be held legally responsible if he distributed malware. That may not mean much if the developer lives in a country with a weak legal system (see below.)
Gatekeeper doesn't depend on a database of known malware. It has, however, the same limitations as XProtect, and in addition the following:
☞ It can easily be disabled or overridden by the user.
☞ A malware attacker could get control of a code-signing certificate under false pretenses, or could simply ignore the consequences of distributing codesigned malware.
☞ An App Store developer could find a way to bypass Apple's oversight, or the oversight could fail due to human error.
Apple has so far failed to revoke the codesigning certificates of some known abusers, thereby diluting the value of Gatekeeper and the Developer ID program. These failures don't involve App Store products, however.
For the reasons given, App Store products, and—to a lesser extent—other applications recognized by Gatekeeper as signed, are safer than others, but they can't be considered absolutely safe. "Sandboxed" applications may prompt for access to private data, such as your contacts, or for access to the network. Think before granting that access. Sandbox security is based on user input. Never click through any request for authorization without thinking.
4. Starting with OS X 10.8.3, a third layer of protection has been added: a "Malware Removal Tool" (MRT). MRT runs automatically in the background when you update the OS. It checks for, and removes, malware that may have evaded the other protections via a Java exploit (see below.) MRT also runs when you install or update the Apple-supplied Java runtime (but not the Oracle runtime.) Like XProtect, MRT is effective against known threats, but not against unknown ones. It notifies you if it finds malware, but otherwise there's no user interface to MRT.
5. The built-in security features of OS X reduce the risk of malware attack, but they are not, and never will be, complete protection. Malware is a problem of human behavior, not machine behavior, and no technological fix alone is going to solve it. Trusting software to protect you will only make you more vulnerable.
The best defense is always going to be your own intelligence. With the possible exception of Java exploits, all known malware circulating on the Internet that affects a fully-updated installation of OS X 10.6 or later takes the form of so-called "Trojan horses," which can only have an effect if the victim is duped into running them. The threat therefore amounts to a battle of wits between you and Internet criminals. If you're better informed than they think you are, you'll win. That means, in practice, that you always stay within a safe harbor of computing practices. How do you know when you're leaving the safe harbor? Below are some warning signs of danger.
Software from an untrustworthy source
☞ Software with a corporate brand, such as Adobe Flash Player, doesn't come directly from the developer’s website. Do not trust an alert from any website to update Flash, or your browser, or any other software. A genuine alert that Flash is outdated and blocked is shown on this support page. Follow the instructions on the support page in that case. Otherwise, assume that the alert is fake and someone is trying to scam you into installing malware. If you see such alerts on more than one website, ask for instructions.
☞ Software of any kind is distributed via BitTorrent, or Usenet, or on a website that also distributes pirated music or movies.
☞ Rogue websites such as Softonic, Soft32, and CNET Download distribute free applications that have been packaged in a superfluous "installer."
☞ The software is advertised by means of spam or intrusive web ads. Any ad, on any site, that includes a direct link to a download should be ignored.
Software that is plainly illegal or does something illegal
☞ High-priced commercial software such as Photoshop is "cracked" or "free."
☞ An application helps you to infringe copyright, for instance by circumventing the copy protection on commercial software, or saving streamed media for reuse without permission. All "YouTube downloaders" are in this category, though not all are necessarily malicious.
Conditional or unsolicited offers from strangers
☞ A telephone caller or a web page tells you that you have a “virus” and offers to help you remove it. (Some reputable websites did legitimately warn visitors who were infected with the "DNSChanger" malware. That exception to this rule no longer applies.)
☞ A web site offers free content such as video or music, but to use it you must install a “codec,” “plug-in,” "player," "downloader," "extractor," or “certificate” that comes from that same site, or an unknown one.
☞ You win a prize in a contest you never entered.
☞ Someone on a message board such as this one is eager to help you, but only if you download an application of his choosing.
☞ A "FREE WI-FI !!!" network advertises itself in a public place such as an airport, but is not provided by the management.
☞ Anything online that you would expect to pay for is "free."
Unexpected events
☞ A file is downloaded automatically when you visit a web page, with no other action on your part. Delete any such file without opening it.
☞ You open what you think is a document and get an alert that it's "an application downloaded from the Internet." Click Cancel and delete the file. Even if you don't get the alert, you should still delete any file that isn't what you expected it to be.
☞ An application does something you don't expect, such as asking for permission to access your contacts, your location, or the Internet for no obvious reason.
☞ Software is attached to email that you didn't request, even if it comes (or seems to come) from someone you trust.
I don't say that leaving the safe harbor just once will necessarily result in disaster, but making a habit of it will weaken your defenses against malware attack. Any of the above scenarios should, at the very least, make you uncomfortable.
6. Java on the Web (not to be confused with JavaScript, to which it's not related, despite the similarity of the names) is a weak point in the security of any system. Java is, among other things, a platform for running complex applications in a web page, on the client. That was always a bad idea, and Java's developers have proven themselves incapable of implementing it without also creating a portal for malware to enter. Past Java exploits are the closest thing there has ever been to a Windows-style virus affecting OS X. Merely loading a page with malicious Java content could be harmful.
Fortunately, client-side Java on the Web is obsolete and mostly extinct. Only a few outmoded sites still use it. Try to hasten the process of extinction by avoiding those sites, if you have a choice. Forget about playing games or other non-essential uses of Java.
Java is not included in OS X 10.7 and later. Discrete Java installers are distributed by Apple and by Oracle (the developer of Java.) Don't use either one unless you need it. Most people don't. If Java is installed, disable it—not JavaScript—in your browsers.
Regardless of version, experience has shown that Java on the Web can't be trusted. If you must use a Java applet for a task on a specific site, enable Java only for that site in Safari. Never enable Java for a public website that carries third-party advertising. Use it only on well-known, login-protected, secure websites without ads. In Safari 6 or later, you'll see a padlock icon in the address bar when visiting a secure site.
Stay within the safe harbor, and you’ll be as safe from malware as you can practically be. The rest of this comment concerns what you should not do to protect yourself.
7. Never install any commercial "anti-virus" (AV) or "Internet security" products for the Mac, as they are all worse than useless. If you need to be able to detect Windows malware in your files, use one of the free security apps in the Mac App Store—nothing else.
Why shouldn't you use commercial AV products?
☞ To recognize malware, the software depends on a database of known threats, which is always at least a day out of date. This technique is a proven failure, as a major AV software vendor has admitted. Most attacks are "zero-day"—that is, previously unknown. Recognition-based AV does not defend against such attacks, and the enterprise IT industry is coming to the realization that traditional AV software is worthless.
☞ Its design is predicated on the nonexistent threat that malware may be injected at any time, anywhere in the file system. Malware is downloaded from the network; it doesn't materialize from nowhere. In order to meet that nonexistent threat, commercial AV software modifies or duplicates low-level functions of the operating system, which is a waste of resources and a common cause of instability, bugs, and poor performance.
☞ By modifying the operating system, the software may also create weaknesses that could be exploited by malware attackers.
☞ Most importantly, a false sense of security is dangerous.
8. An AV product from the App Store, such as "ClamXav," has the same drawback as the commercial suites of being always out of date, but it does not inject low-level code into the operating system. That doesn't mean it's entirely harmless. It may report email messages that have "phishing" links in the body, or Windows malware in attachments, as infected files, and offer to delete or move them. Doing so will corrupt the Mail database. The messages should be deleted from within the Mail application.
An AV app is not needed, and cannot be relied upon, for protection against OS X malware. It's useful, if at all, only for detecting Windows malware, and even for that use it's not really effective, because new Windows malware is emerging much faster than OS X malware.
Windows malware can't harm you directly (unless, of course, you use Windows.) Just don't pass it on to anyone else. A malicious attachment in email is usually easy to recognize by the name alone. An actual example:
London Terror Moovie.avi [124 spaces] Checked By Norton Antivirus.exe
You don't need software to tell you that's a Windows trojan. Software may be able to tell you which trojan it is, but who cares? In practice, there's no reason to use recognition software unless an organizational policy requires it. Windows malware is so widespread that you should assume it's in every email attachment until proven otherwise. Nevertheless, ClamXav or a similar product from the App Store may serve a purpose if it satisfies an ill-informed network administrator who says you must run some kind of AV application. It's free and it won't handicap the system.
The ClamXav developer won't try to "upsell" you to a paid version of the product. Other developers may do that. Don't be upsold. For one thing, you should not pay to protect Windows users from the consequences of their choice of computing platform. For another, a paid upgrade from a free app will probably have all the disadvantages mentioned in section 7.
9. It seems to be a common belief that the built-in Application Firewall acts as a barrier to infection, or prevents malware from functioning. It does neither. It blocks inbound connections to certain network services you're running, such as file sharing. It's disabled by default and you should leave it that way if you're behind a router on a private home or office network. Activate it only when you're on an untrusted network, for instance a public Wi-Fi hotspot, where you don't want to provide services. Disable any services you don't use in the Sharing preference pane. All are disabled by default.
10. As a Mac user, you don't have to live in fear that your computer may be infected every time you install software, read email, or visit a web page. But neither can you assume that you will always be safe from exploitation, no matter what you do. Navigating the Internet is like walking the streets of a big city. It can be as safe or as dangerous as you choose to make it. The greatest harm done by security software is precisely its selling point: it makes people feel safe. They may then feel safe enough to take risks from which the software doesn't protect them. Nothing can lessen the need for safe computing practices.

System crashing after running a few applications/games after extended use

So, I know that everyone is going to say that temperature might be an issue, but I believe it might be due to a defect/software error because my CPU/GPU is very well cooled, and this only started very recently... I have taken all measures to get a new case,
more fans, clean out entire GPU and dusted everything very immaculately but it still seems to crash... I have no idea on how to see how/why my system crashed though.. there is no blue screen just a black screen.
Can anyone help me?

https://onedrive.live.com/redir?resid=ED07DBB027FFA77F!673&authkey=!AKclPJjsvZjTELA&ithint=file%2c.rar
Here it is
EM
This one DMP is called a BCC124 and is hardware related. Since it references AuthenticAMD I would run the CPU stress test first.
You also really need to update to SP-1 as there are many bug fixes in it.
Stop 0x124 is a hardware error
If you are overclocking try resetting your processor to standard settings and see
if that helps.
If you continue to get BSODs here are some more things you may want to consider.
This is usually heat related, defective hardware, memory or even processor though
it is"possible" that it is driver related (rare).
Stop 0x124 - what it means and what to try
Synopsis:
A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint.
Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress.
Generic "Stop 0x124" Troubleshooting Strategy:
1) Ensure that none of the hardware components are overclocked. Hardware that is driven beyond its design specifications - by overclocking - can malfunction in unpredictable
ways.
2) Ensure that the machine is adequately cooled.
If there is any doubt, open up the side of the PC case (be mindful of any relevant warranty conditions!) and point a mains fan squarely at the motherboard. That will rule out most (lack of) cooling issues.
3) Update all hardware-related drivers: video, sound, RAID (if any), NIC... anything that interacts with a piece of hardware.
It is good practice to run the latest drivers anyway.
4) Update the motherboard BIOS according to the manufacturer's instructions and clear the CMOS.
Their website should provide detailed instructions as to the brand and model-specific procedure.
5) Rarely, bugs in the OS may cause "false positive" 0x124 events where the hardware wasn't complaining but Windows thought otherwise (because of the bug).
At the time of writing, Windows 7 is not known to suffer from any such defects, but it is nevertheless important to always keep Windows itself updated.
6) Attempt to (stress) test those hardware components which can be put through their paces artificially.
The most obvious examples are the RAM and HDD(s).
For the RAM, use the 3rd-party memtest86 utility to run many hours worth of testing. (6-8 passes to stress the ram out)
For hard drives, check whether CHKDSK /R finds any problems on the drive(s), notably "bad sectors".
Unreliable RAM, in particular, is deadly as far as software is concerned, and anything other than a 100% clear memory test result is cause for concern. Unfortunately, even a 100% clear result from the diagnostics utilities does not guarantee that the RAM is
free from defects - only that none were encountered during the test passes.
7) As the last of the non-invasive troubleshooting steps, perform a "vanilla" reinstallation of Windows: just the OS itself without any additional applications,
games, utilities, updates, or new drivers - NOTHING AT ALL that is not sourced from the Windows 7 disc.
Should that fail to mitigate the 0x124 problem, jump to the next steps.
If you run the "vanilla" installation long enough to convince yourself that not a single 0x124 crash has occurred, start installing updates and applications slowly, always pausing between successive additions long enough to get a feel for whether
the machine is still free from 0x124 crashes.
Should the crashing resume, obviously the very last software addition(s) may be somehow linked to the root cause.
If stop 0x124 errors persist despite the steps above, and the hardware is under warranty, consider returning it and requesting a replacement which does not suffer periodic MCE events.
Be aware that attempting the subsequent hardware troubleshooting steps may, in some cases, void your warranty:
8) Clean and carefully remove any dust from the inside of the machine.
Reseat all connectors and memory modules.
Use a can of compressed air to clean out the RAM DIMM sockets as much as possible.
9) If all else fails, start removing items of hardware one-by-one in the hope that the culprit is something non-essential which can be removed.
Obviously, this type of testing is a lot easier if you've got access to equivalent components in order to perform swaps.
Should you find yourself in the situation of having performed all of the steps
above without a resolution of the symptom, unfortunately the most likely reason is because the error message is literally correct - something is fundamentally wrong with the machine's hardware.
More advanced reading can be found here from a MS MVP IT PRO
http://captaindbg.com/bug-check-0x124-whea_uncorrectable_error-how-to-troubleshoot/
Wanikiya and Dyami--Team Zigzag

[VIA] Via K7-266 Pro2 - System crashes if use more than 512 MB of memory

Cannot use more than 512 MB of memory or system crashes. After running without a problem for over 2 years with 1 GB of memory installed, system started intermittent crashing, generally after 5 to 30 minutes of use. I worked with the system manufacturer's tech support and they determined that it must be a motherboard problem. I am hoping to find another fix rather than replacing motherboard. System details:
MB: Via K7-266 Pro2 (MS 6380)
OS: MS Windows XP Update 1
Bios: V3.6
I've used Norton Systemworks and Norton Anti-Virus to keep system clean, and SpyBot and Adaware to clean adware
During troubleshooting, we found that it will run with 512 MB of memory without problems, but not with the 1 GB I had installed. My memory was 2 x 256 MB installed with the machine and 512 MB I purchased from Crucial and installed. Computer ran over 2 years with all memory installed without a problem. After the problem started and during troubleshooting, we found that any combination of 512 MB worked fine (either the 2 x 256 MB or the one 500MB chip), apparently in any arrangement of slots. But as soon as I went to higher memory, I was subject intermittent crashes.
Could not ID the source of the crash. It sometimes happened when I was working with a single program open (various programs from IE to Excel to playing at GameSpy), had multiple programs open in background, or even when computer was sitting idle with only the startup programs active.
During troubleshooting we also did a complete re-install of Windows XP, updated the bios to V3.6, and checked bios settings, but the problems persists.
What else could be the problem?

I am beginning to suspect a PSU problem. I neglected to mention in my first post that when the system crashes, it does not freeze but has intermittent reboots.
I ran the memtest86+ test first on the two old sticks of memory then on just the one new 512 MB stick; both passed the test. I also used the Prime95 stress test on both sets, and both ran without incident.
I used PC Alert to report CPU and case temperatures during the stress test. The results maxed at 54 and 41 degrees respectively during the first stress test and 46 amd 39 degrees during the second test (I think part of the difference was due to a lower ambient, room temperature during the second test.) The voltages reported during both tests were similar and were: Vcore1: 1.71v; Vcore2: 1.26v; +5v: 4.76v; 3.3v: 3.31v; +12v: 11.60v; and -12v: 12.60v. I am not sure if that information is meaningful, PCAlert showed all measurements as within the required range.
I periodically have cleaned the dust out of my computer, so I don't think that is the problem.
I used 2 power calculators with major differences in the reported status of the system. The test from pcpowercooling reported minimum and maximum requirements for my system (with the full 1 GB of memory installed) of 300w and 510w. The alternate I found at jscustompcs (from a recent article about power supplies at Extreme Tech) reported a minimuum of 256w (no maximum is calculated with their tool. The two tools had significant differences for memory, CPU, and PCI cards. Off particular relevance to my problem was the difference in memory requirements; Pcpowercooling calculated memory requirements at 8w per 128MGB while jcustompcs used 12.5 per stick, resulting in different totals of 64w vs. 21w. Which is right?
One item that makes me think it is not the PSU, however, is that the problem would occur with the 1 GB of memory while the system was idle, thus I was not using any of the hardware devices. However, I never experienced the problem while using a device (e.g. DVD, CDRW, or tape drive) - either with 500MB or 1GB of memory.
My power unit is a Power Man #FSP 300-60BTV with 300w output, including +3.3v: 28amps; +5v: 30.0 amps; +12v: 15 amps; +5vsb: 20amps; -5v: 0.3amps; -12v: 0.8amps. It also notes max output of +3.3v and +5v of 200amps.
My system also includes a Leadtek nVidia Geforce 3 Ti400 graphics card, DVD, CDRW, HP 14 GB tape drive, 1 case fan, and 4 PCI cards (modem, network, USB2.0, and Audigy 1). The USB card is connected only to a bus in my Dell monitor and I have not used other USB devices.
Any thoughts or suggestions? Do I need to replace the PSU?

MacBook Pro system crashes

I recently upgraded my MacBook Pro to OS10.8. Shortly afterwards I started having the system crash about once a day - sometimes more frequently. It only does it when using apple mail and firefox after having been dormant for a while. It basically goes blank and then after about 30 seconds gives a gray error page and starts to re-boot. The service folks didn't detect any hardware problems. It has 8 GB of ram. All suggestions are welcome.

If you have more than one user account, you must be logged in as an administrator to carry out these instructions.
Launch the Console application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Console in the icon grid.
Select the most recent panic log under the heading System Diagnostic Reports on the left. If you don't see that heading, select
View ▹ Show Log List from the menu bar. Post the entire contents of the panic report — the text, please, not a screenshot. In the interest of privacy, I suggest you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header and body of the report, if it’s present (it may not be.) Please don't post shutdownStall, spin, or hang reports.

Sudden system crashes for Mac mini 2011

I just came home from a 2-week vacation and my computer has begun to crash and reboot, seemingly when I need the computer to do some task more intensive than Internet browsing.
It started when I tried uploading pictures into iPhoto via my camera's SD card--and it invariably happens whenever I try this--but it has also crashed and rebooted during simple multitasking procedures, like clicking to check my download progress in Safari as my iPhone is syncing in iTunes. Yesterday I had to contend with the white (grey?) screen of death for a few hours as I tried different methods. Fiddling around in Safe Mode let me fix that problem, at least, but the sudden system crashes still persist.
Could my computer have been affected by a lack of use over the last two weeks in the summer heat? It's been hot in the house, but not exceptionally so for August. And before I left I shut it down and unplugged the power cord.
Here are the first several dozen lines of the error report from the most recent crash. If anyone could offer me some help, I'd be very grateful.
Interval Since Last Panic Report: 72 sec
Panics Since Last Report:          2
Anonymous UUID:                    5966B3C8-D237-441F-B085-67433211CA95
Thu Aug 30 22:31:31 2012
panic(cpu 0 caller 0xffffff800d7733f2): assertion failed: MBUF_IS_COMPOSITE(m), file: /SourceCache/xnu/xnu-2050.9.2/bsd/kern/uipc_mbuf.c, line: 4003
Backtrace (CPU 0), Frame : Return Address
0xffffff80f52f3c20 : 0xffffff800d41d5f6
0xffffff80f52f3c90 : 0xffffff800d7733f2
0xffffff80f52f3ca0 : 0xffffff800d78d2f8
0xffffff80f52f3d60 : 0xffffff800d77075f
0xffffff80f52f3d90 : 0xffffff7f8e264d2e
0xffffff80f52f3dd0 : 0xffffff7f8e280d7b
0xffffff80f52f3e30 : 0xffffff7f8e2f79d4
0xffffff80f52f3ec0 : 0xffffff7f8e26b62f
0xffffff80f52f3ef0 : 0xffffff800d847078
0xffffff80f52f3f30 : 0xffffff800d845b8a
0xffffff80f52f3f80 : 0xffffff800d845cb9
0xffffff80f52f3fb0 : 0xffffff800d4b2677
      Kernel Extensions in backtrace:
         com.apple.driver.AirPort.Brcm4331(601.15.21)[2D12C2AA-EED3-3C72-8A75-FFF39E64DA AC]@0xffffff7f8e25e000->0xffffff7f8e44ffff
            dependency: com.apple.iokit.IOPCIFamily(2.7)[8C9E06A4-13D0-33F5-A377-9E36F0ECC229]@0xffffff 7f8da4d000
            dependency: com.apple.iokit.IO80211Family(500.15)[3CA3EBF7-D5C1-3819-9346-BE648FC7644E]@0xf fffff7f8e1f2000
            dependency: com.apple.iokit.IONetworkingFamily(3.0)[4DB5B398-8957-33F6-9EC1-0D45D80769DD]@0 xffffff7f8db8f000
BSD process name corresponding to current thread: kernel_task
Mac OS version:
12B19
Kernel version:
Darwin Kernel Version 12.1.0: Tue Aug 14 13:29:55 PDT 2012; root:xnu-2050.9.2~1/RELEASE_X86_64
Kernel UUID: 3005059E-270B-3B9F-940D-7A66C05DDC9D
Kernel slide:     0x000000000d200000
Kernel text base: 0xffffff800d400000
System model name: Macmini5,1 (Mac-8ED6AF5B48C039E1)
System uptime in nanoseconds: 2262319547463
last loaded kext at 432629451752: com.apple.driver.AppleUSBCDC          4.1.22 (addr 0xffffff7f8efac000, size 16384)
last unloaded kext at 543566806951: com.apple.driver.AppleUSBCDC          4.1.22 (addr 0xffffff7f8efac000, size 12288)
loaded kexts:
com.zeobit.kext.Firewall          2.3
com.apple.filesystems.msdosfs          1.8
com.apple.driver.AppleHWSensor          1.9.5d0
com.apple.driver.AppleBluetoothMultitouch          75.15
com.apple.driver.AudioAUUC          1.60
com.apple.driver.AGPM          100.12.69
com.apple.driver.ApplePlatformEnabler          2.0.5d4
com.apple.iokit.IOBluetoothSerialManager          4.0.9f8
com.apple.driver.AppleMikeyHIDDriver          122
com.apple.filesystems.autofs          3.0
com.apple.driver.AppleHDA          2.3.0f2
com.apple.driver.AppleMikeyDriver          2.3.0f2
com.apple.iokit.BroadcomBluetoothHCIControllerUSBTransport          4.0.9f8
com.apple.driver.AppleSMCPDRC          1.0.0
com.apple.iokit.IOUserEthernet          1.0.0d1
com.apple.Dont_Steal_Mac_OS_X          7.0.0
com.apple.driver.ApplePolicyControl          3.2.6
com.apple.driver.ACPI_SMC_PlatformPlugin          1.0.0
com.apple.driver.AppleUpstreamUserClient          3.5.10
com.apple.driver.AppleMCCSControl          1.0.33
com.apple.driver.AppleLPC          1.6.0
com.apple.driver.AppleIntelHD3000Graphics          8.0.0
com.apple.driver.AppleIntelSNBGraphicsFB          8.0.0
com.apple.driver.AppleIRController          320.15
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless          1.0.0d1
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib          1.0.0d1

Remove the "MacKeeper" crapware as follows, then reboot and test. If there's no improvement, post again.
Note: These instructions apply to the version of the product that I downloaded and tested in early 2012. I can't be sure that they apply to other versions, nor do I intend to repeat the test.
IMPORTANT: "MacKeeper" has what the developer calls an “encryption” feature. In my tests, I didn't try to verify what this feature really does. If you used it to “encrypt” any of your files, “decrypt” them before you uninstall, or (preferably) restore the files from backups made before they were “encrypted.” As the developer is not trustworthy, you should assume that the "decrypted" files are corrupt unless proven otherwise.
In the Finder, select Go ▹ Applications from the menu bar, or press the key combination shift-command-A. The "MacKeeper" application is in the folder that opens. Quit it if it's running, then drag it to the Trash. A dialog will pop up asking why you want to uninstall it. You don't have to provide that information. Enter anything you like in the text box, then click the Uninstall button. All the functional components of the software will be deleted. That's the only useful feature of "MacKeeper:" it deletes itself. Reboot.
Do not try to uninstall by dragging the MacKeeper icon in the Dock or the LaunchPad to the Trash.
Here are some general suggestions. If you want your computer to be usable, don't install crapware, such as “themes,” "haxies," “add-ons,” “toolbars,” “enhancers," “optimizers,” “accelerators,” “extenders,” “cleaners,” “defragmenters,” “firewalls,” "barriers," “guardians,” “defenders,” “protectors,” most “plugins,” commercial "virus scanners,” "disk tools," or "utilities." With very few exceptions, this kind of material is useless, or worse than useless.
The more actively promoted the product, the more likely it is to be garbage. The most extreme example is the “MacKeeper” scam.
The only software you should install is that which directly enables you to do the things you use a computer for — such as creating, communicating, and playing — and does not modify the way other software works. Never install any third-party software unless you know how to uninstall it.

Webcam Live Pro causes system crash with Windows XP Home

Ever since installing Webcam Live Pro I have been having random system restarts. This ONLY happens when the webcam is being used. It happens when using the Creative Webcam Center or another application. Sometimes the restart will happen after a few minutes, and other times an hour or more. I am running Windows XP sp2 with all patches, and there are no driver conflicts listed in Device Manager. I have the cam set at 60 hz.
Even though there are no listed driver conflicts in Device Manager, there clearly is a driver conflict that occurs from time to time. I have read of other people having this same problem on this forum with Webcam Live Pro. I am using the driver ...0 which is dated 0//2004, and the automatic update program on this web site says that I am using the latest driver. But in the download section of this web site, the latest driver is listed as .0.0.0 and dated November 9, 2004. The driver numbers or dates do not match, and the driver on the web seems to have an earlier number but a later date!?
Does anyone (especially a Creative tech support person who may be reading this post) have any idea what to do? The driver version is one issue. But the big issue is the system crashes.
Best,
CB

Solution! I discovered the problem causing the system crash, and I think it is sufficiently interesting to note here so that others may benefit from what I discovered. First, there is no fundamental problem/conflict with the driver for Webcam Live Pro. The trouble in my instance is that I was running another program that utilized the web cam, and that program conflicted with the Webcam Live Pro program that was constantly running in the system tray. Basically, the program in the system tray is loaded with the set-up for Webcam Live Pro. It constantly monitors the computer system to see if the cam is connected to the computer. When it does this while another program is using the cam, the conflict occurs, causing the entire computer to reboot. The solution is to right mouse click the icon for Webcam Live Pro in the system tray, go to settings, and to remove the check that allows the program to check for the presence of the web cam. Just to be safe, I then also exited the Webcam Live Pro program from the system tray so that nothing from that program could interfere with my use of the webcam using another program.
The result is that the webcam is rock solid, with no system crashes. I have been running it nonstop for hours without a problem.
I hope this helps someone else.
Best,
CB

Aperture importing Results in System Crash

Similar Messages

Maybe you are looking for