AHHHHH!!! total software failure!

I have had some interesting things happen in the past three or so weeks,
I had a imac die, actually a blessing because that gave me a reason to buy a new mac.
Anyway I bought a mac mini and all went well for about a week, then the weirdness starts, I had a crash that after this crash I could not log in, so I had to archive and install 10.4 again after this the machine was fine for a day or so then it started to act really strange and I noticed that itunes had stopped playing and my entire music library was gone, so I restart hoping that whatever was going on would go away
to my surprise I get the blinking folder(NOOOOOOOOOOO!!!!!), so much for hoping it would go away, so I boot from a external disk as I look at my internal disk I realize that all the folders are there but all of them are empty and the disk was was mostly free, very weird to say the least.
after this I reinstall 10.4 and the same thing happens again.
what the heck is going on?
As I type this I am on the same mini but with as little software as possible installed and none of the updates so its 10.4 (8A451)
not 10.4.2

nope not at all, all files with in all folders on the entire disk were gone the system was not bootable and there was more disk space available than a minimum install of OS X would require.
even the hidden files were gone, the disk was empty other than folders those were there but contained no files this hold true for every thing starting at /
ohh, speaking of the invisable files and folders earlier on the first night it happened I remember seeing stuff that should not be visable such as mach and etc, I at the time was wondering why they were visable in the finder but thought little of it.
this was a very weird thing and there were allot of variables, what I am looking for is the cause, and maybe if someone else has had the issue it will save them some time and fustration.
I am sure that with the install I have now I will be fine and it had something to do with either 10.4.2 OR imported apps/prefs OR the combination of both.
So far it seems like its 10.4.2 combined with my imported items, I have a install that is on one of my externals that should be identical as the second one that crashed, so I am gonna run that one tonight and see if it crashes too with console open to see if that picks up anything, hopfully if it does crash it will lock up with something interesting on the screen.

Similar Messages

BB Z10 Gone completely black. No LED lights when connected to charger.HOW TO KNOW ITS A HARDWARE OR SOFTWARE FAILURE?

My bb Z10 just went completely blacked while i was using it this afternoon. It had above 70%charge while i was using it. i removed the battery and checked again a number of times. I even tried with another z10 battery properly working and found that its not a problem with my battery since the phone worked well with my battery in the other device.
Since i bought the phone from another country and cant get the service here in India (the phone is still in the warranty period) I m confused what to do.
It would be really useful if I could figure out whether its software or hardware failure. If its a hardware prob, i should ship the device for warranty time benefits of service.But it it where a software prob, i could find out someway to solve this somehow here in India.
HOW TO KNOW ITS A HARDWARE OR SOFTWARE FAILURE?

try this,
connect the device to BlackBerry link.by connecting it the conputer using USB cable(you can use your USB charger here)
then while the device is still connected to the computer do not remove the USB but remove the battery.
if BlackBerry link will be able to detect the device you can perform a back up(to keep the data of the device) then update the device. you need internet connection.
this should fix the issue if the problem is with the software
let me know what happens
1. Please thank those who help you by clicking the "Like" button at the bottom of the post that helped you.
2. If your issue has been solved, please resolve it by marking the post "Solution?" which solved it for you!

Premier Elements 12 Cannot burn DVD Get error message of internal software failure

Cannot butn DVD with Premier Elements 12 Get error message of internal software failure.

Great news JMD103.
There should be a big red pop-up, when one adds a Stop Marker to the end of the Timeline, saying "Do NOT do that!" That Stop Marker will almost always yield a failed Project output to DVD.
Good luck, and happy editing,
Hunt

Hp Laserjet 4200, Printer Virus or Software Failure?

Have been using a HP Laserjet 4200/4300 series, very few issues, very good printer.
Background:
Small office, this printer is attached to my computer but able to be used by 4 other machines on the network.
We are using everything from windows ME to Windows 7 xp.
What happened:
all day long we were printing & by the afternoon it just stopped. At that time only 2 computers had sent in print requests. Mine was sending Page prints of gov web sites using the latest version of mozilla firefox and I am running Windows 7 xp and the 2nd was sending Word Perfect docs and its on XP. In going through the Que, the printer says they all now have unspecified errors and will not print.
Printer/Proterties/General - print test page
Will not print
Hardware/Menu/Print test, cleaning, Menu map.. all print
Device is Working
Paper is full
Ink is in
Since then I have cleared the Que and sent several different types of things to print from all different types of programs.. the print manager say they all have errors.
So.. Printer Virus or Software Failure?
Any help will be greatly appreciated!!
thank you for reading. Sorry for not being more technically savvy.
Please ask for any details.

