Académique Documents
Professionnel Documents
Culture Documents
Warning! You must unplug your ATX power supply from the wall before working inside the case.
Troubleshooting PC failures starts with the power supply. In fact, it's easier to diagnose failures where the computer won't turn on at all as opposed to more intermittent issues.
replacement on hand, you can usually scavenge the hard reset switch that isn't used much anymore if the case is equipped with one. The important connection for the power supply to get to a live system is the large ATX connector, generally 24 pins on new systems, that latches onto the motherboard. Power hungry motherboards and adapters have led to a variety of supplemental connectors, including the a 4 pin or 8-pin ATX 12V supply on many systems. With the power supply unplugged, make sure they are properly seated and latched by removing them and reattaching. I've always found the standard ATX latching system to be counter-intuitive. It works kind of like a see-saw with a pivot, you have to squeeze in at the top to pop it open at the bottom. They usually don't make any noise on releasing, but you often get a satisfying click when you remake the connection. The next step in power supply troubleshooting is to limit the possibilities through the process of elimination. We can't try to power up without the motherboard connected because that's a non-starter, but it makes sense to remove the power leads from all of the drives (hard drives and DVDs) to make sure an abnormal draw isn't preventing power up. If you have experience working with a Digital Volt Meter around live voltages, you can try checking the voltages right at the top of the connector to see if they are within reasonable tolerance of the rated voltages. It depends on whether your probe is thin enough and how much room there is next to each wire at the top of the connector to get the probe in. I don't advise anybody to try live testing of this kind without experience, it's safer to try swapping the supply, or if you're a working tech, to buy a cheap ATX power supply tester. The reason for using a special ATX power supply tester or back-probing the connector while it's still attached to the motherboard is because switching power supplies require the proper load to operate. ATX Version 2.2 - 24 wire motherboard connector Pin 1 Pin 2 Pin 3 Pin 4 Pin 5 Pin 6 Pin 7 3.3V Orange 3.3V 3.3V Ground Blue 5V Red Ground Black 5V Red Black Orange Orange Black Black
Pin 8
Pin 9 Pin 10 Pin 11 Pin 12 12V Red 5V 12V Red 5V 3.3V Black Ground
Pin 13 Pin 14 Pin 15 Pin 16 Pin 17 Pin 18 Pin 19 Pin 20 Pin 21 Pin 22 Pin 23 Pin 24 The standard color scheme for the 24 -pin ATX power supply voltages is above, but that doesn't mean all manufacturers choose to follow the standard. I've seen older Dells and other brand name computers with proprietary power supplies and their own color associations, so don't junk a power supply that reads 3.3V where you expected 5.0V unless you're sure it's not a proprietary design. The reason the motherboard is always partially live in an ATX system is because Pin 9 in the connector is always powered at 5V while the power supply is plugged in. That's the power to allow the motherboard to make decisions about whether or not to turn on, based on switch actions and setting like "Wake on LAN" for networked PCs. And that's why you should never work on an ATX PC with the power cord plugged in. It's just that much smarter than counting on there being an override switch on the back of the PC and your remembering to use it. The live power is also available to the bus slots, so replacing adapters with the cord plugged in could cause damage, as can dropping a screw into a slot right right at the powered contact. If your computer has a display connected, can you get a live screen, whether it's a simple text message or a colorful splash screen? If the display shows a message like "No video signal detected", that's the monitor telling you the video port isn't communicating, so you should follow the "No" path for this decision. Sometimes you'll get a live screen but it will show a multiplicity of images or endless scrolling, which means the video adapter is alive and trying but the monitor can't interpret the signals. This doesn't happen as often with modern LCDs that can match a large range of inputs, but it was a frequent occurrence with old CRTs that couldn't handle the refresh rate at higher screen resolutions set in Windows. Newer CPUs like quad cores or better and super-hot PCI Express video adapters have boosted the power needs of gaming PCs by a factor of two over the last decade. The ATX power supply in a basic gaming PC will usually be rated 600W, and power ratings from 750W to 1000W are increasingly common. The big power hogs are multi-core CPUs that can suck down tens of watts per core, so total CPU power needs can go over 200W for just one chip. And PCI Express video cards
for gaming which require their own lead (or two!) from the power supply may draw 200 Watts each, with some systems featuring two of them for increased video processing power. The manufacturers of ATX power supplies brag about their power ratings but the video card makers treat their power requirements more like a dirty secret. When you're building or reconfiguring a gaming PC, you really need to put pen to paper and note the power needs of all the components. Instead of giving a power rating, they may specify the peak current draw in (amps) at a nominal 12V, so you need to multiply the two for the peak consumption in Watts. Buy a power supply that exceeds the requirements by a minimum of 100 watts. All of the high performance video cards for gaming require appreciably more power than is available through the motherboard PCI Express slot, which means you need a power supply with extra 6-pin PCI Express connectors or enough spare drive connectors that can be adapted. If the power comes on but the screen never goes live, try switching back off again and retrying. The switch programming may require you to hold the power button in for a few seconds before the power supply shuts down again. If it refuses to power down, check if there's an override switch on the back of the supply, otherwise you can turn off your power strip if you're using one or just pull the plug. If the PC gets through boot and lights up the screen after a second try, it's likely due to miscommunication between the motherboard and power supply around the power_good signal. The motherboard will shut itself off in self-protection if the power supply isn't stable. Cheaper power supplies may just be a little too sloppy for some motherboards and work OK with others, it's a bit of a mix and match game when the manufacturers cut it too close. Since you don't want to try to boot twice whenever you need to turn on the PC, look into buying a higher quality power supply. Beep codes are reported out by the motherboard BIOS self-diagnostics at power up. A single beep means the POST (Power On Self Test) test was successful and the CPU, memory and video adapter are all reporting present and accounted for. Any longer strings of beeps are usually due to a hardware failure (or something pressing down a key on the keyboard) and the beep codes depend on the particular system. Long strings of slow beeps are usually related to a bad memory module, and repeating strings of 3 or 9 beeps often indicate video card failure. In either of these cases, shut down, unplug, and try reseating either the RAM or the video adapter, though it can't hurt to do both. Beep codes rarely have anything to do with the power supply, so see the motherboard, CPU and RAM flowchart. If there aren't any beeps, make sure that the motherboard has an onboard piezoelectric speaker and doesn't require an old fashioned case speaker. If you've done any work in the case immediately before the boot failure, undo it, even if it means swapping the old component back in. I remember one PC which powered up but wouldn't initialize the video adapter because the old secondary IDE ribbon cable had been reversed on a CD drive! Just because a component you added to the PC worked fine in another system doesn't mean it's compatible with the current PC, or that you hooked the cables up properly, or even that it didn't get zapped with static while you were making the change. Not all power supply problems appear during the boot process. If your power supply is chronically noisy with whistling capacitors or hums, that may be reason enough for you to replace it. A noisy power supply fan can usually be cleaned or replaced easily enough, though you have to watch out for the big capacitors in the power supply when you open it up, even after it's unplugged. And make sure the fan noise isn't due to something stuck in the grille and hitting the fan blades. If your kids hear a whistle that you don't, it's probably beyond your hearing range, and it's not necessarily in the power supply either. I tend to leave these things alone on older PCs if they aren't bothering anybody. Some of the toughest problems to troubleshoot are unstable voltages. If you find yourself stuck in the old parts swapping mode, don't push the power supply off to the last thing. Low quality power supplies can lead to some very funky failures, like a computer does a hard restart if you walk across the living room floor. While modern motherboards include circuitry to regulate the incoming power, it's still got to be within a few percent of what it's supposed to be. If the power supply can't produce stable voltages in the right range, the PC may freeze up or the system may shut itself down for protection. As the PC starts to power up, you should hear the hard drive spinning up, a gentle drone if all is well, and you should also here a very subdued clicking or chuckling from the arm with the read/write head moving in and out. If the drive cage isn't screwed into the case and the cable lengths allow for it, you can twist the cage slowly in the air and it will resist like a gyroscope. But it's not a game and you can hurt the drive by accelerating it too hard while it's spun up, not to mention all the issues of playing with live power. If the drive doesn't spin up despite the system power coming full on, double check that the power lead is firmly seated in the drive socket. Old style Molex connectors used on old IDE hard drives were notoriously hard to insert in the socket, and they rarely ever seated all the way. Try switching to a different power supply lead, and if you're out of leads, steal one from another drive for the sake of testing. It's possible the ATX power supply is failing, but if you have another known
good hard drive, try spinning it up just to make sure the power supply is really powering the drive leads. You can also test the hard drive you've removed in another system if one is available, but don't risk it if you ever thought there was a burnt smell or sparks coming from the drive area. If you're working on a server that uses SCSI drives, make sure the SCSI jumper to delay drive spin-up isn't set. This used to be necessary in SCSI drive arrays so they wouldn't all spin up at once and swamp the power supply. The default is usually for the SCSI adapter to spin them up following their SCSI ID sequence. If you still aren't getting system power, disconnect the drives one-by-one, stopping to try powering up again after each action. You'll know you've discovered a faulty drive or a bad lead from the power supply if the system powers on after a change. If it turns out that all the SATA power leads aren't doing the job but the power supply has an old-fashioned Molex connector, try a cable adapter to power the SATA drive from the old lead. When the PC still won't power on with all of the drives disconnected, try removing any add-in adapters, one-by-one, saving the video card for the end. Remember to unplug the power from the supply before each adapter removal, then plug it back in to test if you've found the problem. If the PC finally does power up, shut down, unplug, and restore all of the adapters and reconnect all the drives except for that last removal that was preventing power on. If the PC works, you might risk powering down and unplugging again and trying the problem adapter in a different slot. If you have an adapter that prevents boot independent of the slot it's in, you can replace it or live without it. When you're running a dual PCI Express configuration, try running with one video card at a time, and make sure you try them both alone. For motherboards with a single video slot, PCI Express or AGP, it's always possible that slot has failed. See if there's integrated motherboard video that can be reenabled, and in cases where you only have motherboard video, consider trying an add-in video adapter if the system seems to power up but nothing will wake the screen. Once every avenue has been exhausted with stripping out removable adapters, and assuming you don't have a spare CPU to try, it's time to pull the motherboard out of the case and look for shorts. On newly built systems, there could be a metal standoff in the wrong place that scratched through the protective coating on the board to hit a live trace, or a screw may have rolled underneath and got stuck in the wrong place. At this point I usually try to build up the PC on the bench without a case, letting the metal shields on the adapter dangle in space and propping the motherboard on any nonconductive surface. The idea is to eliminate any mechanical stresses on the motherboard that may have been flexing it to create an open circuit when it was installed in the case.. Short circuits are normally catastrophic, causing melting, a burnt odor and ruining the motherboard. In a serious electrical failure, some of the installed components (RAM, CPU, add-in adapters) can get zapped as well. You'll often be able to spot the failure by visible burns and melting on the board or a component like a capacitor. It's difficult to identify failures by smell because in a closed case, the smoky smell seems to come from everywhere. If you know there was a short but you can't locate the particular component that caused it, you should can try testing them one by one in a sacrificial system and test the drives in external USB carriers. If you worked your way through the flowchart and arrived here without getting the power on or recognizing any of the known failures, it's pretty much down to a stone dead power supply or motherboard. I always go for the power supply first because it makes more sense than chasing around for a motherboard that will support the same CPU and RAM. Repairing a bad power supply is possible but you'll need a good technical background and it's not something I do myself. And if it's a new build, before you throw anything out, remember you may have simply hit an incompatible motherboard and power supply combination, and a little Internet research may even turn up that it's a known issue.
have double vision, because it may not support the signal format the video controller of the test computer is generating. If your LCD monitor displays a very faint image that doesn't respond to brightness controls, it means your backlight is out. If it's a newer LCD with an LED backlight, it's most likely a failure to power the LED strip. If it's an older LCD with a CCFL backlight, like older laptops, it's more likely the inverter than the CCFL tube. Monitor inverters sometimes buzz audibly when they are failing. LCD monitors often support both DVI and SVGA connectors. If you are using the SVGA connector, inspect the pins to make sure they are all perfectly straight. If any are bent, you can try to straighten them with tweezers or needle nose pliers but if they've been bent over flat, they'll most likely break. It's normal for a few pins to be missing from the connector as long as there aren't broken off stubs, it just means they weren't supported by the monitor. But if you do have a broken pin, I recommend finding a replacement cable (ask friends if they have one around) before trying to solder on a new end. The last time I did one with my shaky hands, it took me a couple hours, and the replacement connector costs more than a factory manufactured cord. New monitors often ship with both SVGA and DVI cables, because the cable cost is low to the manufacturer compared to getting a returned monitor when the customer didn't get the right cable. This means you might have a spare cable yourself, and even though your video adapter in the PC probably doesn't support both types (some do), all you need is a video converter plug, which is a standard computer/electronics store item. SVGA Video Connector Pin-out 1-Red 2-Green 3-Blue 4-Monitor ID (Note: pins for ID bits often not present) 5-Ground 6-Red Return (coax shield) 7-Green Return (coax shield) 8-Blue Return (coax shield) 9 No-Connection 10-Sync Ground 11-Monitor ID 12-Monitor ID 13-Horizontal-Sync 14-Vertical-Sync 15-Monitor ID Did the PC let out a long series of beeps when you turned it on? A long series of beeps is a common code for video card failure, but it doesn't mean the video card is bad, it may have just popped out of the slot. If you search the internet for troubleshooting beep codes, you should be able to find exactly what your PC is trying to tell you. But I mention that the long series of beeps is often video adapter failure in case you don't have access to the Internet because your computer monitor isn't lighting up. Check that the video card is sitting down in the motherboard slot. You have to open up the PC for this procedure, so unplug the power cord first. Before opening the case, take a look for the location of the video port on the PC. If the video port located on one of the shiny stainless steel plates that are lined up one after another on the back of the case near the bottom of a mini-tower, you have an add-in video adapter. But if the video port is within a half inch of the USB ports, mouse and keyboard port, etc, the video controller is probably integrated on the motherboard, so check the manual before you bother opening up the case. Assuming you have an add-in video adapter, the only way to be sure that it's seated is to remove it and reseat it. Check both ends of the adapter at the motherboard level for locking latches before you remove the hold down screw and start pulling on it. After you seat the video card in the slot and close and locking devices, go ahead and put the screw back in, but make sure it doesn't cause the opposite end of the card to rise up as the end under the screw is pushed down. If you couldn't find the meaning of the beep code, and reseating the video adapter doesn't fix the problem, it's likely the video adapter is dead or the RAM installed on the motherboard has failed. RAM failure is also a common, repeated beep code, which is why it's worth looking up which one you have if you can access the web. See the flowchart for troubleshooting the motherboard RAM and skip to that point for the swapping tests you can do.
Does the PC display the initial BIOS screen identifying the hardware and then freeze? If so, it's probably not a video card problem unless you just installed a new one, in which case there could be a conflict or compatibility issue. Did the problem appear right after you installed a new PCI adapter and closed up the case? This type of failure is pretty rare with newer PCs due to dedicated slots for video cards being isolated from the PCI bus, but I try to support older generations of PCs that used plain PCI video cards on the flowchart as well. If this is the case, try uninstalling the most recently added adapter to see if it's a conflict. While you have the case open, whether you have a high performance gaming video adapter or integrated motherboard video, check for the presence of an active heatsink (a fan mounted on finned metal) above the video processor. Some video cards for gaming are practically covered with a heatsink, and if the fan isn't active when the power is on, there's a real good chance it failed, causing the video processor to overheat and fail as well. Does the Windows Desktop appear after stripping the other add-in adapters out of the system? If so, the only thing to do is troubleshoot the problem adapter by replacing them one at a time until the problem reappears, making sure you power down and unplug the power cord before each replacement. If you just built the PC or replaced the motherboard, try the video adapter in another computer before throwing it away because it could be a simple incompatibility. Even if the PCI Express version matches or the AGP speed (8X, 4X, etc) matches and the adapter fit into the slot, it could be the video card brand was never tested for the motherboard brand. Some AGP video cards were supposed to support multiple speeds, which led to funky card notches and confused the issue for everybody.
because it only takes a minute. Just makes sure there isn't something resting on the keyboard, which can produce an unending string of beeps. Are the default settings in CMOS Setup chosen for the motherboard? If you've built a new PC or if you've been playing with overclocking an existing CPU and motherboard combination, the best troubleshooting step at this point is to restore the defaults. New motherboards do this through CMOS but old motherboards often used motherboard jumpers or even DIP switch banks (albeit a long time ago). If CMOS Setup doesn't offer an option to restore the defaults, you'll have to inspect the motherboard (or the documentation) for jumpers. Before you move to the next step, it make sense to try the bare bones configuration suggested in power supply troubleshooting. Strip out everything except the video adapter and disconnect all the drives to see if you can get as far as a live screen with a boot failure message stating that no operating system is found.. Rebuilding the computer outside of the case is the last step in troubleshooting to eliminate mechanical binding due to installation in the case and to make sure there are no shorts under the motherboard. And if you're going to to swap the CPU, it's simply easier to do with the motherboard on the bench than buried in the case, particularly in small format ATX cases with the power supply right next to the CPU socket. You shouldn't try this procedure if you aren't comfortable working around live electronics, and you should never walk away from a system built up without a case or you may come back to find a fire. If you've built the PC yourself in a custom case, make sure that you haven't accidentally included metal standoffs where the motherboard didn't offer a grounding point, and if you're using standoffs from your spare parts pile, make sure that they are all the same height. Whenever I build a PC, I count the number of standoffs installed, and lay aside that number of screws for securing the motherboard. If I don't use up all the screws, I know something is wrong, that there's a standoff in the wrong place with no screw hole in the motherboard. If the system boots up fine without the case and fails again as soon as you reinstall it, try another case and power supply. If the motherboard is new, whether a new build or replacement, it's time to get an RMA and send it back to the retailer. If it's an old motherboard, and running the system outside of the case still won't light up the screen, there's not much left to try other than a CPU swap. If you already noticed that the fan on the heatsink was dead, buying a new CPU (and a new heatsink) is a good gamble, but if the fan was operating, you have to ask yourself if you really want to own that generation of CPU if it turns out the motherboard is faulty and you now have to replace that as well. If the motherboard is old, you should be able to find a cheap CPU as a "pull", a CPU removed from a working PC by a scrap operation. Try eBay and Amazon Marketplace for sellers. I've done a couple generic illustrated pages for removing a motherboard and installing a new motherboard. Does the system beep once and then freeze before beginning to load Windows? Freeze up could occur at a splash screen from the Video adapter BIOS or from the motherboard BIOS, or on older systems, during the memory count or while verifying DMI data pool. Problems with multi-core CPU throttling or CPU parking (you can see these in newer Windows versions through the Task Manager > Performance tab) reduce performance but don't impact anything before the operating system starts to load. Some older Windows installations may fail on dual-core and quad-core CPUs unless you disable all but one core. Sometimes it will be obvious there's a problem managing the multi-core CPU when you look at the performance and see one or more cores pegged at 100% when they shouldn't be doing anything, but those aren't boot issues. Strip out all the add-in cards except the video and disconnect the drives and see if you can get passed the freeze. If the PC now tries to boot and gets as far as complaining about no operating system, reconnect the hard drive and proceed from there. The nice thing about single channel memory systems is you only need two DIMMs to troubleshoot whether one is bad by installing just one DIMM in bank zero, and then the other. Dual channel memory means you need to own four DIMMS to swap banks, though three DIMMs will allow you to shuffle two at a time through a dual channel set-up and may allow you to spot the bad memory module. But all three pieces need to be matched (same manufacturer) or they probably won't play together. The newest motherboard with triple channel RAM mean it takes a minimum of four matched DIMMs go through the possible combinations to eliminate one bad piece, or six DIMMs to swap them out in one shot.
It's a good time to double check that the RAM you are using was tested and approved by the motherboard manufacturer. Using unapproved RAM may be responsible for intermittent lock-ups, which are nearly impossible to diagnose unless they get worse over time or you take the initiative to swap out the RAM with approved DIMMs. If you've changed the CMOS settings from the factory default, try restoring them. This is usually a main menu item is CMOS Setup. If you've been overclocking and resetting to the default allows you to boot, don't rush to start overclocking again, give the system a day or two to see if it's stable now. Don't assume that overclocking has to work in your PC because you read on the Internet where somebody with the same motherboard, CPU and RAM got it to work. Overclocking is about pushing components beyond their rated capacity, so the guy who it worked for may have got pieces that are simply better than yours. An overheating CPU will either lock up the PC or lead to automatic shut-down for thermal protection. If you're getting unintended shut-downs, or if you monitor the CPU temperature from CMOS Setup or within the operating system and see that it's running too hot (and running away), the only thing to try is redoing the thermal compound or replacing the heatsink. With the system shut down and the power cord unplugged, remove the existing heatsink and check the condition of the existing thermal paste or pad. I've always used alcohol for cleaning electronics, other people have their own methods, the important thing is not to leave a foreign residue before you apply the new thermal paste. See the illustrated guide for how to replace a CPU on this site. Don't go over the top with thermal grease or you'll just make a mess. The grease isn't a gasket or a sealer, it's just there to fill in the microscopic pits and valleys in the CPU to bring them into thermal contact with the heatsink. And don't use some random goo you had lying around the house for thermal grease, buy some from an electronics store or online. If the fan on your heatsink doesn't spin when it's powered, you may be able to replace just the fan (if you can find one that size) or you may have to purchase a new heatsink with the fan installed. Avoid buying a generic heatsink that's supposed to work with a lot of different systems. Try finding one designed for you particular motherboard socket and CPU by searching online stores that sell motherboard and CPU bundles, and checking what heatsink they provide with your particular motherboard and CPU.
If the drives still don't register properly, make sure the power cable is seated in the drive's power socket, which can take a bit of force. The ribbon cable connectors must also be seated all the way into the IDE port on both the drives and the motherboard, or adapter card if you're are using a RAID adapter. The most common reason for a cabling failure of this sort is that the connection was partially dislodged when you were working in the case on something else. Try a new ribbon cable. While cable failures are rare, it can happen, and it's a favorite trick of investigative reporters writing articles about computer repair rip-offs to intentionally introduce a bad IDE cable into a PC, just to see how many parts a shop will sell them. Are the ribbon cable connectors and the IDE ports on the drives and the motherboard keyed such that the cable can only go one way? Check the pin 1 location on all of the connectors and ports. On IDE drives, pin 1 is traditionally located next to the power cord, but it's not a 100% rule for all time. Motherboards can be pretty strange about cable ports. I've even remember an old one where the pin numbering on the floppy and IDE interfaces were oriented in opposite directions. The pin 1 location on the motherboard is normally marked with an arrow, a dot, a white square, anything to show one end of the interface as different from the other. If the motherboard won't register any drive you attach, even on new cables, and if those drives are spinning up, it indicates that either the IDE controller is bad or all the drives you've tried are bad. You can try running on the secondary IDE controller if you've only been working with the primary, but the next stop is installing an add-in IDE adapter or replacing the motherboard. The troubleshooting procedures for ATA drives that aren't recognized by the BIOS are identical, whether they are hard drives, CDs, DVDs, tapes or any other ATA device. If the BIOS registers the installed ATA drives correctly and the drive you're having problems with is a CD or DVD, proceed to the CD or DVD Failure diagnostics. Does the drive cycle up and down? Try swapping the power lead for a spare or one used by another drive. For older IDE drives, try isolating the drive on its ribbon cable, even if it means temporarily doing without another drive for the sake of troubleshooting. If neither fix helps, try disconnecting the data cable to ensure that the drive isn't receiving some flaky power down signal from a bad ATA interface or crazy power management scheme. If it still cycles up and down, the drive is probably toast. Test the drive in another system or a USB shell before labeling it dead. If you have an old drive that spins up but won't seek (you never hear the head move in and out), it's probably a mechanical failure. The last ditch effort before giving up or sending it out for data recovery is tapping lightly with a screwdriver on the cover of the drive, away from the circular section where the disks are spinning. This might encourage a stuck head to get moving. Freezing the drive for a few hours in the freezer (use a sealed bag) may get you temporary access to a drive with failing electronics that overheat in a hurry. Just make sure you have your backup media prepared if you try any of these last ditch efforts, because it may work just the one time. Does the drive make little clicking noises and fail to get going? Restart the machine, with the reset button if you have one, and hopefully it will boot. If not, try in a warmer room, or put the PC in direct sunlight to warm up and then try it again. You can also replace a laptop hard drive, in fact, it's one of the few components that can be easily procured. It's far from guaranteed, but this is one of the few problems that can result from the drive being too cold rather than too hot. If you do get it started, run ScanDisk. It doesn't hurt to reseat all of the cables on the drive and the ribbon cable to the motherboard, since connections can also loosen up over time. However, if you can't get it going, it could be a legitimate drive failure. If you mind losing all of the data onboard, try FDISKing and reinstalling the operating system again. Does the BIOS report the transfer mode correctly for older PATA drives, ie, UDMA/100, ATA/66? UDMA must be enabled in CMOS, or set on "Auto," for high speed transfers. IDE hard drives after around 1995 require the 80 wire ribbon cable, at least for high speed operation. You can check CMOS Setup to see if there's a manual override to select the higher speed transfers, though the automatic settings should pick it up. Also try isolating the hard drive as the sole device on the primary controller. If you're adding a new hard drive to an older system, it's possible that the old motherboard and BIOS simply don't support the faster transfer, even with the new cable. I'd be leery of flashing the BIOS to try to get the speed up, even if the motherboard manufacturer supplies it. Can you install an operating system, or access the drive with any generation of FDISK to create or view partitions? Check again that the ribbon cable is fully and evenly seated and there aren't any "read only" jumpers set on the drive (normally only found on SCSI's). Try a new ribbon cable. If this doesn't do it, it sounds like either the drive's MBR is messed up, or there's a problem with the way the software is communicating with the BIOS, which really shouldn't happen. If you don't mind losing whatever info is on the drive, you can try FDISK/MBR and see if it helps.
old location to the hub. It could be the patch cable, easy to test now by swapping it into the new location, it could be the cabling in the wall, or it could be the port that it's ultimately connecting to at the patch panel or hub. On the other hand, if the PC can't connect to the network at the new location, you know that the problem is within the PC, either the network adapter or the software configuration. Are you (meaning the PC) experiencing intermittent problems connecting to the network rather than a total failure? The RJ-45 connector may be at fault as the wires can loosen up in the crimps and make for a flaky connection. In rare cases, you might be getting so much noise on a badly routed cable that it's overcoming the network signal level. But it's more likely that the problem is really software, some other task essentially locking up the network software you are using which then appears to be a network failure. See if rebooting helps, and if the problems only occur after you've used other applications. And talk to other network users to make sure that it's not a network wide traffic or resource issue that you or the user of this workstation is just noticing. Are we talking about an obsolete setup with shielded twisted pair or another type of shielded cable other than Cat 5? For grounded cable, the shield can only be grounded at one end or a current loop will likely ensue, while if neither end is grounded, the shield functions as an antenna which can weaken the network signal or attract noise. Don't count on any cable's noise isolation to make it 100% safe to route it through the noisiest electrical environment, it makes more sense to stay away from problems. Don't forget that networks all have distance limitations, whatever equipment is used. You can't count on using the maximum distance defined by the network standard, you have to use the lowest number given by any of the hardware components (hubs, routers, network adapters) on the circuit. And remember that all distances are actual cable distances, not measurements from a blueprint. If you're using repeaters to boost the signal, there are limits there as well since the distances effect transmission times and can lead to time-out problems if the setup is finicky. Did you try connecting to a known good port on the hub? Never assume that a hub or router port is good because it used to work and the light seems active. Move the workstation cable to a RJ 45 port that's working now. Can you associate the problems with peak usage periods for the network? If the problems only show up when everybody is working on Friday payroll processing or watching Internet videos at lunch, odds are it's just a bandwidth issue and you need a faster network or to split the existing network in two. If the network runs a mix of 1000BaseT and 100BaseT adapters, it's worth updating everybody to Gigabit, even if it means sticking PCI network adapters in older PCs that have 100BaseT integrated on the motherboard. Are you sure the problems only show up when the PC is using the network? If the PC is having trouble all the time, you're really on the wrong troubleshooting flowchart. Run the usual anti-virus and anti-malware software to make sure the operating system hasn't been compromised, and then start back at the beginning of the troubleshooting series, especially the motherboard CPU and RAM and hard drive troubleshooting flowcharts. I find it really helpful to keep one super long bypass cable that will let me temporarily connect any workstation to a hub without using the in-wall wiring. Sometimes it's just more practical than moving the whole PC, though you shouldn't run a wire on the floor while other people are working in the office. Did you try swapping in a cheap PCI network adapter? PCI network cards are practically free, so any time you're dealing with PCs rather than laptops, it make sense to stick in a PCI network adapter to make sure the existing add-in adapter or motherboard network support hasn't failed. You may have to disable the motherboard network adapter in CMOS to get the new one recognized. At this point, we've eliminated the physical layer of the network as being the problem, so if the PC can't connect with a proven replacement adapter, the problem is software settings.
For older CD and DVD drives, whether they are SATA or older IDE drives, a separate stereo audio cable had to be strung from the back of the drive to the sound card to play music CDs. The drive actually had a built in D/A converter and played the music CD at the same 1X speed used by stereo equipment. Check that this 3 or 4 wire cable is connected to the back of the drive on the one end and the sound card or motherboard sound controller on the other end. If it's a new build, you'll also have to make sure that you chose the right connection points, because the thin connectors are unkeyed and can be forced onto just about any set of pins. If you have two DVD drives, or a DVD recorder and a separate player, or any combination of DVD and CD drives in the system, it may be that only one of them will have the audio patch cable, and that's the one you should play music CDs in. If DVD movie discs that play on your TV won't play on your PC, it usually means there's a software problem with the CODEC (Coder/DECoder). Don't assume a given DVD disc is good because it's new or you just got it in the mail from NetFlix, check for yourself that it plays on the TV. Sometimes your PC media player will report an error message that the screen settings (resolution, number of colors) are wrong for a particular movie DVD, which will prevent it from trying to play. Your player software might also lack the particular decoder (CODEC) for that disc. I remember one instance where the movie player software received an automated update after which a movie that played fine a few weeks before was no longer supported. There are plenty of Internet pirates selling CODECs for movie players, but if you search for the manufacturer of the software that came with your PC or drive, you should be able to get an updated version for free. The movie industry is always experimenting with copy protection schemes which may make some movie discs unplayable in computer drives (versus entertainment DVD players) even though you aren't trying to copy them. In radical cases, your DVD player might require a firmware update to play newer Hollywood studio movies, which can only come from the drive manufacturer . Do you have trouble recording DVD or CD discs? See the troubleshooting flowchart for CD/DVD recording problems. If you have trouble reading or booting a retail disc in a recorder, continue here. The funny thing is it's getting harder to tell real manufactured (pressed) discs from recorded discs due to the fancy labeling software and direct on disc printing options available for recorded discs. It used to be obvious because discs pressed in factories had a silver read surface while recorded CDs were gold or green, but but some companies have taken to producing short runs of DVDs with recorders and packaging them like factory discs. Does the DVD drive read the volume information for the disc? As soon as you mount a disc in a drive and it spins up, the drive should report the volume information, title, capacity, type of disc, in Windows. You should also be able to view the disc contents through My Computer or Explorer. At this point in the troubleshooting flowchart, it doesn't matter if you can install the software or play the disc, only that the drive is reporting that it can see the DVD or CD contents. Does the PC fail to boot operating system DVDs or known good rescue CDs that have boot tracks? Make sure you try changing the CMOS Setup boot sequence so that the DVD drive or CD drive you are trying to boot from is the first drive in the boot sequence. It shouldn't be necessary if you've just installed a new hard drive that hasn't been made bootable yet, but sometime the BIOS sees a bootable device where one doesn't really exist, so the order trumps appearances. In the old days, it wasn't that uncommon to find CD or DVD drives that took so long to spin up that they missed the BIOS request for bootable media at power on. That where opening and closing the drive to initiate spin up and hitting the old reset button used to work, but it's really a legacy issue. Does your PC include both DVD and CD drives? Dumb as it sounds, I see plenty of those PCs still in use and you're never going to get anywhere trying to read a DVD in a CD drive. Back when DVD recorders were still expensive, some manufacturers sold CD recorders that could read but not record DVD discs, which confused the pants off a lot of people. For problems reading recorded discs, skip to the troubleshooting flowchart for recording issues. Are you sure you put the disc in the right drive? When a PC has two physical drives, watch the LEDs on the drives to make sure the operating system is actually trying to read the drive you put the disc in. I once opened up a PC to check the connections because I had been fooled by the labels (D: and F:) pasted on the faceplates of the drives, which didn't actually agree with how the operating system saw them. Did you try a selection of different DVD discs in your DVD drive, or CD discs in your CD drive? Try the drives with a variety of factory stamped discs. If some discs work and other discs don't, the problem much more likely the discs than the drive. Visually inspect the discs for obvious scratches, abrasions, stains or fingerprints. I use a bit of flannel shirt to clean discs, whatever you use for eye glasses should work fine. Just remember that the disc surfaces are plastic so you can't use any chemical cleaning agents that might melt in. If there are deep scratches on the label surface of the disc, they can
distort the other surface to the point of making it unreadable. Always try your discs in another player before throwing them away. Does the operating system show that the drive is installed? Check My Computer in Windows for the drive or see the installed hardware in Control Panel > Device Manager. If the drive appears in CMOS Setup but not in the operating system, get the latest version of the driver software from the manufacturer website and try installing it according to instructions. If the drive boots an operating system disc but the drive doesn't show up when the operating system boots from the hard drive, it's definitely an software driver issue. There may be a firmware update for operating system compatibility of the drive available through the manufacturer, but this really shouldn't come up unless you just upgraded to a new operating system version or bought a drive that's been sitting in a warehouse for quite a while. I never had any faith in cleaning kits for DVD or CD drives, but they aren't that expensive so I wouldn't blame you for trying one. If your system is new enough for the DVD recorder to be SATA, there won't be any cabling issues or Master/Slave setting to worry about. If it's a new build, about the only thing you can get wrong is attaching the SATA cable to a motherboard RAID controller rather than a standard SATA connector. If the drive powers up OK and spins discs but won't read anything, the best thing to do is check it in another system with SATA support. There is always the chance for a conflict or Master/Slave jumpers being set wrong on older ATA drives using ribbon cables for data. You can quickly try moving the DVD drive to the secondary controller if it's been set as Slave to the boot hard drive on the primary controller, but otherwise, you should see the troubleshooting flowchart for ATA drive failure.
service. Cable modem are much less likely to work if you move them from location to location because cable companies have all sorts of schemes for preventing piracy, and you may find you need them to reprogram a modem to get it to work on a different account. If you are experiencing intermittent signal failures with a cable modem, there's a good chance it has to do with wind or weather disrupting the connection outside your house. But it also pays to shorten the path from the cable modem to the interface installed by the cable company as much as possible, as every connection and splitter inside the house results in a drop in signal strength and increased electrical noise. Return to Diagnostic Chart DSL modems require you to install high frequency filters on every other phone connection that uses the same circuit (phone number) that the DSL modem is using. If you don't install the filters, you'll get background noise whenever you talk on the phone that degrades with Internet activity. Worse than that, some intelligent phones, fax machines and answering machines create their own digital traffic on the line, interfering with the DSL modem so it can't negotiate or maintain an Internet connection without the filters being installed. Any time you are setting up a DSL modem for the first time, if it can't negotiate an Internet connection after the phone company reports that Internet access has been turned on, you should unplug every other device using the phone circuit to see if that makes a difference. If it does, you can easily work out the problem device or the faulty filter by process of elimination. Return to Diagnostic Chart The easiest test to see if your DSL modem has failed is to borrow the same model from a neighbor who uses DSL from the same phone company. If the modems aren't identical, it may still work without any software installation, it's just easier if they are the exact same model. If you don't like asking to borrow a modem, you can do the opposite and bring your modem to their house and connect it in place of their own. The point is to isolate the problem to the modem or the phone wiring. Return to Diagnostic Chart In cases where your modem only offers a choice between a single network port and a USB port to connect your PC, try uninstalling the software, connecting by the other method (ie, the one you weren't using), rebooting, and reinstalling the software. If you're using the USB connection, try swapping out a known good USB cable from a printer or any other USB device. If you're using the yellow network cable with RJ-45 connectors, see if you can dig up one from the past to try, as they get shipped with all sorts of modem and router devices. If your modem includes a multi-port router, connect the cable from the PC to a different network port. Just because the LED link light for the port is lit doesn't mean that it's working, it's just a continuity test for power. If you've only tried to connect via a wired PC and the router includes a wireless capability, enable wireless and try connecting with a laptop or a WiFi Kindle, anything that could confirm that the Internet connection is good, and therefore, your PC networking link is the failure point. When any one of the alternates above work, like taking the modem to a friend's house or successfully connecting to the Internet via wireless, it reduces the possible problems to your PC.
You can certainly test the USB port if you've connected via USB, testing the network port would require a networkable device, but if you've swapped cables and Windows claims the network adapter functioning, it probably is. The remaining issue is software, either the installation of the software supporting the modem or the presence of other software on your PC preventing it from working. The main culprit is usually fire wall software blocking Internet access, and other than disabling the firewall, it can be very tricky to troubleshoot. If you can stand waiting on hold, try calling the technical support line of your Internet service provider and they should be able to take you step-by-step through all the possible choke points. Return to Diagnostic Chart Did the modem take the phone off hook and dial? PC modems always include a tiny speaker that's good enough to hear the dial tone and to listen to the phone dialing. If you aren't sure if the volume is on, go to Control Panel in Windows and check the modem properties. If you're using a laptop computer, the modem sound normally plays through the speakers, so make sure the regular volume control is turned up. Return to Diagnostic Chart Do you hear the ISP modem connect and negotiate with your modem (whistling and hissing). If the modem on the ISP end doesn't pick up, double check the phone number you are using. To check if the ISP is working, you can dial the phone number from a voice phone and see if their modem picks up and tries to negotiate with you! Return to Diagnostic Chart Modems aren't any smarter about outside lines and prefixes than regular phones, so if you need a dialing prefix to connect from your regular phone, make sure the modem is using it as well. If you work in a business, try dialing out over the fax line, which will have a clear path through any PBX equipment. Dialing "9" to get out of a PBX is common, and for a modem prefix, add a couple commas after the "9" to introduce a delay and allow for the outside line to be connected. Of course, if the ISP phone is busy, that's a problem on their end, and they may just not have enough function modems in their pool. Finally, if your modem dials but instead of trying to connect a call, all you hear is the dial tone followed by a recorded message from the phone company that your phone is off hook, it means your line was set up for an old rotary pulse dialer, while the modem is using the modern push button tone system. You can change from "tone" to "pulse" in the modem properties which can be found through the Control Panel icon in Windows. Return to Diagnostic Chart Does your dialer software kick back with an error message like "bad protocol" or "can't connect" after you hear the ISP modem pick up? These errors tend to be so vague that they could mean anything from a mistake typing your user name or password, to the fact that your service was cancelled because you didn't pay the bill. If you've connected with the same modem before, try
redialing a couple times through the course of the day to make sure the problem isn't just noisy phone lines or bad modem in the ISP pool. Return to Diagnostic Chart Can you confirm that your account information and password is correct by refering to correspondence from the ISP or by contacting them over the phone? If you have the password and the login name correct and these have never changed, it's unlikely that the problems are due to specific modem settings (unless you made changes). If you can connect at some times and not at others, the problem is almost certainly due to line conditions cropping up from weather, heavy phone traffic at a certain time of day, or randomly hitting faulty modems in the ISP's modem pool. Wet weather is a killer for old telephone company infrastructure, as is windy weather. Return to Diagnostic Chart Can you get an Internet connection if you lower the modem speed? You may have to search the Internet for a command line control string to do this since the changes to the speed done through Windows Control Panel aren't always effective. I know you don't want your slow dial-up connection to work even slower, but it's a good troubleshooting test. If you can connect at a lower speed, move to the flowchart for modem performance Return to Diagnostic Chart Have you tried connecting to another ISP? If your modem dials, whistles, all the good stuff, and you still can't get a connection, the fault may be with your ISP. If you can find a CD from another service kicking around, AOL or whoever, you can install it just to find out if the modem will connect to their service. You don't need to sign up with them for this test, if it gets to the point that they are asking for your credit card, you'll know that the modem is working fine and you can quit. Return to Diagnostic Chart If you get a message stating "No Dial Tone", it means that you plugged the phone wire into the wrong port on the modem or the phone wire isn't live. The proper port on the modem to connect to the patch cable to the wall jack is labeled "line." The jack labeled "phone" is for connecting a voice phone to the modem to save you from needing a splitter. To test that the wall jack is good, connect a regular phone and see if you get a dial tone. If the wall jack is live and the PC doesn't report a dial tone, swap out the phone patch cord from the modem to the wall jack, and if that doesn't do it, the modem is bad. Return to Diagnostic Chart Has the most recent software driver for your modem been installed? Whether your modem is an add-in adapter or integrated on the motherboard, you should be able to find the latest driver on the manufacturer's website. As with all add-in adapters, modems often sit on the store shelf for many months or even a year or two before selling, so the fact you just bought it doesn't mean you got the most recent driver software in the box. See my illustrated page for replacing dial up modems
Return to Diagnostic Chart Does the modem show up in Device Manager without any problem reports? If Device Manager reports anything wrong, an exclamation mark or a question mark, the first step is to reinstall the latest drive. You really shouldn't run into Interrupt Request (IRQ) conflicts on recent PC's with plug-n-play operating systems, and most add-in modems no longer come equipped with jumpers for manually setting the resources. If you do have a conflict, try uninstalling the modem, going through a reboot cycle, shutting down and reinstalling, and see if Windows can sort it out. If not, see the troubleshooting flowchart for conflict resolution. Return to Diagnostic Chart Did Windows report that the modem was already in use when the software tried to dial? The first thing to do is shut down, reboot, and see if the problem fixes itself. Next, try using the "More Info" option for the modem which is reached through the Modems icon in Control Panel, under the Diagnostics tab, to see if Widows believes the modem operational. When the port is reported as already in use, it means Windows thinks that another program is using the modem. This isn't a common error anymore but in the old days, it sometimes happened that other serial port users, like the original digital cameras or the personal data assistants (PDAs) that have been replaced by smart phones, used poorly written software that took over the modem's resources on boot. Return to Diagnostic Chart
chipset on the motherboard, check the motherboard manufacturer website and see if they have an updated driver. Return to Diagnostic Chart Did the sound card or the motherboard sound chipset show up in Device Manager? Even more importantly, if the audio hardware did show up in Device Manager, was it reported as working properly? Device Manager should be able to identify sound controller hardware by it's response even if no driver is installed. If Device Manager can't locate the sound card at all, make sure that it's seated properly in the PCI slot (if it's an add-in adapter) and that it's enabled in CMOS setup if it's on the motherboard.. Return to Diagnostic Chart If Device Manager sees a conflict between the resources required by the sound card and other PC hardware, check the resources for all the devices installed to find out where the conflict is being generated. New computers shouldn't have these problems because most devices today have their resources allocated by software, but some add in adapters may still hard wire an interrupt or the address space with jumpers. Try changing the resources allocation in Device Manager, and if that doesn't work, try pulling an add-in adapter to free up resource space and let the allocations reshuffle. Any time you see a "!," "?" or "i" in Device Manager for your audio hardware, move on to the flowchart for troubleshooting hardware conflicts. Return to Diagnostic Chart Check the documentation for the sound card if the symbols stamped into the metal above the audio jacks aren't obvious to you or clearly color coded. If the speakers aren't plugged into the right jack, you can't expect them to work. Most new sound cards support some variety of surround sound, 5.1, 7.1, 8.1 audio, but always try to get the front speakers working first. The stereo audio jacks should all be plugged firmly into the corresponding ports, and the cables shouldn't display signs of having been pinched to the point of crushing. Of course, if you are running USB speakers, they bypass the standard sound system entirely, and will work as long as the right driver is installed and the USB hardware hasn't failed. Return to Diagnostic Chart If you are troubleshooting USB speakers or a USB sound card (really an external sound system connected by USB), move the connection to a different USB port on your PC. The USB ports on the front of the PC case are always connected to the motherboard by wires, while the USB ports on the back of the PC are generally mounted directly on the motherboard in the I/O core. The USB ports can fail physically when something outside the PC jerks on a connected cord, like tripping over a connected printer or dropping a USB keyboard. Try your USB speakers on another computer or laptop. If you can get the USB sound to work on another system, you know that there's a problem with your USB ports or that the software isn't installed properly. Of course, it could also mean that you have the "muted" all sound in the software mixer on your PC and took a wrong turn in the troubleshooting flowchart.
Return to Diagnostic Chart Software volume settings are the main culprit when PC sound suddenly fails, and it can be tough for you to find the mixer controls if you've never used them yourself, but somebody else turned down the sound while working on your computer - perhaps so you wouldn't hear them playing video games all night! There are often multiple volume controls to go along with the main volume in the system tray at the bottom of the Windows Desktop. Some devices include their own mixer panel to allow you to disable other sound functions in the computer when using them, and if the software is poorly written, sound may appear to be enabled in one place and disabled in another. It's much less of a problem on new PCs, and almost unheard of with brand names, but if you've built your own PC with an add-in sound card, a DVD recorder, and installed recording and communications software that offers a lot of options, hunt through the sound controls for these to check for "mute" buttons being enabled or volume sliders being turned off. Return to Diagnostic Chart Do you get all of the sounds you expect out of your PC except you can't hear music CDs? See the troubleshooting flowchart for CD and DVD playback if this is the case. A test you can do for your speakers and cables is simply moving them to any other sound producing device like a laptop or an old radio that has an unamplified speaker (line) jack. Any time you try using powered speakers on a different system, turn the volume control on the speakers and the stereo all the way down first, in case the audio output is actually amplified. If your speakers don't work anywhere, their internal amplifier or their power supply is blown or the cables have failed. You can try swapping the cables if they plug in at both ends, rather than being molded to the speakers. And if you have a multimeter, you can measure the output of the power transformer and see if it matches the label. Return to Diagnostic Chart If the sound card is only recognized by Device Manager after you remove every other add-in card except the video adapter, it means there's a hard wired conflict or an incompatibility between the sound card and one of the adapters that's been removed. If we're talking about a brand new sound card or a newly built PC, check the manufacturer's instructions for the exact procedure they wanted you to follow when installing the sound card. It may be that the software had to be installed before adding the sound card, or it could be the hardware was expected before the software was run. If this was done backwards, you must uninstall the audio software in Control Panel, shut down, do a clean reboot, shut down again and then start the installation process over again. You might want to see my step-by-step illustrated guide to replacing a sound card. Return to Diagnostic Chart If you don't have an add-in sound card and the integrated motherboard sound controller is your only audio source (ie, no USB speakers), restart the PC and enter CMOS Setup to make sure the motherboard sound is enabled. If you have the motherboard documentation, you should also check that there isn't a jumper on the motherboard for disabling the built-in sound controller. But if you are using an add-in sound card, you absolutely have to disable and motherboard sound controllers before it will work properly. If you determine that your motherboard sound has failed, the easiest fix is to buy a pair of USB speakers. If you are looking for higher quality sound for gaming, a USB
sound card that does 7.1 sound would probably be your choice. But if you play CDs or DVDs on your PC and you make the change to USB sound, those drives must support DAE (Digital Audio Extraction). USB sound won't be able to play analog music unless DAE is supported by the drives. Return to Diagnostic Chart In the case where Windows won't register a sound card in Device Manager no matter what you try, strip every adapter except the video card out of the PC, shut down and reboot, and let Windows adjust to the minimal configuration. After you go through the reboot cycle and Windows stops reporting errors, shut down, install the sound card according to instructions, and give it another shot. If Device Manager still won't recognize the sound card, it's either incompatible with your motherboard or it's bad out of the box. Return to Diagnostic Chart