Logs de erros comuns (Pode ser utilizado para outras versões do Windows)

 STOP Errors

Error Message: "STOP: 0x000000B8 (0x00000000,0x00000000,0x00000000,
0x00000000) ATTEMPTED_SWITCH_FROM_DPC address 0xf729a248 in XX."

Translation: When you access an Iomega Zip drive that's connected to your computer's parallel port, you may see this STOP error message (an unexpected system error that Windows is unable to recover from; also known as a fatal system error). Two of the files the Zip drive uses, Ppa.sys and Ppa3.sys (represented by XX in the error message), have problems that sometimes interfere with other Win2000 processes.

Solution: The Win2000 SP4 (Service Pack 4) corrects this problem. You can download SP4 via the Windows Update service or directly from www.microsoft.com/windows2000

Error Message: "STOP: 0x0000000A" or "IRQL_NOT_LESS_OR_EQUAL."

Translation: This usually means that a hardware device in your computer has failed. The most common culprit is a faulty memory module on the motherboard, but it can also be the CPU, motherboard, or drive controllers. If the message occurs during or after installing new hardware, one or more device drivers (small programs that let Windows communicate with a computer's hardware) may be using an improper memory address.

Solution: If the problem is hardware failure, remove all unnecessary hardware devices from your computer and try restarting your computer with a single memory module, disk controller, and video card. If the computer boots successfully, install additional hardware, one device at a time, rebooting after each installation. Continue this process until you determine which hardware device is defective.

If the problem is a new hardware installation, remove the hardware and its device driver. Contact the manufacturer to ensure that the device is compatible with Win2000. Update the driver, if necessary.

Error Message: "STOP: 0x00000077 (0xParameter1, 0xParameter2, 0xParameter3, 0xParameter4) KERNEL_STACK_INPAGE_ERROR."

Translation: This series of errors indicates a problem with accessing the page file (the file the processor uses to temporarily store data when actual RAM is unavailable) on your hard drive. Four parameters display in the error message, which we've labeled 0xParameter1, 0xParameter2, 0xParameter3, and 0xParameter4. If 0xParameter1 and 0xParameter3 are not zero (that is, not 0x00000000), then 0xParameter2 contains the I/O (input/output) status code (information about an operation that is transferring information from [input] or to [output] a device that's external to the computer's main processor), which describes what happened.

Possible values for 0xParameter2:

_RESOURCES. There isn't enough physical memory to load the paging file or there isn't enough free space on the hard drive to store the paging file.

_ERROR. There are bad blocks on your hard drive.

_CONNECTED. The drive controller cannot access the hard drive, possibly due to a faulty cable or connector.

•0xC000016A—STATUS_DISK_OPERATION_FAILED. There are bad blocks on your hard drive.

•0xC0000185—STATUS_IO_DEVICE ERROR. Improper termination or a defective cable on a SCSI (Small Computer System Interface)-based device.

Solution: Use the corresponding method to resolve the error.

•0xC000009A: Add memory or remove unnecessary files to create more hard drive space.

•0xC000009C or 0xC000016A: Use a hard drive utility to perform a surface scan of the drive and map out the bad blocks. Consider replacing the drive.

•0xC000009D or 0xC0000185: Check the cabling between the hard drive and the drive controller for breaks and tears. Make sure that cables are properly seated and any SCSI devices are properly terminated.

Error Message: "STOP: 0x00000023 (0xParameter1, 0xParameter2, 0xParameter3, 0xParameter4) FAT_FILE_SYSTEM."

Translation: This error occurs when you are using the FAT file system (the method an OS uses to keep track of files) and have a physical problem with a hard drive, or an IRP (Interrupt Request Packet, a method of sending data or commands between devices and the Windows Plug-and-Play manager) didn't complete successfully or is corrupted.

0xParameter1 contains the source file number (the first four hexadecimal characters after 0x) and the source line number (the last four hexadecimal characters) where the STOP error occurred.

Solution: Disable all backup utilities, virus scanners, firewall software, and any other software that runs automatically at startup. Verify the file system's integrity by running the CHKDSK utility and repairing any errors it reports. To do this, click Start and Run, type chkdsk in the Open field, and click OK. Contact the manufacturer to ensure that you have the latest drivers for your hard drive(s) and any removable media drives, including tape backup and optical drives.

If you are unable to boot your computer to run CHKDSK, try using the Recovery Console to run the CHKDSK routine. To do this, you will need to boot from a Win2000 setup CD or startup floppy diskettes. If you don't have these handy, you can make a set by booting from any Windows startup diskette that includes support for CD-ROM drives, such as Windows 95/98/Me.

After you successfully boot with CD-ROM support, insert the Win2000 CD. Navigate to the SUPPORTBootdisk directory on the CD-ROM drive and then run the Make-boot.exe or Makebt32.exe program to create the setup diskettes.

Boot from the setup diskettes. When the Welcome To Setup dialog box displays, press F10 to start the Recovery Console. When the Recovery Console prompt displays, you can try to repair the corrupted NTFS drive or partition by typing the command chkdsk X: /p where X is the drive letter (for example, C). When the command finishes, remove the diskette, type exit, press RETURN, and restart your computer.

If you still can't boot your computer, you may need to delete and re-create the corrupted partition. Unfortunately, you will lose all data on the partition.

Error Message: "STOP: 0x00000024 (0xParameter1, 0xParameter2, 0xParameter3, 0xParameter4) NTFS_FILE_SYSTEM."

Translation: There's a problem with the Ntfs.sys file, the driver that enables your computer to read and write data to a hard drive that uses the NTFS file system. The problem can be a corruption in the file, a damaged hard drive disk, or damaged SCSI or IDE (Integrated Drive Electronics) controllers (any device that controls data transfer between a device and a computer).

0xParameter1 contains the source file number (the first four hexadecimal characters after 0x) and the source line number (the last four hexadecimal characters) where the STOP error actually occurred.

Solution: Use the Event Viewer to check for error messages from SCSI or FASTFAT (the driver that Win2000 uses to access FAT file systems) in the system log. To launch the Event Viewer, click Start, Settings, and Control Panel; double-click Administrative Tools; and double-click Event Viewer. Check for error messages from Autochk in the application log. Error messages may tell you whether a device or a device driver is causing the STOP error.

Disable virus scanning, backup, disk defragmenting, and other programs that actively monitor the file system. If you have a hardware diagnostic program, it may be able to determine which device is causing the problem.

Run the CHKDSK utility with the /r switch to detect and correct file system damage, if any. To do this, click Start and Run, type chkdsk /r in the Open field, and click OK. If you are unable to boot your computer to run CHKDSK, try using the Recovery Console to run the CHKDSK routine. To do this, you will need to boot from Win2000 startup diskettes.

Before booting from the startup diskettes, you must modify the Txtsetup.sif file, located on the first setup diskette to disable the Ntfs.sys file from loading at boot time. Insert the first setup diskette into a working computer and then use Notepad to open the Txtsetup.sif file. Scroll through the file until you find the section labeled [FileSystems.Load]. Locate the line that begins with ntfs = ntfs.sys. Put a semicolon at the front of this line and save your changes. The new line should read, ";ntfs = ntfs.sys."

Boot from the setup diskettes. When the Welcome To Setup dialog box displays, press F10 to start the Recovery Console. When the Recovery Console prompt displays, you can try to repair the corrupted NTFS drive or partition. To attempt this, type chkdsk X: /p where X is the drive letter (for example, C).

When the CHKDSK utility finishes, remove the diskette, type exit, press RETURN, and restart your computer. If you still can't boot your computer, you may need to delete and recreate the corrupted partition.

Error Message: "STOP: 0x0000002E (0xParameter1, 0xParameter2, 0xParameter3, 0xParameter4) DATA_BUS_ERROR."

Translation: A parity error has been detected. This generally indicates a RAM failure in system memory, the L2 RAM cache, or Video RAM. It can also indicate a virus in the MBR (Master Boot Record, a small program, usually located at the beginning of a hard drive, that launches whenever the computer first boots) or a device driver attempting to access memory in a memory range that doesn't exist.

The four parameters provide the following information:

•0xParameter1: This parameter contains the virtual address that was in use when the fault occurred. This information can help experienced programmers locate a problem within a software program.

•0xParameter2: This parameter contains the physical memory address that was in use when the fault occurred. This information may point to a specific memory chip that
is defective.

•0xParameter3: This parameter contains the value of the Processor Status Register, which tracks CPU activity. The data represents the value that was present at the time of the fault. Programmers and hardware developers can use this information to determine the events the processor was involved in when the fault occurred.

•0xParameter4: This parameter contains the value of the faulting instruction register. This information may contain the instructions that the processor executed when the fault occurred.

Solution: If the error occurred after you installed RAM, there may be a problem with the installation. Make sure that the RAM is seated correctly in its connector and that the contacts are clean. If the problem persists, verify that the RAM is the correct type for this installation and is correctly rated for speed, voltage, and other parameters required by your specific computer. If everything is correct, contact the manufacturer of your computer's motherboard for BIOS (Basic Input/Output System, a small program that contains all the code necessary to access the basic hardware on the motherboard) updates, if any.

If there are no new components to explain the error, the problem may be a failed RAM module, a virus in the MBR, or a failing hard drive.

If your computer manufacturer provided a hardware test utility, use it to diagnose which RAM module is bad. If you don't have a diagnostic application, remove all but one RAM module and reboot your computer. If you don't get an error message, add one RAM module back at a time and reboot your computer until the problem returns. Replace the defective module.

Run a current virus scanner that can check and repair the Master Boot Block (the first location on a hard drive; usually contains the MBR) on your hard drive.

Although rare, it's possible for a failing hard drive to generate this error message. Use the CHKDSK utility to validate your drive. If your drive was formatted using NTFS, use CHKDSK with the /f (error-fixing) and /r (information recovery) switches. To do this, click Start and Run; type chkdsk /f /r in the Open field and click OK.

If none of these steps resolves the problem, consider taking your computer to a competent diagnostic testing facility. The problem may be a motherboard failure.

Error Message: "STOP: 0x0000007B: (0xF741B84C, 0x00000034, 0x00000000, 0x00000000) INACCESSIBLE_BOOT_DEVICE."

Translation: You may see this error message if you move a hard drive that contains a Win2000 OS to a different computer or if you install a new motherboard or hard drive controller. The Registry (a database that Windows uses to store configuration information) stored on the hard drive you're booting from doesn't have the correct entries for the new motherboard or hard drive controller. The Registry contains the PnP (Plug-n-Play) IDs that identify the hard drive controller. Win2000 uses the PnP ID to load the correct driver for the mass storage device. In this case, the device driver that Win2000 is loading from the Registry doesn't work with the new motherboard or your PC's hard drive controller.

Solution: If you see this error message after installing a new hard drive controller, your current Win2000 installation doesn't have the necessary drivers or the proper Registry entries. You can solve the problem by reconfiguring your computer with the old hard drive controller and attaching the hard drive that contains the operating system back to the original controller. Confirm that you can boot successfully and then install the new hard drive controller, leaving the old controller in place and the hard drive connected to the old controller. Boot your computer. Win2000 will recognize that a new controller has been added, install the necessary drivers, and make the necessary entries in the Registry. After you successfully install the new controller, shut down your computer, remove the old controller, attach the hard drive to the new controller, and reboot your computer.

If you see this error message after moving your hard drive to another computer, or after installing a new motherboard, you can repair the Windows installation. Boot from the Win2000 setup diskettes or the Win2000 CD. At the Welcome to Setup screen, press ENTER. Press F8 to accept the license agreement. Select your current Win2000 installation (it may already be selected) and press R. Follow the on-screen instructions to complete the repair process.

Error Message: "STOP: 0x0000007F (0xParameter1, 0xParameter2, 0xParameter3, 0xParameter4) UNEXPECTED_KERNEL_MODE_TRAP."

Translation: This error can indicate hardware or software problems, but the most likely cause is hardware. The actual failure is listed in 0xParameter1; the other parameters have no meaning. 0xParameter1 contains the actual trap values, which you can look up in X86 processor (any processor that's compatible with the Intel X86 architecture) manuals. The most common failures are:

•0x00000000: Divide By Zero Error. The system made an attempt to divide a number by zero. Poorly written software or corrupted data in memory can cause this problem.

•0x00000004: Overflow. An overflow condition occurs when the result of an operation, such as addition or multiplication, is beyond the range of the processor register that holds the result.

•0x00000005: Bounds Check Fault. This indicates that a chunk of data stored in memory exceeds its expected size. Poorly written software or faulty memory can cause this problem.

•0x00000006: Invalid Opcode (a program instruction that memory loads as needed). In this case the processor received an instruction it couldn't interpret. Failed memory that's corrupting data before it's sent to the processor is the usual culprit.

•0x00000008: Double Fault. A double fault usually results from a memory page fault. Here the processor attempted to access an unavailable memory page. The double fault occurs because the invalid access result usually generates an interrupt request with invalid data.

All of these errors can be caused by faulty hardware, usually RAM that has failed. Other probable causes include overclocking the processor, faulty hardware devices, or badly written software.

Solution: If you're trying to overclock (manipulate hardware and/or software settings to eke out extra speed) your computer, this error message is telling you that the speed you're attempting isn't viable. Lower your overclock settings or consider returning to the default values for your processor.

Use a diagnostic utility to check for RAM failure. Replace affected RAM modules if indicated.

Remove any unnecessary controller cards, such as sound cards, game controllers, and USB (Universal Serial Bus) or FireWire add-ons and see if the problem recurs. If it
doesn't, add one controller back at a time, reboot, and check again. Continue this process until you find the defective controller card. You can replace the controller card or do without it if you don't need it.

If you've recently installed new software, uninstall it and reboot your computer. If the problem still occurs, contact the software manufacturer for updates.

Modem Errors

Error Message: "Error 692: Hardware failure in port or attached device."

Translation: Windows was unable to access or detect the modem. If it's an external modem, it may be turned off, or the modem cable may be disconnected. For internal and external modems, the modem may not be recognized as compatible with Win2000 or the handshaking option (a method of exchanging information that ensures each side has sent or received valid data) may be set incorrectly.

Solution: If you have an external modem, be sure the power is on and the cable is firmly attached. Reset the modem, if needed.

For internal and external modems, check the Windows Hardware Compatibility List at www.microsoft.com/whdc/hcl/search.mspx. Contact the modem manufacturer for the latest drivers.

Error Message: "Error 633. The modem is already in use or not configured for dialing out."

Translation: Win2000 couldn't open a connection to your modem. This message usually occurs when an external modem is turned off or wasn't connected to your computer when you booted.

The easiest solution is to turn the modem on and/or reconnect it to your computer and then reboot.

If for some reason you can't reboot your computer, but you still need to access the modem, reconnect the modem and make sure it's turned on. Click Start, Settings, and Control Panel. Double-click the System icon. Select the Hardware tab and then click Device Manager. In the list of devices, right-click Modems and select Sca
n For Hardware Changes. A dialog box will open, indicating that the scanning is in progress. When the scan is complete, the dialog box will go away, and the hardware list will be updated with any changes. The modem should now be available for use.

Error Message: "Modem is busy or not responding."

Translation: Windows is unable to connect to the modem because it's already in use by another application. This generally occurs when a background process uses the modem to retrieve information while you are connected to, or trying to connect to, a network using your modem. This error can also occur if you're trying to use two different network services that both require a modem.

Solution: Exit from the application that's currently using the modem and retry the connection with the second application. If the error persists, try resetting the modem (external modem) or rebooting your computer (internal modem).

Printer Errors

Error Message: "Could not connect to the printer: The system cannot find the file specified." or "Servernamesharename is an invalid port name." or "Test Page failed to print. Would you like to view the printer troubleshooter for assistance? The filename, directory name, or volume label syntax is incorrect." or "Test page failed to print. Would you like to view the printer troubleshooter for assistance? Unable to create a job." or "Could not start a print job."

Translation: These erroneous error messages crop up when you try to print to a password-protected Win2000 printer share (a printer configuration that provides printing access to users on a network).

Solution: You can prevent these error messages by doing one or more of the following.

Log on to the PC with an account that has the correct permissions. Remove the password protection from the Windows printer share. Double-click the My Network Places icon on your Desktop and then double-click the computer hosting the shared printer. A window should open, showing shared resources on the selected computer, including the problem printer.

Click Start, Accessories, and Command Prompt. In the Command Prompt window, type net use lptX servernameprintername password, where X is the next available LPT1 (line printer terminal) port for your computer, servername is the name for the computer hosting the printer, printername is the shared printer's name, and password is the password you use to access the shared printer. Press ENTER.

Click Start, Settings, and Printers. Double-click the Add Printer icon. When the Add Printer Wizard launches, click Next. Select Local Printer and click Next. In the list of available ports, select the LPT port you specified in the Net Use command above. Click Next. Follow the Add Printer Wizard's prompts to complete the installation. The next time you print, select the printer you created with the Add Printer Wizard.

Error Message: "There was an error found when printing the document XX to LPT1. Do you want to retry or cancel the job?"

Translation: By itself, this error message (in which XX represents the name of the file you're trying to print) may not indicate a hardware problem. If it occurs frequently, the parallel port your printer connects to may be set to a nonactive state, either by your motherboard's BIOS or by Win2000.

Click Start, Settings, and Control Panel. Double-click the System icon. Select the Hardware tab and then click Device Manager. Expand the Ports (COM & LPT) entry by clicking the plus sign (+). Double-click the LPT port your printer connects to. Click the General tab and check the Device Status area. If the status is "Code 29: Firmware not correctly installed," then the LPT port is disabled.

Solution: Restart your computer and then enter the BIOS setup page (usually by pressing DELETE when your computer starts to boot). There are many different BIOSes, so consult your computer or motherboard manual to find out how to access your particular BIOS. What you need to do is locate the configuration information for the parallel port, which may be under an Advanced, I/O Configuration, or Communication section of the BIOS Setup program. Locate the LPT port and change the setting from Automatic, OS Controlled, or Disabled to Enabled or ECP+EPP (contact your BIOS manufacturer for detailed information about setting the parallel port parameters). The important point is that the port should not be disabled or set to Automatic or OS Controlled.

Error Message: "A port with that name already exists. Choose another port name."

Translation: This message appears when you use the Add Printer Wizard after failing to install a printer, usually because you canceled the installation because of missing information.

When you cancel the Add Printer Wizard, it doesn't perform a cleanup to remove anything it has already configured, so it has probably already assigned a printer to the port you're now trying to use.

Solution: Remove the port the Add Printer Wizard created. Click Start, Settings, and Printers. From the File menu, select Server Properties and then click the Ports tab. Highlight the port you're trying to use, click Delete Port, and click OK.

Drive Errors

Error Message: "Not ready reading drive X."

Translation: There's a problem reading a drive (X above), usually removable media.

Solution: Make sure the drive has media in it. Remove the media, reinsert it, and try accessing the drive again. If the problem recurs, check the media to be sure it isn't damaged, blank, or in the wrong drive, such as an optical drive. If the problem persists, check the media in another computer. If it works, try cleaning the drive with a cleaner designed for that type of drive.

Error Mes
"Serious Disk Error Writing Drive X."

Translation: The X represents a drive that has a serious problem. In many cases, you can recover the drive using Windows' error-checking utility or a third-party hard drive utility. In some cases, you may need to replace the drive.

Solution: Before using a disk utility, try to back up the drive or copy any important files to removable media such as diskettes or CD-Rs. You may not be able to complete the backup or copy all of your files, but it's always worth a shot.

Double-click the My Computer icon on your Desktop. Right-click the drive named in the error message, select Properties, click the Tools tab, and click Check Now. In the Check Disk options dialog box, put a check mark next to Automatically Fix File System Errors and click Start. If the drive you're trying to repair is the boot volume, you'll see the following message: "The disk check could not be performed because exclusive access to the drive could not be obtained. Do you want to schedule this disk check to occur the next time you restart the computer?" Click Yes and restart your computer.

If these steps succeed at repairing the drive, perform a full backup of the drive and plan to replace it soon. In the meantime, back up your files on a regular basis. If you were unable to repair the drive, you will need to replace it.

Error Message: "Non-System disk or disk error. Replace and press any key when ready."

Translation: During the boot process, Windows scans the floppy drive to see if a diskette is present. If there's a diskette in the drive, Windows reads it to determine whether it contains a bootable system. If it does, the boot process continues, using the data on the diskette. If the diskette is blank or doesn't contain a bootable system, you'll see the error message above.

Solution: If you intended to boot from a boot diskette, make sure you chose the correct diskette. Then reinsert it and press any key. If you didn't intend to boot from a diskette, remove it. Then press any key to continue the boot process.

Device Manager Errors

Error Message: "This device is not configured correctly (Code 1). To update the drivers for this device, click Update Driver. If that doesn't work, see your hardware documentation for more information."

Translation: Although this error message is pretty explicit, it's helpful to know what's behind it. Win2000 contains a ConfigFlags (data that reflects a device's current status) value for every device in the Windows Registry. In this case, the device has been enumerated (detected), but the Device Manager wasn't able to find an associated inf file, which is necessary to finish configuring the device. Therefore, the ConfigFlags value for this device was never set. This happens when you install a new piece of hardware but, when prompted for a device driver, fail to install the correct driver.

Solution: Click the Update Driver button. If the Update Driver button isn't on the General tab, click the Driver tab and then click Update Driver. You'll need the driver software to complete the installation. Check with the manufacturer to be sure you have the latest drivers.

Error Message: "The driver for this device might be corrupt, or your system may be running low on memory or other resources. (Code 3)."

Translation: In most cases, this message appears because a damaged device driver is being loaded into the computer's memory. It's unlikely that the cause really is low memory. To check, press CTRL-ALT-DEL and then click Task Manager. Click the Performance tab where you can verify whether your computer is low on available memory.

Solution: Replace the bad driver. Contact the manufacturer and, if a more current driver is available, follow the manufacturer's instructions for installation. If no new driver is available or if the driver didn't come with instructions, click the Update Driver button, which should be just below the error message. If there's no button, select the Driver tab. Then click Update Driver and follow the on-screen instructions.

After you install the new driver, reboot your computer. Check the Device Manager to ensure that the error message is no longer present. Then use the Task Manager to check memory usage. If you're still using a large amount of system memory, consider adding more RAM.

Error Message: "Windows cannot identify all the resources this device uses. (Code 16) To specify additional resources for this device, click the Resources tab and fill in the missing settings. Check your hardware documentation to find out what settings to use."

Translation: This usually indicates a corrupted or incompatible driver or a hardware failure. Windows was unable to retrieve the resource setting information from the hardware device's configuration memory, and the driver didn't provide the necessary information.

Solution: According to the error message, you should manually configure the resource settings, but this usually isn't an acceptable option because it can interfere with other PnP hardware devices. Contact the manufacturer for the latest Win2000-compatible drivers. Use the Update Driver button under the Driver tab to launch the Update Driver Wizard and follow the on-screen instructions.

Restart your computer and then use the Device Manager to check the status of the suspect device. If the problem still exists, contact the manufacturer for any special instructions for uninstalling older drivers or installing new drivers. If there are no special instructions, the hardware device may be damaged and may need to be repaired or replaced.

Miscellaneous Errors

Error Message: "General Protection Fault in module XX."

Translation: General protection faults occur when an application or DLL (dynamic-link library, a small file containing functions that can be used by multiple applications), represented by the XX above, attempts to write or read memory assigned to another application.

This is almost always a software-related problem, usually caused by compatibility issues between two or more app
lications, but it can also be caused by a memory error, either in system RAM or the graphics card's video RAM.

Solution: Use a memory testing utility to verify that RAM isn't the problem. Contact your video card manufacturer for a utility to test the video card. These utilities can usually also test video RAM.

Error Message: "While setting up DVD-video playback, it was found that XX Video cannot be shown on the computer monitor because of one of the following reasons: Low video memory. Please try using lower display resolution and/or colors. The display adapter is incompatible with the DVD decoder. Please try to obtain a display driver update."

Translation: The video card doesn't have enough memory or the DVD playback software isn't compatible with the video card.

Solution: Contact the manufacturer of your DVD decoder software for an update that works with Win2000 and your video card. Follow the manufacturer's instructions to update the software.

If your video card doesn't have enough video RAM or performance, you can alleviate the problem by reducing your display resolution. Right-click your Desktop and select Properties from the pop-up menu. Click the Settings tab. Drag the Screen Area slider to the left to reduce screen resolution. A good starting point is 800 x 600, although you can try various screen sizes. Click OK and try the DVD player again. Repeat until the error message disappears and playback quality is acceptable.

If you plan to watch a lot of DVDs on your computer, consider upgrading your video card for better performance.