Just got off the phone with a friend (who is a lot smarter than I) and recommended turning off the printer, then truning it back on and holding down the mainuser button (the one with the check mark) and letting the printer do its thing.
just printed the test page.. so good news there. Still not sure what exactly happened..

White Screen - total system failure

I just purchased a new MacBook Pro, 1.83 GHz, serial # begins with W8614. I set up the AirPort wireless base and at first I could only get an internet connection right next to the base - I lost it if I moved farther away. I tried again later from the next room and this time the internet connection seemed to work. I was browsing the web and suddenly the entire screen went white for a few seconds, then nothing. The screen went dark and the computer died.
I unplugged it from the power source and plugged it in again, closed and opened it, tried every button, couldn't get anything to happen, the screen was totally dark. The computer was still on, though, because it was hot and the little white light at the latch on the front was on. I assumed the battery was still running, so I waited overnight for it to run out.
The next morning it was cold and the latch light was off. I plugged it back into the power adapter and tried to turn it on. For a second I heard a flicker of noise and then nothing again.
I called Apple tech support and they asked me to try a few things like resetting the power manager but nothing worked, it was still dead. So they arranged for me to send it in for repair. My question is: what could cause this kind of total system failure? It died completely in the first few minutes I was using it! Apple's always crowing about how reliable its computers are compared to the competition, but this performance is ghastly. It does not inspire confidence, to say the least. Can this kind of problem be repaired? Should I have any faith in the machine once it's returned to me? Yipes.

I bought it from Amazon, not Apple. Amazon allows you to return opened computers within 30 days, but they charge a 15% fee. I was hoping when I called Apple tech support that they'd just offer to replace it right away, but I guess if you buy the computer somewhere else their policy is to try repair first.
Certainly if Apple can't repair it, they'll send me another one. It's just that I never heard of a computer totally dying like that right after purchase - I wasn't aware how often that occurs. I'm just worried it might be buggy and crash frequently after I get it back - in other words, it might be a lemon. Hopefully I won't have to have it repaired over and over. Plus, of course I'm annoyed that I just acquired my shiny new expensive machine and now I have to wait two weeks before I can begin to use it.
Thanks for replying. Do you have an idea what causes this type of white screen demise? Any reassurance would be helpful.

Constant crashing - 'Total system failure'

Hey, if anyone could help me with this problem I seem to have I'd be really grateful, I don't know much about what's going on.
Basically, yesterday for no obvious reason a few apps started crashing on my iMac G4 running 10.4.9. Not being too technically gifted I used the solution to most of my problems, restarting the computer. Almost as soon as it started up though, it froze, so I had to restart again. This time safari refused to stay open for more than 5 minutes and msn messenger just bounced once in the dock and then stopped. I haven't installed anything dodgy recently, and the last thing that I got from apple was the 2007-004 security update.
So I ran the apple disc utility, and got it to fix some user permissions, but when it came to the 'verify disc' test, it didn't seem to happy. It said there was something wrong with the hard disc but it couldn't fix it. I got this message:
Verifying volume “Hard Disc”
Checking HFS Plus volume.
Checking Extents Overflow file.
Checking Catalog file.
Illegal name
Keys out of order
The volume The volume isc needs to be repaired.
*** FILE SYSTEM WAS MODIFIED ***
*** REBOOT NOW ***
Error: The underlying task reported failure on exit
1 HFS volume checked
Volume needs repair
Unfortunately, have no idea what that means. Almost instantly after this though, some DOS-like black lines popped out from the left hand side of the screen, with white text full of numbers and computer jargon I didn't understand. As far as I could make out the kernel was involved It said something about a total system failure, and that it was waiting for a remote access code or something.
Anyway the point is, my computer is a tiny bit broken Doe anyone know if this is something ordinary that can be fixed with a few clicks of the mouse, or is there a virus involved? My initial thought was that it could have been the recent security update, but that was 4 days ago and this started last night.
Any help would be appreciated, thanks.
iMac G4 Mac OS X (10.4.9)

Hi Ali_J;
May I welcome you to the Apple Discussion Forums.
First of all this is a virus.
Do you have a backup?
The error message "Keys out of order" indicates that you have some really serious problems which your disk. Do you have any idea as to exactly how full your disk is?
If you have run your free disk space very low this can cause this problem. If not, you might have a wonky disk. To repair this problem you are going to need a much more powerful tool then Disk Utility. DiskWarrior may be able to repair this problem. If it not able to fix the problem for you about the only alternative then is to reformat and reload.
Allan

ACE serverfarm total connections failures

I have many server farms in various contexts and every single serverfarm shows something like this:
NDCD23ACERT1/Internal-1295# sh serverfarm FINPROD88_80 detail
serverfarm : FINPROD88_80, type: HOST
total rservers : 3
description : -
predictor : ROUNDROBIN
failaction : purge
total conn-dropcount : 0
----------connections-----------
real weight state current total
---+---------------------+------+------------+----------+--------------------
rserver: FINPRODAPP5
10.1.129.39:8320 2 OUTOFSERVICE 2 138
total conn-failures : 348
rserver: FINPRODAW1
10.1.129.29:8320 1 OPERATIONAL 25 179
total conn-failures : 418
rserver: FINPRODAW2
10.1.129.30:8320 1 OPERATIONAL 8 165
total conn-failures : 456
The conn-failures counter keeps growning on all of the farms. What exactly could be the problem? People aren't complaining but it bothers me to see those counters grow.
Casey

total conn-failures counter can increment due to several reasons
1. When Server sends RST to close the connection
2. When Client Sends an invalid HTTP request
3. If "persistence-rebalance" & "layer 7 class map" is configured and ACE doesnt find a L7 condition in client request.
So increments in the counter doesnt always means that there is a server problem :)
There are bugs reported for all the above conditions.I am not sure if they are fixed in the latest release.
Hope it helps
Syed

Sudden total boot failure. Any idea what would cause this??

Today I was adding more apps to my clean install (on an external drive) and I had to go back to my original "update" installation to get a password off Keychain (I did not migrate). After I got the pw, I shutdown and my Powerbook would not reboot! I got the chime and then utter blackness. No disk access was attempted on my external, nothing from internal drive, and still nothing when I tried the Leopard installation DVD.
I kept trying and finally (after 10-15 minutes of getting nothing except the initial startup sound) the screen lit up and I got to the Startup Manager disk selection. I was still unable to boot from the DVD; the boot sequence had progressed only part way and then totally stalled (I gave it about 3 times as long as it would normally take to boot from a CD or DVD). I tried this twice more so I thought I had suffered catastrophic hardware failure.
But, then, after a pram reset, I was able to restart into single-user mode and did a couple of the fsck's (file-system check in Unix) and it said the internal disk was OK both times. Got through login and to the Finder Desktop after a regular boot, and after a safe boot, but found that the Finder was corrupted and repeatedly crashed with almost everything I tried to do.
Reluctantly then tried to boot from external drive and found that - it worked!
Tried to fix internal drive unsuccessfully. Eventually found that DVD drive was working again too, so I did a Time Machine restore of the internal drive after booting from the Leopard install disk.
After getting the internal drive to boot again (Time Machine worked!!), the Wacom tablet driver immediately crashed (even though I had supposedly loaded a Leopard-compatible version), so I then went to Terminal and got rid of all the StartupItems and PreferencePanes in the root Library and my user Library. I tried rebooting and since it did so without issue this time, I hooked up Time Machine and made a new backup.
How did the total boot failure get caused? I had never seen anything like this before where the screen stayed totally black and not even the DVD would boot.
I am now back to "normal" after 7 hours. Moral of the story is that even when your computer looks completely dead, keep trying. I just hope it doesn't happen again, since I'm not sure what the issue was.

Faulty battery. Make Genius reservation and take this iPhone back.

Error 0xBFFA4001 software failure when initiating acquisition on NI-5102

Dear Support,
When running my software I recieve an error hex 0xBFFA4001 software failure at the niScope_InitiateAcquisition function. I understand this may be due to improper installation and configuration of the scope's software on my computer. I am using the NI-5102 PCMCIA digitizer along with:
Traditional NI-DAQ 7.1
NI-VISA 3.0
NI-SWITCH 2.1
NI-SCOPE 2.5
Using the test panels, the device works fine. Previous to calling the initiate acquisition function I call:
init
configure acquisition
configure vertical
configure horizontal timing
configure trigger digital
actual record length
Is there perhaps something that I may have not configured of configured incorrectly? Or, am I
using the wrong version of some software? Please let me know if you have any insight into this problem.
Thank You.

This might just be an installation issue. I would start off by trying one of the shipping examples to see if they work. You can also try the NI-SCOPE version 2.6. You can find on the Drivers and Updates page from ni.com/support.

Adobe genuine Software Failure.

Cannot download software due to error: Adobe genuine Software Failure. How do I fix this?

See http://helpx.adobe.com/x-productkb/global/digital-certificate-revoked-aam.html

How to recover from a software failure on the 6120 Fabric Interconnect

Hi all,
Had a software failure while upgrading the fabric interconnects. Does anyone know the process to recover from a software failure.
Ive copied up the kickstart and system images, from the loader prompt ive booted the kickstart image and then loaded the system image but the fabric interconnect still reboots to the "switch(boot)" prompt.
Thanks in Advance
Darren

Hi Robert,
Thanks for the tips, but unfortunately im still stuck on the switch(boot): prompt.
The bootflash: only has 2 files in it, the kickstart and system image.
Each time i get the FI to the boot prompt, i can ping the device, but not access via the GUI. (i dont have a local copy of UCSM installed)
What files should i have in the bootflash: for the FI to correctly load.
below is a log of the FI as it loads the kickstart image from the Loader prompt.
loader> boot bootflash:ucs-6100-k9-kickstart.4.1.3.N2.1.3c.bin
Booting kickstart image: bootflash:ucs-6100-k9-kickstart.4.1.3.N2.1.3c.bin....
....................................................................Image verif
ication OK
Starting kernel...
Usage: init 0123456SsQqAaBbCcUu
INIT: version 2.85 booting
Starting Nexus5010 POST...
Executing Mod 1 1 SEEPROM Test......done
Executing Mod 1 1 GigE Port Test.......done
Executing Mod 1 1 Inband GigE Test.....done
Executing Mod 1 1 NVRAM Test....done
Executing Mod 1 1 PCIE Test..............................done
Mod 1 1 Post Completed Successfully
Mod 2 Post Completed Successfully
POST is completed
Creating /callhome..
Mounting /callhome..
Creating /callhome done.
Callhome spool file system init done.
Checking all filesystems..... done.
Warning: switch is starting up with default configuration
Checking NVRAM block device ... done
The startup-config won't be used until the next reboot.
Loading system software
INIT: Sending processes the KILL signalkernel daemon...don
Cisco Nexus Operating System (NX-OS) Software
TAC support: http://www.cisco.com/tac
Copyright (c) 2002-2010, Cisco Systems, Inc. All rights reserved.
The copyrights to certain works contained in this software are
owned by other third parties and used and distributed under
license. Certain components of this software are licensed under
the GNU General Public License (GPL) version 2.0 or the GNU
Lesser General Public License (LGPL) Version 2.1. A copy of each
such license is available at
http://www.opensource.org/licenses/gpl-2.0.php and
http://www.opensource.org/licenses/lgpl-2.1.php
switch(boot)#
From here i can the load the system image, but it always fails and drops me back to the same prompt, output show below
Uncompressing system image: bootflash:/ucs-6100-k9-system.4.1.3.N2.1.3c.bin
Loading plugin 0: core_plugin...
plugin_link_to_exec_path: plugin_path = /isan/plugin/0, tar_log = /isan/plugin_extract_log/0
Loading plugin 1: eth_plugin...
plugin_link_to_exec_path: plugin_path = /isan/plugin/1, tar_log = /isan/plugin_extract_log/1
plugin_file_is_excluded_from_exec_path: /boot/ is excluded from linking
plugin_file_is_excluded_from_exec_path: /boot/lib/ is excluded from linking
plugin_file_is_excluded_from_exec_path: /boot/lib/libplugin_sysreg.so.0.0.0 is excluded from linking
plugin_file_is_excluded_from_exec_path: /boot/lib/libplugin_sysreg.so.0 is excluded from linking
plugin_file_is_excluded_from_exec_path: /boot/lib/libplugin_sysreg.so is excluded from linking
plugin_file_is_excluded_from_exec_path: /boot/etc/ is excluded from linking
plugin_file_is_excluded_from_exec_path: /boot/etc/plugin_exclude.conf is excluded from linking
plugin_file_is_excluded_from_exec_path: /boot/ is excluded from linking
plugin_file_is_excluded_from_exec_path: /boot/lib/ is excluded from linking
plugin_file_is_excluded_from_exec_path: /boot/lib/libplugin_sysreg.so.0.0.0 is excluded from linking
plugin_file_is_excluded_from_exec_path: /boot/lib/libplugin_sysreg.so.0 is excluded from linking
plugin_file_is_excluded_from_exec_path: /boot/lib/libplugin_sysreg.so is excluded from linking
plugin_file_is_excluded_from_exec_path: /boot/etc/ is excluded from linking
plugin_file_is_excluded_from_exec_path: /boot/etc/plugin_exclude.conf is excluded from linking
Loading plugin 2: fc_plugin...
plugin_link_to_exec_path: plugin_path = /isan/plugin/2, tar_log = /isan/plugin_extract_log/2
plugin_file_is_excluded_from_exec_path: /boot/ is excluded from linking
INIT: Sending processes the TERM signal /boot/lib/ is excluded from lin
INIT: (boot)# l
INIT: Sending processes the KILL signaldaemon...don
Cisco Nexus Operating System (NX-OS) Software
TAC support: http://www.cisco.com/tac
Copyright (c) 2002-2010, Cisco Systems, Inc. All rights reserved.
The copyrights to certain works contained in this software are
owned by other third parties and used and distributed under
license. Certain components of this software are licensed under
the GNU General Public License (GPL) version 2.0 or the GNU
Lesser General Public License (LGPL) Version 2.1. A copy of each
such license is available at
http://www.opensource.org/licenses/gpl-2.0.php and
http://www.opensource.org/licenses/lgpl-2.1.php
switch(boot)#
please let me know if you require any further information.
Thanks in Advance
Darren

Multiple-point Hardware And Software Failures in Two, Separate and Not-connected Computers At The Same Time...

A few days ago, I was working on a restoration of a 100-years-or-so-old Calculus book on one of my Linux based computers, while my other computer with the Microsoft Windows Vista operating system was serving as Broadcast TV receiver with its USB HDTV tuner
in the afternoon. The weather in Los Angeles was summer-like in November, with clear skies and 90 degree Fahrenheit temperatures. All of a sudden, my Linux based computer halted in the middle of the processing it had performed hundreds of times
before in hotter days. It would not restart. The entire boot block of the disk seemed to have been garbled. This did not seem even feasible at all, so I decided to shut its power off for a while. It came back up after a while,
and everything looked normal. Then, it did the same thing again. I decided to open its cover and check on its multiple fans as there was nothing else that could go wrong.
I then noticed that the computer with the Microsoft Windows Vista Operating system which had been receiving the broadcast TV, was displaying a freshly-booted log-in screen. It had "Blue-screened" while I was working on the other computer
across the large room. This again did not seem any feasible as there had been utterly no connection between these two computers. Even the AC power line circuit was different. Furthermore, this computer had the most extensive air-cooling system
I had built to have it work through 107 degree Fahrenheit temperatures indoors. Anyway, I logged back in and started the broadcast TV reception again. Sure enough, after a while it "blue-screened" one more time...
I went back to the Linux-based computer and found all of its fans operating, but with somewhat hotter disk drives. The problem was that in hotter days, the same computer had cooler disk drives with nothing different. I concluded that somehow
the 80 mm fan mounted in the front side of the case, with its side with rotating blades clamped on the perforated part of the steel case serving as the fan grill, was starting up fine. But, as the time passed the spring-loaded rotating hub was slowly
drawn toward the perforated steel case by two means: The partial vacuum formed by the suction generated by the blades of the fan, and by the magnetic attraction of the rotating hub with electro-magnets in it to the partially magnetized, perforated steel casing.
The first effect was always there, so it was not the real cause, but once something else came along, it really helped the latter. The hub was slowly drawn to the perforated steel casing due to magnetic attraction, with the holes in the casing
inducing a huge air-drag on the hub blades as there was no by-pass around to supply the extra-air needed to reduce the partial vacuum. In addition, the rotating hub with the electro-magnets now was very close to the conducting metal surface and the induced
eddy-currents in the metal by the moving electro-magnets had added even more drag on the rotating hub, causing it to come nearly to a halt. The disk drive electronics was heating up and was causing DMA access faults which in turn caused the Linux kernel
to panic and halt.
Well, this was nearly unbelievable, but true... I had not brought any magnets into the room and I still do not know how the computer case got magnetized. It has been working at the same location for years. The solution was to move the fan
away from the perforated steel casing a little so that some air could come in through the gaps on the sides of the fan (hence supplying a by-pass), reducing the partial vacuum in front of the fan. This kept the rotating hub far enough away to prevent
the massive induced eddy-current drag from slowing the fan down to a halt. The computer now works perfectly with the very same fan as it has had been doing for years.
The real solution is to saw the perforated part of the steel casing in front of the fan away, and to replace it with a better fan grill. The best fan grill material I have found is the finely perforated, thin, black aluminum sheet that is usually
used as a car audio speaker grill. In fact, I use these in my Microsoft Windows Vista based computer. The fans are quieter, with more air flow. It also keeps dust away and you can brush the collected dust off easily.
The next problem was the halting of the computer with the Microsoft Windows Vista operating system with a blue-screen. The fans in it could not be the cause of this, as it had already had the best improvements I could put in it, with even
externally powered fans that did not load the computer power supply. And, all of the fans were working well. In the meantime, the Microsoft November 2014 updates for the Microsoft Windows Vista came out, and as usual I told the computer to
load and to implement them. Sure enough, the computer again "blue-screened" in the middle of the update procedure.
That was somewhat too much, but there was nothing else I could do other than to debug it. I had not changed anything in the computer and its power supply, completely internally updated by myself a few years ago, was working perfectly. Whatever
was causing it was not in the hardware. It was not in the November 2014 software updates either as it "blue-screened" before those were announced. I brought the computer back up after several disk and other software checks and after the
completion of the updates, I gingerly turned the network modem on. I then sent the reports on the six failures (three "blue-screen" type failures and three "Anti-malware Executable" failures) to Microsoft with all of details
requested using the Microsoft Windows Vista problem reporting system. Within minutes, the Microsoft came up with a diagnosis that the USB driver code in the system had a serious bug. I had not changed this code in years. It suggested that
I should use the "Microsoft Fix-It" for this problem and it pointed to a link to download it. I did download it. It ran and the "blue-screen" problem just went away, as if it had never been there...
-- Yekta

I ordered the capacitors on Friday and they arrived on Monday, November 17, 2014. I removed the motherboard from the machine, by removing all PCI and AGP boards, drive and fan connectors and the computer power supply first. The motherboard then
simply unbolted from the case and came out with the CPU fan assembly still attached.
I wrapped the solder side of the motherboard with aluminum foil and set up a work place with the aluminum foil under the motherboard and myself electrically well grounded. Here came another surprise: There were four more capacitors of the same
kind just behind the CPU fan assembly and their tops were also deformed with one of them leaking the electrolyte inside from the the top. Luckily, I had ordered more than two capacitors to get the quantity discount and the lower rate of shipping.
I do use them in other circuits I occasionally build.
Technically, the only thing one needed to do was to unsolder the six old capacitors from the motherboard and to solder six new ones in in their place with the correct polarities. However, due to fact that the capacitors span the 3.3 V power plane and
the ground plane in the multi-layer motherboard, it is nearly impossible to unsolder these capacitors using regular, fine-tip soldering irons. The thick copper of the power and the ground planes carry the soldering iron heat away very fast, preventing
the solder from melting quickly. Continuous application of heat at this point will simply burn the internal insulating epoxy layers and cause shorts inside the motherboard which are impossible to fix in any reasonable amount of time.
The only reasonable way to remove these capacitors was to dismantle the capacitors from the top leaving their already soldered leads in place. The new capacitors were then tack soldered to these stubs using lead-free, hard solder. However, the
CPU fan assembly and the CPU itself had to be removed from the board to be able to work on these capacitors.
To dismantle the capacitors from the top, I first drilled small holes at the tops of the capacitors at the intersections of the indentations using the tip of a hobbyist's knife. I then used needle nosed pliers to peel back the triangular sections
of aluminum from the center at the tops to their bases at the top edges of the capacitors. Next, I removed the plastic layers covering the outside of the capacitors by scoring the plastic layers first from the bottom to the top using the tip of
the hobbyist's knife and peeling the plastic layers off starting at the cut. The following step was to cut the aluminum cans of the capacitors from the top to the bottom using the hobbyist's knife like a can opener. One could not use a saw like
tool here to accomplish the feat as the saws generated very fine metal chips which were very hard to remove and were certain to cause shorts in the densely populated mother board. The cans were then peeled off the rest of the capacitors starting from
the top at the cuts using needle nose pliers, revealing the spiral-wound metal-paper layers of the capacitors.
The wound layers of the capacitors were peeled off layer by layer by cutting into the layers from the top to the bottom, leaving only the two aluminum electrodes which were crimped and soldered to the leads of the capacitors. The picture below shows
the six capacitors with one of them dismantled (left) and with all of them dismantled (right):
The black disks below the aluminum electrodes are the rubber plugs covering the bottoms of the capacitors. The rubber plugs were then cut in half using the hobbyist's knife and removed using the needle nose pliers. It was not possible to
solder to the aluminum electrodes, so these were trimmed at the point they were crimped on the leads of the capacitors, leaving only the stubs of the capacitors' leads soldered to the motherboard.
The new capacitors with suitably trimmed leads were then soldered to these stubs with the correct polarities using lead-free, hard solder. The capacitors were lightly bonded together using a flexible glue to prevent them from moving. The picture
below shows the new capacitors as installed into the motherboard:
I then assembled everything back together and turned the computer on. The BIOS complained on the boot screen that the CPU was out of its socket and it needed to be reset. I set BIOS parameters correctly to their original values. The computer
came up and worked without any problems. I typed this message on my newly repaired computer running the Microsoft Windows Vista operating system.
By the way, the manufacturing date on the motherboard is 09/12/2002 and the CPU is a Socket-478, 2.4 GHz, Intel Pentium-4.
-- Yekta

Why is my Macbook Pro suddenly and constantly shutting down/crashing on me and giving me a blacked out or blued out screen with lines? Seems like a total system failure is happening?

Macbook Pro- shortly after upgrading to free software upgrade to Mavericks- 10.9.5-
has suddenly been freezing up, but went more directly to 'shutting down,' CRASHING on its own. Most of the time, if I'm even able to successfully get the laptop turned back on, it only stays up/on for a few moments before repeating the failure. The failure is often accompanied with the monitor going 'blank,' or most typically either 'blacking out,' or going blue/green or grey screen with lines or grids all over the monitor. All Desktop visibility, functions or applications in process disappears. This has caused repetetive 'forced shut downs,' which I never usually do, unless prompted to because I have no choice like this.... Or as I said, the computer itself will just shut down and turn off by itself.... Can anyone tell me what this issue is, and I'm pretty sure other Mac users have seen this exact thing I'm describing happening on their laptops, with their systems or on their monitors. Someone please explain or point me in the right direction... as naturally my laptop just went out of warranty as well.... And I don't know if this means the entire system is basically corrupted, dying/dead... and or if it is a monitor issue, a hardware issue, software issue or if there is anything that can be done to restore, repair it, etc.? Also another thing I have noticed ever since getting this laptop- (few years old now...) is that it runs VERY HOT... has in fact burned my lap /skin many times... and seems like the fan or internal operating systems/functions are also perhaps not functioning properly. Can this also be causing the problem? Or is it a corruption or virus of some kind? etc. Thank you.

What you describe sounds like a hardware issue. Unfortunately, you'll need to get that checked out by Apple. If you have an Apple Store near you, make an appointment with the Genius Bar and take the machine in for evaluation.

Hardware or Software failure? Mac Book Pro

I got my Macbook Pro last year in October. It is a MacBook Pro (13-inch Mid 2012), OS X Yosemite (10.10). It came with mavericks. Right after I was offered to upgrade to Yosemite and in my inexperience with Macs I just went for it. Then I realized that many features I saw in my friends' Macs were gone in Yosemite, so I went back to Mavericks. But then again I reverted to Yosemite because iCloud drive was only available with this OS X.
I ended up getting Microsoft office for Mac because the Apple suite Pages and such lack so many features that were present in older versions, but at least with Yosemite I could use iCloud drive.
But now, after the last update to Yosemite iCloud drive is just working like nuts, deleted folders keep reappearing, files or folders get duplicated multiple times, and other folders are emptied without notice, files just gone!. I created another Apple ID and this a new iCloud account to which I added just a couple folders to see if it worked better, but almost immediately one of the files in the them was duplicated 5 times.
As a result I abandoned iCloud and went to Google Drive and I am pretty happy with it. What I am not happy with is spending lots of money in a Mac only to end up using Microsoft, Google and other third party apps because Apple seems to be messing up big time, and going by what I read from countless customers it seems they cannot care less about what customers like or want or need.
Now the new issue. After the update to 10.10.3 not only iCloud has gone insane. Safari is slow, stops for minutes, or does not open some pages or part of pages. To complicate things now the cursor started to disappear and after a couple minutes my laptop just shuts down. This has happened a few times the last couple days so far but it is a big concern. (I m thinking how a key went lose the first week I got the laptop too, Apple replaced the key).
All said, I am now not sure what is what, is it a software problem I am having or worse, is it a hardware failure. At times I wish I would have gotten just a PC laptop.
What should I do?
Thanks
JC

Please read this whole message before doing anything.
This procedure is a diagnostic test. It’s unlikely to solve your problem. Don’t be disappointed when you find that nothing has changed after you complete it.
The purpose of the test is to determine whether the problem is caused by third-party software that loads automatically at startup or login, by a peripheral device, by a font conflict, or by corruption of the file system or of certain system caches.
Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards, if applicable. Start up in safe mode and log in to the account with the problem. You must hold down the shift key twice: once when you turn on the computer, and again when you log in.
Note: If FileVault is enabled in OS X 10.9 or earlier, or if a firmware password is set, or if the startup volume is a software RAID, you can’t do this. Ask for further instructions.
Safe mode is much slower to start up and run than normal, with limited graphics performance, and some things won’t work at all, including sound output and Wi-Fi on certain models. The next normal startup may also be somewhat slow.
The login screen appears even if you usually login automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
Test while in safe mode. Same problem?
After testing, restart as usual (not in safe mode) and verify that you still have the problem. Post the results of the test.

How do I notify Apple of a software failure: in Win 7 64 bit, using Get Info function causes iTunes 10.5 to fail and exit?

I have Win7 64 bit running iTunes 10.5. When I import a CD and click on the "Get Info" context menu item for the CD drive item on the left side of the window, the expected context menu and input boxes appear. When I type anything into any of the available input boxes, iTunes immediately throws a fail exit to Windows. Here are relevant screen shots:
Right click on CD Device item to get context menu:
Click on Get Info menu item to open CD Info window:
Key in "A" in Artist input box, get immediate failure:
So far Microsoft hasn't notified me of any solutions to this failure.
This info needs to get to Apple, but I am not paying to give them information to fix their problems!
Thanks for passing this along.
D. V. Hirst
PS: As a work around, I can highlight the entire CD worth of tracks and edit the common information in the Get Info function at that level... Still, iTunes should not be throwing program failure exceptions in any case. It is especially annoying on such common functions. One might have expected a more thorough testing program prior to general release.
DVH

Thanks for your response. I attempted to do that, but I couldn't find any way to access the configuration for the Zhone router. Typing the IP address into my web browser's address bar only resulted in "page could not be found" or "page timed out", etc. I called tech support at Northstate, who likewise suggested that the Zhone router should be set to bridge mode and the AEBS set to router mode since it would be easier for me to configure the AirPort. After wrangling a bit with them over my inability to change any settings for the Zhone, they sent a technician over. He messed around with the Zhone, apparently putting it in bridge mode, and we managed to get the AirPort to work without any double NAT errors. I reset the AirPort and created a new configuration file. Unfortunately, when I went to the Advanced/Port Mapping menu and repeated the original steps to forward port 7777, tests at www.whatsmyip.org still returned "timed out". The technician said he wasn't knowledgable enough about Apple products to assist me any further and suggested I call their tech support or visit the nearest Genius Bar. So that's about it. Any other ideas?

AHHHHH!!! total software failure!

Similar Messages

Maybe you are looking for